Zwave error

upgraded zwave js and core to latest and now I have errors when trying to operate zwave devices.

core - 2024.10.2
zwave js - 0.7.2

Failed to perform the action switch/turn_on. Unable to set value 7-37-0-targetValue: zwave_error: Z-Wave error 202 - Failed to send the command after 1 attempts (ZW0202)

If i restart zwave js it works for like one time then I get the errors again. Whats going on here.

the log shows this after a restart and attempting to turn on/off devices:


2024-10-12T22:50:13.835Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2024-10-12T22:50:33.725Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2024-10-12T22:51:05.490Z CNTRLR   The controller is unresponsive
2024-10-12T22:51:05.494Z DRIVER   Controller missed Send Data callback. Attempting to recover...
2024-10-12T22:51:05.496Z CNTRLR   Performing soft reset...
2024-10-12T22:51:05.518Z CNTRLR   Waiting for the controller to reconnect...
2024-10-12T22:51:06.729Z CNTRLR   reconnected and restarted
2024-10-12T22:51:06.730Z CNTRLR   Starting hardware watchdog...
2024-10-12T22:51:06.733Z CNTRLR   Switching serial API to 16-bit node IDs...
2024-10-12T22:51:06.832Z CNTRLR   The controller is no longer unresponsive
2024-10-12T22:51:06.861Z CNTRLR   Switching to 16-bit node IDs successful
2024-10-12T22:51:43.983Z CNTRLR   The controller is jammed
2024-10-12T22:51:48.100Z DRIVER   Attempting to recover jammed controller...
2024-10-12T22:51:48.101Z CNTRLR   Performing soft reset...
2024-10-12T22:51:48.122Z CNTRLR   Waiting for the controller to reconnect...
2024-10-12T22:51:49.330Z CNTRLR   reconnected and restarted
2024-10-12T22:51:49.330Z CNTRLR   Starting hardware watchdog...
2024-10-12T22:51:49.333Z CNTRLR   Switching serial API to 16-bit node IDs...
2024-10-12T22:51:49.362Z CNTRLR   Switching to 16-bit node IDs successful
2024-10-12T22:51:49.510Z CNTRLR   The controller is no longer jammed

What controller?

Hope this answers the question.

Silicon_Labs_CP2102

It does not, that’s the model of the serial to USB chip. Looking for a brand and model of the Z-Wave controller, such as Zooz ZST10 700, Aeotec Z-Stick, etc.

This is what was on the order form when I purchased it.

MFG : SILICON LABORATORIES INC / SLUSB001A

DESC: Z-WAVE 700 UZB-7 USB STICK

What firmware / SDK version is installed?

and where do i find that?

On the Device page.

sorry not as familiar with home assistant as I should be. Can you tell me more precisely where to find the info?

https://www.home-assistant.io/integrations/zwave_js/#device-panel

Settings → Devices & Services

I don’t see anything listed as SDK in there but here is the firmware

700/800 Series

by Silicon Labs

Firmware: 7.18.8

That firmware should be OK, although there is an upgrade to 7.21.4 which might help. I can’t say 100% it will though.

Have you tried physically removing the USB stick and re-inserting?

Also, make sure you are using a USB extension cord. Take a look at these troubleshooting docs: https://zwave-js.github.io/node-zwave-js/#/troubleshooting/first-steps

I am for sure using a USB extension. I will try physically reinserting it. Should that be done at power off or powered on?

Ok re-inserting the USB did seem to have somewhat of a better longer fix than restarting z-wave js. But it is now failing again with the same issues.

I have also started to see these “Unable to set value 9-37-0-targetValue: zwave_error: Z-Wave error 202” in my log since one of the resent updates.

Z-Wave JS Current version: 0.8.1
700/800 Series by Silicon Labs Firmware: 7.21.4
Core2024.10.3
Supervisor2024.10.3
Operating System13.2

1 Like

same here… I also have 7.21.4 and ZWAVE JS 13.10.1
But I read some errors like that one … “unable to set value…”
I don´t know why… and I don’t know how could I fix it.

any idea?

Is anyone looking into this issue? It’s really bad because automations fail just because the z-wave commands dont go through. Why is there no retry when commands fail?

What information can I provide for anyone looking into solving this?

I’ve been battling this exact error for the past 3 days. Finally figured it out - I had 2 bad nodes (light switches) in my network. As soon as I disabled them (pull the airgap on the switch), the network restarted responding.

Same problem here.
Setup:
Aeotec Zwave 700 stick FW: v7.21.5 SDK: v7.21.5
ZwaveJS: 3.17.0
Core 2024.11.2
Supervisor 2024.11.2
Operating System 13.2

@DoctorB how did you find the bad nodes?