Problem: I came home and none of my automations were working. A reboot fixed it. What would be helpful is if a reboot hub command were available in RM. I would then have the hub reboot every night, say 3AM when no one is awake. This could probably prevent the few times Hubitat fails to work.
Let’s try to find the root cause of why the automation is not working instead.
I checked my logs. Mode changed to home as normal, All motions were logged properly, but lights didn't activate per RM. Garage door opening detected. Several rules didn't fire, primarily based on motion of various motion sensors. So it wasn't due to a specific device not sensing motion, but multiple rules did not function.
Were these by chance lights connected via Hue integration?
No. I don't have any Hue devices. I have a combination of Osram bulbs and various switches, ST, GE, and Iris.
OK. Was just curious because for some reason my hall light would not turn on via my Lightify motion sensor this evening. Sensor was working, clock was right, mode was right, but wouldn’t turn on. Didn’t reboot, but tried turning on the light via its driver settings (which is connected via Hue Integration) and it turned on too.
After that, the automation worked fine.
Chiming in because I am now rebooting my hub daily because any automation that is time sensitive fails… to say time sensitive I mean a light that needs to shut off after 5 minutes AS WELL AS a mode change at sunset.
Rebooting fixes this and it has happened since 706.
I sent in a support ticket and the response was akin to we are aware of bugs, we are releasing a fix . . . stay tuned. This is not the most comforting.
Just throwing my hat in the ring: I am having issues with the Hubitat since the latest update to 706. It seems for me one random zigbee device stops working until I reboot. For example, at first one of my bedroom Lamps wouldn’t respond; a reboot fixed it. But then with in less than 24 hours a motion sensor stopped responding. Again a reboot fixed it. Repeat this daily. Now it’s another light not responding. Seems to be one random device fails after each reboot and only zigbee so far. The log files shows absolutely nothing for the failed device - it’s like I didn’t even issue a command. Anyone else having a similar issue? It’s getting annoying to reboot all the time. I am wondering if I had a bad update and should do a repair or restore?
Well, we all knew what “early adopters” was all about. I think we can expect to see other problems crop up now and then. We just need to make sure the development team hears about the problems and hopefully they will respond with speedy updates that don’t break other things.
This from my personal experience has been due to lack of repeater coverage. I have also not had good luck with ZLL bulbs as repeaters.
I’ve had similar issues that require a reboot to fix. It’s not as frequent as everyday. Maybe every few weeks I’ll notice automations are really slow to respond or something just isn’t working or responding at all and a reboot fixes it.
Would be nice if there is a hub resources tracking page. I would like to know system resources taken up over time.
Just a thought…
Maybe some virtual device types with information we can collect with influxdb for logging.
I noticed that I am experiencing exact same issue. Automation begin slow to respond then some just would not work. Reboot fixes this issue. But I have to reboot almost every other day.
This is a serious issue. I’ve had an open support ticket for 2 weeks. My main issue is that events that are time dependent (ie. change mode to morning at 7:00 a.m.) do not trigger.
If I do a reset mode changes will trigger but only for a day at best.
Anyone figure out what’s happening ? I’m seeing regular issues unfortunately
Could you be a bit more specific?
Just to chime in, I was having issues with my automations also not kicking in. When I dug in I found that the schedules were all hanging for some reason.
Further digging with support showed that it was one of my WeMo switches that were hanging the whole system for some reason after a SOAP request. I ended up rebooting that device and the system has been stable ever since.