Trouble installing z-wave integration

Just purchased a silicon labs z-wave usb stick and am trying to install the integration. The stick is recognized and the add-on installs and starts. When I go to add the integration I check the box to use the supervisor to make the connection but it just hangs. Errors in the log file:

6-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:41:58] INFO: Both β€˜network_key’ and β€˜s0_legacy_key’ are set and match. All ok.
[14:42:00] 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:42:00] INFO: Successfully send discovery information to Home Assistant.
2022-11-05T21:42:02.576Z DRIVER β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— β–ˆβ–ˆβ•— β–ˆβ–ˆβ•— β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— β–ˆβ–ˆβ•— β–ˆβ–ˆβ•— β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— β–ˆβ–ˆβ•— β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•—
β•šβ•β•β–ˆβ–ˆβ–ˆβ•”β• β–ˆβ–ˆβ•‘ β–ˆβ–ˆβ•‘ β–ˆβ–ˆβ•”β•β•β–ˆβ–ˆβ•— β–ˆβ–ˆβ•‘ β–ˆβ–ˆβ•‘ β–ˆβ–ˆβ•”β•β•β•β•β• β–ˆβ–ˆβ•‘ β–ˆβ–ˆβ•”β•β•β•β•β•
β–ˆβ–ˆβ–ˆβ•”β• β–ˆβ–ˆβ•‘ β–ˆβ•— β–ˆβ–ˆβ•‘ β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•‘ β–ˆβ–ˆβ•‘ β–ˆβ–ˆβ•‘ β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— β–ˆβ–ˆβ•‘ β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•—
β–ˆβ–ˆβ–ˆβ•”β• β–ˆβ–ˆβ•‘β–ˆβ–ˆβ–ˆβ•—β–ˆβ–ˆβ•‘ β–ˆβ–ˆβ•”β•β•β–ˆβ–ˆβ•‘ β•šβ–ˆβ–ˆβ•— β–ˆβ–ˆβ•”β• β–ˆβ–ˆβ•”β•β•β• β•šβ•β•β•β•β• β–ˆβ–ˆ β–ˆβ–ˆβ•‘ β•šβ•β•β•β•β–ˆβ–ˆβ•‘
β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— β•šβ–ˆβ–ˆβ–ˆβ•”β–ˆβ–ˆβ–ˆβ•”β• β–ˆβ–ˆβ•‘ β–ˆβ–ˆβ•‘ β•šβ–ˆβ–ˆβ–ˆβ–ˆβ•”β• β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— β•šβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•”β• β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•‘
β•šβ•β•β•β•β•β•β• β•šβ•β•β•β•šβ•β•β• β•šβ•β• β•šβ•β• β•šβ•β•β•β• β•šβ•β•β•β•β•β•β• β•šβ•β•β•β•β• β•šβ•β•β•β•β•β•β•
2022-11-05T21:42:02.581Z DRIVER version 10.3.0
2022-11-05T21:42:02.581Z DRIVER
2022-11-05T21:42:02.675Z CONFIG version 10.3.0
2022-11-05T21:42:03.437Z CNTRLR querying controller IDs…
2022-11-05T21:42:04.678Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2022-11-05T21:42:05.784Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2022-11-05T21:42:07.902Z 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:3990:23)
at ZWaveController.identify (/usr/src/node_modules/zwave-js/src/lib/contro
ller/Controller.ts:713:33)
at Driver.initializeControllerAndNodes (/usr/src/node_modules/zwave-js/src
/lib/driver/Driver.ts:1208:26)
at Immediate. (/usr/src/node_modules/zwave-js/src/lib/driver/Dr
iver.ts:1015: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:3990:23)
at ZWaveController.identify (/usr/src/node_modules/zwave-js/src/lib/controller/Controller.ts:713:33)
at Driver.initializeControllerAndNodes (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1208:26)
at Immediate. (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1015:16) (ZW0100)
at Immediate. (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1032:6)
at processTicksAndRejections (node:internal/process/task_queues:96:5) {
code: 100,
context: undefined,
transactionSource: undefined
}
Shutting down
[21:42:07] WARNING: Halt add-on
s6-rc: info: service legacy-services: stopping
[21:42:08] INFO: Service restart after closing
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

Not sure what to try next.
re,
Allen

which add-on did you install?

it sounds like you installed an add-on and then told the integration to install the supervisor controlled add-on as well. β€œthere can be only one!” :wink:

if you want to keep the previously installed add-on then don’t check the supervised box in the integration. you’ll also likely need to uninstall the automatically installed supervised add-on too.

if you want the supervised add-on then remove the previously installed add-on and select the supervised check box in the integration.

