Hi everyone. About 3 weeks ago, I began having issues with most of my z-wave devices in that they would take 20-30 seconds for them to respond. Prior to that, the devices would respond right away e.g. lights on or off, roller shades open and close, etc.
The C8 hub is in the same location as it has always been, though I did upgrade to 2.4.2.158 either a little before, or a little bit after (I think a little after hoping it would help).
I also added 3 Tappo matter outlets around the same time, but not sure how that would cause issues with my z-wave devices - or would it?
i unplugged the hub and let it sit for about 10 minutes, but no change in behavior.
So are those devices still working and just failing the repair, or have they stopped working?
Stop doing full mesh repairs, you will probably only make things worse at this point.
Regular C8 or C8-Pro? Are you running Zwave JS or legacy ZIP? (Zwave JS is normally only available on the Pro but can be forced on the C8 so I have to ask).
See below and provide the requested info and screenshots. Make sure you click Refresh Stats button and refresh before getting z-wave details screenshots.
Was this your first Matter device and you just enabled matter on the hub, or was it already enabled and you just added 3 new devices? Having Matter enabled consumes a bunch of extra resource on the hub, so it could possibly impact other services.
Hi and thanks for the response. The devices that fail to repair are still working, but they are taking 20-30 seconds - and sometimes more - to respond to commands whereas, prior, they were responding within a second or two.
The hub is a C8 and I have not configured Zwave JS.
The hub is powered by the power supply brick. I had previously added 3 Linkind Matter outlets while the 3 outlets added a few weeks ago are TP-Link Tapo.outlets
I'm not seeing any ghosts in the zwave details page and have attached a png
of the details page.
Also, how long was the hub running and did you refresh stats before getting the screenshot? Most devices do not have any stats. Hub needs to be running for 12-24 hrs.
Hi and thanks for the response. So, it appears that the zwave issues were due to a Hubitat update I made a few weeks ago. I just updated to 2.4.2.159 from 2.4.2.158 this morning and all the devices are back to responding within a second or two.
Not sure what caused the issue to begin with, but I'm happy that things are back to normal.
And, just to clarify, I had previously rebooted the hub a number of times as well as unplugging the hub for several minutes a few times as well.
Zero changes in .159 above with anything to do w/Z-Wave. Same w/158:
If there had been a general and significant Z-wave issue in .158 the noise here about it would have been deafening. You may be benefitting from "reboot short-term luck." I'd pay attention to @nclark if I were you:
I know I saw somewhere something about a fix for lag on legacy dashboards. So that’s the only chance a recent update fixed anything, was if the delay only happened with dashboard interactions.
