Hi
I`ve been using z-wave with the zwave JS addon for quite a while now but then, apparently after some update it simply stopped working. I then tried to re-install zwave with the Zwave-JS addon, unfortunately without success. Furthermore all I get now is an error where I gannot install zwave JS addon thus also zwave. Honestly I think it is due a wrong zwave JS input in the configuration.
it sayys:
## Z-Wave
Failed to connect
even though the usb stick is plugged in correctly.
If I remove and then reinstall zwave JS
I can choose from 3 different inputs:
this is what I get in the logs when starting zwaveJS:
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
[22:49:07] INFO: Both 'network_key' and 's0_legacy_key' are set and match. All ok.
[22:49:09] 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
[22:49:10] INFO: Successfully send discovery information to Home Assistant.
2022-11-27T21:49:14.101Z DRIVER ββββββββ βββ βββ ββββββ βββ βββ ββββββββ βββ ββββββββ
ββββββββ βββ βββ ββββββββ βββ βββ ββββββββ βββ ββββββββ
βββββ βββ ββ βββ ββββββββ βββ βββ ββββββ ββββββ βββ ββββββββ
βββββ ββββββββββ ββββββββ ββββ ββββ ββββββ ββββββ ββ βββ ββββββββ
ββββββββ ββββββββββ βββ βββ βββββββ ββββββββ ββββββββ ββββββββ
ββββββββ ββββββββ βββ βββ βββββ ββββββββ ββββββ ββββββββ
2022-11-27T21:49:14.110Z DRIVER version 10.3.0
2022-11-27T21:49:14.111Z DRIVER
It does not seem to lead me anywhere.
Do I need to update the firmware of the zmeeuzb1 stick and how on earth would I do that (only windows machine available+ the raspberry 4 where hassio is running on)
I am lost for ideas.
Thenks for your help, a solution or any suggestion.
Sascha
This is the device ID for the Z-Wave device and the one you should be using. The Texas Instruments ID is for Zigbee and ttyAMA0 is the onboard Bluetooth of your Raspberry Pi 4.
Another possibility would be to reconnect the UZB1 stick, just to power cycle it.
Hi,
thanks for the quick reply.
I did actually try to re-install it again.
unfortunately without luck.
## Z-Wave
Failed to start the Z-Wave JS add-on.
when I look in the logs of the add-ons. it first starts successfully but then it stops working.
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
[22:01:29] INFO: Both 'network_key' and 's0_legacy_key' are set and match. All ok.
[22:01:31] 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
[22:01:32] INFO: Successfully send discovery information to Home Assistant.
2022-11-28T21:01:35.621Z DRIVER ββββββββ βββ βββ ββββββ βββ βββ ββββββββ βββ ββββββββ
ββββββββ βββ βββ ββββββββ βββ βββ ββββββββ βββ ββββββββ
βββββ βββ ββ βββ ββββββββ βββ βββ ββββββ ββββββ βββ ββββββββ
βββββ ββββββββββ ββββββββ ββββ ββββ ββββββ ββββββ ββ βββ ββββββββ
ββββββββ ββββββββββ βββ βββ βββββββ ββββββββ ββββββββ ββββββββ
ββββββββ ββββββββ βββ βββ βββββ ββββββββ ββββββ ββββββββ
2022-11-28T21:01:35.629Z DRIVER version 10.3.0
2022-11-28T21:01:35.630Z DRIVER
2022-11-28T21:01:35.771Z CONFIG version 10.3.0
2022-11-28T21:01:37.175Z CNTRLR querying controller IDs...
2022-11-28T21:01:38.563Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2022-11-28T21:01:39.673Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2022-11-28T21:01:40.533Z DRIVER unexpected response, discarding...
2022-11-28T21:01:41.813Z 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
[21:01:41] WARNING: Halt add-on
s6-rc: info: service legacy-services: stopping
[21:01:42] 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
I have no idea what the reason for this failure could be.
Thanks
I think the problem was within on ofthe zwarve Nodes. It started working normally again as soon as I unplugged the Fibaro SmartPlug. So the issue is not really solved but I found a reasonable workarround.