I've tried to apply this update a couple times now. My Hub downloads and extracts the update like normal. Then it says rebooting. Shortly afterwards it goes back to the home screen with the update still available. What should I do?
Have you tried reloading the page?
I've rebooted a couple times in a different ways. Same problem occurs. My hub is also locking up a lot today. I can't figure out what's causing it. Would appreciate some help there as well. I've checked the device and app logs and nothing stands out more than it used to.
What version is the diagnostic tool showing? From your screenshot it's booting 2.2.9.134.
Diagnostic shows .134 also
Try downloading the update using the diagnostic tool.
1 Like
This could be symptomatic of database corruption. Have you considered performing a soft reset?
2 Likes
Update through the diagnostic tool didn't work, sadly.
If a Soft Reset means I have to rebuild all the rules and automations, I just don't have time for that right now. That would take me many days.
A soft reset does not mean you have to rebuild any rules, nor do you have to re-pair any devices. It is a very simple process as outlined in the official Soft Reset documentation that @aaiyar linked above.
2 Likes
Could you please check if 140 is available in Diagnostic tool's Restore previous version selection? If yes, select it there and it should reboot with 140.
4 Likes
Well, I'll give it a few more minutes... but after doing that, the hub is now refusing to connect both the standard interface and the diagnostic tool.
EDIT: I spoke too soon. Dunno why that took longer than normal, but it came up right after I posted. Running .140 now. Thanks.
2 Likes
There was a handful of similar reports, but I couldn't reproduce the behavior myself. Adding some extra logging to 141 iteration to get to the root of the issue.
1 Like
I read the linked doc a couple times to make sure I didn't miss anything. It mostly just outlines the process of how to do it. It doesn't really say what it does outside of the screenshot of the warning from the hub. What I got from that was that after a soft reset, I'd still have all my devices. It doesn't say anything about apps or rules.
There are times when I want to tinker with smart home stuff and then other times I just need it to work. This happens to be one of those latter times. I just can't spend a whole lot of time on it right now. But I do very much appreciate the help! If after a Soft Reset, my hub will be back to working order with everything loaded, then I'll go ahead and do it.
2 Likes
FWIW (or for future reference), rules and other apps are in the hub's database. So a Soft Reset followed by "Restoring a Previous Database" (outlined in the link above) restores everything - devices & apps.
2 Likes
Perhaps the confusion is that there are multiple databases. There is one database (aka “Hub Database”) that is backed up and restored by the Settings > Backup and Restore page. A Soft Reset wipes out this database on the hub. The process of making a backup of the Hub Database writes the SQL database record by record, which sanitizes the database and, many times, can clean up a corrupted database so that, when it is restored, the Database will not be corrupted (in most cases, and also will have all necessary records). If the Database is badly corrupted, you may have to go further back in time to find a good backup to restore.
There is also a “database” in the Z-Wave radio and one in the Zigbee Radio. When devices are paired, they are entered into the radio databases and into the Hub’s Database, which contains additional information such as the driver and device name, etc. A Soft Reset does not affect the Z-Wave radio’s database or the Zigbee radio’s database.
When the Z-Wave radio’s database gets corrupted, “ghost” devices appear that cause disorder. Supposedly, the Z-Wave radio’s recent update to 7.15 will lessen that corruption.
AFAIK, the only way to backup/restore the Z-Wave radio’s database is with the Hub Protect subscription service.
4 Likes
I have had this problem a lot over the last week with all the updates. If I hard power cycle the Hubitat and then redownload the update, everything seems to work.
Not advisable, might corrupt your database. Better to go to your.hub.ip:8081 and revert to prior version. If 2.2.9.140 is shown, boot to that. Otherwise, download that version or reboot from there.
1 Like
@gopher.ny
I had the same issue tonight going from 141 to 142 on my C4 hub which I saw 141 update should of helped with.
When I went to Check for Updates, it'll say it's extracting the update then reboot but doesn't update to new version. If I do Check for Updates again, it just reboots the hub without doing the update.
I had to go to the Diag Tool on that hub and go to Restore Previous Version to get it to update to 142 then it updated successfully. I had no issues with my C5 and C7 hub, just my C4 update in the last several updates like what others has reported.
I already soft reset this hub this past weekend trying to fix that issue before discovering Restore Previous Version let me update the hub so not sure how likely it would be to be due to a DB issue.
