If the integration is reloaded, the log is filled with errors about non-unique id's being generated.
Looking into this step-by-step it seems that somehow entities are not cleaned up and stay lingering around, despite the fact that they do get a request for removal, as I've confirmed by adding some logging to the async_will_remove_from_hass callback.
The old entities are still present in the UI, although they are not responding anymore.
Try to control a light for example will issue a warning in the log: Unable to find referenced entities light.fibaro_dimmer_2_instance_1_level
This needs fixing because it will confuse users.
Usecases:
1) User unloads the integration and adds it back
2) A user enables a disabled entity (core reloads the integration for that)
If the integration is reloaded, the log is filled with errors about non-unique id's being generated. Looking into this step-by-step it seems that somehow entities are not cleaned up and stay lingering around, despite the fact that they do get a request for removal, as I've confirmed by adding some logging to the async_will_remove_from_hass callback.
The old entities are still present in the UI, although they are not responding anymore. Try to control a light for example will issue a warning in the log: Unable to find referenced entities light.fibaro_dimmer_2_instance_1_level
This needs fixing because it will confuse users.
Usecases: 1) User unloads the integration and adds it back 2) A user enables a disabled entity (core reloads the integration for that)