Noticed nothing was responding or responding very slowly. Tried to access runtime stats and I see this in the log:
Tried a reboot but it hung. Was able to access :8081 and do a shutdown from there. It came back up but I'm still getting lots of odd errors. Looks like my database might be corrupt but I don't know how. Do I just need to try a restore? Here's the current log:
No idea why the message about a firmware update failure I didn't have one pending to run.
I am proceeding with a restore to see if that helps. Note we had no power outages and the hub is on a UPS anyway.
Restore seems to have worked but no clue why it broke in the first place. The only thing I did this morning was collapse some expanded views on the APPS page. That's it.
What is app 652?
"SQL Error" tells me, first thing to try is a Soft Reset.
Restore does a big portion of the soft reset and I'm glad it helped.
A RM rule to turn a fan off once the humidity drops. Been unchanged for a year.
In general, yes. Soft reset, followed by restoring a backup (assuming the database corruption isn’t in that backup as well), should clear up database errors.
Not sure if this is relevant, but the hub can update the firmware on some z-wave and zigbee devices now (not clear from the log snippet whether the firmware update is referring to a device or the hub itself).
Next time, please add a bit more words to the title, like what is it that stopped working.
And some details in the original post about hub model and firmware version. Makes it much easier spot a problem and suggest something to try.
Ya sorry it was early and I do know better.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
Download the Hubitat app
