Not sure if it will matter, but let's enable logging and make sure activation optimization is disabled for both scenes...
Cool. Done 
Currently since reboot we have reaction from motion sensors. Alexa still says the room is offline if asked to change lights. But will give half hour to hour and see if motion continues to work as it usually does for a short while after reboot.
@gopher.ny Worked for around an hour on motion sensors but now stopped again 
No errors currently showing in logs, just doing nothing
My hub also started throwing the "com.hubitat.app.exception/LimitExceededException" error after the recent update the moved the Mode section to "Legacy" and added the new Mode app. The change literally broke everything in my house and rendered the mode changes useless.
After a fresh reboot on the hub, everything works for a short time then dies. I fixed it by rolling back to a version before the new Mode app was rolled out. Everything is now perfect.
As with all the problems that came from the new Scene/Group changes (Which also broke absolutely everything in my hub and created a situation where I had to build everything from scratch all over again) - I'd recommend you restore to a previous known-good version that's dated before the Mode changes and power cycle the device.
Don't update for a few major versions and plan to completely rebuild everything for your Modes from scratch in the new app once you do. That'll likely fix everything.
Good luck.
Edit: I rolled back to 2.3.2.141 and everything is smooth and fully operational if that helps. Anything beyond that completely trashes my Modes and starts throwing those same errors after a short period of time. The hub is completely unusable when this happens and nothing works.
Or, just thinking out loud, maybe a bug and will get resolved without you having to rebuild everything on future upgrades...
1 Like
Or, just thinking out loud, maybe a bug and will get resolved without you having to rebuild everything on future upgrades...
That's the hope. I mean you update and hope everything works, but if you're prepared to have to rebuild everything you can't really lose.
I waited for half a year for the scenes/groups issues to be corrected but ultimately the only thing I could do was rebuild everything. I updated and rolled back a half dozen times hoping the problems would be fixed.
Edit: Don't take this advice as a negative. It's the price we pay for new versions of apps and constant improvement on features. It just comes with the territory.
Is strange as I didn't do any updates before the problem incurred however I had a back local backup on 2.3.2.141 and having successfully rolled back to this. I still had to disable hive and echo speaks which is fine but fingers crossed everything else seems to be working and it's been a couple of hours now.
How long do I not update for though? Surely it should be better to keep updated
1 Like
You definitely should be able to update w/out things blowing up. By not updating you will primarily not have access to new app and driver features, and platform enhancements that should make your overall experience better. But there is much to be said for "if it ain't broke..." You might want to wait until the next hub update (usually 3-ish months between them) and try again then. In the meantime if things are stable and working for you, you're not really losing out on anything in terms of day-to-day use.
3 Likes
You're really asking a question that there is no answer to.
Most people that upgraded have absolutely no problems like you are seeing, so for them the answer to how long was immediately.
For individuals having one-off problems, the sheet woukd be not yet...
So there's no single answer to the how long question.
I would encourage you to work it through support, and if they find the root cause then they should be able to definitively tell you when they fix is implemented, if a fix is indeed necessary and it isn't some database corruption or other non-code issue..
4 Likes
If you have any battery operated end devices, try changing the batteries.
I recently had a bunch of problems in my home. I would see bulbs constantly jumping from repeater to repeater, Alexa saying "Sorry, I'm having trouble understanding right now......", devices dropping, and "null" devices showing up on the neighbor and routing tables.
I thought these issues were due to the update to the hub.
This turned out to be a low battery level in one of my Bosch Motion Detectors. Took a while to figure out, and got some help from another topic about Zigbee Device IDs changing (which I also witnessed on my hub).
Once I changed the batteries in all of my Bosch Motion Detectors, everything went back to normal.
I think it had something to do with the motion detector constantly trying to rejoin, but didn't have the power to stay joined. This caused havoc on the hub.
So, if you have any battery operated end devices, try changing the batteries.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
