Well, that didn’t go to plan.
I just tried to add battery level monitoring to my zwave network.
I tried with a single device first up, borrowing technique from here:
I have a hass.io on Ubuntu system.
I restarted home assistant to bring in the new sensor (and automation).
And… lost all my zwave devices. Gone. “Error: Entity Not Found” badges everywhere.
At first I thought it was a USB device issue… ACM0 vs ACM1 or something… but no… putty’d in and all looks right and hardware under hass.io, system tab looks ok.
(I have 40 odd zwave devices and my system is usually pretty stable… USB device name issues are my most common problem and that is not common)
After poking around, zwave integration menu was present but showing no nodes… I thought a restart of hass.io might get me going (don’t judge, we all do it)…
And after that the controller (Aeotec zstick) came up but nothing else.
Looking at the OZW log and there is communication happening… to many nodes, but still they all show Not Found.
I commented out the new battery level sensor and gave it another restart.
This time, after a little while all powered nodes came back… and only one battery powered node… a Dome Siren… but it’s entity ID (name remained unchanged) and all it’s child entity ids and names reverted to default.
None of the other zwave device entities for battery powered devices are found.
6 x Aeotec MS6, 1 x Vision Door Sesnor, 2 x Fibaro Motion.
The OZW Log is showing communication with these nodes if I activate them.
Very odd.
If someone has a suggestion regarding possible cause/fix, I’d appreciate it.