Hi2UAll!
When updated to 2025.5.x the Fibaro Hub Integration all devices moved its entities as a separate entity!
Seems like the Fibaro Hub Integration Master devices are discoupled the slave entities some how. It was working before updating to 2025.5.
This has, for me using a HC2 (old) Fibaro Hub, a big impact on the Energy visualisation and entity location (room) assignment.
Please help!
Hello Domoticon ,
If you believe you have found a bug, check here and add if it is new or thumbs up if you also are seeing it…
FYI, an issue is reported:
opened 08:47AM - 18 May 25 UTC
integration: fibaro
### The problem
FYI, as reported as in [Home Assistant Forum](https://community… .home-assistant.io/t/2025-5-x-bug-fibaro-hub-integration-all-devices-moved-its-entities-as-separate/891602).
Looks like _Fibaro Hub Integration_ entities (slave, child) are discoupled from its device (master, parent) reporting empty _Devices_ and all entities are reported as single _entities,_ which has impact to Energy visualisation and location (floor, room) assignment.
### What version of Home Assistant Core has the issue?
2025.5
### What was the last working version of Home Assistant Core?
2025.4.4
### What type of installation are you running?
Home Assistant OS
### Integration causing the issue
Fibaro Hub
### Link to integration documentation on our website
https://www.home-assistant.io/integrations/fibaro
### Diagnostics information
_No response_
### Example YAML snippet
```yaml
```
### Anything in the logs that might be useful for us?
```txt
```
### Additional information
Using a (old) Fibaro HC2 hub with firmware version: 4.630 (latest, EOL).
Checked logs while debug-logging was enabled: no errors reported as far I can see. I do not want to share logs because of privacy/security risks.
Just want to share the progress of this issue. I got in contact of the very helpful code owner and it seems to be a dedicated HC2 user account does not have enough rights to get the id 1 (com.fibaro.zwavePrimaryController).
Only the superuser has those rights. Maybe it can be fixed but at this moment I’ll wait and see. If there is any progress I will report it.
Bug is fixed, when updating to 2025.5.3!
A big, big, big thumbs up to the code owner for being so helpful, his commitment, time spend, and speed (within a week!) solving this issue!!!
Impressive and higly appreciated, thank you so much!
