Physically dead z-wave device reappeared

Hello,

I had a Zooz dimmer switch physically fail. I removed the device from Home Assistant, went into .storage and yanked the entries from core.*. On my last reboot of HA the device reappeared. HA thinks it is communicating with the device, it shows as “ready”.

Any thoughts?

did you remove the failed node from the Z Wave controller? If you didn’t, HA is reading the nodes from the controller and sees a node it doesn’t have in its entity registry and recreates it.

I’m going to go with “no” as I’m not sure how to do that.

It’s currently showing as “ready” though, not failed so I cannot do “remove failed node”.

what integration for Z wave are you using? Built-in, zwave2mqtt, the new zwavejs, or something else? Also what hardware is your zwave controller? Aeotec, zwave hat, or some other dongle?

what you’ll need to do is somehow force the controller to see the node as dead. that may entail a test or heal network or forcing the node to dead, again within the controller. once dead, you can do the remove failed node. You might still be able to remove the node through normal removal means even without the node in place, but it’s been a while since I’ve had to do that.

I’m OG Home Assistant so I’m running the built in z-wave (waiting for migration path!). My controller is a Zooz ZST10 S2.

ok I’m not familiar with the Zooz controller, but I use the built-in zwave integration too. go to your integrations page and click on “configure” under the zwave integration. find the device/node in the node list and you might be able to attempt a heal/test node. once the controller fails that it should mark it as dead. then you can use the remove failed node link towards the top of the configure page.

EDIT: it looks like the remove failed node command doesn’t exist anymore, so maybe the normal “remove node” command works. make sure the node is selected and try that.

Attempted a couple of “test node” and “heal node” and nothing is getting it to mark as failed. I can see in the log that all the commands are failing though.

Just seeing your edit - I’ll attempt to “remove node”. I thought that was to put the controller into exclusion mode and required physical input on the device?

Attempted to force the node to show as failed per instructions here Z-Wave Control Panel - Home Assistant (home-assistant.io) - that causes “remove failed node” to show up.

Crashed Home Assistant.

yes, the remove node command puts the controller into exclusion mode requiring input from a node. I wasn’t sure where the remove failed node command went, that’s why I suggested trying just remove node. Now I know it only shows up when it sees a dead node. Not sure why the command caused HA to fail. check the OZW log to see if the command succeeded or failed.

HA trying to reboot. Following in logs:

2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594160185345}) on node 7


2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594160185368}) on node 7


2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594160185384}) on node 7


2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594168574000}) on node 7


2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594168574017}) on node 7


2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594168590340}) on node 7


2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594169442307}) on node 7


2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594169491457}) on node 7


2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594169491478}) on node 7


2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594169491494}) on node 7


2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594165592084}) on node 7


2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594165592100}) on node 7


2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594165592116}) on node 7


2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594165592134}) on node 7


2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594165592148}) on node 7


2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594165592166}) on node 7


2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594165592196}) on node 7


2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594165592209}) on node 7


2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594165592225}) on node 7


2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594165592241}) on node 7


2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594165592260}) on node 7


2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594169835524}) on node 7


2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594169835537}) on node 7


2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594169835560}) on node 7


2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594169835569}) on node 7


2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594169835588}) on node 7


2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594169835606}) on node 7


2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594169835624}) on node 7


2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594169835640}) on node 7


2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594169835652}) on node 7


2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594169835670}) on node 7


2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594170146823}) on node 7


2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594170146839}) on node 7


2021-02-10 19:25:43 WARNING (Dummy-6) [openzwave] Z-Wave Notification ValueRemoved for an unknown value ({'id': 72057594170146855}) on node 7


2021-02-10 19:25:43 ERROR (Dummy-6) [openzwave] Error in manager callback


Traceback (most recent call last):


  File "/usr/local/lib/python3.8/site-packages/openzwave/network.py", line 944, in zwcallback


    self._handle_node_removed(args)


  File "/usr/local/lib/python3.8/site-packages/openzwave/network.py", line 1249, in _handle_node_removed


    dispatcher.send(self.SIGNAL_NODE_REMOVED, \


  File "/usr/local/lib/python3.8/site-packages/pydispatch/dispatcher.py", line 333, in send


    response = robustapply.robustApply(


  File "/usr/local/lib/python3.8/site-packages/pydispatch/robustapply.py", line 55, in robustApply


    return receiver(*arguments, **named)


  File "/usr/src/homeassistant/homeassistant/components/zwave/__init__.py", line 499, in node_removed


    entity = hass.data[DATA_DEVICES][node_key]


KeyError: 'node-7'


2021-02-10 19:26:13 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 7 not ready after 30 seconds, continuing anyway

A zombie node, hard to kill those :sunglasses:

1 Like

Command failed in OZW_log before HA crashed.

HA back up. Now I have Node 7 “unknown” and I have another entry for the Zooz switch as “undefined”.

Node 7 was that failed switch.

The undefined Zooz entity was being “recreated” by HA as it couldn’t find it. So that was as simple as “remove entity”.

Node 7 “unknown” is still “initializing”.

Ok we’re getting somewhere I think. Yes zombie nodes are difficult. the node may now be removed from the controller, hence the “unknown” and “initializing” status. You can now go into the entity and device registry from the frontend/configuration page and find this device and node and remove like you did with the zombie Zooz entity. It may take a couple reboots to fully remove it.

ok - I’ve done a couple reboots.

Node 7 is no longer showing up in the z-wave control panel; however, the “Zooz” device is showing up under the device registry with no option to remove it from the frontend.

Thoughts?

You might now need to dig into the .storage files and delete from there if it cannot be removed from the device or entity registry. I seem to remember having this issue myself removing a node (even one that wasn’t dead). Ultimately in the end I shut down HA, deleted the entity registry file in the folder, and because I run HA Container I deleted the container and recreated it, then started HA and it rebuilt the entity registry but this time without the zombie node.

I’ll give the .storage file method a shot. I did that originally and it came back leading me to create this thread!

but at least it has been removed from the controller now, so it shouldn’t come back this time.

I think we have it solved! Thank you @squirtbrnr!

1 Like