Is there any reason that I wouldn’t want to remove nodes manually within the zwcfg_0x… file? I’ve removed them using the OZCP, but noticed that they still remain in the zwcfg_0x file. It’s recently become an issue with me lately as I’ve had to remove and re-add several z-wave devices and when I go to rename them with the old entity ID it states “save failed: Entity is already registered”.
If I’m unable to delete them from the zwcfg_0x… file it seems that I’d have to go back through and update the entity ID names in all of my other files to track the “new” device.
I’ve noticed even though I remove the device completely that the OZWCP still continues to add the next node to the the next highest available node. For example, if I remove Node 012 when I go to add it back it will assign it Node 027 because that was the next higher available number.
If I were to remove Node 012 from the zwcfg_0x file, would I be able to add it back in place of Node 012 when adding it back to the network–or is that not possible?
I think the problem are the HA entity registry and the device registry. They currently don’t get updated when a Z-Wave device is removed - that is where your naming conflict is coming from - safest is to rename them as ‘removed’ devices and then rename the re-added entities as you wish.
Alternatively you can go and manually edit the device and entity registries - this is NOT recommended.
This is not directed specifically at you so please don’t take offense…
The problem is that with the current (poorly done) implementation of the “entity_registry” concept (which has been evolving for over a year now…) there are times that people are FORCED into manually editing all kinds of files that aren’t recommended to be edited.
the devs have put us in a position in which we are forced to manually edit files then they say they won’t support anyone who has edited those files.
I’m not sure that you need to edit the ozwcgf file but it couldn’t hurt just to make everything consistent.
It’s more likely that it’s the files stored in you /config/.storage/ folder. Try looking in the core.entity_registry or core.device_registry.
The data for the entity_id is in the entity_registry file and for the zwave device it is in the device_registry. always make sure you make a backup of the files before modifying them.
Great, thanks. That seems like it would be a better approach than making extensive manual modifications which could potentially cause additional issues down the road. Of course, each time I go into the file I’d be looking to back it up because you just never know!
I think it’s more my OCD kicking in. Knowing that there are nodes in the registry which should be deleted. I guess it’s good to see that there’s a lot more discussion taking place regarding this issue.
I did see some other discussions taking place in other areas of this forum when I was trying to search for an answer to my question. I guess that it makes me feel a little better knowing that I’m not the only one that’s noticed a disconnect. I appreciate all of the effort that is being placed into developing this software and am excited, and hopeful, that it will only continue to get better as the updates get pushed out.
Admittedly, I’m only a few months into using the software so I have a LOT to learn.
@finity Thanks for giving me some additional direction to look into. I may dabble in the files a bit to see what they look like and if it’s something that I feel comfortable in tackling. Otherwise I’ll know now to rename the old entity name prior to removing them from the network if a repairing is required. The last issue I had which required me to do this was an Aeotec Multisensor 6 which wouldn’t ever connect to more than 1 neighbor which was the hub itself even though it was surrounded by several other powered switches/plugs. Repairing fixed that, but that’s when I started to notice the existing entity issue.