My C8 Hub worked perfectly for years. Then after multiple electrical outages one morning during a storm, I have had lots of weird behavior. I have worked through many of the problems, but I am still getting random reboots of my Hub, maybe once every week or two. And it always happens at exactly 4:13am. Nothing on my end should be occuring at that time. Don't see anything in my Logs except for the reboot. Any ideas what is causing this? Anything in particular that should be occuring in the system at that time?
Sounds like a time that a backup may be scheduled. If so, an extremely low memory reading or loss of a radio or connection to the router if on wifi during that event could potentially trigger a reboot IIRC.
1 Like
You can look at all the scheduled jobs on the logs page under Scheduled Jobs. You can find which one is firing at that time. I see there are jobs scheduled by the hub, like appCleanup.Job, nightlyCleanup.Job, etc. I wonder if one of those jobs is causing the issue, though is could just be the backups job like thebearmay mentioned.
Hmm. My backups are scheduled for 2:30am and I doubt they run until 4:13am. I looked at the Scheduled Jobs but it does not go back or forward far enough to see anything scheduled at 4:14am. I'll make a point of checking it the next time my Hub reboots at 4:13am.
Scheduled jobs are a list, so it isn't like anything has dropped off of that list due to time.
If there is no scheduled job in the list for that time, then there is not a scheduled job at that time. Which is odd, since this really looks like a repeating scheduled event.
Next Run column should show the next run for any repeating scheduled job. You can also look in Location events and Hub events.
Happened again at 4:13am this morning.
The Location Events Log shows:
- 4:10am. WifiDisconnect (cannot connect to wifi for 600 seconds, rebooting now)
So that is the culprit. Any ideas why I am loosing wifi occasionally? OH Crap, just checked and my Router reboots on Wednesdays at 4:00. Any way to tell Hubitat to ignore Wifi disconnects?
1 Like
Connect via ethernet?
1 Like
I connected my Hub via Ethernet for years and never had a problem. Recently moved all of my iOT devices onto my Guest WiFi to isolate them from my network. If there is no way to tell Hubitat to ignore loosing WiFi, I guess there is no harm in the reboots?
What I am seeing on the web (if AI is to be trusted) is that the 600 seconds is a built-in time-out for wifi. I doubt your router takes the full ten minutes to reboot, so the problem is that the hub is not reconnecting after the router reboot, and then it times out, even though the router is probably back up by then.
One possible solution would be to use a TP-LINK wifi extender, the kind that gives you an ethernet port. Then you could use the ethernet connection, even though you are actually connecting back to wifi. I think that would keep the hub happy, as the TP-Link ethernet port would stay active, even though it has no connection to the router until the router reboots.
Edit: Actually, just using an extender without an ethernet port could probably work. I use one in my basement to connect an ethernet laser printer to wifi, so I didn't have to run cables. I also connect to the wifi on the extender for things in the basement. I have noticed that when the router reboots, those wifi connections remain through the reboot. The extenders create new SSIDs, mine just tacts on _EXT to the end of the router wifi connection name.
2 Likes
Should a WiFi disconnect cause a hub reboot? Surely if that's intended it should be a user selectable option rather than forced
2 Likes
Reboot has been the best way to ensure that the WiFi connection gets restablished from the hub side for a while. Don't know of an endpoint that could affect the wait time time before the hub reboots, but if another SSID is available during the router reboot (unlikely) I do knw an endpoint that could be used to switch to it.
@dean To answer your question, a regular reboot rarely makes anything worse.
Is your IoT on a different VLAN than your other stuff? If not, than the hub can be plugged into your LAN. If so, it is possible to get things communicating across VLANS, though not trivial. If you are using VLANS, can you put the port the hub would plug into in that VLAN? Some routers will, some won't.
I don't mind the reboot if the WiFi signal is lost, I just wish I could change the time before it decides to reboot my Hub.
Since it was @thebearmay that initially informed me of this, above, I assume that others may have experienced the same issue. Shouldn't it be pretty easy to have an option to change the time when WiFi is lost before it reboots? Not that I have ever been able to get Hubitat to implement anything...
I’m not sure if that would help, if @chrisbvt is correct about what the underlying problem is:
If the hub isn’t reconnecting to WiFi despite the router having finished rebooting, then increasing the timeout before hub reboot wouldn’t be likely to avoid the problem.
If the hub reboot after loss of WiFi was disabled instead, then the hub is still left with no WiFi connection.
1 Like
Is the weekly router reboot really required...I don't reboot my router ever, unless I have a FW update to apply. What router brand/model and reason for reboot?
5 Likes
I think that's the case for most people, maybe a semi-annual event.
1 Like
If its digital, I reboot it periodically.
I did that as well. I was of the belief that memory leaks gradually build so a fresh reset in the middle of the night once a week would be therapeutic. Then I had a Hubitat database crash and the system didn't recover after one of these reboots. I had to do a manual restore from backup. I don't do periodic reboots anymore.
As for your router you can do a smart reboot using a product called keep connect. It monitors WiFi and WAN connection and if it detects a persistent outage it reboots the router/modem by power cycling it. I have this in both of my locations so the wifi system can be self recovering if I lose wifi or internet connectivity. It is around $60 so not overly expensive.
1 Like
It seems possible that in the case of your router, and on a weekly frequency, it’s creating more problems than it’s solving (unless there was something more specific in this case too).
4 Likes
I may have missed this in the conversation, but do you know if the channel for the Wi-Fi is fixed, or could that have changed as part of the router reboot?
