Need a hand with Z-wave issues using a HUSBZB-1 stick. Zigbee devices working fine but my z-wave devices became undetectable.
I reset the only z wave device I have running to try and “repair” it (which didn’t work) then found the actual integration in HA to also be unresponsive to the stick. I then uninstalled the z wave integration and tried reinstalling and haven’t been able since. Keep getting the following errors.
I clicked around the ui for days to see if an obvious fix was there. Clearly nothing. I’ve googled and searched for days but don’t see an obvious path the follow.
Any help or direction would be greatly appreciated! Thanks in advance!
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
[08:04:32] INFO: Both 'network_key' and 's0_legacy_key' are set and match. All ok.
[08:04:34] INFO: Virtual Machine detected, disabling 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
[08:04:34] INFO: Successfully send discovery information to Home Assistant.
2022-12-08T13:04:38.294Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗
╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝
███╔╝ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ █████╗ ██║ ███████╗
███╔╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ╚════╝ ██ ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║
╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝
2022-12-08T13:04:38.304Z DRIVER version 10.3.0
2022-12-08T13:04:38.305Z DRIVER
2022-12-08T13:04:38.450Z CONFIG version 10.3.0
2022-12-08T13:04:40.436Z CNTRLR querying controller IDs...
2022-12-08T13:04:41.875Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2022-12-08T13:04:52.001Z CNTRLR No response from controller after 2/3 attempts. Scheduling next try in 1100 ms
.
2022-12-08T13:04:53.122Z DRIVER unexpected response, discarding...
2022-12-08T13:04:54.127Z 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
[13:04:54] WARNING: Halt add-on
s6-rc: info: service legacy-services: stopping
[13:04:54] 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
What kind of VM solution are you using? Have you tried reconnecting the HUSBZB-1 stick? How is it passed to HA? What path(s) are configured for the Z-Wave and Zigbee addons?
What you’re seeing is either:
Vm can’t talk to usb stick.
For this make sure. Your Vm solution is properly allowing the USB device to be mounted by your Vm.
HA can’t talk to USB stick -
This is usually either configuration
Check that you are using the By-id path to your stick and not the shorthand port identification. (sometimes the port can change, especially in VM land, ByID prevents this)
Or
USB interference - short extension /USB hub is usually enough to mitigate this.
So out of those, the cheapest and easiest ways to try to fix this - verify you are using the by-id path and then put in a short USB cable between the machine and the device… There’s long standing issues with these sticks and USB bus interference.
The errors you display are a dead ringer for what people see when interference is causing issues. Also let’s just say the nortek combination stick isn’t the best of the bunch.
When you get that done is the Aeotec USB or battery powered.
i ensured that the proper by-id was selected (coincidentally there are two duplicate paths, in addition to the generic shorthand). i’ve tried to do this process using both by-id’s and still it timed out.
i also added the usb extenson prior to doing all this, rebooted the server, and rebooted the VM a few times.
is the final line of your reply suggesting a different (Aeotec) device in place of the one I have? I am more than happy to replace this with another stick / hub if that was the solution.
