Zwave js only showing 4 of 52 nodes ready

Configuration Z-Wave
1

my zwave js network has been working quite nicely over the last several months but then all of a sudden today it’s only showing 4 of 52 nodes ready. any idea how to troubleshoot this? i’ve restarted etc…

2

Did zwavejs get restarted? If so they have to interview the nodes again and battery operated nodes can take a while.

3

my home assistant was likely restarted but it doesn’t take this long to re-interview. and manually trying to re-interview fails. it says to check the logs for more information but I don’t know what I’m looking for.

4

Mine is the same. Updated to the new July release and now it’s Nodes ready: 6 / 44 as opposed to 43/44 before (known problem with one). The only ones connected are battery ones that are Asleep.

What is weird is that before I did a reboot and almost all went Dead I could get one toggle click out of them (so I turned a switch on in the UI and the light came one) but then they wouldn’t respond.

5

I tried to Heal the network from the integration page but looking at the JS to MQTT Control Panel, all the Dead ones were skipped.

6

yeah. i figured i wasn’t the only one with this problem. i just got done resetting my usb zwave device to factory defaults, deleted all my zwave configs in file browser and started from scratch. takes a while to include everything back but i didn’t want to wait even longer to try to find a fix either. it did serve to clean up my old and unused devices though so there’s that… lol
now hopefully this doesn’t happen again…

7

Silver lining :slight_smile:
Like you, my concern is that without a root fix, this may happen again tomorrow or on the next update/restart.

I understand though - as of right now my HA is severely crippled.

8

May be unrelated but I am seeing a disabled ‘sensor’ added to all of my devices that wasn’t there before.

For example:
sensor.ge_quick_fit_smart_in_wall_paddle_switch_node_status_10

I am fairly confident it wasn’t there before because I made sure to rename all the entities and these aren’t named appropriately.

9

yeah, that’s interesting. i’d check my config to see if i had the same thing but i deleted them…

10

This is just new functionality added in 2021.7. Always a good idea to read the release notes. 2021.7: A new entity, trigger IDs and script debugging - Home Assistant

Each node now has a status sensor available and can be pinged using the new zwave_js.ping service.

1 Like
11

Thanks - I saw the Heal Network part but missed that new sensor :blush:

Wish that new sensor followed the naming convention of the rest of the entities for a given device though.

This answers the sensor part but my devices are still showing Dead. Did I miss some breaking change? I reverted to 2021.6 but the devices didn’t come back then either. I then upgraded again. Happy to provide whatever detail is needed.

12

I’d guess the naming of the entity is probably because it’s disabled by default. In the past I’ve noticed that all of the disabled sensor don’t use the device naming, nor are the entity names updated if you rename devices.

The integration has no influence over the state of the nodes, it’s connecting to a “remote” (depending on how you’ve installed it) server. Simply restarting HA, upgrading/downgrading really has no relevance to the z-wave network.

I’d look at the addon/container logs of the server (Z-Wave JS addon, zwavejs2mqtt server) for details. Dead nodes are usually indicative of a z-wave network problem.

13

I had the same problem.

  • switches were asleep or dead (no battery)
  • some switches looked like they were alive, but when I try to use them nothing happened…

I thought it was something here. I tried Zwave2MQTT, but for some reason it did’t work.
Factory rest the zwave.me stick with Z-way and also factory reset the zwave switches.
But the problem not is, that everything looks ok, but add node isn’t working. :frowning_face:

14

I ended up unplugging the zstick and moving it around (extension). All my devices came back and so far seem to be responding.

15

i had tried moving the zooz zwave stick that i use to different ports on my HA machine but that didn’t help either. When I factory reset it and cleared out my zwave configs in home assistant, everything inside zwave JS has been working okay…

16

Factory resetting the stick would remove any zombie nodes in the network that can cause routing issues. There is software for Windows that can remove individual nodes without resetting the stick though.

17

After the factory reset of the stick – also deleted Zwave JS on HA, reboot OS 2x,
reinstalled Zwave JS with a new Network key and tried to ad node (the node was les then 1 m from my zwave stick). But no integration.

18

@24zeven is it only the one node you’re having trouble with or all of them?

19

I tried 4 nodes; all with the same result.

  • 1 Neo Coolcam powerplug (NAS-WR01Z)
  • 1 MCO Dimmer (MH-P220)
  • 2 Heltun High Load switches (HE-HLS01)
20

Problem is solved…
All switches/nodes are reset and joint the network again.

HA was running on a SSD-PI… I suspect it was a software error or hardware error on the SSD.
When I finally replaced the SSD with my backup SD-card of HA z-wave came back to life again…
The strange thing was that only z-wave didn’t work… Therefore I never thought that it could be the SSD…