Search the Community

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