ZWaveJS woes…

Configuration Z-Wave
1

Hey all,

So I have 42 Zwave devices between hard-wired Zooz switches/dimmers, door locks, garage door openers and battery operated Zooz, Remotec motion and door sensors all supported by a gen5 Aeotech ZWave stick. For the most part my ZWave network is fairly stable and I don’t have to tinker with it over the past year. With recent updates (and I like to ensure I am up to date with all system and components) I have found that somehow my ZWave network has become very unstable and devices are showing up dead. Healing the device or network just seems to make things worse and eventually I have to remove and add the device back into the network (which is never successful the first 2-3 interviews).

Today my network cannot include/exclude anything resulting in devices I need to bring back into the network useless. I have rebooted the VM, I have restored to a previous known good state and I have even excluded the devices using a Nortek stick on my Windows laptop.

I watch the logs and never see messages for inclusion/exclusion though the UI says it is doing so.

Looking for advice as my only “fix” for this the last 2 times this happened was to start from scratch with my ZWave network and both times that was a lot of work.

Host: Windows 10 running VirtualBox
HassOS: current 2022.2.x version
All components up to date

2

Can you share some logs from your network? Is any of your devices spamming messages? Could you maybe have WiFi or Bluetooth interference on the Z-Stick? (Do you happen to have a USB extension cable to test bringing it further away from the laptop) Are you using the legacy Z-Wave integration, Z-WaveJS addon or Z-WaveJS2MQTT addon?

3

Good call out. I am running ZwaveJS native. I don’t have anything relevant for logs. When watching the ZWave JS logs you never see the initiating device or exclusion of device. This is the issue that I am worried I will be having to redo this entire network again. I am almost about to just ditch ZWave completely and go wifi everywhere.

4

What do your startup logs look like? Can you just post some of your logs? Also there are tools to export your setup so that people can look at it. What’s happening is not normal. Lastly, have you cleared your cache recently on the browser you’re using? Buttons might not work after an update if you don’t clear your cache because the browser might be pointing to old information (If that information was updated).

5

I can export out just need some guidance on what tool to use.

Cache isn’t the issue either as I have attempted to use a few different devices to try the inclusion/exclusion.

6

I’m just curious what your logs look like on bootup. I’m no expert but something should stick out in your logs. There are others who I can point to this thread for additional help.

7

I can post the homeassistant.log but I don’t think that is what you are looking for. Is there a place the ZwaveJS logs are stored so I can acquire those and post?

8

there should be a way to get the logs out through the integration.

integration → click configure on zwavejs → logs tab then there is a little download button above the logs

9

OK I tried to grab the logs as best I could.

This is trying things with inclusion of a Zooz 23 Switch:

Subscribed to Z-Wave JS Log Messages…
2022-02-20T17:14:52.896Z CNTRLR   [Node 056] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2022-02-20T17:14:53.410Z CNTRLR   The controller response indicated failure after 1/3 attempts. Scheduling next 
                                  try in 100 ms.
2022-02-20T17:14:53.520Z CNTRLR   The controller response indicated failure after 2/3 attempts. Scheduling next 
                                  try in 1100 ms.
2022-02-20T17:14:55.703Z CNTRLR   [Node 056]   supports CC Central Scene (0x5b) in version 3
2022-02-20T17:14:55.703Z CNTRLR » [Node 056]   querying the CC version for Supervision...
2022-02-20T17:14:55.718Z CNTRLR   The controller is now ready to add nodes
2022-02-20T17:14:55.726Z CNTRLR   The controller response indicated failure after 1/3 attempts. Scheduling next 
                                  try in 100 ms.
2022-02-20T17:14:55.837Z CNTRLR   The controller response indicated failure after 2/3 attempts. Scheduling next 
                                  try in 1100 ms.
