Did you figure out what the cause was?
I’m finding z-wave has become pretty slow in the last 3-4 weeks for me.
Will collect some more info and read thru suggestions above. Thanks
You’ll need logs.
https://zwave-js.github.io/node-zwave-js/#/troubleshooting/index?id=rule-1-use-the-driver-log-luke
Just to add some wight to this topic. I have the same issue since some weeks.
It seems I have more background noise (-80 dBm) but the question is why. Could this be introduced by software?
Either it is a bug or zwave ist just a bad/sensitive protocol.
I simply don’t have these issues with zigbee.
Noise is generated by physical things, not digital things.
Yes but if the software is sending gibberish it would also count as background noise, right?
No it would not.
Why not? If a device screams some values, what is the difference?
For me this seems to have resolved with supervisor upgrade 2022.06 with HA 2022.07.0 and reboot of the host.
Still have a separate issue that HA takes 10+ seconds to notice the change in state of a z-wave device outside of HA. Will investigate more. Thanks
That would be considered congestion, not noise. “Noise” is radio interference on the same spectrum used by Z-Wave, causing communication to fail. There is generally less radio noise at Z-Wave’s lower 860-925MHz frequencies than there is at Zigbee’s 2.4GHz (shared by WiFi, Bluetooth, microwaves, etc.)
1 Like
Thais for making that clear.
I was experiencing the exact same issue now on 2022.11.1 running z-wave js 0.1.74 - after migrating approx 30 zwave devices from my Fibaro HC2 yesterday since this morning all z-wave device had a 1-2 sec delay in reacting and 5-10 sec delay to update the status on the UI after changing the status…
…tried healing and a few other things - then it turned out that the Aetoec stick was constantly in discovery mode looking for new devices // highlighted in integration → zwave js - turned it off there and everything was fine again.
2 Likes
My saviour!
I was going nuts, then finaly i found this. Turned it of like 10 minutes ago and it seems like it solved all my issues,
My z-wave was acting just like yours, or even worse.
Bluetooth became unavailable. (onboard bluetooth)
My zigbee2mqtt behaved somewhat like my z-wave js.
Just want to add that the switch to turn ofauto discovery is under integration → zwave js → System options for z wave.
This? Doubtful.
Well it seems it fixed it for me…
But now when you say it like that im not so sure anymore.
Was not The only thing i tried. Need to back track my movement.
Also see If my issues return.
Edit: What i can recall what I also did (except alot of reboot) was reinterviewing devices and a heal network. Did not work.
I did a system reboot after the changes above and that might have been the first after I did the heal network.
I’m using Z-Wave JS UI, an aeotec gen 5 stick and Generic x86-64 installation.
I have turned that switch back on and my system is running fine so if it not affected something “behind the scene” I just had dumb luck that i got it working.
Still, 2022.11.1 running z-wave js 0.1.74 has this issue in some cases and congestion fits my experience
Maybe it helps someone out there.
Healing can take a Loooong time.
That option I posted as a screenshot above is not auto-discovery as was mentioned and shouldn’t as someone else stated be responsible for anything like "Aetoec stick was constantly in discovery mode looking for new devices "
Found this thread because of the same issue after adding a new device. Come to find out my ZWaveJS was still searching for devices in the background. Turned it off by clicking Configure on the integration and saw it was still searching in there. That fixed the speed of my devices. thanks!