I got a notification overnight that my hub had gone "Away" and gone back to "Night" at 2:19am. After investigation, this was due to it restarting (I have a rule configured to fix mode manager properly when the hub starts up) and I'd like to determine what triggered it. The power did not go out (everything is on a UPS anyway) so I don't believe this to be a power issue.
All I can see in the logs are "System startup with build: 2.4.3.177".
Are there any logs anywhere else that can determine what happened / what triggered this? I'm slightly worried that maybe my hub was accessed remotely, but I don't know why triggering a reboot would be all that someone would've done.
Maybe your hubs memory dropped to a critical point causing your hub to initiate a self reboot. You can try the below link (Assuming it still works and the history wasn't erased due to the reboot) to check your hubs memory level history.
I doubt it was hacked, but I would maybe install the Hub Information Driver v3 and keep an eye on things like free memory, in case it happens again. It could have been a one off, a power blip, who knows? I would only be concerned after the next occurrence of it happening.
Gopher (Victor) recently patched a Java Free Mem (IIRC?) leak that could (again, IIRC) cause an unsolicited reboot... Since you're still on 2.4.3, perhaps that's what you're running into.
I had an "unexplained" reboot (a couple of them, actually) and Victor confirmed they were due to low Java memory report on the hub. Events looked like below:
There isn't. I have used an app to reboot hubs on a schedule in the past, but never on this hub and not on any in a year or more. This is the first time this hub has ever done that, that I know of. That's what made me nervous.
I don't. I do use Hubitat Remote access and the password is completely random (not re-used anywhere else on the internet).
I'd be surprised. Nothing else went offline overnight (I have 2 Hubitat hubs, many Wi-Fi cameras, a Firewall that tells me every little thing that goes on with my devices and ISP, etc.) and the C8 is plugged into a UPS battery backup (along with some of those other devices I mentioned).
I had one of those recently on a C7, same build. Victor had a look at the engineering logs and they were clean so suspected a power glitch, but like you I have it hooked up to a UPS along with other things (rpi, router) that didn’t reboot. If it’s a one off probably not worth sweating it. Can always check / replace the power cable and/or power brick.
Same story here (.177). But my logs showed the critical memory error. I never heard back from the review of my engineering logs though. Firmware has been updated twice since then. So, if it was the java memory issue, it was fixed I hope.