I removed the Z Wave JS add on, started with +integration, left the box checked to use the supervised add on, the add on was installed but the integration install just hangs. Same errors in the add on log.

Is the supervisor add-on using the correct zwave controller hardware config?

I’m going to be of limited help from here on since I don’t use the Supervisor.

The supervisor discovers a path that looks like the stick:

Device

/dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_f23bcaad6b4fe811942337fdc2460985-if00-port0

There is only one device in the USB slots so I am guessing this is correct.

Here is the debug log:

                                  1 registered
2022-11-06T16:16:27.040Z DRIVER   added request handler for RemoveNodeFromNetwork (0x4b)...
                                  1 registered
2022-11-06T16:16:27.041Z DRIVER   added request handler for ReplaceFailedNode (0x63)...
                                  1 registered
2022-11-06T16:16:27.043Z CNTRLR   querying controller IDs...
2022-11-06T16:16:27.254Z SERIAL Β» 0x01030020dc                                                         (5 bytes)
2022-11-06T16:16:27.257Z DRIVER Β» [REQ] [GetControllerId]
2022-11-06T16:16:27.273Z SERIAL Β« [DISCARDED] invalid data 0x0d0a4765636b6f20426f6f746c6f61646572207 (128 bytes)
                                  6312e352e310d0a312e2075706c6f61642067626c0d0a322e2072756e0d0a332e2065626c20696
                                  e666f0d0a424c203e20000d0a4765636b6f20426f6f746c6f616465722076312e352e310d0a312
                                  e2075706c6f61642067626c0d0a322e2072756e0d0a332e2065626c20696e
2022-11-06T16:16:27.276Z SERIAL Β« [DISCARDED] invalid data 0x666f0d0a424c203e20000d0a4765636b6f20426f (64 bytes)
                                  6f746c6f616465722076312e352e310d0a312e2075706c6f61642067626c0d0a322e2072756e0d
                                  0a332e2065
2022-11-06T16:16:27.280Z SERIAL Β« [DISCARDED] invalid data 0x626c20696e666f0d0a424c203e20000d0a476563 (64 bytes)
                                  6b6f20426f6f746c6f616465722076312e352e310d0a312e2075706c6f61642067626c0d0a322e
                                  2072756e0d
2022-11-06T16:16:27.285Z SERIAL Β« [DISCARDED] invalid data 0x0a332e2065626c20696e666f0d0a424c203e2000 (64 bytes)
                                  0d0a4765636b6f20426f6f746c6f616465722076312e352e310d0a312e2075706c6f6164206762
                                  6c0d0a322e
2022-11-06T16:16:27.289Z SERIAL Β« [DISCARDED] invalid data 0x2072756e0d0a332e2065626c20696e666f0d0a42 (25 bytes)
                                  4c203e2000
2022-11-06T16:16:28.277Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2022-11-06T16:16:28.379Z SERIAL Β» 0x01030020dc                                                         (5 bytes)
2022-11-06T16:16:28.380Z DRIVER Β» [REQ] [GetControllerId]
2022-11-06T16:16:28.387Z SERIAL Β« [DISCARDED] invalid data 0x0d0a4765636b6f20426f6f746c6f616465722076 (64 bytes)
                                  312e352e310d0a312e2075706c6f61642067626c0d0a322e2072756e0d0a332e2065626c20696e
                                  666f0d0a42
2022-11-06T16:16:28.392Z SERIAL Β« [DISCARDED] invalid data 0x4c203e20000d0a4765636b6f20426f6f746c6f61 (64 bytes)
                                  6465722076312e352e310d0a312e2075706c6f61642067626c0d0a322e2072756e0d0a332e2065
                                  626c20696e
2022-11-06T16:16:28.398Z SERIAL Β« [DISCARDED] invalid data 0x666f0d0a424c203e20000d0a4765636b6f20426f (64 bytes)
                                  6f746c6f616465722076312e352e310d0a312e2075706c6f61642067626c0d0a322e2072756e0d
                                  0a332e2065
2022-11-06T16:16:28.403Z SERIAL Β« [DISCARDED] invalid data 0x626c20696e666f0d0a424c203e20000d0a476563 (64 bytes)
                                  6b6f20426f6f746c6f616465722076312e352e310d0a312e2075706c6f61642067626c0d0a322e
                                  2072756e0d
2022-11-06T16:16:28.409Z SERIAL Β« [DISCARDED] invalid data 0x0a332e2065626c20696e666f0d0a424c203e2000 (64 bytes)
                                  0d0a4765636b6f20426f6f746c6f616465722076312e352e310d0a312e2075706c6f6164206762
                                  6c0d0a322e
