.174 was bad, but .183 is much worse?


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


I noticed slow performance with my automations after .174 and after a few days of those slowing down I made a huge mistake and updated the hub to the latest .183. 76 Zigbee devices no longer connect, 20 or so do sometimes. How can I roll back to whatever came before .174 if my cloud backups only go back to .174? Can I restore the .174 backup onto an older version and recover? C8Pro

Use the Hub Diagnostic Tool to restore previous version.

Hubitat is awesome

Well I restored an older version, and a locally saved backup (as the cloud back up doesn’t go back very far) and my network is still trash.

It would be unusual for an update to have this type of severe effect. I also think it would be very unusual to have an update slow down a C8Pro.

I think you likely have a runaway device, or automation. I would start by looking at your Logs, and in particular seeing if you have anything in Device Stats or App Stats taking up a lot of hub time in general and/or a lot of time compared to other devices.

You can also look in Settings tab, Zigbee Details, and see if any device is reporting a lot of Messages (sort the right column) compared to other devices. Z-wave also has something similar, it would be worth checking both.

There were a series of Z-wave Jasco/GE switches that would freak out and flood the Z-wave network and cause symptoms like this. Other devices seem to act weird with low battery and spam the network. I suspect you have something like this happening...

Hub logs also are very helpful to dig through and see if there is any sign of a spammy or overly active app or device.

You should include some screenshots of the Device and App stats pages, and Logs, otherwise we are all guessing as to what is going on. It doesn't seem to be the update if you rolled back and that didn't fix it. I didn't think rolling back would when I read your post the other day, but glad you did to eliminate that possibility.