home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.38k stars 30.64k forks source link

Z-wave JS won't start. #107697

Closed rosnermd closed 9 months ago

rosnermd commented 9 months ago

The problem

After upgrading HA (core, supervisor, os) to the latest, z-wave js won't initialize. Using the CECOMINOD016164 HUSBZB-1 which the zigbee portion of it is working fine.

What version of Home Assistant Core has the issue?

2024.1.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Z-wave JS

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zwave_js/

Diagnostics information

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 [21:23:41] INFO: No 'network_key' detected, setting it to 's0_legacy_key' for backwards compatibility

[21:23:44] INFO: Flushing config to disk due to creation of new key(s)... [21:23:47] INFO: Soft-reset set to automatic [21:23:47] 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 [21:23:50] INFO: Successfully send discovery information to Home Assistant. 2024-01-10T02:23:53.352Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗ ╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝ ███╔╝ █████╗ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ ██║ ███████╗ ███╔╝ ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ██ ██║ ╚════██║ ███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║ ╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝ 2024-01-10T02:23:53.361Z DRIVER version 12.4.1 2024-01-10T02:23:53.362Z DRIVER
2024-01-10T02:23:54.451Z CONFIG version 12.4.1 2024-01-10T02:23:56.470Z CNTRLR querying Serial API capabilities... 2024-01-10T02:23:57.968Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i n 100 ms. 2024-01-10T02:23:59.080Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i n 1100 ms. 2024-01-10T02:24:01.208Z 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:5256:23) at ZWaveController.identify (/usr/src/node_modules/zwave-js/src/lib/contro ller/Controller.ts:897:37) at Driver.initializeControllerAndNodes (/usr/src/node_modules/zwave-js/src /lib/driver/Driver.ts:1432:26) at Immediate. (/usr/src/node_modules/zwave-js/src/lib/driver/Dr iver.ts:1226: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:5256:23) at ZWaveController.identify (/usr/src/node_modules/zwave-js/src/lib/controller/Controller.ts:897:37) at Driver.initializeControllerAndNodes (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1432:26) at Immediate. (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1226:16) (ZW0100) at Immediate. (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1246:6) { code: 100, context: undefined, transactionSource: undefined } Shutting down [02:24:01] 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 s6-linux-init-shutdown: fatal: unable to talk to shutdownd: Operation not permitted

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 9 months ago

Hey there @home-assistant/z-wave, mind taking a look at this issue as it has been labeled with an integration (zwave_js) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `zwave_js` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign zwave_js` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


zwave_js documentation zwave_js source (message by IssueLinks)

kpine commented 9 months ago

Did you upgrade the Z-Wave JS add-on as well? If so, from which version to which version?

rosnermd commented 9 months ago

Did you upgrade the Z-Wave JS add-on as well? If so, from which version to which version?

Running latest Zwave JS, 0.4.3

ErikL1984 commented 9 months ago

Same issue here after upgrading to 2024.1.2: Failed to connect: Cannot connect to host core-zwave-js:3000 ssl:default [Connect call failed ('172.30.33.2', 3000)]

Home Assistant on Intel NUC Z-Wave Plus Aeotec Z-Stick 7

Core: 2024.1.2 Supervisor: 2023.12.0 Operating System: 11.4 Frontend: 20240104.0 Zwave JS: 0.4.3

edit: Unfortunately, Z-Wave JS no longer works when you downgrade back to 2024.1.1

BigAlUK commented 9 months ago

Seeing the same - only found out when I couldn't unlock my front door to get in 😬

Logger: homeassistant.components.zwave_js Source: components/hassio/addon_manager.py:380

Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value @ data['options']. Got {'device': '/dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_14250a3e6694eb1197833a703d98b6d1-if00-port0'

Home Assistant Yellow Z-Wave Plus Aeotec Z-Stick 7

Core 2024.1.2 Supervisor 2023.12.0 Operating System 11.4 Frontend 20240104.0 Zwave JS: 0.4.3

kpine commented 9 months ago

Did you upgrade the Z-Wave JS add-on as well? If so, from which version to which version?

Running latest Zwave JS, 0.4.3

Did you upgrade from a previous version, or no?

kpine commented 9 months ago

Same issue here after upgrading to 2024.1.2: Failed to connect: Cannot connect to host core-zwave-js:3000 ssl:default [Connect call failed ('172.30.33.2', 3000)]

You would need to look for more logs to see why the connection failed. You can also check the add-on logs.

edit: Unfortunately, Z-Wave JS no longer works when you downgrade back to 2024.1.1

The version of HA doesn't matter in this case. Z-Wave JS is an add-on. Failed to connect typically corresponds to an add-on problem.

kpine commented 9 months ago

Seeing the same - only found out when I couldn't unlock my front door to get in 😬

Logger: homeassistant.components.zwave_js Source: components/hassio/addon_manager.py:380

Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value @ data['options']. Got {'device': '/dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_14250a3e6694eb1197833a703d98b6d1-if00-port0'

Home Assistant Yellow Z-Wave Plus Aeotec Z-Stick 7

That error means your USB stick is no longer detected by the operating system.

BigAlUK commented 9 months ago

That error means your USB stick is no longer detected by the operating system.

Ok, so it seems to correlate with OS upgrade I did today 11.3 -> 11.4. 😕

rosnermd commented 9 months ago

Did you upgrade the Z-Wave JS add-on as well? If so, from which version to which version?

Running latest Zwave JS, 0.4.3

Did you upgrade from a previous version, or no?

I updated Zwave JS to 0.4.3 when it was available on Dec 9, with no issues. Like @BigAlUK and @ErikL1984 called out, seems to be related to the core/os/supervisor updates recently.

I haven't gone as far as replacing my zwave dongle to rule out flaky hardware. Was hoping this was software first.

BigAlUK commented 9 months ago

I downgraded the OS 11.4 back to 11.3 and Z Wave came back in my case.

rosnermd commented 9 months ago

I downgraded the OS 11.4 back to 11.3 and Z Wave came back in my case.

tried downgrading to 11.3, no luck. Will try 11.2, but I might have a hardware problem 🤷‍♂️

rosnermd commented 9 months ago

Replaced hardware and back to working on 11.3 and 11.4. closing the issue