However, I just recongized, that my Fibaro Smart Implant does not show the two output switches.
In the integration these are deactivated and I cannot activate them from the integration (it says: "Condition cannot be changed. Deactivated by config entry).
Interestingly there is a similar post on the forum about swapping Zigbee integrations and a device had the same error message because it was associated with the previous Zigbee integration. It may be possible that the entries are somehow still tied to your previous Zwave JS add-on configuration. You’d have to investigate in the .storage folder to be sure, and I’m not sure how comfortable you are with that.
That would make sense IMHO.
Shouldn’t this be deleted if I delete the original ZWAVE JS add-on?
In the past I took a look in the .storage folder, but wouldn’t like to change something. I would most likely make it worse.
Any specific file I could take a peek at?
If I remove the node and re-include it, this should also fix the issue, wouldn’t it?
I rocognized on another device, that it helps to exlude this as failed and re-include this then. This will lead to a new Node ID and will be “cleaner” I guess.
EDIT:
I found the Implant in several files and will check these out. core.entity_registry, core.restore_state, homeassistant.exposed_entities, and various xxx.tmp files.
Is it safe to delete the xxx.tmp files? I have tons of them.
I also find this for some old stuff (previous car) I removed from my config.
Why are these zombies still there even if I uninstalled the integrations?
Is there a way to clean this up?
By the way: Out of a sudden the Smart Implant showed some new entities and one of them is the button to trigger the Garage door