I'm sorry to write this post but for some time now my Hubitat has become unusable. Too often I have found Hubitat with "corrupt database" just when I was away and I wish I could count on Hubitat.
So, again, I have to waste time looking for the backup configuration that works. Today I have already tried four without success.
Last reboot was over an hour ago and still unresponsive, not even on port 8081.
I'm so sorry to have to give up Hubitat because it's one of a kind and because it's exactly what I want, but it doesn't work for me anymore.
I don't know if the causes are the latest updates or if my HW version is too old, but the configuration hasn't changed for years and it worked for years.
So when I come back I'll unplug it definitely and start looking for an alternative, perhaps less ideal but hopefully more reliable.
Sorry to hear that. Frequent database corruptions are indicative of unresolved problems. Performing a reset and restoring a backup is only good to bring the hub online, but without addressing the issues that caused the database to become corrupted, it's only a matter of time before the hub is locked up again. Have you checked the logs/past logs to see what caused the problem? Also, what hub model do you currently have?
That is a different kind of issue. Being unable to reach the Diagnostic Tool is indicative of a network problem, or a hardware issue.
I have this happing 2-3 times a week. I'm over it
Have what happening specifically?
More details would be helpful if you’d like to troubleshoot.
This is how many times my hub has reboot today alone. And random every couple of days I get the corrupt date base error. I haven't even did a restore yet to the hub. I've had this issue ever increasingly over the past year.
Description
Value
Event type
Date
System startup with build: 2.3.5.146
2.3.5.146
2023-06-03 03:45:16.650 PM EDT
System startup with build: 2.3.5.146
2.3.5.146
2023-06-03 03:42:24.570 PM EDT
System startup with build: 2.3.5.146
2.3.5.146
2023-06-03 02:42:14.058 PM EDT
System startup with build: 2.3.5.146
2.3.5.146
2023-06-03 02:29:42.903 PM EDT
System startup with build: 2.3.5.146
2.3.5.146
2023-06-03 01:42:16.862 PM EDT
System startup with build: 2.3.5.146
2.3.5.146
2023-06-03 01:35:08.416 PM EDT
System startup with build: 2.3.5.146
2.3.5.146
2023-06-03 01:22:37.206 PM EDT
System startup with build: 2.3.5.146
2.3.5.146
2023-06-03 01:19:34.451 PM EDT
System startup with build: 2.3.5.146
2.3.5.146
2023-06-03 12:46:33.893 PM EDT
System startup with build: 2.3.5.146
2.3.5.146
2023-06-03 12:42:33.527 PM EDT
System startup with build: 2.3.5.146
2.3.5.146
2023-06-03 12:40:34.157 PM EDT
System startup with build: 2.3.5.146
2.3.5.146
2023-06-03 11:58:44.863 AM EDT
System startup with build: 2.3.5.146
2.3.5.146
2023-06-03 11:42:31.583 AM EDT
Updated with build: 2.3.5.146
2.3.5.146
2023-06-03 09:35:36.022 AM EDT
Sparse detail, but with that frequent of a reboot I’d guess a corrupt database that a restore might fix.
Without more details it is really difficult to gather what could be wrong. If you had this problem for months, and you screened Logs/past logs and resolved any errors and warnings, yet the issue persists, then you may be dealing with a hardware malfunction. I suggest creating a warranty case (if you didn't already) so we can evaluate if the hardware has problems, as this is highly unusual:
Hub should not typically reboot on its own. Usually if something goes horribly wrong it will just lock up and stop working, not reboot. Are you sure it is getting consistent power? Almost sounds like power is dipping causing it shut off and restart. This would also be a cause for database corruption if power dips while activity is happening. I would try putting it on a known good power supply and cable. My go-to is old Apple phone blocks which are 1A, or a tablet power block which is usually 2A+ giving plenty of power to spare.
This has done the trick, so far no random reboots for 13 days now. Thanks for the tip!
After trying two old power supplies (the ones I had available) as well as obviously the original one without success, today I tried a 3A power supply and my Hubitat started instantly; i installed the latest backup on it with no problems, updated it and so rebooted at least four times quickly. I don't want to claim victory prematurely but I think I was foolish not to think of it sooner. Thank you jtp10181
No problem, its odd you had to go to 3A since the hub only draws 1A. Or maybe that's just what you had available? I have been using one of those old tiny iPhone 1A blocks on both the C7 and now the C8 without any issues. A lot of the other old phone chargers I have laying around are only 700-800mA which would not be enough. I started tossing anything under 1A as they are virtually useless now-a-days.
My wife stockpiles batteries to recycle.
There were some super tiny phone batteries in the pile.
A battery used in today's phone could likely power an old flip phone for a month.
The two I tried without success were from old phones and similar to the original of my Hubitat, so I tried one that I took for a Raspberry (with power problems). Speaking of Raspberry, I think a low power indicator on the Hubitat would be helpful too. But the lesson (for me) is: don't assume that the power supply is adequate just because the LEDs light up.
I love those things.
