Been using HA on a rPi4b for years now and everything was working great. In the past 2-3 days, I have noticed my Wave not loading and Zigbee no longer seeing my Waxman LeakSmart valve. This essentially takes out all of my ‘in case of water, turn off main’ automations/protections.
The rPi4b hasn’t moved and nothing has been added. I have both sticks on USB2 extenders. I have tried turning the system off, disconnecting the sticks and reconnecting to no avail.
Log for a clean start shows:
Logger: homeassistant.config_entries
Source: config_entries.py:430
First occurred: 7:51:45 AM (1 occurrences)
Last logged: 7:51:45 AM
Config entry ‘Z-Wave JS’ for zwave_js integration not ready yet: None; Retrying in background
Logger: homeassistant.components.zwave_js
Source: components/hassio/addon_manager.py:380
Integration: Z-Wave (documentation, issues)
First occurred: 7:51:45 AM (5 occurrences)
Last logged: 7:53:22 AM
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’: ‘REDACTED’, ‘s2_access_control_key’: ‘REDACTED’, ‘s2_authenticated_key’: ‘REDACTED’, ‘s2_unauthenticated_key’: ‘REDACTED’}
Home Assistant 2023.8.4
Supervisor 2023.08.1
Operating System 10.5
Frontend 20230802.1 - latest
/dev/serial/by-id/usb-Nabu_Casa_SkyConnect_v1.0_70dd299a9014ed11a060bc8be054580b-if00-port0
I don’t see my zwave stick in Hardware…
First they may nor may not be related - pick one to work on for now. Zwave or Zigbee. It will get too confusing to try to fix both at the same time in this thread.
Your Zwave issue looks like a configuration issue. Maybe a busted file or something - but it cant start because its saying it has invalid settings - you may also want to redact your ZWave keys from that error message.
The Zigbee appears unrelated. Maybe a signal issue because the controller is talking to your install. So which one are you picking first?? (I’d open a second question for the second item and post an edit in your first thread on which you want to tackle here)
I enabled logging in Zwave. Tried reloading. Got this:
Logger: homeassistant.components.zwave_js
Source: components/hassio/addon_manager.py:380
Integration: Z-Wave (documentation, issues)
First occurred: 7:51:45 AM (39 occurrences)
Last logged: 8:36:24 AM
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’: ‘REDACTED’, ‘s2_access_control_key’: ‘REDACTED’, ‘s2_authenticated_key’: ‘REDACTED’, ‘s2_unauthenticated_key’: ‘REDACTED’}
The maybe you have a different issue cause this one is new for sure, if, for you, it happens every 3 months then my assumption is that the way you say it, it always has been like that.
To me (and I think quite some others as well) that is not the case, my Zwave network is very stable and has been like that for a very long time, until some recent update caused issues.
I’m unsure if this is related, but I also had a super stable zwave js network until recently (last two weeks or so).
All devices (59) are reporting back temps and wattage etc and are alive. But operating switches / relays etc has suddenly broken.
Switching in the UI - nothing happens
Switching them manually - not reported back to HA.
I saw this happen again the other night late. Left it to the morning and i guess zwavejs has restarted (or HA) as the last update time for every device was now recent and the same - and everything was working again.
Its just happened again tonight. I noticed because my automations to turn off pond pumps hadnt run and I was outside after sunset and they were still on.
tried switching them manually and they appear to switch in the UI but nothing happens.
input devices like zwave motion sensors are reporting back and controlling non zwave lights etc just fine with automations.
Its anything with a switch/relay suddenly
Very strange. Never happened before and has now happened 3 times in the last 2 weeks.
Not yet sure why or best how to mitigate or resolve.
HA restart doesnt fix it
zwave add on restart seems to resolve it a couple of minutes after restart when everything is re-pinged and it restarts.
Before zwave add-on restart, add-on cpu usage is reported as under 1%
After zwave add-on restart, add-on cpu usage is 24% and drops back to <1%
I have the logs set to verbose when it happens and
I see some things like this:
2023-09-07T20:21:20.405Z DRIVER all queues busy
2023-09-07T20:21:20.409Z DRIVER » [REQ] [GetBackgroundRSSI]
2023-09-07T20:21:20.416Z DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -72 dBm
channel 1: -75 dBm
2023-09-07T20:21:20.420Z DRIVER all queues idle
I understand that this does not deal with the cause, but this is what I have done:
I connected the power supply of the Yellow Box to a Kasa plug. This allows me, at home or away, to perform a power cycle of the Yellow Box using the Kasa App on my Iphone.
Of course I would like to resolve the issue but in my case it does not happen more than 2 or 3 times a year.
I have the exact same problem. All devices report temperatures, power consumption (watts), and other data normally, and they appear to be online. However, the switches and relays aren’t working. This issue has been happening for about a year, but only occasionally. In those cases, restarting Home Assistant has resolved it. Now, possibly since the latest Z-Wave JS UI update, the problem occurs randomly every 15 minutes or every couple of hours.
Has anyone managed to fix this? I’m using the Zoom 800 as the Z-Wave USB stick.
Very strangely, this hasn’t been an issue for many months, network with 66 nodes really stable… Now in the last few days I have had it happen twice.
No recent z-wave updates, and I’ve not had chance to check logs exactly when it’s started again. HA Restart seems to resolve it
I just restarted everything and pulled the z wave stick (Aeotec 500 in HA Yellow) and reinserted it.
If it happens again I’ll check what exactly solves it, (controller soft reset command in jsui didn’t) & revert HA version once I see which update coincides with the logs.