2022-02-20T17:14:56.958Z CNTRLR   [Node 078] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2022-02-20T17:15:00.296Z CNTRLR « [Node 078] parameter #4 has value: 0
2022-02-20T17:15:00.297Z CNTRLR » [Node 078] querying parameter #5 value...
2022-02-20T17:15:13.397Z CNTRLR   [Node 056] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2022-02-20T17:15:13.402Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:15:13.439Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:15:13.597Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:15:13.705Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:15:13.761Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:15:29.298Z CNTRLR   [Node 056] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2022-02-20T17:15:29.495Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:15:29.817Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2022-02-20T17:15:42.387Z CNTRLR   [Node 056] The node did not respond after 3 attempts, it is presumed dead
2022-02-20T17:15:42.388Z CNTRLR   [Node 056] The node is now dead.
2022-02-20T17:15:42.405Z CNTRLR   [Node 056] Embedded device config loaded
2022-02-20T17:15:42.418Z CNTRLR   [Node 056] Interviewing Association Group Information...
2022-02-20T17:15:42.419Z CNTRLR » [Node 056] Association group #1: Querying name...
2022-02-20T17:15:42.420Z CNTRLR » [Node 056] pinging the node...
2022-02-20T17:15:43.693Z CNTRLR   [Node 056] The node is now alive.
2022-02-20T17:15:43.694Z CNTRLR   [Node 056] Beginning interview - last completed stage: NodeInfo
2022-02-20T17:15:43.696Z CNTRLR   [Node 056] Interviewing Version...
2022-02-20T17:15:43.696Z CNTRLR » [Node 056]   querying the CC version for Version...
2022-02-20T17:15:43.699Z CNTRLR « [Node 056] ping successful
2022-02-20T17:15:54.284Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:15:55.138Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:15:55.203Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:15:55.268Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:15:55.554Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:15:55.700Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:15:55.800Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:15:55.882Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:15:55.911Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:15:56.131Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:15:57.793Z CNTRLR   [Node 073] treating BasicCC::Set as a report
2022-02-20T17:15:57.886Z CNTRLR   [Node 073] treating BasicCC::Set as a report
2022-02-20T17:15:58.354Z CNTRLR   [Node 073] treating BasicCC::Set as a report
2022-02-20T17:15:58.971Z CNTRLR   [Node 073] treating BasicCC::Set as a report
2022-02-20T17:15:59.052Z CNTRLR   [Node 073] treating BasicCC::Set as a report
2022-02-20T17:15:59.187Z CNTRLR   [Node 078] Timed out while waiting for a response from the node (ZW0201)
2022-02-20T17:15:59.188Z CNTRLR « [Node 078] received no value for parameter #5
2022-02-20T17:15:59.188Z CNTRLR » [Node 078] querying parameter #6 value...
2022-02-20T17:16:03.183Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2022-02-20T17:16:03.294Z CNTRLR   The controller response indicated failure after 2/3 attempts. Scheduling next 
                                  try in 1100 ms.
2022-02-20T17:16:06.547Z CNTRLR   stopping inclusion process...
2022-02-20T17:16:11.301Z CNTRLR   [Node 004] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2022-02-20T17:16:16.630Z CNTRLR   The inclusion process was stopped
2022-02-20T17:16:18.338Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try in 100 ms.
10

This is attempting to exclude that same device:

Subscribed to Z-Wave JS Log Messages…

2022-02-20T17:16:25.828Z CNTRLR « [Node 056] Association group #1 has name "Lifeline"
2022-02-20T17:16:25.828Z CNTRLR » [Node 056] Association group #1: Querying command list...
2022-02-20T17:16:26.351Z CNTRLR « [Node 078] parameter #6 has value: 0
2022-02-20T17:16:26.352Z CNTRLR » [Node 078] querying parameter #8 value...
2022-02-20T17:16:26.959Z CNTRLR « [Node 056] received response for node versions:
                                    library type:      Enhanced Slave (0x03)
                                    protocol version:  5.3
                                    firmware versions: 4.0
                                    hardware version:  2
2022-02-20T17:16:26.959Z CNTRLR » [Node 056] querying CC versions...
2022-02-20T17:16:26.960Z CNTRLR » [Node 056]   querying the CC version for Binary Switch...
2022-02-20T17:16:31.428Z CNTRLR   starting exclusion process...
2022-02-20T17:16:33.216Z CNTRLR » [Node 056] Association group #2: Querying name...
2022-02-20T17:16:33.227Z CNTRLR   The controller is now ready to remove nodes
2022-02-20T17:16:33.237Z CNTRLR   The controller response indicated failure after 1/3 attempts. Scheduling next 
                                  try in 100 ms.
2022-02-20T17:16:33.348Z CNTRLR   The controller response indicated failure after 2/3 attempts. Scheduling next 
                                  try in 1100 ms.
2022-02-20T17:16:45.533Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:16:45.650Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:16:45.907Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:16:45.971Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:16:45.977Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:16:46.082Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:16:46.422Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:16:48.435Z CNTRLR   [Node 078] Timed out while waiting for a response from the node (ZW0201)
2022-02-20T17:16:48.436Z CNTRLR « [Node 078] received no value for parameter #8
2022-02-20T17:16:48.436Z CNTRLR » [Node 078] querying parameter #9 value...
2022-02-20T17:16:51.987Z CNTRLR   [Node 056]   supports CC Binary Switch (0x25) in version 1
2022-02-20T17:16:51.988Z CNTRLR   [Node 056]   skipping query for All Switch (0x27) because max implemented vers
                                  ion is 0
