Jump to content

Welcome to Smart Home Forum by FIBARO

Dear Guest,

 

as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.

 

As a member you can:

  •     Start new topics and reply to others
  •     Follow topics and users to get email updates
  •     Get your own profile page and make new friends
  •     Send personal messages
  •     ... and learn a lot about our system!

 

Regards,

Smart Home Forum by FIBARO Team


Zembaty

Member
  • Posts

    12
  • Joined

  • Last visited

About Zembaty

Profile information

  • Country
    Poland
  • Gateway/s
    Home Center 3
    Home Center 3 Lite
    Home Center 2

Recent Profile Visitors

153 profile views

Zembaty's Achievements

Newbie

Newbie (1/8)

1

Reputation

  1. Aeotec Range Extender Zi: https://www.zigbee2mqtt.io/devices/WG001.html Recognized as parent only - unconfigured: ... but looks like it works. I have connected one Xiaomi LYWSD03MMC (https://www.zigbee2mqtt.io/devices/LYWSD03MMC.html) device flashed custom firmware changing blutooth to zigbee (https://smarthomescene.com/guides/convert-xiaomi-lywsd03mmc-from-bluetooth-to-zigbee/#convert-lywsd03mmc-to-zigbee-ota-pvvx). Without Extender I can't connect it to HC3 - too far. With added Aeotec Extender in the same room - Xiaomi termometer has been recognized by HC3 and works fine.
  2. Hallo All, Let me connect to this topic. I just replaced my old HC2 to HC3 by removing all devices from HC2 and factory reset and add them all to HC3 with Z-WAVE 3.0. I have a problem with garage gate sensor Vision zg8101. HC3 recoginze it but doesn't report any changes of the sensor. I have anotother HC3L with Z-WAVE 2.0 and added here, works perfeclty fine. So looks like Z-WAVE 3.0 doesn't support Vision zg8101... Any plans to add support to this device in Z-WAVE 3.0? I have exactly the same problem with Fakro AMZ Solar roller shutter. Works fine on HC3L with Z-WAVE 2.0. Doesn't work on HC3 with Z-WAVE 3.0. Both controllers (HC3 and HC3L) on the newest firmware = 5.120.10.
  3. Hi All, Please check how did you add your Heat Controller? As secure or not. I had the same problem when I added it as secure. I found solution on Polish forum. You have to remove Heat Controller and add it back as non-secure. Finally I did successful upgrade - after 8-10 tries... and other errors... but possibly distance from HC2 is a key. HC2 i 2 levels higher... but it works... you have to be patient and use non-secure Z-WAVE connection. I hope it will help.
  4. Szybko poszło! Dzięki! Pobawię się tym w tym tygodniu.
  5. Dzięki! ID interesującej nas stacji szukamy na mapie: https://map.airly.eu/ Klikając w interesującą Cię stację adres zmienia się jak niżej, np: https://map.airly.eu/pl/#latitude=49.98194&longitude=20.07015&id=519 Dobre jest również zapytanie oparte o koordynaty GPS, np: https://airapi.airly.eu/v1/nearestSensor/measurements?latitude=49.98194&longitude=20.07015&maxDistance=5000&apikey=XXXX Powyższe zwraca informacje z najbliższego czujnika w promieniu 5km. Przydatne w sytuacji gdy najbliższy nas czujnik z jakiegoś powodu nie działa.
  6. Dzięki! Scenami w LUA jeszcze się nie bawiłem. Dopiero zaczynam. Rozumiem, że że dla VD się nie da? To gotowe rozwiąznie nic mi nie daje. Czujniki są za daleko. Najbliższy ponad 10 km... to po co mi taki? Czujnik Airly mam 1km od miejsca zamieszkania, kolejne 8 w promieniu 5km i ich baza cały czas rośnie.
  7. Witam, Nadchodzi okres grzewczy a tym samym spadnie nam niestety jakość powietrza. Chciałbym mieć możliwość wyświetania danych z najbliższego czujnika Airly: https://map.airly.eu/pl/#latitude=49.95096&longitude=20.03479&id=473 API jest fajnie rozpisane: https://airly.eu/en/api/ Ale Airly używa HTTPS i nie bardzo wiem czy i jak można ściągać dane z API do Urządzenia Virtualnego. Wymyśliłem sobie to tak: local apihost = "airapi.airly.eu" local port = 443 local deviceID = "473" local token = "XXXX" diag = Net.FHttp(apihost, port); response = diag:GET("/v1/sensors/" ..deviceID.. "?apikey=" ..token) result = json.decode(response); fibaro:debug("name: "..result.name) ale nie działa... Jakaś podpowiedź? Jak wyciągnąć takie dane z API po HTTPS? Dzięki z góry za wszelkie podpowiedzi.
×
×
  • Create New...