Cannot Remove Failed Z-Wave Node

Configuration Z-Wave
1

Hello all,

I recently bought some GoControl door sensors and I’ve been having trouble getting one paired with HomeAssistant and my Aoetec Z-Stick. The pairing process works great, but then when I put the cover back on the sensor, it just goes to sleep forever on the network and the device led just blinks (like it went back into pairing mode). Due to this problem, I’ve tried to remove and add the device multiple times, so now I have about 5 unwanted nodes showing up in my zwave list, all referencing the same device.

I’ve gone through the steps to forcefully remove them from the network, (setting is_failed=true and using “remove failed node”), but the removal always fails. I’ve tried restarting the zwave network, healing the network, restarting the host system, all to no avail. Any help would be greatly appreciated. Here is the relevant log entries I get when trying to remove the node.

2018-11-20 06:25:51.661 Detail, Node032, Queuing (Controller) Remove Failed Node
2018-11-20 06:25:51.661 Info, ControllerCommand_RemoveFailedNode
2018-11-20 06:25:51.661 Detail, contrlr, Queuing (Command) ControllerCommand_RemoveFailedNode: 
0x01, 0x05, 0x00, 0x61, 0x20, 0x8d, 0x36
2018-11-20 06:25:51.661 Detail, Notification: ControllerCommand - Starting
2018-11-20 06:25:51.662 Detail, 
2018-11-20 06:25:51.662 Info, contrlr, Sending (Command) message (Callback ID=0x8d, Expected 
Reply=0x61) - ControllerCommand_RemoveFailedNode: 0x01, 0x05, 0x00, 0x61, 0x20, 0x8d, 0x36
2018-11-20 06:25:51.663 Detail, contrlr,   Received: 0x01, 0x04, 0x01, 0x61, 0x08, 0x93
2018-11-20 06:25:51.663 Detail, 
2018-11-20 06:25:51.663 Warning, contrlr, WARNING: Received reply to 
FUNC_ID_ZW_REMOVE_FAILED_NODE_ID - Node not found
2018-11-20 06:25:51.663 Detail, Node147,   Expected callbackId was received
2018-11-20 06:25:51.663 Detail, Node147,   Message transaction complete
2018-11-20 06:25:51.663 Detail, 
2018-11-20 06:25:51.663 Detail, contrlr, Removing current message
2018-11-20 06:25:51.663 Detail, Notification: ControllerCommand - Failed
2

Same here … I tried to remove a dead zwave node but was running into the same issues as described above (0.82.1).

3

See this post:

4

That does not work … BUT I 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
5

I haven’t got this option in my menu?

My system added the same probe three times. Now I’m unable to remove them.

I tried to set the state according to this description:

But it doesn’t work.

6

Have you restarted Home Assistant?

7

I used the services to remove the devcies. Restarted HA and the devices were removed.

Again, I have the problem that the Fibaro Motion Sensor is only so long active as long as HA isn’t restarted. After a restart the sensor seems inactive and doesn’t send updates (like temperature)

8

Just ran into this problem with a Zooz ZEN22 device and HUSBZB-1 stick. I ran a firmware update which apparently nuked the inclusion information. OK no problem, just do a ZWave replace as I’ve had to do on a handful of other Zooz devices after updating firmware. Attempting to run that process returns:

INFO ZWAVE: The node replace process could not be started due to the following reasons:

· The node replace process is currently busy (ZW0362) replaceFailedNode undefined

I’m using zwavejs2mqtt in docker on an rpi. Restarting the container and restarting Home Assistant did not resolve the issue. I stopped the container, physically removed the ZWave stick, plugged it back in, then started the container. After letting everything spin back up I was able to successfully run the replace process.

9

Hi,

i’m getting the error ZW0360 and can’t remove the failed node (that’s fun because this node haven’t been integrated, ad it’s a new node on the ZWave network).

I tried your workaround, stopping and deleting ZJS MQTT container, unpluged the USB key, plugged the key again, restarted the container, but it’s not working :frowning:

Anyone have an idea ?

1 Like
10

have the same issue with yale keyless connected lock and a 4 button nodon rubber switch

The device could not be removed from your Z-Wave network.

Z-Wave error 360: The node removal process could not be started due to the following reasons: · The node removal process is currently busy (ZW0360)

11

Restart HASS/zwavejs.

12

I have the same problem. How can i force remove a node. Where i can set the node zo a failured node?