A few updates ago I started getting an alert about the local database backup failing. When I click on Alert details the page would be blank. This is related to the scheduled backups. I can take manual backups all day long. To give a little more back history, I upgraded from 2.3.6.146 to 2.3.7.139 and had some sluggishness and delays with my automations. I reverted back to 2.3.6 and all was well. A few days later I upgraded to 2.3.7.140. I honestly don't know if the local backup alerts started after the revert or second upgrade. I upgraded to 2.3.7.144 a few days later, but I am still getting the alerts.
I only found one other post about this and also looking through the community, it appears that a software reset should resolve this. The help pages are a little contradicting. One said to create a backup and immediately restore it. Somewhere else it said to add the soft reset in between the backup and restore. My question is, how long is an extended period of time?
I tried the first option. Backup and immediately restore. I waited about 10-15 minutes with it sitting at 15%. I then did a soft reset via the diag tool and then selected local restore on the Getting started page. It's been over 20 minutes now and I'm still at 15%.
1 hour 15 minutes, still stuck at 15%. I didn't really want to tag support, but I'm starting to stress over this now. @bobbyD or @gopher.ny - Anything I can try?
EDIT: At the 1 hour 45 minute mark I reverted to 2.3.7.140 via the Diag page and I'm now at 10 minutes of being stuck at 15%.
EDIT EDIT: I think I'm screwed now. After another 45 minutes I restored to 2.3.6.146 via the diag. I got the Error 500 Something went wrong message. I did a soft reset and after it returned asking to Get started, I powered it down and unplugged it for 5-6 minutes. Powered it back on and uploaded my 2.3.6.146 backup to restore. Eventually it went to the Rebooting page where it stayed. I opened a new tab and pointed at the hub and the Error 500 page was back. Rebooted via Diag again, but I'm back to the 500 error.
Try reverting to that 2.3.6.246 and don't restore a backup. It will be as if you got the hub fresh out of the box (ignoring the register the hub part )
Then, go to the Diagnostic Menu and download latest version. When that completes, Restore previous version, picking 2.3.7.144 (the latest as of this moment.)
From the Getting Started page, I click on the big green button.
It forced the upgrade from 2.3.6.146 to 2.3.7.144.
I verified via HE Diags, that 2.3.7.144 was now showing.
When the screen returned to Getting Started, HE Diag did not show a Restore to previous version of 2.3.7.144. Only .139 or .140.
At this point I did a restore from local backup and chose the backup on the hub from this morning.
Currently sitting at the 15% stage for 5 minutes as of right now
I think that is just telling you it is already downloaded when you clicked the download latest button.
People have had better luck UPLOADING a downloaded backup, not using one from the hub. Not sure if the format changes when you download it or what. You may also need to go back one or two backups if the most current one is having an issue.
If that's not working, you could also try reverting back to 2.3.6 (firmware). Soft reset. Then restore from your downloaded backups. It should not force you to update to current platform
I had tried uploading my most recent backup, but it wouldn't ever get past 15%.
Am I correct in what I've read, I can restore a backup from 2.3.7.140 onto the hub running 2.3.7.144?
there are no DB changes for the past couple of releases.
You can restore a 2.3.5.x backup to 2.3.7.
You can restore a 2.3.6.x backup to 2.3.7.
You can restore a 2.3.7 backup to 2.3.6.x. (Which you've already done, at least once.)
Did a soft reset on 2.3.7.144 and uploaded a backup of 2.3.7.140 from 12/29 to the hub.
Realistically, how long should it take to get past the 15% DB update step?
Any plans to add some viewer into the HE diag, or ssh access, so one can see what it's doing? Or where it is actually erroring out?
EDIT: At the 20 minute mark I reverted to a previous release of 2.3.7.140 and then uploaded a backup from 2.3.6.146 taking at 3 AM on Dec 20. My thought are that something in my backups are off. I upgraded to 2.3.7.139 mid-morning on 12/20, but then reverted back to 2.3.6.146 mid-afternoon. Still stuck at the 15% for 10 minutes now.
Open to any more suggestions. I'm starting to fear the worst here, which will be a complete factory (hard) reset and starting over from scratch. No fun there with nearly 100 devices, if not more. And I can't tell you how many rules.
When I go to the Diagnostics tool, the screen comes up, but then won't let me log in w/ the MAC address. I click log in and the button grays out for a few seconds, and then nothing.
Backup version is not related to actual firmware version.
So... did you revert to a prior FIRMWARE / PLATFORM?
From diagnostics use the restore previous version, go back to 2.3.6
Then after reboot, soft reset from diagnostics.
Then restore from a downloaded backup (can be a 2.3.7 backup).
)
