I did a soft-reset this morning because my hub was sluggish and then froze. I tried restoring from an offline backup from yesterday, and it was stuck at the restore screen.
So I redid the soft-reset and tried to restore from a backup on the hub. None of them work. The error message I get is, "Data failed to restore. Contact Support". I have contacted support@hubitat.com, but I figured I had nothing to lose by checking for help here as well.
I have the highest regards for our Support@huitat.com... but until they respond with the real answer...
If you do the soft reset and end up at the Green Get Started page... at the bottom is the restore from backup? In the middle, large, hard to get past is the Get Started button. Which did you use?
If you use the Get Started button you have to agree to terms and then see a tutorial and set your Location, to get to the main menu. There you can go to settings and restore again.. I'm curious if the menu and all it's options are functional for you.. before the DB gets layered on. In other words, is a "factory fresh" DB allow your hub to function properly? I know there's no devices, I know there are no Apps, but can you download a backup? Or check for an update? and have it work as expected?
Long ago, 10% seemed to be the point where it was hunting for a functional DB.. rotating thru all 4 onboard ones..
He walked me through the soft reset again, and it worked perfectly. I had already rolled back the platform, so it was easy to update back to the new version after @bobbyD got everything working.
Couple things to say:
First, I know that support is @bobbyD's job, but I think it unbelievable to be helping a customer at 8 pm on a Saturday night. I am really grateful - thank you very much!
The issue has been present for almost 2 weeks and ive made changes during that time,
so I dont really want to restore from an offline older than that.
So - restore from yesterdays off the hub maybe ?
In general, a DB restore will result in a 'clean' DB.
That does not mean there are never, ever any cases where the backup/restore cannot overcome the corruption. But as a FIRST TRY, it's alright to assume that a backup of a few mins ago, restored, will result in a clean DB.
Those 'edge cases' are why multiple off-hub backups are desirable. That way you can go back 3 weeks with no trepidation (minus the work you've done between then and now.)
There's not a lot of risk Either it works or it doesn't. As long as you can get back to :8081 you can always try another DB.
Thank you, csteele, that was the problem, I was logged in. Once I logged out I was able to soft reset my hub. By the way, I was able to soft reset restoring with 2 days old backup, but not with yesterday's backup. Both of them said that the database was successfully restored, but yesterdays backup always gets stucked in 10% while rebooting, even if first I soft reset with 2 days old backup, reboot ok, and then try to restore yesterdays backup.
Either it works or it doesn't. As long as you can get back to :8081 you can always try another DB.
