Hello!
Like many others’ I’ve fallen in the trap of having entities without a unique_id that I can’t seem to get rid of.
This is a new installation of HA in docker, hence I am running separate containers for HA and MQTT. I’ve just moved away from HassOS as I’ve changed hardware.
During the installation I have tried to connect my Nuki Smart Lock via MQTT so that it published data directly to MQTT, instead of relying on the custom integration. That didn’t really work out the way I was expecting so I switched back to the custom component and removed the MQTT configuration from the Nuki Smart Lock.
Since then I have these entities I can’t seem to get rid of:
I’ve tried to publish an empty topic on MQTT, and have also removed the topic from underneath “homeassistant” and “nuki” via MQTTExplorer, followed by multiple restart. None of these actions seem to have triggered the deletion of the entities.
At which point I have stopped the MQTT container, got rid of the database, and rebuilt the container, so to start with a brand new MQTT instance. I can clearly see in MQTT no references to the Nuki Lock, and I’m sure no data has been persisted as I’ve created a new DB.
This is confirmed by the screenshot below.
Nonetheless, despite multiple HA restarts, the explicit exclusion from recorder (and removal through Purge) of the entities from the database, I can’t seem to get rid of them.
I’ve verified and in the MQTT integration the Nuki Smart Lock no longer appears.
In HA I still get a “lock” entity for this no-longer existing MQTT entity.
And if I try do delete it, I don’t get the option.
I’ve also checked for the known_device file in the config folder, but this is not present.
The only reference I could find were under “deleted_entitites” in the .storage/core.entity_registry" file.
Would anyone be able to suggest me how to get rid of them, please?
It it as easy as deleting the entries from the core.entity_registry file? Is there any other (better) way?
Thanks!