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”?
Guess not… deleted that with no effect
Perhaps a bug, you might want to create an issue. The options look correct to me, so it could just be a misleading error message with some other underlying issue.
Or you could take this moment to switch to Z-Wave JS UI. The integration tries to be smart and configure and manage the core add-on. If you switch to Z-Wave JS UI you don’t need to worry about that.
1 Like
Is the Z-Wave JS UI considered “best practice”? If so, I will probably take the time to do that.
It gives you the most options and flexibility, many users prefer it. The main benefit in my eye is a much better troubleshooting experience. The Z-Wave JS add-on really falls flat when it comes to that. It is still the “preferred” choice by the HA org of course, as they maintain it and it provides the managed installation (which is giving you headaches ATM).
If you follow the instructions, you can just swap it in and HA won’t notice the difference.
1 Like
Well… I tried to install the JS UI and it also wouldn’t start. So, I went to my other add-ons, like Samba Share and File Editor, and they also show the same behavior - red dot but logs are okay. I tried to launch the File Editor and it says “Add-on is not running. Please start it first”. Seems like it’s a wider issue than just Z-wave. Not sure where to go from here. Any ideas?
Well, apparently you do have bigger problems, those which are beyond my abilities (I guess ignoring the red dot was not the right answer, but in the past it was inaccurate due to bugs, probably fixed…).
1 Like
That fixed it.
To be clear, the fix was to navigate to System–>Hardware–>Overflow dots (3 on top right)–>Reboot System. And… this is not the same as rebooting HA. I’d already tried that several times.