Same problem for me, I got 7 devices and all are now undefined. 
I got the same issue, maybe it has to do something with the new version of Hassio. I upgraded it to 0.107.X this week.
Mine was specifically caused by ubuntu upgrade but yes it look like 107 also have some issue
Just chiming in that restoring old zwcfg_*.xml from a snapshot fixed the Node: undefined undefined problem for me as well.
Unsure why it ensued in the first place. Had done some minor changes in automations and restarted to reload config. A routine-restart. Once it had started, I experienced the same problems others have reported. Tried some restarts; some z-wave restarts; some heal network. Nothing worked — except replacing with a old zwcfg_*.xml. (Sooo relieved that did work! Would’ve been quite a chore to re-add all the nodes, all the customized names, and all the… rest.)
1 Like
Also having this problem on my system, many non-function undefined zwave devices after a restart. I submitted bug report here: https://github.com/home-assistant/core/issues/33486
The issue is re-occurring for me. Happens at some, but not all, restarts of HA.
It’s easily resolvable, as I now have a working zcfg -file stored, and can fix it by replacing faulty zcfg with the working backup. But obviously not a desirable situation, where there repeatedly is a need to do so. Great that you filed a bug report, @MattMattMattMatt! I’ll see if I can contribute to the discussion / troubleshooting over there.
I also suddenly had all my nodes at node:undefined. In my case it could revive it by restarting my virtual machine on which I have a docker HASS…pffff
I replaced zwcfg_*.xml from a backup of 0.107.6 and restarted and all zwave entities/devices came back. Thanks!
I had the same issue myself today. Unfortunately, I added the device late last night and hadn’t backed up yet.
I was lucky, I had another device of the exact same type (Both Aeotec Recessed door sensors). I copied the section <Manufacturer …> to from the working sensor to the undefined sensor. The undefined sensor started working again. At least well enough for me to do a ‘heal node’ / ‘refresh node’
So in my case:
<Manufacturer id="86" name="AEON Labs">
<Product type="102" id="59" name="ZW089 Recessed Door Sensor Gen5" />
</Manufacturer>
Update: To get the entities back afterwards, I had to copy the entire Command Classes section as well.
<CommandClasses>
...
</CommandClasses>
1 Like
Running 0.107.5 and had the same issue.
Solved it by selecting that node, tapping the Node info-button and there I found an option to remove that node.
Now it’s gone from my system.
hassio on Ubuntu 18.O4, had 30% of my nodes dissapear after upgrading to 0.107.5 , shutting down, replacing zwc_*.xml with one out of a snapshot (extract the previous snapshot /usr/share/hassio/backup/xxxxxxx.tar and cherrypick zwx_*xml out of homeassistant.tar.gz) fixed it. Thanks guys!
EDIT:Did something change in the zwave stack. I have no numbers, but loading network seems waaaaay slower.
I also am having this issue, just updated to Core 110.6 and supervisor 227. Zwave has been extremely painful for the last few versions since last week. Of course I dont have a backup of the file I need.
I am seeing this:
Aeotec Limited ZWA005 TriSensor (Node:undefined undefined)
Unknown Node 2 (Node:2 Complete)
Unknown Node 5 (Node:5 Probe)
chiming in with an unhappy “me too” welp.
in my case its coincided with a network upgrade and a move to a different host. my HA is a vanilla docker setup. about 30-40% of nodes are “undefined” and grayed out. no node info available:
alas i do not have a recent enough backup of zwcfg… i have 40+ devices, hundreds of customized entities… this isnt going to be fun unless there’s a solution.
a side question, i’m on aeotec gen5 z-stick now. anyone knows of an alternative with linux-friendly tooling for backup/restore? thanks.
While browsing around i’ve come across this post:
Which looks a lot like what happened in my case. It might be a clue as to what is happening here.
Like i mentioned, in my case the troubles coincided with a network upgrade which entailed quite a few incidents of intermittent network unavailability. Perhaps unluckily timed network outs/lags cause OZW to corrupt zwave network’s internal configuration/state somehow and ultimately dump it into zwcfg_ file. I wish i knew more about inner workings of OZW to be more specific.
Oh and i ended up finding a slightly stale backup for my zwcfg, not perfect but way better than re-including 30 devices (whew!).
same issue here
I have the issue here also. Only 2 devices… a sensor & a lock. Yesterday I tried excluding then including one of them which fixed the problem temporarily, but now it shows undefined again.
Hi all,
At least I’m not alone… I have been running homeassistant perfectly configured and some days ago when I tried to add some new devices it started the nightmare. The thing is that I succesfully recovered some nodes but when I recover some of them I lose other ones, I try to add again and I lose some already recovered and sometimes I cant recover anything…
It’s very frustrating because you don’t know how much you use some automations until you lose them…
I hope we find a solution soon because I have been dealing with this issue this last three weeks.
This happened to me today. I’m not ready to switch to the OZW add-on and was worried that I’d have to jump into it. I tried many things like restarting the zwave network, restarting hassio. In the end, it took a few restarts of the hassio OS itself before all nodes finally started registering correctly.
Hi All,
I’ve read many articles but none is actually providing a solution.
I have one device that wasn’t added well and now it shows like
Unknown Node 22 (Node:undefined undefined)
Just had the same, after a power cut and UPS depleted, was running 2021.5.1. fix for me:
- On the CLI stop ha core, this is important before replacing the file
ha core stop
-
Replace zwcfg*.xml with on from a snapback (Download snapshot, extract, extact homeassistant.tar.gz. I replaced with a version from 2021.4.6
-
Start ha core again
ha core start
I believe if you replace zwcfg*.xml with HA running, it replaces/save on restart.