2022-11-06T16:16:28.413Z SERIAL Β« [DISCARDED] invalid data 0x2072756e0d0a332e2065626c20696e666f0d0a42 (25 bytes)
                                  4c203e2000
2022-11-06T16:16:29.383Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                                  n 1100 ms.
2022-11-06T16:16:30.486Z SERIAL Β» 0x01030020dc                                                         (5 bytes)
2022-11-06T16:16:30.486Z DRIVER Β» [REQ] [GetControllerId]
2022-11-06T16:16:30.493Z SERIAL Β« [DISCARDED] invalid data 0x0d0a4765636b6f20426f6f746c6f616465722076 (64 bytes)
                                  312e352e310d0a312e2075706c6f61642067626c0d0a322e2072756e0d0a332e2065626c20696e
                                  666f0d0a42
2022-11-06T16:16:30.498Z SERIAL Β« [DISCARDED] invalid data 0x4c203e20000d0a4765636b6f20426f6f746c6f61 (64 bytes)
                                  6465722076312e352e310d0a312e2075706c6f61642067626c0d0a322e2072756e0d0a332e2065
                                  626c20696e
2022-11-06T16:16:30.504Z SERIAL Β« [DISCARDED] invalid data 0x666f0d0a424c203e20000d0a4765636b6f20426f (64 bytes)
                                  6f746c6f616465722076312e352e310d0a312e2075706c6f61642067626c0d0a322e2072756e0d
                                  0a332e2065
2022-11-06T16:16:30.510Z SERIAL Β« [DISCARDED] invalid data 0x626c20696e666f0d0a424c203e20000d0a476563 (64 bytes)
                                  6b6f20426f6f746c6f616465722076312e352e310d0a312e2075706c6f61642067626c0d0a322e
                                  2072756e0d
2022-11-06T16:16:30.515Z SERIAL Β« [DISCARDED] invalid data 0x0a332e2065626c20696e666f0d0a424c203e2000 (64 bytes)
                                  0d0a4765636b6f20426f6f746c6f616465722076312e352e310d0a312e2075706c6f6164206762
                                  6c0d0a322e
2022-11-06T16:16:30.519Z SERIAL Β« [DISCARDED] invalid data 0x2072756e0d0a332e2065626c20696e666f0d0a42 (25 bytes)
                                  4c203e2000
2022-11-06T16:16:31.502Z 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:3990:23)
                                      at ZWaveController.identify (/usr/src/node_modules/zwave-js/src/lib/contro
                                  ller/Controller.ts:713:33)
                                      at Driver.initializeControllerAndNodes (/usr/src/node_modules/zwave-js/src
                                  /lib/driver/Driver.ts:1208:26)
                                      at Immediate.<anonymous> (/usr/src/node_modules/zwave-js/src/lib/driver/Dr
                                  iver.ts:1015: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:3990:23)
    at ZWaveController.identify (/usr/src/node_modules/zwave-js/src/lib/controller/Controller.ts:713:33)
    at Driver.initializeControllerAndNodes (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1208:26)
    at Immediate.<anonymous> (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1015:16) (ZW0100)
    at Immediate.<anonymous> (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1032:6)
    at processTicksAndRejections (node:internal/process/task_queues:96:5) {
  code: 100,
  context: undefined,
  transactionSource: undefined
}
Shutting down
2022-11-06T16:16:31.511Z DRIVER   destroying driver instance...
2022-11-06T16:16:31.513Z DRIVER   driver instance destroyed
[16:16:31] WARNING: Halt add-on
s6-rc: info: service legacy-services: stopping
[16:16:31] INFO: Service restart after closing
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```

Sorry about being limited help but…

Have you tried removing all the integrations and the add-ons and restarting the supervisor and HA to try to start from scratch?

Heck maybe even a reboot of the host might be necessary if the add-on can’t communicate with the controller. Maybe something has locked the controller from the previous attempts with two add-ons and a reboot might release it.

Yeah, tried removing the add on, rebooted the server, unplugged the stick, tried a different port.
Clearly I am missing the correct sequence.
Always seem to be getting the same result.

I suppose it could be possible that the stick is malfunctioning too?

I would think the log messages would be clue but I do not know the code. So the errors meaning is not clear.

Is your USB controller installed with a short extension cable? https://zwave-js.github.io/node-zwave-js/#/troubleshooting/connectivity-issues?id=general-troubleshooting

1 Like

I always forget about that.

I’ve never had any issues and my two zwave controllers are connected directly to my NUC and 6 inches apart and I’ve never had any issues with that.

No, direct connection to server usb port.

Solved it. Bought a new Zooz z-wave USB stick and everything installed as documented. Silicon Labs stick must have issues.

1 Like