Z-Wave Node Shows Ready But Does Not Exist and Cannot Remove It

alteredstate · May 14, 2020, 12:56pm

Hello everyone!

Currently on:

~ $ ha info
arch: aarch64
channel: stable
hassos: "3.13"
homeassistant: 0.109.6
hostname: hassio
logging: info
machine: raspberrypi3-64
supervisor: "222"
supported_arch:
- aarch64
- armv7
- armhf

and I have a Z-Wave node that stopped working so I removed the physical node but it still shows up as Ready:

Just to show that the node is indeed gone I went to Z-Wave Node Management, selected the node and clicked: Test Node. The log shows this operation timed out (because the node does not exist anymore):

2020-05-14 08:34:47.871 Info, Node020, NoOperation::Set - Routing=true
2020-05-14 08:34:47.872 Detail, Node020, Queuing (NoOp) NoOperation_Set (Node=20): 0x01, 0x09, 0x00, 0x13, 0x14, 0x02, 0x00, 0x00, 0x25, 0xe2, 0x34
2020-05-14 08:34:47.872 Detail,
2020-05-14 08:34:47.872 Info, Node020, Sending (NoOp) message (Callback ID=0xe2, Expected Reply=0x13) - NoOperation_Set (Node=20): 0x01, 0x09, 0x00, 0x13, 0x14, 0x02, 0x00, 0x00, 0x25, 0xe2, 0x34
2020-05-14 08:34:57.874 Error, Node020, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-05-14 08:34:57.874 Detail, Node020, Removing current message
2020-05-14 08:34:57.874 Detail, Node020, Notification: Notification - TimeOut

I’m also trying to remove the node by selecting the node under: Developer Tools --> STATES and setting the: State attributes (YAML, optional) to: is_failed: true

Then back to Z-Wave Node Management, select the node and click REMOVE FAILED NODE

It does not appear this is working because I see this error in the logs:

2020-05-14 08:49:21.612 Detail, Node020, Queuing (Controller) Remove Failed Node
2020-05-14 08:49:21.613 Info, ControllerCommand_RemoveFailedNode
2020-05-14 08:49:21.613 Detail, contrlr, Queuing (Command) ControllerCommand_RemoveFailedNode: 0x01, 0x05, 0x00, 0x61, 0x14, 0xe4, 0x6b
2020-05-14 08:49:21.613 Detail, Notification: ControllerCommand - Starting
2020-05-14 08:49:21.615 Detail,
2020-05-14 08:49:21.615 Info, contrlr, Sending (Command) message (Callback ID=0xe4, Expected Reply=0x61) - ControllerCommand_RemoveFailedNode: 0x01, 0x05, 0x00, 0x61, 0x14, 0xe4, 0x6b
2020-05-14 08:49:22.615 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-05-14 08:49:22.615 Detail, contrlr, Removing current message
2020-05-14 08:49:22.616 Detail, contrlr, Notification: Notification - TimeOut
2020-05-14 08:49:22.622 Detail, Notification: ControllerCommand - Error - Failed

Would anyone know what’s going on and how to correct this? Also, why does the node show up as Ready when it is clearly not even physically present and has long since been buried in a landfill?

squirtbrnr · May 14, 2020, 1:11pm

It’s coming back to haunt you for burying it in a landfill…

But in all seriousness, have you restarted HA after removing the node? I’m guessing you have. In my experiences, a node does not actually get removed until I use the remove node service on the zwave configuration panel then restart. Sometimes it will let me delete the associated entities before I restart, but will always let me remove them all after.

alteredstate · May 14, 2020, 2:47pm

Okay…so this is crazy but I did reboot HA 3 times last night and no change. But after your post I decided to try the entire process all over again and for some reason it changed:

The only thing I did differently this time was reboot HA from the CLI:

~ $ hassio host reboot

Whereas before I went to: Supervisor --> System --> Reboot. Which I thought rebooted the host but apparently it’s different than the CLI command?

Since the Z-Wave node shows: unavailable how do I remove it now?

alteredstate · May 14, 2020, 2:58pm

Is this it:
Configuration --> Z-Wave Node Management select node then NODE INFORMATION

Then it shows REMOVE ENTITY

but if I click the “Gear Icon” it shows DELETE

What’s the difference between REMOVE ENTITY and DELETE?

squirtbrnr · May 14, 2020, 4:03pm

That’s a good question.

I believe one deletes the top level device (the zwave entity) and the other deletes the switch or sensors it creates alongside. I could be wrong though. I usually go into the configuration panel, entity list (might be called entities), and delete from there. It may give you the same popups so I’d say go ahead and click remove entity and delete as well. Then reboot again and verify neither entity shows up in the entity registry.

As for the difference in rebooting via CLI or Supervisor, I don’t know. I run HA Core in docker and always just restart my container to reboot HA. I don’t use any of the server reboot controls from the frontend because I’ve never had good success with them in the past. Hopefully someone more familiar with rebooting on a supervised system can chime in.

EDIT: actually, I think since that popup is specific for just the zwave node, remove entity and delete should do the same thing. You’ll want to also go find your switch.<whatever_you_named_it> and remove that entity as well.

alteredstate · May 18, 2020, 2:24pm

Yes, I believe you are correct but I’ve always wondered why there are two “entities” (sometimes more) for all my Z-wave devices? Seems like the entities could be condensed into one entity. Anyway, thanks for all the help!