THE PROBLEM:
This was a previously working HA instance. As of this morning, all my Z-wave devices became unavailable. Under Settings–>Integrations–> Z-Wave JS, there is an error message as follows: “Retrying setup: None”.
STEPS TAKEN:
- Updated HA → problem persisted, then
- Wiped HA and reinstalled a backup from 2 days ago → problem persisted, then
- Confirmed Z-wave stick firmware was up-to-date → it was, then
- In HA navigated to Settings–>System–>Hardware–>All Hardware → confirmed device was plugged in
- Confirmed physical connections were good. Device is on with the blue LED light.
- Read this reddit post → No solution there for me.
- I also have a help request on r/homeassistant
SYSTEM INFO:
Hardware:
- Raspberry Pi 4
- Aotec Z-stick Gen5+
Software:
- Home Assistant Version 2023.1.4
- Supervisor 2022.12.1
- Operating System 9.4
- Frontend 20230110.0 - latest
- Aotec ver 6.07
Look in your add-on log for an error.
1 Like
I don’t see any errors, but I’m not great at navigating these logs. Does anything jump out at you?
> Blockquote
2023-01-16T00:43:53.443Z CNTRLR [Node 030] The node is ready to be used
2023-01-16T00:43:53.454Z CNTRLR « [Node 030] ping successful
2023-01-16T00:43:53.716Z CNTRLR [Node 031] The node is alive.
2023-01-16T00:43:53.718Z CNTRLR [Node 031] The node is ready to be used
2023-01-16T00:43:53.723Z CNTRLR « [Node 031] ping successful
2023-01-16T00:43:54.538Z CNTRLR [Node 032] The node is alive.
2023-01-16T00:43:54.540Z CNTRLR [Node 032] The node is ready to be used
2023-01-16T00:43:54.546Z CNTRLR « [Node 032] ping successful
2023-01-16T00:44:01.598Z CNTRLR [Node 033] The node did not respond after 1 attempts, it is presumed dead
2023-01-16T00:44:01.600Z CNTRLR [Node 033] The node is dead.
2023-01-16T00:44:01.618Z CNTRLR [Node 033] ping failed: Failed to send the command after 1 attempts (Status No
Ack) (ZW0204)
2023-01-16T00:44:01.782Z CNTRLR [Node 034] The node is alive.
2023-01-16T00:44:01.784Z CNTRLR [Node 034] The node is ready to be used
2023-01-16T00:44:01.794Z CNTRLR « [Node 034] ping successful
2023-01-16T00:44:01.913Z CNTRLR [Node 035] The node is alive.
2023-01-16T00:44:01.914Z CNTRLR [Node 035] The node is ready to be used
2023-01-16T00:44:01.921Z CNTRLR « [Node 035] ping successful
2023-01-16T00:44:02.153Z CNTRLR [Node 036] The node is alive.
2023-01-16T00:44:02.155Z CNTRLR [Node 036] The node is ready to be used
2023-01-16T00:44:02.160Z CNTRLR « [Node 036] ping successful
2023-01-16T00:44:02.397Z CNTRLR [Node 037] The node is alive.
2023-01-16T00:44:02.399Z CNTRLR [Node 037] The node is ready to be used
2023-01-16T00:44:02.405Z CNTRLR « [Node 037] ping successful
2023-01-16T00:44:02.503Z CNTRLR [Node 038] The node is alive.
2023-01-16T00:44:02.505Z CNTRLR [Node 038] The node is ready to be used
2023-01-16T00:44:02.511Z CNTRLR « [Node 038] ping successful
2023-01-16T00:44:02.906Z CNTRLR [Node 039] The node is alive.
2023-01-16T00:44:02.907Z CNTRLR [Node 039] The node is ready to be used
2023-01-16T00:44:02.913Z CNTRLR « [Node 039] ping successful
2023-01-16T00:44:02.962Z CNTRLR [Node 040] The node is alive.
2023-01-16T00:44:02.963Z CNTRLR [Node 040] The node is ready to be used
2023-01-16T00:44:02.980Z CNTRLR « [Node 040] ping successful
2023-01-16T00:44:03.104Z CNTRLR [Node 041] The node is alive.
2023-01-16T00:44:03.114Z CNTRLR [Node 041] The node is ready to be used
2023-01-16T00:44:03.121Z CNTRLR « [Node 041] ping successful
2023-01-16T00:44:03.294Z CNTRLR [Node 042] The node is alive.
2023-01-16T00:44:03.295Z CNTRLR [Node 042] The node is ready to be used
2023-01-16T00:44:03.302Z CNTRLR « [Node 042] ping successful
2023-01-16T00:44:03.448Z CNTRLR [Node 043] The node is alive.
2023-01-16T00:44:03.449Z CNTRLR [Node 043] The node is ready to be used
2023-01-16T00:44:03.474Z CNTRLR « [Node 043] ping successful
2023-01-16T00:44:04.008Z CNTRLR [Node 046] The node is alive.
2023-01-16T00:44:04.010Z CNTRLR [Node 046] The node is ready to be used
2023-01-16T00:44:04.015Z CNTRLR « [Node 046] ping successful
2023-01-16T00:44:04.135Z CNTRLR [Node 047] The node is alive.
2023-01-16T00:44:04.136Z CNTRLR [Node 047] The node is ready to be used
2023-01-16T00:44:04.143Z CNTRLR « [Node 047] ping successful
2023-01-16T00:44:04.581Z CNTRLR [Node 048] The node is alive.
2023-01-16T00:44:04.583Z CNTRLR [Node 048] The node is ready to be used
2023-01-16T00:44:04.588Z CNTRLR « [Node 048] ping successful
2023-01-16T00:44:04.822Z CNTRLR [Node 049] The node is alive.
2023-01-16T00:44:04.824Z CNTRLR [Node 049] The node is ready to be used
2023-01-16T00:44:04.829Z CNTRLR « [Node 049] ping successful
2023-01-16T00:44:05.283Z CNTRLR [Node 050] The node is alive.
2023-01-16T00:44:05.284Z CNTRLR [Node 050] The node is ready to be used
2023-01-16T00:44:05.290Z CNTRLR « [Node 050] ping successful
2023-01-16T00:44:05.565Z CNTRLR [Node 051] The node is alive.
2023-01-16T00:44:05.566Z CNTRLR [Node 051] The node is ready to be used
2023-01-16T00:44:05.571Z CNTRLR « [Node 051] ping successful
2023-01-16T00:44:05.614Z CNTRLR [Node 052] The node is alive.
2023-01-16T00:44:05.615Z CNTRLR [Node 052] The node is ready to be used
2023-01-16T00:44:05.621Z CNTRLR « [Node 052] ping successful
2023-01-16T00:44:05.798Z CNTRLR [Node 053] The node is alive.
2023-01-16T00:44:05.800Z CNTRLR [Node 053] The node is ready to be used
2023-01-16T00:44:05.800Z CNTRLR All nodes are ready to be used
2023-01-16T00:44:05.805Z CNTRLR « [Node 053] ping successful
2023-01-16T00:44:13.030Z CNTRLR [Node 024] treating BasicCC::Set as a report
2023-01-16T00:44:57.698Z CNTRLR « [Node 056] received wakeup notification
2023-01-16T00:44:57.703Z CNTRLR [Node 056] The node is now awake.
2023-01-16T00:44:58.708Z CNTRLR » [Node 056] Sending node back to sleep...
2023-01-16T00:44:58.820Z CNTRLR [Node 056] The node is now asleep.
2023-01-16T00:48:08.138Z CNTRLR [Node 056] treating BasicCC::Set as a report
2023-01-16T00:48:38.047Z CNTRLR [Node 056] treating BasicCC::Set as a report
2023-01-16T00:49:10.146Z CNTRLR [Node 056] treating BasicCC::Set as a report
2023-01-16T00:49:40.156Z CNTRLR [Node 056] treating BasicCC::Set as a report
2023-01-16T00:49:48.212Z CNTRLR [Node 013] [Notification]
type: Access Control
event: Manual lock operation
2023-01-16T00:51:25.974Z CNTRLR [Node 013] [Notification]
type: Access Control
event: Manual unlock operation
2023-01-16T00:51:33.144Z CNTRLR [Node 013] [Notification]
type: Access Control
event: Manual lock operation
2023-01-16T00:52:26.370Z CNTRLR [Node 013] [Notification]
type: Access Control
event: Manual unlock operation
2023-01-16T00:52:34.475Z CNTRLR [Node 013] [Notification]
type: Access Control
event: Manual lock operation
2023-01-16T00:53:36.719Z CNTRLR [Node 056] treating BasicCC::Set as a report
2023-01-16T00:54:07.076Z CNTRLR [Node 056] treating BasicCC::Set as a report
2023-01-16T01:04:03.200Z CNTRLR [Node 056] treating BasicCC::Set as a report
2023-01-16T01:04:45.610Z CNTRLR [Node 056] treating BasicCC::Set as a report
2023-01-16T01:08:29.187Z CNTRLR « [Node 054] received wakeup notification
2023-01-16T01:08:29.190Z CNTRLR [Node 054] The node is now awake.
2023-01-16T01:08:30.193Z CNTRLR » [Node 054] Sending node back to sleep...
2023-01-16T01:08:30.228Z CNTRLR [Node 054] The node is now asleep.
2023-01-16T01:17:40.075Z CNTRLR [Node 056] treating BasicCC::Set as a report
If I tried an uninstall/reinstall of Z-Wave JS, would that wipe out everything on my Z-stick? Just wondering if its something I should try.
I believe it is the official Z-Wave JS, version 0.1.74 (see screenshot). Note the red dot on the top right, and that it’s stopped.
So… to answer your question, I think I only have one, the official.
If it’s actually stopped, well then nothing’s going to work. What happens when you start it? Any errors in the logs?
1 Like
When I click start, nothing happens.
Looking over the logs, I notice the date looks like it’s 1 day ahead, at “2023-01-16” (today is the 15th). Maybe I’m reading that wrong.
Does the z-wave network follow the stick or the Z-Wave JS server? If it’s all on the stick, then wouldn’t it make sense to just uninstall and reinstall Z-Wave JS?
The driver logs are in UTC.
Yes, the network is stored on the stick, however the results of the interviews are stored as cache files. If you uninstall, you’ll have to make sure everything re-interviews after re-installing. Battery devices require manual wake ups.
There should be some errors in the logs. Not sure what a re-install is going to accomplish, but I guess if that’s the last resort…
Be sure to backup your network keys. If anything is included securely and you lose the keys, you’ll be required to re-include those.
1 Like
I did the uninstall / reinstall, but it’s still “stopped” with a red dot.
Updated logs:
firmware versions: 5.54
hardware version: 255
2023-01-16T02:05:22.115Z CNTRLR » [Node 048] querying CC versions...
2023-01-16T02:05:22.115Z CNTRLR » [Node 048] querying the CC version for Basic...
2023-01-16T02:05:22.458Z CNTRLR « [Node 049] received response for node versions:
library type: Enhanced Slave (0x03)
protocol version: 6.4
firmware versions: 5.54
hardware version: 255
2023-01-16T02:05:22.459Z CNTRLR » [Node 049] querying CC versions...
2023-01-16T02:05:22.460Z CNTRLR » [Node 049] querying the CC version for Basic...
2023-01-16T02:05:23.752Z CNTRLR [Node 050] Timed out while waiting for a response from the node (ZW0201)
2023-01-16T02:05:23.758Z CNTRLR [Node 050] Interview stage completed: CommandClasses
2023-01-16T02:05:23.759Z CNTRLR [Node 050] Interview stage completed: OverwriteConfig
2023-01-16T02:05:23.759Z CNTRLR [Node 050] Interview completed
2023-01-16T02:05:23.760Z CNTRLR [Node 050] The node is ready to be used
2023-01-16T02:05:23.763Z CNTRLR » [Node 050] Assigning SUC return route...
2023-01-16T02:05:24.051Z CNTRLR [Node 051] supports CC Z-Wave Plus Info (0x5e) in version 2
2023-01-16T02:05:24.057Z CNTRLR [Node 051] skipping query for CRC-16 Encapsulation (0x56) because max implem
ented version is 1
2023-01-16T02:05:24.057Z CNTRLR » [Node 051] querying the CC version for Manufacturer Specific...
2023-01-16T02:05:25.498Z CNTRLR [Node 052] supports CC Configuration (0x70) in version 1
2023-01-16T02:05:25.498Z CNTRLR » [Node 052] querying the CC version for Manufacturer Specific...
2023-01-16T02:05:25.641Z CNTRLR « [Node 053] received response for node versions:
library type: Enhanced Slave (0x03)
protocol version: 6.4
firmware versions: 5.54
hardware version: 255
2023-01-16T02:05:25.642Z CNTRLR » [Node 053] querying CC versions...
2023-01-16T02:05:25.642Z CNTRLR » [Node 053] querying the CC version for Basic...
2023-01-16T02:05:26.011Z CNTRLR [Node 008] supports CC Manufacturer Specific (0x72) in version 2
2023-01-16T02:05:26.015Z CNTRLR [Node 008] skipping query for Device Reset Locally (0x5a) because max implem
ented version is 1
2023-01-16T02:05:26.016Z CNTRLR » [Node 008] querying the CC version for Association...
2023-01-16T02:05:26.062Z CNTRLR [Node 014] supports CC Manufacturer Specific (0x72) in version 2
2023-01-16T02:05:26.067Z CNTRLR [Node 014] skipping query for Device Reset Locally (0x5a) because max implem
ented version is 1
2023-01-16T02:05:26.068Z CNTRLR » [Node 014] querying the CC version for Association...
2023-01-16T02:05:26.123Z CNTRLR [Node 015] supports CC Manufacturer Specific (0x72) in version 2
2023-01-16T02:05:26.129Z CNTRLR [Node 015] skipping query for Device Reset Locally (0x5a) because max implem
ented version is 1
2023-01-16T02:05:26.130Z CNTRLR » [Node 015] querying the CC version for Association...
2023-01-16T02:05:26.413Z CNTRLR [Node 016] supports CC Manufacturer Specific (0x72) in version 2
2023-01-16T02:05:26.414Z CNTRLR [Node 016] skipping query for Device Reset Locally (0x5a) because max implem
ented version is 1
2023-01-16T02:05:26.415Z CNTRLR » [Node 016] querying the CC version for Association...
2023-01-16T02:05:29.472Z CNTRLR « [Node 011] received response for manufacturer information:
manufacturer: Allegion (0x3b)
product type: 0x01
product id: 0x0469
2023-01-16T02:05:29.478Z CNTRLR [Node 011] Interviewing Version...
2023-01-16T02:05:29.478Z CNTRLR » [Node 011] querying the CC version for Version...
2023-01-16T02:05:29.593Z CNTRLR [Node 017] supports CC Manufacturer Specific (0x72) in version 2
2023-01-16T02:05:29.598Z CNTRLR [Node 017] skipping query for Device Reset Locally (0x5a) because max implem
ented version is 1
2023-01-16T02:05:29.599Z CNTRLR » [Node 017] querying the CC version for Association...
2023-01-16T02:05:29.653Z CNTRLR [Node 021] supports CC Manufacturer Specific (0x72) in version 2
2023-01-16T02:05:29.658Z CNTRLR [Node 021] skipping query for Device Reset Locally (0x5a) because max implem
ented version is 1
2023-01-16T02:05:29.659Z CNTRLR » [Node 021] querying the CC version for Association...
2023-01-16T02:05:29.705Z CNTRLR [Node 022] supports CC Manufacturer Specific (0x72) in version 2
2023-01-16T02:05:29.710Z CNTRLR [Node 022] skipping query for Device Reset Locally (0x5a) because max implem
ented version is 1
2023-01-16T02:05:29.711Z CNTRLR » [Node 022] querying the CC version for Association...
2023-01-16T02:05:29.756Z CNTRLR [Node 023] supports CC Association Group Information (0x59) in version 1
2023-01-16T02:05:29.761Z CNTRLR » [Node 023] querying the CC version for Manufacturer Specific...
2023-01-16T02:05:29.903Z CNTRLR [Node 024] supports CC Manufacturer Specific (0x72) in version 2
2023-01-16T02:05:29.904Z CNTRLR » [Node 024] querying the CC version for Association Group Information...
2023-01-16T02:05:32.907Z CNTRLR « [Node 013] received response for manufacturer information:
manufacturer: Allegion (0x3b)
product type: 0x01
product id: 0x0469
2023-01-16T02:05:32.913Z CNTRLR [Node 013] Interviewing Version...
2023-01-16T02:05:32.913Z CNTRLR » [Node 013] querying the CC version for Version...
2023-01-16T02:05:33.131Z CNTRLR [Node 030] supports CC Manufacturer Specific (0x72) in version 2
2023-01-16T02:05:33.136Z CNTRLR [Node 030] skipping query for Device Reset Locally (0x5a) because max implem
ented version is 1
2023-01-16T02:05:33.136Z CNTRLR » [Node 030] querying the CC version for Association...
2023-01-16T02:05:33.336Z CNTRLR [Node 031] supports CC Manufacturer Specific (0x72) in version 2
2023-01-16T02:05:33.340Z CNTRLR [Node 031] skipping query for Device Reset Locally (0x5a) because max implem
ented version is 1
2023-01-16T02:05:33.340Z CNTRLR » [Node 031] querying the CC version for Association...
2023-01-16T02:05:33.543Z CNTRLR [Node 032] supports CC Manufacturer Specific (0x72) in version 2
2023-01-16T02:05:33.549Z CNTRLR [Node 032] skipping query for Device Reset Locally (0x5a) because max implem
ented version is 1
2023-01-16T02:05:33.549Z CNTRLR » [Node 032] querying the CC version for Association...
2023-01-16T02:05:33.889Z CNTRLR [Node 034] supports CC Manufacturer Specific (0x72) in version 2
2023-01-16T02:05:33.895Z CNTRLR [Node 034] skipping query for Device Reset Locally (0x5a) because max implem
ented version is 1
2023-01-16T02:05:33.896Z CNTRLR » [Node 034] querying the CC version for Association...
2023-01-16T02:05:34.171Z CNTRLR [Node 035] supports CC Manufacturer Specific (0x72) in version 2
2023-01-16T02:05:34.176Z CNTRLR [Node 035] skipping query for Device Reset Locally (0x5a) because max implem
ented version is 1
2023-01-16T02:05:34.176Z CNTRLR » [Node 035] querying the CC version for Association...
2023-01-16T02:05:34.359Z CNTRLR [Node 036] supports CC Configuration (0x70) in version 1
2023-01-16T02:05:34.364Z CNTRLR » [Node 036] querying the CC version for Manufacturer Specific...
2023-01-16T02:05:35.292Z CNTRLR [Node 037] supports CC Manufacturer Specific (0x72) in version 2
2023-01-16T02:05:35.297Z CNTRLR [Node 037] skipping query for Device Reset Locally (0x5a) because max implem
ented version is 1
2023-01-16T02:05:35.298Z CNTRLR » [Node 037] querying the CC version for Association...
Sounds like you need to dig deeper in the Supervisor or HA logs then, there must be some indication as to why the add-on will not start.
1 Like
These logs are from the add-on? It looks like it’s running to me.
1 Like
Yeah… they are from the add-on. According to them it looks like it’s on. But, the red dot indicates it’s stopped.
Try refreshing the page. I wouldn’t worry about the red dot then. Look in the HA logs for zwave errors.
1 Like
HA logs show this:
Logger: homeassistant.components.zwave_js
Source: components/hassio/addon_manager.py:380
Integration: Z-Wave (documentation, issues)
First occurred: 18:15:11 (17 occurrences)
Last logged: 18:42:13
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-0658_0200-if00', 's0_legacy_key': '1DD4C0712A2A3DA3E244C0A929ECDA05', 's2_access_control_key': 'B4DF4E5A1F9EA15ABA0F50E49D6F6815', 's2_authenticated_key': '87B300246DE4BEB12AC839FFA1D591D9', 's2_unauthenticated_key': '453B1FD9D682C177ADAEFAEFC8156CF0'}
Is the problem that “unathenticated key”?
