Wish I never upgraded to the newest version .73 I was 100% good on .72 but then I did the update and having a lot of issues. Lights on motions aren’t working currently everything is so slow. Wasn’t an issue at all on .72 really hope they fix this soon. I understand it’s the holidays hopefully it get fixed within the next 2 weeks. lol I knew I shouldn’t done the update.
Just roll back. Use the Diagnostic Menu to pick the previous Platform. No waiting 
5 Likes
NO. You did an upgrade to Platform v2.4.173. You didn't need to do anything to your Zigbee or ZWave deviecs, right?? The same is true for going backwards. The Diagnostic Menu offers that choice.
2 Likes
Can you be more specific about your problem? What kinds of devices are they? Is it one specific protocol that is affected or everything? Any errors in Logs or concerning stats? The general hub troubleshooting steps here are good place to start:
The Diagnostic Tool can help you roll back, as mentioned above -- but if your problems don't go away, something else was wrong, and the update was just coincidental, so the above may help.
1 Like
I am using motion and lighting within Hubitat I use motion sensors to turn off and on lights with motion in rooms. With .72 the performance was fine everything was fast no issues at all. Once I updated to .73 sometimes lights never shut off sometimes lights never come on . It’s a train wreck.
No that is not the menu I'm referencing.
Settings: Diagnostic Tool. Enter the MAC address of your hub (found on the bottom), then Restore Previous Version. A list of Platform images on your hub will appear and you can pick the version you believe to be functional for you.
I agree that the current version is probably coincidental, but rolling back is so easy, it's going to tell you if your hunch is correct or not.
Just so I’m clear if I roll back to .72 with the tool i’m not going to have to repair zigbee or Zwave devices correct? It’s going to be like doing an update, but I’ll be just rolling back. Once it’s done, everything should be set correct ? I’m just trying to figure out what I’m getting myself into. I have over 130 devices and over 75 automations
Again, the roll back is virtually identical to performing an update.
When you've completed the rollback and concluded it is not the source of your problem, you can update yet again. If a rollback does improve your situation then you can remain on that version for days, weeks or months
7 Likes
Thank you !!
You should take your own advice from another post you made tonight:
2 Likes
It would be helpful for future readers if you clarified the full version number. Someone who stumbles upon this months if not years from now will not have any frame of reference.
There were only two very minor changes between these versions, There were no device driver changes, nor any rule or automation changes. I don't see how this update could have bombed out your hub like you are describing.
Changes from 2.4.3.172
App Updates
- SharpTools updated to minimize the amount of data the app subscribes to.
Bug Fixes
- Likely fix for Ecobee "Authentication failed" errors.
That said, you can roll back like others have indicated above to see if that fixes things. It will be interesting to see if that fixes things, or if you have a different issue.
6 Likes
This ^^^
Highly unlikely the update to 2.4.3.173 made any changes to your hub that messed things up...most likely the reboot that is a part of the platform update process surfaced some existing issues that were building/waiting to present.
4 Likes
I'm tempted to add "(user confused: correlation does not imply causation)" to the title of this thread.
4 Likes
I get the same thing after updating from time to time. I find that simply rebooting the hub will fix it. It was never so bad that I've had to roll back, but that's always an option.
I'll usually stick to a version for a while unless there are new features or updates to drivers I actually use.
Ok so I rebooted the hub twice didn’t fix anything then I shut down and waited 20 minutes still didn’t fix anything. This was all done over the course of several hours.
Today I went back to .172 and everything is 100% flawless. So it’s fixed admin can close this thread. Thanks to everyone that actually helped instead of passing judgment.
1 Like
