Z-Wave JS won't start after upgrade today

Configuration Z-Wave
1

This is what I see each time I try to restart the add-on.

Any idea ?

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/config.sh
[14:06:57] INFO: Both 'network_key' and 's0_legacy_key' are set and match. All ok.
[14:07:05] INFO: Virtual Machine not detected, enabling soft-reset
cont-init: info: /etc/cont-init.d/config.sh exited 0
cont-init: info: running /etc/cont-init.d/structure.sh
cont-init: info: /etc/cont-init.d/structure.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun zwave_js (no readiness notification)
s6-rc: info: service legacy-services successfully started
[14:07:10] INFO: Successfully send discovery information to Home Assistant.
2023-04-27T21:07:19.714Z DRIVER   ███████╗ ██╗    ██╗  █████╗  ██╗   ██╗ ███████╗             ██╗ ███████╗
                                  ╚══███╔╝ ██║    ██║ ██╔══██╗ ██║   ██║ ██╔════╝             ██║ ██╔════╝
                                    ███╔╝  ██║ █╗ ██║ ███████║ ██║   ██║ █████╗   █████╗      ██║ ███████╗
                                   ███╔╝   ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝   ╚════╝ ██   ██║ ╚════██║
                                  ███████╗ ╚███╔███╔╝ ██║  ██║  ╚████╔╝  ███████╗        ╚█████╔╝ ███████║
                                  ╚══════╝  ╚══╝╚══╝  ╚═╝  ╚═╝   ╚═══╝   ╚══════╝         ╚════╝  ╚══════╝
2023-04-27T21:07:19.735Z DRIVER   version 10.16.0
2023-04-27T21:07:19.740Z DRIVER   
2023-04-27T21:07:21.114Z CONFIG   version 10.16.0
2023-04-27T21:07:26.104Z CNTRLR   querying controller IDs...
2023-04-27T21:07:28.364Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2023-04-27T21:07:29.486Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                                  n 1100 ms.
2023-04-27T21:07:31.653Z DRIVER   Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK 
                                  from the controller (ZW0200)
                                      at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Drive
                                  r.ts:4199:23)
                                      at ZWaveController.identify (/usr/src/node_modules/zwave-js/src/lib/contro
                                  ller/Controller.ts:930:33)
                                      at Driver.initializeControllerAndNodes (/usr/src/node_modules/zwave-js/src
                                  /lib/driver/Driver.ts:1292:26)
                                      at Immediate.<anonymous> (/usr/src/node_modules/zwave-js/src/lib/driver/Dr
                                  iver.ts:1098:16)
Error in driver ZWaveError: Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK from the controller (ZW0200)
    at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:4199:23)
    at ZWaveController.identify (/usr/src/node_modules/zwave-js/src/lib/controller/Controller.ts:930:33)
    at Driver.initializeControllerAndNodes (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1292:26)
    at Immediate.<anonymous> (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1098:16) (ZW0100)
    at Immediate.<anonymous> (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1115:6)
    at processTicksAndRejections (node:internal/process/task_queues:95:5) {
  code: 100,
  context: undefined,
  transactionSource: undefined
}
Shutting down
2

try to pull the controller out of USB socket en put it back :wink:

3

I did that and it didn’t help. However, doing a hard reboot of the system worked. Very weird.

4

I have the same problem but neither pulling the controller out and back in nor a hard reset did. help. Even restoring a backup didn‘t help.
Has anybody an idea what to do?

5

Got it working again, I put the controller in another USB port and magically it started to work again :exploding_head:

6

This keeps happening, and I don’t have any idea why. I just tried moving the Zooz ZST10 stick to another USB port, and that didn’t help. Tried to do a hard reboot, didn’t help either. I’m at a loss.
Is everyone else running into this problem using the same Zooz ZST10 stick ?
Is there a more reliable stick that can be used ?
I have some really critical Z-Wave automations like leak detections, valve automations, and I can’t afford for the Z-Wave to randomly stop working and suddenly require some sort of magical incantation to restore (what it might be, I don’t know, right now my system is in SOL state…).

7

This is what I’m running into right now …

2023-05-28T01:46:22.992Z DRIVER   version 10.22.2
2023-05-28T01:46:22.997Z DRIVER   
2023-05-28T01:46:24.339Z CONFIG   version 10.22.1
2023-05-28T01:46:29.089Z CNTRLR   querying controller IDs...
2023-05-28T01:46:31.391Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2023-05-28T01:46:32.517Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                                  n 1100 ms.
2023-05-28T01:46:34.690Z DRIVER   Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK 
                                  from the controller (ZW0200)
                                      at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Drive
                                  r.ts:4301:23)
                                      at ZWaveController.identify (/usr/src/node_modules/zwave-js/src/lib/contro
                                  ller/Controller.ts:908:33)
                                      at Driver.initializeControllerAndNodes (/usr/src/node_modules/zwave-js/src
                                  /lib/driver/Driver.ts:1342:26)
                                      at Immediate.<anonymous> (/usr/src/node_modules/zwave-js/src/lib/driver/Dr
                                  iver.ts:1148:16)
Error in driver ZWaveError: Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK from the controller (ZW0200)
    at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:4301:23)
    at ZWaveController.identify (/usr/src/node_modules/zwave-js/src/lib/controller/Controller.ts:908:33)
    at Driver.initializeControllerAndNodes (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1342:26)
    at Immediate.<anonymous> (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1148:16) (ZW0100)
    at Immediate.<anonymous> (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1165:6)
    at processTicksAndRejections (node:internal/process/task_queues:95:5) {
  code: 100,
  context: undefined,
  transactionSource: undefined
}
Shutting down
[01:46:35] WARNING: Halt add-on
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
8

No problems with my ZST10 700. What USB device path are you using, /dev/serial/by-id/...? Is the USB stick on an extension cord?

9

The problem occurs sometimes on hard reboots. The path is /dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10_700_Z-Wave_Stick_0001-if00-port0 .

Yes, it’s on an extension cord. I have tried to remove the cord to no avail.

What fixed it yesterday was to move it to the bottom left of the 4 ports on my Raspberry Pi 3B+. Normally it’s on the top left. Moving it to the top right didn’t work.

The problem doesn’t happen often, but when it does, it is very pervasive and requires manual intervention, which is really problematic.