The only thing I’ve seen identified so far are the Xiaomi community drivers. I haven’t seen anything else mentioned (and I have probably been on here way too much this past week).
1 Like
That is interessting as I have a lot of Xiaomi devices. Do you know if there is a fix?
We have a new beta version that trims states and events on startup, among other things. One of the common slowdown causes of general slowdown is a large number of either stored in the database, so there's a good chance this new beta will help once it becomes available. Right now, it is at a point of getting user feedback, so it shouldn't be too long.
5 Likes
Thanks for the feedback. I'll hangon until the new version is released. What version number should I be looking out for?
Anything newer than 2.2.3.119. 
Not trying to be a smart arse - the final number isn't set yet as it gets revved up if there are issues found in testing (hopefully not ).
Reporting back... my C5 hub has been running fine since I (re)upgraded 3 days ago.. Has now been up longer than the first time I upgraded so all good so far.
Nothing really changed other than I updated the Unofficial Ring app to the latest version and removed Mode Manager app which I am not currently using. Also rebooted after making those changes. I don't think those apps really had any effect on the issue way or the other... but the Ring app is a custom app.
My hub was more than 5 times slower on 2.2.3 compared to 2.2.2. I left it overnight for the maintenance to run (and trim the events from the DB) which trimmed the backup from 6.5MB to 1.2MB. It was faster after the maintenance had run, but it was still 3 times slower than on 2.2.2. I've rolled back to 2.2.2.
This is on a C4 with zigbee and Z-wave disabled and all apps and devices disabled except for the hub watchdog. The only (now disabled) devices on this hub are devices from remote hubs coming in via HubConnect. Now that I have rolled back to 2.2.2 I have enabled all apps and devices again though which didn't affect the responsiveness of the hub (based on watchdog measurements of virtual switch). Zigbee and Z-wave radios are permanently disabled on this hub and the stick physically removed.
There is a new version of 2.2.3 out today. I have tried to install it as a test to see if the unresponsive hub issues have been resolved.
It has been stuck "Initializing Hub: 15%" for half an hour now so doesn't appear to be a great success unfortunately.
Which hub do you have? C3, C4, C5, C7?
Installed 2.2.3.132 yesterday and my C-5 hub stuck at 'initialising 15%' for a long time, was just starting to worry when it sprung back to life and completed fine.
I updated 2 - C4's and 2 - C5's to "2.2.3.132" and all is working well for me.
My main hub C4 did seem to take a little longer to start up at first (it has the most devices) but now reboots fairly quickly again. Could just be my imagination though.
My C4 is stuck at 15% too. I powered it off and on and I'm back at 15% again. Been about 15 minutes but I'll continue to wait after seeing note from @plumsden
There were some database updates in 2.2.3.. If you have a particularly large database, this process may take longer than usual.
2 Likes
Sure enough, the hub booted just fine. About 20 minutes I'd guess. Thanks all!
4 Likes
The latest 2.2.3 does a big one-time cleanup on startup. It might take a while depending on how many devices there are and how much event/state history is around at the time of upgrade. Give it time to complete, it's not really stuck.
3 Likes
Need a better progress bar then. 
"Pruning xxx of yyy records"
Or, we can just all be patient.
2 Likes
Ok, so i need to be a bit more patient! Install finished and hub looks to be running well.
Thanks guys for sorting this out
2 Likes
I updated my C-5. It was "stuck" on 15% for quite a while, but I was patient and let it finish. After the reboot, a system message said that the z-wave radio was disabled. I have a rule that periodically turns the z-wave radio off and then back on again. I ran that rule and there was no change. I waited a little while, then rebooted. The radio came back on. I ran a z-wave repair and it completed with no problems. All seems to be OK now. 
@bcopeland apparently not! looks like 37min is what it needed... all good so far - it's on at least!
1 Like
