HA 12.3: Z-Wave JS add-on won‘t start anymore (Aeotec Z-Stick Gen5+)

Hi everyone,

Please help - this is what happened:

  • Fresh installation of Home Assistant (DIY with Raspberry Pi)
  • Factory reset of my Aeotec Z-Stick Gen5+
  • After plugging in it will be discovered in integrations
  • After confirming the dialog without providing any keys
  • the Pi will become unresponsive.

What‘s wrong? Any hints?

Many thanks in advance!

Z-Wave JS LOG:

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
[15:12:31] INFO: Both ‘network_key’ and ‘s0_legacy_key’ are set and match. All ok.

Home Assistant Core LOG:

Ended unfinished session (id=12 from 2024-05-26 07:34:02.908197)
15:14:25 – (WARNING) Recorder
The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly
15:14:25 – (WARNING) Recorder

As a suggestion, provide more information, as there is nothing obvious in the logs. Also, what does it mean “Pi will become unresponsive”?

Hi Tommy,

Thanks for your feedback! Let me try to provide helpful detail:

After ignoring the security keys and confirming the setup the popup window ‚The Z-Wave JS add-on installation has started (can take several minutes)‘ appears again.

After a few minutes the web browser won‘t get any answers from HA. After appr. 15-20 minutes HA will restart with the Z-Wave JS add-on stopped.

Thanks again!

It is unusual of course for HA to restart itself. I’m wondering if your system maybe memory or disk space limited (I don’t really know). Anyway, when you Start the ZWaveJS AddOn, then goto UI->System->Logs choose ZWaveJS from upper right pull down to see if you get any indication from it, and also check Supervisor logs as well as Home Assistant Core to see if there are any issues with the ZWave Integration.

Hi Tommy, thanks for your help! Here is my ZWaveJS Log:

2024-06-08T15:04:04.162Z CNTRLR   Enabling TX status report successful...
2024-06-08T15:04:04.163Z CNTRLR   finding SUC...
2024-06-08T15:04:04.188Z CNTRLR   No SUC present in the network
2024-06-08T15:04:04.189Z CNTRLR   There is no SUC/SIS in the network - promoting ourselves...
2024-06-08T15:04:04.225Z CNTRLR   Promotion to SUC/SIS succeeded.
2024-06-08T15:04:04.227Z CNTRLR   setting serial API timeouts: ack = 1000 ms, byte = 150 ms
2024-06-08T15:04:04.252Z CNTRLR   serial API timeouts overwritten. The old values were: ack = 1500 ms, byte = 15
                                  0 ms
2024-06-08T15:04:04.442Z CNTRLR   Interview completed
Starting server on <all interfaces>:3000
2024-06-08T15:04:04.733Z CNTRLR   [Node 001] Beginning interview - last completed stage: None
2024-06-08T15:04:04.751Z CNTRLR   [Node 001] new node, doing a full interview...
2024-06-08T15:04:04.759Z CNTRLR » [Node 001] querying protocol info...
ZwaveJS server listening on <all interfaces>:3000
2024-06-08T15:04:05.273Z CNTRLR « [Node 001] received response for protocol info:
                                  basic device class:    Static Controller
                                  generic device class:  Static Controller
                                  specific device class: PC Controller
                                  node type:             Controller
                                  is always listening:   true
                                  is frequent listening: false
                                  can route messages:    true
                                  supports security:     false
                                  supports beaming:      true
                                  maximum data rate:     100000 kbps
                                  protocol version:      3
2024-06-08T15:04:05.277Z CNTRLR   [Node 001] Interview stage completed: ProtocolInfo
2024-06-08T15:04:05.374Z CNTRLR   [Node 001] Embedded device config loaded
2024-06-08T15:04:05.376Z CNTRLR   [Node 001] Interview stage completed: OverwriteConfig
2024-06-08T15:04:05.630Z CNTRLR   [Node 001] Interview completed
2024-06-08T15:04:05.635Z CNTRLR   [Node 001] The node is ready to be used
2024-06-08T15:04:05.638Z CNTRLR   All nodes are ready to be used
2024-06-08T15:04:05.647Z CNTRLR   [Node 001] The node is alive.
2024-06-08T15:04:05.652Z CNTRLR   Interviewing nodes and/or determining their status: 
s6-rc: info: service legacy-services: stopping
Shutting down
Closing server...
Server closed
[15:24:26] 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
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
[17:34:19] INFO: No s0_legacy_key is set, generating one...

