Help ! Hub acts like it's been completely reset

Hub was working as usual when I went to bed last night. This morning I got the 500 page load error from the app, could not connect to hub at all. Power cycled, now it acts as if I have no devices and it's a completely new hub. I have not made any changes for weeks. When I start the app (ios) it shows no dashboards, no devices, nothing. File manager shows no files.
When I go the to hub's webpage from a PC browser, it shows me a "Get Started" screen.
Can someone please help me understand what's going on and how to fix this?

First, do you have any backups downloaded from when you last made changes? If not, do you have any backups showing in Settings? If you do, the first step is to download all of them.

1 Like

Sorry for the troubles. What likely happened is that the nightly clean up process identified an issue with your database and attempted to auto-perform a "Soft Reset" to remedy the problem. The auto-restore failed, so that's why you are seeing the "Get Started" page. Please scroll down on the "Get Started" page and click on the link to restore a backup.

source: Soft Reset - Hubitat Documentation

2 Likes

Has this feature been added recently? Like in the last 2-3 months?

Thanks for your response.

The file manager shows "no files found, please upload a file". I have a backup on my PC from May.
What could have happened that it destroyed the backups that were on the hub itself? Is this something that other users encounter frequently - the hub simply wipes itself clean and you get to start over? I'm very, very concerned about continuing with this hub unless I understand the root cause.

Have the hub on a UPS?

It's not the file manager, it's in "Backup and Restore".

First, see if you can download more of your backups. As Bobby mentioned above, it is probably due to a corruption detected during the nightly checks. This can have many reasons, if it happens once I wouldn't be concerned, but a second time... It would be good to go through some of the common reasons for DB corruption though.

2 Likes

I've never encountered this on two hubs running for over a year. But I totally understand why this would be very worrying.

2 Likes

I'm going to go download a backup right now.

2 Likes

OK I see the restore from backup and I get a list of the last 5 but the size of the last one is suspect:

Is that last backup possible corrupted and I should use the 7-21 instead?

1 Like

I would download all of them regardless, then try to restore to the one from the 21st.

1 Like

Please restore the second last

2 Likes

@bobbyD @markus
Thanks to both of you for the quick responses. I was able to restore the 7-21 backup.

I mistakenly thought that File Manager would show backup files on the hub so that freaked me out a bit when it showed no files.

After the restore, when I start the Hubitat app (ios) it now shows an "invalid token" error.
If I use chrome (ios or windows pc) to navigate to the hub's page, no problems.

Any ideas on how to fix the "invalid token" error after a restore? I've killed/restarted the app on ios but same result.

Your input is always appreciated!

2 Likes

Yes it's on a UPS. I'm certain that the hub was powered. The explanation that the nightly cleanup process did this as a response to some database error seems to be the most plausible reason.

1 Like

If you ever experience this again, you probably need to look into what is causing the corruption. The reasons are many and varied, with a UPS you avoid one common reason; shutdowns by loss of power. Others include excessive amount of events from power monitoring devices and other devices with similar volume of events. I'm no expert at this since it has, almost, never happened to any of my hubs, not even the dev hub. I'm sure others have better insight.

1 Like

I think so also - and this is confirmed by the smaller backup.

1 Like

For future reference ... the solution I found was to go to "Settings" on the ios app, log out, then log back in.

5 Likes