Thanks, that sounds very interesting. Will try and report. 
You have to wait for it to be marked as failed.
Note that zwcfg_*.xml is a cache - if the controller still thinks the devices are included, it’ll re-populate the cache because as far as far as it knows they should be there.
I can confirm that deleting those nodes from the .xml does not help. It gets repopulated after the next reboot.
The nodes have been in the same state for several weeks now. I do not have the hope they will ever get marked as dead.
at this point you might have to resort to factory resetting your z stick in order fr them to go away.
If you do that remember to un-pair your existing devices before you do or you will have to factory reset those as well before you can re-include them again.
1 Like
Yipp. Thanks everyone. When I have a free weekend.
I had a “bad node” that didn’t exist, but wasn’t marked as dead either, that I couldn’t get rid of. I believe it was stuck at the Probe state. Some searching on google led to this:
https://www.domoticz.com/forum/viewtopic.php?t=17497#p134637
I applied the procedure to Home Assistant (HassIO for me) and voila, the node was gone!
For me, it went like this, your mileage may vary:
-
Go to Z-Wave Network Management
-
Click STOP NETWORK (first time I have ever done that…)
-
Open zwcfg_xxxx.xml (done that lots of times to rename nodes)
-
Find the “bad node” (search for --> Node id=“XX” <-- where XX is node number of the “bad node”)
-
Delete the following from the zwcfg_xxxx.xml file (this part was a bit scary)
Find where it says “COMMAND_CLASS_WAKE_UP” that is the section of code that needs to be deleted. Delete this section starting with “<CommandClass” all the way up to, and including, “”. You will also see and in this section. 4 lines of code are deleted. -
Save the zwcfg_xxxx.xml file
-
Go back to Home Assistant and click START NETWORK under Z-Wave Network Management. At this point I had 2 of everything listed in the Nodes section of Z-Wave NODE Management. I was pretty sure this was going to go badly, but it ended up working.
-
Under Z-Wave Node Management, find the “bad node” in the drop down box, click it, then click REMOVE FAILED NODE. Since all nodes were duplicated, I did this twice.
-
Restart Home Assistant
-
Go back to Z-Wave Node Management, each node is only listed once now (phew!) and the “bad node” is now in the Unknown State instead of the Probe state it was in before. I clicked the “bad node” and once again clicked REMOVE FAILED NODE.
-
Restart Home Assistant again
-
“Bad Node” is gone! Yay.
I didn’t come up with this. It was taken from the link above. Just figured others may benefit from it.
9 Likes
@RonJ103 - I know this is an old thread but thank you so much! I’ve been banging my head against the wall trying to get rid of 3 “phantom” nodes that were failure to add correctly. Even with the battery power device powered-down (smoke detector) I waited weeks and it would never show as failed. This worked on the first shot! I really, REALLY appreciate it!
1 Like
Ron,
many thanks indeed! for this walk-through. As reported above I had a few bad nodes. Now I don’t. Great stuff!
I had to make a few slight alterations or rather additions to your method though using the original source and try-and-error. My first try ended in me re-including and/or refreshing a few of my nodes as I believe I went through the process to quckly)
I therefore post your amended walk through for future reference:
Go to Z-Wave Network Management
Click STOP NETWORK (first time I have ever done that…)
Open zwcfg_xxxx.xml (done that lots of times to rename nodes)
Find the “bad node” (search for --> Node id=“XX” <-- where XX is node number of the “bad node”)
Delete the following from the zwcfg_xxxx.xml file (this part was a bit scary)
Find where it says “COMMAND_CLASS_WAKE_UP” that is the section of code that needs to be deleted. Delete this section starting with “<CommandClass” all the way up to, and including, “”. You will also see and in this section. 4 lines of code are deleted.
Save the zwcfg_xxxx.xml file
Go back to Home Assistant and click START NETWORK under Z-Wave Network Management. At this point I had 2 of everything listed in the Nodes section of Z-Wave NODE Management. I was pretty sure this was going to go badly, but it ended up working. :grinning:
Under Z-Wave Node Management, find the “bad node” in the drop down box, click it, then click REMOVE FAILED NODE. Since all nodes were duplicated, I did this twice.
–> WAIT a few minutes! (I used around 10 mins)
Restart Home Assistant / I had to use REBOOT!
(I) Go back to Z-Wave Node Management, each node is only listed once now (phew!) and the “bad node” is now in the Unknown State instead of the Probe state it was in before. I clicked the “bad node” and once again clicked REMOVE FAILED NODE.
–> WAIT a few minutes! (I used around 10 mins)
Restart Home Assistant again / I had to use REBOOT!
“Bad Node” is gone! Yay.
–> If there are any bad nodes left, repeat from (I) - I had to do it three times to get rid of ALL of my bad nodes
Yay!!!
Hope this helps anyone cleaning up their ZWave network!
3 Likes
[quote] Delete the following from the zwcfg_xxxx.xml file (this part was a bit scary)
Find where it says “COMMAND_CLASS_WAKE_UP” that is the section of code that needs to be deleted.[/quote]
I was just trying to delete a dead zwave device but that command class does not show up for the affected device. So any more ideas on how to delete a failed device?
Thanks
You might try removing/refreshing and healing the node through the ZWave configuration in Home Assistant.
Been there, done that. No success.
I’m using Home Assistant 82.1 and this is how I have successfully removed a dead node using the GUI
Restart Home Assistant and verify the Dead Node has been successfully removed
1 Like
Solved it!
Neither restarting HA nor rebooting the server helped. I had to power down the box and unplug the USB zwave stick (it was still flashing when the server was shut down!). The dead zwave device was gone after HA was up and running again.
1 Like
Hello,
I have tried most of the solutions, put the node to dead and failed state but all solutions ends with “remove dead node” button. Every time I press it the log reads:
2019-01-13 11:38:32.299 Warning, contrlr, WARNING: Received reply to FUNC_ID_ZW_REMOVE_FAILED_NODE_ID - Remove process busy
2019-01-13 11:38:32.299 Detail, Node139, Expected callbackId was received
2019-01-13 11:38:32.299 Detail, Node139, Message transaction complete
2019-01-13 11:38:32.299 Detail,
2019-01-13 11:38:32.299 Detail, contrlr, Removing current message
2019-01-13 11:38:32.300 Detail, Notification: ControllerCommand - Failed
Any ideas? I have tried restart, reboot etc.
Update: the device re-appeared in Home Assistant even it was not online at all (it was unplugged).
I then used ozwcp (open zwave control panel) to remove it from the zwave controller (even not supported though) and it did not re-appear so far.
Different but related question. I’m just getting started. I successfully added my first node. I also tested that I could remove a node via the config GUI.
It all seemed to work fine as far as Home Assistant is concerned. However, when I added the node back again, it was assigned Node ID 3 in the network. It was originally Node ID 2.
Is node id 2 now dead in the controller?
I’m using Aeotec Zstick Gen 5 running HA 0.100.2 on Hassbian.
Yes, but no.
The controller assigns node id’s in sequential order without re-using any that have already been used. So what you are seeing is normal.
But after you get to 255 nodes (I think that’s the limit) it will start over again using nodes it had skipped previously. At least that’s my understanding since I haven’t gotten to the limit yet.
But I have seen the node skipping behavior and I know that part is correct. 
1 Like
Not dead, but still listed in your zwcfg_.xml file.
To get rid of it so the number doesn’t increase, you would need to find the node in the zwcfg file and delete it, pretty much everything from <Node id=“#” to “Node” just before the next <Node id=“#”, or reboot HA after removing the node before re-adding it, hope this make sense.
Thanks @finity and @Coolie1101 for the replies.
There is no Node id="2" in my zwcfg_*.xml. There are only <node id="n"> tags for the devices HASS shows as active in the GUI and various drop downs. So all looks ok there.
Doing a little more digging, in OZW_Log.txt, a mention of Node002 shows up during a Heal. I don’t really understand what I’m looking at there. It appears that it never sends anything to Node 2, but it prints these lines, which I interpret as having receiving some sort of response that looks like it comes from Node 2? (There are no other references in the log to Node002 or [nN]ode 2.)
2019-10-27 16:38:40.119 Detail, Node002, Expected reply was received
2019-10-27 16:38:40.120 Detail, Node002, Message transaction complete
Also when adding more switches, the inclusion for one of them seemed to fail. Worked on the second try, but skipped Node 8, so the new device should up as Node 9.
I also see similar lines for Node033 which I don’t have as far as I know. (My max node number is currently 10 – I have no idea where Node033 came from – anyone have any clues?)
2019-10-27 16:38:40.192 Detail, Node033, Expected callbackId was received
2019-10-27 16:38:40.192 Detail, Node033, Expected reply was received
2019-10-27 16:38:40.192 Detail, Node033, Message transaction complete
So I’m hoping it is as @finity mentioned – if/when it comes to it, and node numbers wrap around 2, 8, etc. will be available for assignment.