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
Search the Community
Showing results for tags 'ID'.
-
Hi everyone, I am writing this to report a critical bug I recently encountered on my Yubii Home Pro and to warn others who might face similar "ghost" issues. I experienced a massive database integrity failure where the system assigned duplicate IDs to both LUA Scenes and Z-Wave Devices simultaneously. The Setup / Scenario: 1. I had existing LUA Scenes running on IDs 202, 208, 209, and 210. 2. I then included a new Z-Wave device: Remotec ZXT-800 (IR Extender for AC). 3. The Bug: During the inclusion process, the HC/Yubii assigned the Remotec's child devices (Thermostat, Sensors, etc.) the EXACT SAME IDs (202, 208, 209, 210) that were already occupied by my Scenes. The Result: • Total conflict. • The system had a Scene ID 202 and a Device ID 202 at the same time (see attached screenshots). • LUA scripts referencing ID 202 were conflicting with the hardware device, causing crashes and unpredictable behavior. The Workaround: I had to manually delete all affected scenes to "free up" the IDs for the hardware (since hardware seems to take precedence but doesn't check for occupied Scene IDs). I then recreated the scenes, which were assigned new, higher IDs. The system is clean now, but this required significant manual effort. To @Fibaro Support: This seems to be a serious firmware bug regarding ID allocation, specifically when including multi-channel devices (like the Remotec) that spawn multiple child IDs. The system fails to check if an ID is already taken by a Scene before assigning it to a new Device. Has anyone else experienced this? This creates a massive reliability risk if we have to cross-check IDs manually after every inclusion. System: Yubii Home Pro Firmware: 5.200.13 (I did NOT do the Beta Update to 5.201.18) Device causing conflict: Remotec ZXT-800 Best regards
- 7 replies
-
- critical bug
- double id
-
(and 4 more)
Tagged with:
-
maybe a simple question, but is there a way to extract a list of all devices (inluding actors, reactors, users) and its corresponding ID ?
-
Hi guys, I have the following issue when I try to obtain Fibaro ID: 1. After registering for Fibaro ID, I don't see my HCL in the list. When I try to register my HCL, the system says it has been already registered; 2. Maybe some time ago I had registered my HCL, but I neither find the e-mail and the password or delete my previous HCL registration. The system offers to use my old pass, but it is a stupid loop!!!!!!! 3. I sent an e-mail to the Fibaro support but have no reply. Please advice how to proceed? Best regards Nick
-
W jaki sposób mogę znaleźć ID telefonu, tabletu etc. na które są wysyłane wiadomości PUSH, tak aby w Virtual ustawić powiadomienie wysyłane na telefon : -- ustaw poziom informowania o stanie baterii battery_level_notify = 10; -- pobierz tel, który należy poinformować notify_phone = fibaro:getGlobalValue("Phone_M_ID"); - tutaj mam jako zmienną i w niej chciałbym wpisać ID -- pobierz dane o urzadzeniach z HC2 HC2 = Net.FHttp("127.0.0.1", 11111); response ,status, errorCode = HC2:GET("/api/devices/") if (tonumber(status) == 200) then jsonTable = json.decode(response); for key,value in pairs(jsonTable) do -- wybierz urzadzenia nadrzedne i takie ktore moga posiadac atrybut battery if jsonTable[key].interfaces ~= nil and tonumber(jsonTable[key].parentId) == 1 then interfaceTable = jsonTable[key].interfaces; for ikey, ivalue in pairs(interfaceTable) do propertiesTable = jsonTable[key].properties; -- weryfikacja czy urządzenie jest bateryjne if interfaceTable[ikey] == "battery" then notifier = jsonTable[key].name .. " - battery level: " .. jsonTable[key].properties.batteryLevel; fibaro:debug(notifier); if tonumber(jsonTable[key].properties.batteryLevel) < battery_level_notify then notifier = "Warning - " .. notifier; fibaro:log(notifier); fibaro:call(tonumber(notify_phone), "sendPush", notifier); end; end; end; end; end; end; Chyba że jakoś inaczej można wysłać push o stanie baterii???
-
Is it possible to check if the virtual device button was pressed in lua? Is there any function for that in lua? I want to code something like this: (If Button "3" of virtual device with an ID of 674 was pressed than a=a+1) for example
-
Mayby a stupid question but I cannot find the ID of notifications. I want to send via LUA. I managed to find out de DeviceID via HC2 Toolkit but cannot find the number of notification. syntax of used call: fibaro:call(<ID>, "sendDefinedPushNotification", "<NotificationID>") Many thanks in advance
- 2 replies
-
- sendDefinedPushNotification
- LUA
-
(and 1 more)
Tagged with:
-
Every devices added to HC2 gets its personal ID, but there's a lot of gaps in ID number. HC2 says I have 32 devices, the last one added got ID #180.. Will this be a problem in the long run..?
