Hi all.
I’ve been going round my house today including nodes onto my new setup (moved from Domoticz) and a new aeotec stick.
At some point, I restarted home assistant and a few of my nodes have now had their node numbers taken away and now state ( undefined:undefined).
These were included, attached entities are still in HA but are showing an error.
Is there some way to gain their node numbers again?
I’ve tried a HA restart, that didn’t work.
Thanks all.
Hi,
Do you have a sollution? I have the same problem 
.
Gr. Tinus
Ok, I’ve had a go today at resolving it and I’ve manage to get one node working again.
Firstly, the node I had troubles with was a fibaro dimmer 2, which I have many of.
I went into the config files and found my openzwave .XML file.
Once there, I found the relevant node, which I know was node 94.
From there I copied all the information from another working dimmer 2, then pasted over node 94.
Remember to edit to node number to node 94 once copied.
That got the node working for me.
Make sure there are no errors (so backup your .XML file beforehand) as any errors will mess up your z-wave and may need to be rebuilt on next startup.
I learnt all this from working with domoticz/openzwave.
@stuiow By any chance would you have the .xml data that I could past over my node for the Fibaro Dimmer 2? I added to my Z-wave network last week but has not worked as it remains undefined. Have been searching since on how to sort it.
After trying to include 2 Fibaro buttons with great difficulty, i have now obtained some undefined:undefined nodes again.
It appears the editing of the zwcf*********.xml file isn’t a 100% way of fixing it.
I have just this moment discovered another way.
Triple clicking of the nodes, waiting a few minutes to ensure a success communication, then a reboot of the home assistant instance.
@stuiow When you say “Tripple Clicking the nodes” can you explain further? Do you recomend this method in conjunction with modifiying the .xml or on its own?
Triple clicking the z-wave button on the node to wake it up and send info frame to the controller.
What i have also found recently is some node that are noted in HA as undefined:undefined are dropping off the controller completely.
(i use a Aeotec z-wave Stick Gen5).
I plugged it into my PC and noted on the node list that some of the unfined nodes were not on there at all. (they had dropped off for some reason.
What i did here was selected add node in the HA z-wave screen, then went to the node to triple click it to re-include it.
It might not look like anything has changed, but when you next reboot HA, hopefully, the undefined node will come back.
I’m learning all this as i go - a similar thing used to happen when i was running Domoticz (nodes dropping off the controller list for no reason) - a nasty OZW trait it seems.
I have deleted 11 nodes with undefined:undefined. First delete zwave integration, restart ha and add zwave integration. Sometimes this help. If not delete the dead entities in zwave integration under integrations.
Although it is an old topic, maybe someone will face similar issue and seems I have a fix 
In my case behaviour was very similar to above, some of my nodes were becoming “unavailable: unavailable” after HA restart. The fix was to change access rights to 666 and owner to the home assistant user (8123 in my case) for zwcf*********.xml file. And bingo, all works ok now!
Hello all,
I am having the same issue. I have nodes that are mysteriously going missing and it’s like the node was never there. It is not getting reported as dead, it’s just not there.
I am using Leviton Switches and some dimmers with a total of 34 nodes.
Any help would be very much appreciated.
Thank you
I had one disappear off again the other day.
I have a Aeonlabs Gen5 z-wave stick.
All i did was shut down home assistant, took the stick down to the node that had fallen away, re-included it with the stick.
I then popped the stick back into my HA pi, started HA again and the node was back, some node number.