This happens from time to time, but sometimes, Zwave gets really slow to respond. Almost infurating.
I try to reset all my switches and devices, but I find that some of them do not have a reset or airgap thing to reboot them.
So what I do , is just shut down the entire house, I pull most of the fuses and then turn it back on. That seems to fix the issue.
I would like to know how to in the future, find out what exact device is causing the issue. I have over 50+ Zwave devices, and I am sure some of them do not play well all the time. So, the reboot helps.
Ideas? or should I just every other month reboot the house..
P.s this was an issue since I had the C5 and then moved to a C8pro.
Please provide your hub model (C7, C8, etc.) and its platform version from Settings>Hub Details.
Check out the following post for help troubleshooting problems and gathering details that will help others to identify and solve the problem you are experiencing: ‼ READ FIRST - Before Posting in Get Help
You may have a hardwired Zwave device that gets "stuck", from the sounds of it.
That is assuming you have looked at logs and tried to figure out what the root cause is first, using the many methods you can find in this forum about diagnosing Zwave issues. The Zwave logs could show the network is being spammed by a device that is otherwise working, or the device may be going silent and not responding or repeating for other devices anymore. Lack of a Zwave log for a device when the issue is happening can be as telling as seeing spamming in the log from a working device.
If you think it is a bad device, you will need to try resetting each device separately to find it, which will be quick to get through the air-gappable ones first, but then you need to move to individual circuits for the others. When you find the specific circuit that fixes it, and if it has multiple non-airgapable devices on it, you would have no choice but to open those boxes and disconnect them one at a time to find the one with the issue. Hopefully you find the bad device among the air-gapable ones or on circuits with only one device before it gets to that.
I had a similar problem, it turned out to be an Eva Logix Zwave dimmer, two of them, actually. They would get stuck and just stop communicating, but a quick air-gap would fix them for awhile. Then my whole zwave network started going down regularly after a few months of resetting the switches to get just the switch working. I basically just assumed my network issues were from those switches, since I had needed to air-gap them in the past to keep them working individually, so I went ahead and replaced them, and I had no Zwave issues after that. I assume they stopped repeating when they locked up, and finally enough devices were routing through them to take down the network when they got stuck, or something like that.
I once had a Z-wave slowdown like that. Rebooting the hub would clear it up for a while. Eventually I realized that a box was leaning against a wall switch and flooding the mesh with commands.
Keep an eye on the logs and see if you are getting repeat events from a device that shouldn't be triggering at that time. It may just be a bad device and not user error like it was for me.
