[CRITICAL BUG] Database Integrity: Duplicate IDs assigned to Scenes AND Devices (Yubii Home Pro)

[Vitruv 0]

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

 

 

 

 

Edited February 12 by Vitruv

[SmartHomeEddy 1,005]

I always thought devices and scenes have their own IDs so can overlap. They don’t share one ID counter. 

[rraptorr 4]

I have scenes with the same IDs as devices in multiple Home Centers (HC3 and HC3L). No problems with this, scene IDs seems unrelated to device IDs and can overlap. No problems with referencing those ID from LUA either.

[m.roszak 763]

3 hours ago, SmartHomeEddy said:

I always thought devices and scenes have their own IDs so can overlap. They don’t share one ID counter. 

Exactly.

 

Issues mentioned here are not related with that.

 

@Vitruv please create a ticket on our support to investigate. Not here, its community forum.

[Vitruv 0]

19 hours ago, m.roszak said:

Exactly.

 

Issues mentioned here are not related with that.

 

@Vitruv please create a ticket on our support to investigate. Not here, its community forum.

Thank you very much - will do!

[Vitruv 0]

23 hours ago, rraptorr said:

I have scenes with the same IDs as devices in multiple Home Centers (HC3 and HC3L). No problems with this, scene IDs seems unrelated to device IDs and can overlap. No problems with referencing those ID from LUA either.

Thank you very much - good to know.

So the problem is another one.

On 2/11/2026 at 6:58 PM, SmartHomeEddy said:

I always thought devices and scenes have their own IDs so can overlap. They don’t share one ID counter. 

Thank you very much - good to know.

So the problem is another one.

[SmartHomeEddy 1,005]

37 minutes ago, Vitruv said:

So the problem is another one.

What was the problem? 

[Vitruv 0]

Yubii continuing to crash. 

 

See my first post 

 

But as you and the others write the problems seem not to be the ID m

 

So the problem must be something else. 

 

And I would like to know what the problem is. 

 

But I have learned that this is the wrong place. 

 

I have written to Fibaro Support. 

 

We will see and I let you know if they could solve the problem above. 

 

Have a good night