Zooz z wave adapter no longer working

[lostreaver]

The problem

Zooz z wave 800 adapter stopped working.

Log details (ERROR)
Logger: homeassistant.components.zwave_js
Source: components/hassio/addon_manager.py:380
Integration: Z-Wave (documentation, issues)
First occurred: October 6, 2023 at 6:16:44 PM (1149 occurrences)
Last logged: 7:22:18 PM

Failed to start the Z-Wave JS add-on: Image homeassistant/amd64-addon-zwave_js:0.1.96 does not exist for addon_core_zwave_js
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-Zooz_800_Z-Wave_Stick_533D004242-if00', 's0_legacy_key': '6D1E8CE7F75A68020801F454AA492AB8', 's2_access_control_key': '29E5813430E2C0A67313FB96803F6F38', 's2_authenticated_key': '3A01C85E9F03F206C82A32EE9FC1BD89', 's2_unauthenticated_key': '3080AC9B38DE23EC87D9B0B700CEFB07'}

What version of Home Assistant Core has the issue?

core-2023.10.1

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

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[lostreaver]

Will upload error data file when back at a computer. Can't do it from Android?

[RGlintmeijer]

Same error here on home assistant core-2023.9.3:

Image homeassistant/amd64-addon-zwave_js:0.1.96 does not exist for addon_core_zwave_js

And in Core log (First occurred: 7 october 2023 at 00:57:36 CEST):

Logger: homeassistant.components.zwave_js
Source: components/hassio/addon_manager.py:380
Integration: Z-Wave (documentation, issues)
First occurred: 7 oktober 2023 om 00:57:36 (1479 occurrences)
Last logged: 09:54:47

Failed to start the Z-Wave JS add-on: Image homeassistant/amd64-addon-zwave_js:0.1.96 does not exist for addon_core_zwave_js`

Core logging at 7 october 2023 at 00:57:

Logger: homeassistant.config_entries
Source: config_entries.py:1248
First occurred: 7 oktober 2023 om 00:57:00 (1 occurrences)
Last logged: 7 oktober 2023 om 00:57:00

Config entry 'Z-Wave JS' for zwave_js integration not ready yet: Failed to connect: Cannot connect to host core-zwave-js:3000 ssl:default [Connect call failed ('172.30.33.2', 3000)]; Retrying in background

edit: see also home-assistant/supervisor#4610

[home-assistant]

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.

_{^{(message by CodeOwnersMention)}}

---

zwave_js documentation
zwave_js source
_{^{(message by IssueLinks)}}

[supernovae]

Mine stopped working with latest updates. Anything i should submit for logs?

[supernovae]

So, i went and changed the logging to debug and now when i click start, it actually shows a message

Image homeassistant/aarch64-addon-zwave_js:0.1.96 does not exist for addon_core_zwave_js

not sure why you have to be in debug to see the real message - but i guess i'll chase that down.

I'm running on a raspberry pi4 and haven't touched/changed arche's

[BigValveman]

I have Aeotec Gen 5 Zwave hub that quit working after installing latest Zwave-JS update. Error message is:
"This entity is no longer being provided by the zwave_js integration. If the entity is no longer in use, delete it in settings."

I'm running on a Tinkerboard S R2.0. Everything was working well before the update.

[superpsych0]

Mine stopped working with latest updates. Anything i should submit for logs?

Running HA on

• RPi 4B
• Zooz 700 Series Z-Wave Plus S2 USB Stick ZST10 700

When the problem occurred, I downgraded from 0.1.196 to partial backup of 0.1.193 and I was back up and running.

Unfortunately, I had the damn thing set to auto-update, so it went back to 0.1.196 overnight... and then didn't respond to partial restores anymore, tried all the way back to 0.1.188 I believe.

0.1.197 does not fix the problem.

Please let me know what to provide, would love to have my door locks and a bunch of light automations back ASAP.

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
[19:18:11] INFO: �[32mNo 'network_key' detected, setting it to 's0_legacy_key' for backwards compatibility�[0m
[19:18:13] INFO: �[32mFlushing config to disk due to creation of new key(s)...�[0m
[19:18:15] INFO: �[32mVirtual Machine not detected, enabling soft-reset�[0m
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
[19:18:17] INFO: �[32mSuccessfully send discovery information to Home Assistant.�[0m
2023-10-09T23:18:20.297Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗
╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝
███╔╝ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ █████╗ ██║ ███████╗
███╔╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ╚════╝ ██ ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║
╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝
2023-10-09T23:18:20.308Z DRIVER version 12.0.0
2023-10-09T23:18:20.310Z DRIVER
2023-10-09T23:18:29.393Z DRIVER Failed to open the serial port: Error Resource temporarily unavailable Cannot
lock port
Unable to start driver ZWaveError: Failed to open the serial port: Error Resource temporarily unavailable Cannot lock port (ZW0100)
at Driver.openSerialport (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1225:9)
at Immediate. (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1060:5) {
code: 100,
context: undefined,
transactionSource: undefined
}
[23:18:29] WARNING: �[33mHalt add-on�[0m
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

[lostreaver]

Looks like the latest z-wave-js updated 0.1.97 fixed the issue. Did require a full HA reboot.