I know nothing happens for no reason, but my hub evidently rebooted on its own in the middle of the day yesterday.
I received a notification that my hub was going to shutdown. That should have been triggered by a rule that watches my Ring extenders going to battery. The problem is I didn't receive the initial notification of the power failure that would have triggered the shutdown notification, nor is anything related to the shutdown/reboot in the logs, not even the notification that I got.
The only way I know the hub rebooted is that a rule runs on reboot to refresh some of my devices and it did run according to the logs. The logs don't even have the notification that was sent to my phone. (Unfortunately, I cleared the notification on my phone.)
Should I just chalk this up to a one-off or investigate some more? The issue there is I don't know where else to go since the logs don't show anything. This is the first time I can recall it happening. Everything appears to be working fine today.
Do you think the hub shut down cleanly? How was the notification that the hub was going to shut down triggered? You could create a little rule to catch some key indicators. Here's one I use:
Where are you looking for this? It's under "Logs" (as of recent firmware), but it's not a traditional log entry. You need to look under Logs > Hub Events, and you should see something like a systemStart event listed there. If not, I'd say it didn't happen. (I assume the rule is triggered on this event so it probably did? Otherwise, how that is triggered would be good to know.)
I don't believe any event is generated for a shutdown (polite or otherwise), so I'm not sure how the other rule is being triggered or how the notification is happening, and I share the curiousity of the above post.
I couldn't find one... though it actually would be kind of handy. Of course if the hub is shutting down I don't quite know what you would have time to do with it! Maybe a notification... "I'm dyinnnnnnn---"
I think it did shut down cleanly, but I have no way of knowing. Like I said, everything appears to be in order this morning. Rules are firing, hub is accessible and looks normal on the web pages.
I am reasonably sure that I did not lose utility power during this time. (A combination of no events on the hub and other devices and other external indicators around the house that show power continuously being present, like my PC that did not reboot.)
Sorry, I was a bit unclear. Yes, I know the system did startup, and have the entry in Hub Events, but what I don't know is why it did so. (I suppose stated properly, the question is why it shutdown/rebooted to cause the startup.) There is nothing in logging or events or anywhere else that I know to look for to explain the 'why.'
Here's the rule that would have conceivably triggered the notification:
The issue is that the device events for 'Living Room Extender' do not show any events of going to battery. And, I have a complimentary rule that uses the same trigger and it did not fire nor send any notification, either. (I should have gotten a notification close to simultaneously for the other rule and did not get it.) Also, all of these rules are long established and have both been tested/simulated and fired 'for real' with no issues.
This is a snip of my logs around the reboot. Note that there's nothing that shows any rules firing or any notifications sent to my phone. I was thinking that there could possibly have been some sort of rogue power event, but if that were the case, why is nothing in the logs? I would think that if my rule did actually fire and I got a notification on my phone, something would have been written to the logs, but nothing...
(And in case you're wondering what's below (older in the logs:) nothing, just usual, regular log entries. Nothing about rules firing or notifications.)
Think it may have been addressed in the latest release, but at one point running the hub on wifi if the hub lost DHCP connection and was not able to restore the connection, it would reboot to try and reconnect. Trying to remember, but I believe the DHCP loss messages were in the Location Logs.