[17:34:23] INFO: No 'network_key' detected, setting it to 's0_legacy_key' for backwards compatibility

[17:34:26] INFO: No s2_access_control_key is set, generating one...

[17:34:30] INFO: No s2_authenticated_key is set, generating one...

[17:34:34] INFO: No s2_unauthenticated_key is set, generating one...

[17:34:37] INFO: No lr_s2_access_control_key is set, generating one...

[17:34:41] INFO: No lr_s2_authenticated_key is set, generating one...

[17:34:43] INFO: Flushing config to disk due to creation of new key(s)...
[17:34:49] INFO: Soft-reset set to automatic
[17:34:49] 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
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
[17:38:24] INFO: Both 'network_key' and 's0_legacy_key' are set and match. All ok.
[17:38:32] INFO: Soft-reset set to automatic
[17:38:32] 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
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
[17:48:26] INFO: Both 'network_key' and 's0_legacy_key' are set and match. All ok.
[17:48:35] INFO: Soft-reset set to automatic
[17:48:35] INFO: Virtual Machine not detected, enabling soft-reset

From the Supervisor Log:

2024-06-08 17:56:18.204 ERROR (MainThread) [supervisor.addons.addon] Add-on core_zwave_js has invalid options: Device '/dev/serial/by-id/usb-0658_0200-if00' does not exist in Z-Wave JS (core_zwave_js). Got {'device': '/dev/serial/by-id/usb-0658_0200-if00', 'log_level': 'info', 'log_to_file': False, 'log_max_files': 7, 'soft_reset': 'Automatic', 's0_legacy_key': 'CCBC8C884E257CF05AC013E9C1CA0E76', 's2_access_control_key': '3C18177A73ADADA53A10A82383502B5A', 's2_authenticated_key': 'EBB31D4EBD2A93A4A6F854253BE18D24', 's2_unauthenticated_key': '97FDE4604CF27AFA3FB857F6765F572D', 'lr_s2_access_control_key': '3FE2417209008449E6BF35B9B0F75D0D', 'lr_s2_authenticated_key': '5C4F92C6715C9059E1E2A6E48F51...
2024-06-08 17:56:18.223 WARNING (MainThread) [supervisor.addons.manager] Can't start Add-on core_zwave_js

Home Assistant Core:

Ended unfinished session (id=11 from 2024-06-08 15:28:16.201509) 
 17:56:41 – (WARNUNG) Recorder
The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly 
 17:56:41 – (WARNUNG) Recorder

In a different approach (after a clean install of HA “DIY with Raspberry Pi”) I just clicked on ‘configure’ in this new discovered integration:

After just confirming the network keys (leaving all fields empty) this appears:

And after more than 15 Minutes both LEDs of the Pi3 will stay on permanently and HA (http://homeassistant.local:8123) becomes unresponsive:

The only way to regain access to HA is to unplug the Aeotec Z-Stick Gen 5+.

The logs indicate that it sees the Z-Stick and seems to be OK with it at the beginning, then it tries to interview additional nodes and that is where it crashes. This is very unusual, and I don’t have knowledge at this point to know what is going on. My only suggestion is to factory reset the Z-Stick and if you still see this problem, post a question along with the logs to ZwaveJS GitHub and see if someone there can help.

Thanks, Tommy!

Check your host logs.

2 Likes

Downgrading to HAOS 12.2 solved my issue!

Thank you.

2 Likes

I had to do the same issue! 12.3+ broke Bluetooth and ZWave on my Ras.Pi.3.

Had to reinstall using 12.2 image. Won’t be upgrading for a while. Spent a week trying to figure out what was wrong with HA.