C8 kept up on latest firmware, version 2.4.3.131, with quite a few Z-Wave and Zigbee devices. Operation is 100% solid until I do an update or there is a power outage, then I'll have 20 or so devices that Device Activity Check reports out of touch. Device Activity Check is using a 2 day window.
So 2 days since the disturbance, and it hasn't recovered.
This has happened the last half dozen updates or power losses.
Repair and wait a day doesn't help.
Restart hub doesn't help.
Refresh on devices that support it doesn't help.
It isn't just battery devices, although most of them tend to be Zooz.
No ghost nodes.
Refresh from Z-Wave details doesn't help.
Applying moisture to water sensors or removing/replacing batteries or clicking the sensor button 4 times to wake the sensor up all "fix" the problem. Logs show the devices are reporting at 12 hour intervals for example after doing this.
Any suggestions?
And ChatGPT suggests a work-around of restoring a recent backup to fix the Z-Wave network. Should I believe it? It says backups didn't use to include the network but on the C8 they do.
I left that out - it is on a UPS but has died a couple times before I could do a shutdown. I've got a bigger UPS on its way
Is the Reboot / Rebuild database different than me doing a Z-Wave / Rebuild Network? I've tried that on two of the instances and it didn't seem to help.
And great suggestion I didn't realize is an option, I'll try next time. Thanks for the quick response.
Just as a side note if you have the capability with your UPS.
My PC is on the same UPS as my hub.
I have my PC do a shutdown based on the UPS software function of time/battery remaining.
My hub pings my PC every 5 minutes and when it sees it has gone off line, aka shutdown, I tell the hub to do a shutdown as well.
If your UPS doesn't have the software ability there is an app in HPM called Power Outage Manager. If you have a device that runs off main or battery power and indicates the differ ence n Hubitat you can use that device as a trigger and use the app to shut down your hub after an amount of time you set. I use a Ring Range Extender.
Great suggestions. That UPS doesn't have anything that does a graceful shutdown, but I'll have to look at that Power Outage Manager. Or a big post-it somewhere that that says "Shut down the Hubitat!"
The Reboot-Rebuild option is not related to the Z-wave rebuild Network option.
You should go ahead and do the Reboot-Rebuild now, even if you aren't currently having any problems. It will not cause any new issues and it will help you avoid further issues, if database corruption is one of the roots of your problems.
Great, thanks. I'll do that in a couple days when the new UPS arrives. You have me wondering if I might have corrupted something when I took steps to get rid of a couple ghost nodes. I'm not sure of the timing for when this started happening, but it might be related.
I was pretty excited about this, but I did an update, and restart last night with the Rebuild Network checked and the problem persists. I have 10 devices that should have reported in by now.
Another tidbit to add to the mix is that I have a Konnected alarm panel virtual device that uses a custom driver to talk to the Konnected panel over TCP/IP. I notice although the panel itself is talking fine to the Hubitat by updating its up-time, none of its child devices (motion, contact, etc) are updating anymore.
So the virtual Konnected devices are having a problem similar to the Z-Wave devices. Can the custom device be interfering with the Z-Wave devices? It seems like an odd coincidence that the Z-Wave and TCP/IP devices would suddenly both lose touch.
I notice although the Z-Wave devices stopped sending battery heartbeats, they do send a change of state like moisture/dry so that is weird that they obviously can talk to the hub OK.
I read the thread, and I didn't see any mention of doing a controlled shutdown, unplug hub for 30 seconds, and replug hub. I might have missed it. It's usually something you try.
Thanks for the taking the time. You're right. I did a controlled shutdown, unplug for 30 seconds, and replug earlier tonight. We'll find out tomorrow what the sensors think of this.
I am also having the same problem. Lost power on the hubitat the other day, and although i can access the devices in the dashboard, i can't make changes in the dashboard (ie: can't adjust thermostats). But if i make a change on the physical thermostat itself, the hubitat sees the change.
I have repaired the database and rebuilt the zwave network - no dice.
I'm doing a restore as we speak, to see if that brings the devices back to talking. I'm pretty dependent on the Hubitat these days, so this would at least be a stop-gap measure until I find a real solution.
Even the restore left me with a bunch of devices not checking in. I ran around and triggered them, and that worked. I've got the bigger UPS on it now and I just won't do updates very often and I'll see how it does. Maybe it will fix itself
I was thinking of using this as an excuse to get a C8 Pro, and moving things to it a few at a time to make sure that gets me away from the problem. But, I'm not quite at that point yet.
I took your advice and rolled back a version to 2.4.2.138 (thankfully still had the backup). And i created a new dashboard. That combo of steps fixed it for me.
I also would like to be 'forced' t upgrade, but that day is not today
For the Konnected problem, not my Hubitat problem - Nate at Konnected put out a new version today that fixed it. It you used HPM, you can use it for the update. Nice they fixed it so quickly.