2022-02-20T17:16:51.991Z CNTRLR » [Node 056]   querying the CC version for Z-Wave Plus Info...
2022-02-20T17:16:55.628Z CNTRLR   [Node 073] treating BasicCC::Set as a report
2022-02-20T17:16:56.208Z CNTRLR   [Node 073] treating BasicCC::Set as a report
2022-02-20T17:16:56.532Z CNTRLR   [Node 073] treating BasicCC::Set as a report
2022-02-20T17:16:56.613Z CNTRLR   [Node 073] treating BasicCC::Set as a report
2022-02-20T17:16:56.669Z CNTRLR   [Node 073] treating BasicCC::Set as a report
2022-02-20T17:16:56.752Z CNTRLR   [Node 073] treating BasicCC::Set as a report
2022-02-20T17:16:56.930Z CNTRLR   [Node 073] treating BasicCC::Set as a report
2022-02-20T17:17:01.050Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:01.150Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:01.159Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:01.918Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:02.117Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:03.153Z CNTRLR   [Node 056] Timed out while waiting for a response from the node (ZW0201)
2022-02-20T17:17:03.153Z CNTRLR » [Node 056] Association group #2: Querying command list...
2022-02-20T17:17:05.540Z CNTRLR   [Node 073] treating BasicCC::Set as a report
2022-02-20T17:17:06.661Z CNTRLR   [Node 073] treating BasicCC::Set as a report
2022-02-20T17:17:07.351Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:07.381Z CNTRLR   [Node 073] treating BasicCC::Set as a report
2022-02-20T17:17:07.403Z CNTRLR « [Node 078] parameter #9 has value: 0
2022-02-20T17:17:07.404Z CNTRLR » [Node 078] querying parameter #10 value...
2022-02-20T17:17:07.413Z CNTRLR   The controller response indicated failure after 1/3 attempts. Scheduling next 
                                  try in 100 ms.
2022-02-20T17:17:08.395Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:08.554Z CNTRLR   [Node 073] treating BasicCC::Set as a report
2022-02-20T17:17:08.793Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:09.109Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:10.569Z CNTRLR   [Node 056]   supports CC Z-Wave Plus Info (0x5e) in version 2
2022-02-20T17:17:10.570Z CNTRLR » [Node 056]   querying the CC version for Association...
2022-02-20T17:17:17.243Z CNTRLR   [Node 073] treating BasicCC::Set as a report
2022-02-20T17:17:17.280Z CNTRLR   [Node 073] treating BasicCC::Set as a report
2022-02-20T17:17:17.438Z CNTRLR   [Node 073] treating BasicCC::Set as a report
2022-02-20T17:17:17.886Z CNTRLR   [Node 073] treating BasicCC::Set as a report
2022-02-20T17:17:18.150Z CNTRLR   [Node 073] treating BasicCC::Set as a report
2022-02-20T17:17:18.715Z CNTRLR   [Node 073] treating BasicCC::Set as a report
2022-02-20T17:17:19.619Z CNTRLR   [Node 073] treating BasicCC::Set as a report
2022-02-20T17:17:20.715Z CNTRLR   [Node 056] Timed out while waiting for a response from the node (ZW0201)
2022-02-20T17:17:20.715Z CNTRLR » [Node 056] Association group #3: Querying name...
2022-02-20T17:17:20.733Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2022-02-20T17:17:20.857Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                                  n 1100 ms.
2022-02-20T17:17:24.821Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:25.152Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:25.216Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:25.395Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:25.477Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:29.692Z CNTRLR   [Node 073] treating BasicCC::Set as a report
2022-02-20T17:17:29.911Z CNTRLR   [Node 073] treating BasicCC::Set as a report
2022-02-20T17:17:29.993Z CNTRLR   [Node 073] treating BasicCC::Set as a report
2022-02-20T17:17:31.732Z CNTRLR   [Node 073] treating BasicCC::Set as a report
2022-02-20T17:17:31.951Z CNTRLR   [Node 073] treating BasicCC::Set as a report
2022-02-20T17:17:32.134Z CNTRLR   [Node 078] Timed out while waiting for a response from the node (ZW0201)
2022-02-20T17:17:32.135Z CNTRLR « [Node 078] received no value for parameter #10
2022-02-20T17:17:32.135Z CNTRLR » [Node 078] querying parameter #11 value...
2022-02-20T17:17:32.152Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2022-02-20T17:17:33.169Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:33.233Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:33.299Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:33.330Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:33.549Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:33.684Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:33.725Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:33.772Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:34.114Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:35.552Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:36.969Z CNTRLR « [Node 062] TODO: no handler for application command
2022-02-20T17:17:37.647Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:38.003Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:38.041Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:38.281Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:38.398Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:38.623Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:39.104Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:39.487Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:39.645Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:39.909Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:40.114Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:17:42.460Z CNTRLR   [Node 056] Timed out while waiting for a response from the node (ZW0201)
2022-02-20T17:17:42.461Z CNTRLR   [Node 056] CC version query for Association timed out - assuming the node supp
                                  orts version 1...
2022-02-20T17:17:42.461Z CNTRLR » [Node 056]   querying the CC version for Multi Channel Association...
2022-02-20T17:17:56.950Z CNTRLR   [Node 056] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2022-02-20T17:17:57.128Z DRIVER     the node is unknown or not initialized yet, discarding...
2022-02-20T17:18:10.009Z CNTRLR   stopping exclusion process...
2022-02-20T17:18:10.418Z CNTRLR   [Node 056] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2022-02-20T17:18:10.820Z CNTRLR   [Node 073] treating BasicCC::Set as a report
11

Not sure how to acquire boot up logs btw

12

@petro

Looks like my Zooz Powerstrip went haywire again and was flooding the network. I still have controller errors but at least the network is back up. Zooz had a later version of OTA for me that I have applied and has drastically reduced the chatter on the network. Appreciate the help!

1 Like