I've been using Hubitat for over a year, no major issues. I had originally setup a simple rule to change modes at sunrise, sunset, night time etc.. all worked just fine. Those stopped working about a week ago, so i removed those and used Mode Manager to setup the same times to change modes. It's not working. I've removed and re-added it and still no change. But I've also noticed that some events like turning outdoor lights on at a specific time no longer work either. So mode manager won't change modes, some rules don't appear to run (time based and sensor based). The hub time/date appears to be correct. I don't see any scheduled jobs (shouldn't all my timed rules show up ?) Most of the posts on this topic suggest removing and adding Mode manager, but I feel like there is something else going on. would appreciate any inputs.
Depending on your time selections, you should see something under either "Scheduled Jobs" or "Subscriptions" for the app in question (for specific times, probably a scheduled job, but things like sunset exactly can be done with a subscription). Different apps may handle how and when they do this in different ways, so it may not all make sense unless you wrote the app or are working with the developer, but if there's nothing under either, then the app isn't likely to work since nothing will ever "wake it" besides you going into the app yourself.
Normally, I'd suggest the following:
- verify that your hub's time zone and location are correct (under Settings > Localization)
- verify that the hub time is correct (after doing the above) and that sunrise/sunset calculations look reasonable
- go into the apps in question and hit "Done" to re-establish their schedules/subscriptions
However, it sounds like you've done at least some of that already. You may also want to:
- Enable logging, if available, for the apps in question. Some have a single logging option; Rule Machine has several, with at least event and action logging generally being the most helpful, but all wouldn't hurt.
Sometimes, what looks like an app problem is actually a different problem, like a device (e.g., a light) not responding. The above can help you figure that out.
If all else fails, have you noticed any other oddities? Sometimes, a backup, soft reset, and restore are suggested to help with database corruption and related oddities. That can't hurt to try here just in case (it's a pretty safe process--just don't do a full reset, soft only, and don't reset your radios). When restoring, look for the link at the bottom of the screen to restore from backup instead of needing to go through the whole setup wizard again, by the way.
Thanks for the reply, most appreciated.
I tried all of the above, and only the restore worked. I think I'll say clear of mode manager, that seems to be when the problems began. Does it really matter if I use Basic Rules or Mode Manger to change modes ?
No, Mode Manager is just a purpose-built app that generally makes it easier--but it's nothing you can't re-create with rules, a custom app, or other solution. (That being said, Mode Manager should work...)
I have also had Mode Manager stop changing modes. It seemed to coincide with my recent update to 2.3.2.139. I updated to 2.3.2.140 yesterday and mode still isn't changing. If I manually change mode, my rules work as expected but the time-of-day (sunset, sunrise, etc.) seems to have simply stopped working.
I would try:
- go into Mode Maanger and hit "Done" to re-establish its schedules/subscriptions
- verify that your hub's time zone and location are correct (under Settings > Hub Details)
- verify that the hub time is correct (after doing the above) and that sunrise/sunset calculations look reasonable
I am having the exact problem descirbed here. Mode manager is no longer working, any delay timers do not execute. When I look at Logs > Scheduled Jobs things many jobs are not appearing. I can confirm this issue is related to 2.3 upgrade. Downgrading to 2.2.8.156 restores everything. Interestingly, some rules using a fixed time and method allHandlerT do show up in Scheduled Jobs, but anything using a delay timer based on a trigger or time based on sunrise or sunseet does not show up.
As an example,
[app:13] 2022-08-09 10:13:56.277 pm [info] Action: Rule Boolean False: Hot water active in bathroom except 2a-5a --> delayed: 0:01:55
[app:5] 2022-08-09 10:13:56.253 pm [info] Hot water active in bathroom except 2a-5a: Set Boolean true from hot water 2 min duty cycle
then no scheduled or runnin jobs show for these apps, and sure enough 1:55 later nothing in the logs (and all logging is enabled). Example next log entry:
[dev:5] 2022-08-09 10:16:24.171 pm [info] Motion Detector - Master Bath is active
Actually I correct myself here, they do show up but they are never triggered (eg, next run has past in time). Then I found something interesting, there is a timezone in Hubitat called US/Pacific-New. Just to try thigns I changed to this timezone, but still no joy. I see the things appear in scheduled jobs but they never execute and just remain in scheduled jobs. My lat and lon are correct as is my zip code. I tried changing back us US/Pacific and using 24hr instead of 12hr clock. Still broken. How can I find the service/job/function that should be checking scheduled jobs and its health?
[app:13] 2022-08-09 10:26:30.032 pm [info] Action: Rule Boolean False: Hot water active in bathroom except 2a-5a --> delayed: 0:01:55
[hot water 2 min duty cycle] false delayedAct 2022-08-09 22:28:25 PDT
I have the same issue since last system upgrade - sunrise & sunset scheduled mode changes are broken and no longer trigger.
I am also suffering from this error. Scheduled apps are not running. Repeat actions are not repeating. It also appears that sensor data is not refreshing. Example thermostat temp does not change until reload of dashboard.
I tried all the suggestions of resetting the mode manager, update and done on apps, reset system date and time, none of which made a difference. I also tried going back to previous upgrades. Still no change.
What I did notice is that my daily backups where also not happening. What that meant was that the last backup was the last 'good' setup. Restored to that backup and Voila !!!
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
