Hub Model: Hubitat Elevation C-7 Current Platform Version Attempted: 2.5.0.143 Prior Stability: Hub has been completely stable with zero issues prior to attempting this update.
The Problem: My C-7 is currently stuck on the startup screen showing:
"Initializing Hub: 30% - updating app definitions to version 2.5.0.143"
It remains on this screen indefinitely and will not complete the boot process.
Diagnostic Tool & Troubleshooting Status:
Diagnostic Tool Works Perfectly: I have no issues accessing the Diagnostic Tool (:8081). The hardware seems completely responsive here.
Successful Rollback / Restore: From the Diagnostic Tool, I can successfully restore a previous platform version or an older backup without any errors. The hub will then boot up normally and work perfectly.
The Update Loop: Almost immediately after the successful rollback and boot, the hub automatically triggers the platform update sequence again. As soon as it downloads and attempts to initialize the update, it goes right back to the frozen 30% screen.
Hard/Soft Reboots: Attempted both; neither clears the 30% freeze once the update loop starts.
Questions for the Community:
Has anyone else run into a database/app definition migration freeze specifically on 2.5.0.143 with a C-7?
Since my Diagnostic Tool is fully functional, is there a specific command, hidden endpoint, or sequence I can use right after a successful restore to block or pause the automatic update download?
Could a specific heavy community app or custom driver be causing the database conversion to lock up at 30%? (If so, what's the best way to safely strip it during my brief window of uptime after a restore?)
Okay, I tried to go back to a prior version, and now it's stuck on 25% on the lower version now as well. This is behaving differently, and I'm not sure what to do.
Just wondering how long indefinitely was, as I’ve been in that updating process for like 45 minutes before, restoring backups to a different platform level. Just checking that you didn’t give up after 20 minutes or something. Granted, I have a lot of apps and devices that get updated, so that adds to the app and device upgrade/downgrade time.
I was able to revert to a prior version (2.4.4.156) and get through to the “Get Started” screen (http://192.168.50.168/getstarted). However, because I am now on lower version, the system forces me into a hub firmware update wit the following message…
”Update hub firmware
Your hub will now update to the latest firmware to ensure you have the latest apps, drivers, and features.
This may take several minutes, and the LED light on the hub will change colors and turn on/off while hub reboots.
Do not unplug your hub during this process.”
At that point, my only options are “Update Now”, “Start Over”.or “Restore from local or cloud backup?“ All these options lead back to the same point where I end up stuck again on the Initializing Hub screen.
So right now, I cannot get past the forced firmware update/restore loop. And and stuck with a dump house with non of my automations and smart triggers working. Very frustrated.
After you’ve restored the previous platform and sucessfully boot, download a local backup. Shut down hub and unplug for 1 minute and power back up. Once back up restore local backup (this will ensure a clean database). Once that is done go ahead and upgrade to the latest platform and see if it finally updates.
That makes it sound like you did try restoring a a backup, instead of updating, as you imply you tried all the options, saying that all lead to the same point… So you did restore a backup and you are still stuck?
Just curious as I recently had an issue where all of my recent backups were corrupted and restoring them caused the same issues with the UI spinning trying to load, then the UI locking up, and then an automatic hub reboot. Hopefully you are not in that situation.
In my case I ran with low memory warning for weeks, and all the backups made during that time were useless. A local backup still hanging around from February was all that would restore and work.
Yes. I was running in circles for a bit… however I got it back to a stable point and I’m working again! Currently on platform version 2.4.4.156 though.
To get there, I booted into safe mode and restored from a backup that I knew was 100% functional. I had actually attempted this process a few times before, but the only difference this time that I recognize, was that I used an incognito browser session and validated that my cache was fully cleared before proceeding that last time.
The initialization process took a long time (about 1hr), but it eventually completed successfully.
At this point, I am not going to attempt the update again till we are past version 2.5.0.143.
Please forgive the delayed update. I found a fix and wanted to report back with the exact steps that finally broke the loop on my C-7, just in case anyone else hits this same wall.
I tried the new platform version as suggested, but it immediately triggered the exact same 30% initialization freeze. Here is the specific sequence that finally got me sorted out:
Booted into Safe Mode: I used the Diagnostic Tool to boot the hub into Safe Mode so no apps or drivers were actively running.
Restored Backup First: While in Safe Mode, I restored my working backup while keeping the current platform version.
Rebuilt the Database: Immediately after the restore, I ran a database rebuild to clean up and commit the data structure.
(Note: It’s highly possible that just running the database rebuild alone while in Safe Mode might have fixed it, but I didn't think to try that option by itself until after I had already kicked off the restore!)
Once I exited Safe Mode and did a standard reboot, the hub started right back up with zero issues. The runaway initialization screen is completely gone, and everything is perfectly stable now (until the next update I guess).
Give 2.5.0.153 a try.