cc @JimB
Thanks, that was quick.
Just set up my shades so Schedule Manager won't set them during boot up when the Shade Height rules are active.
Another "feature creep" request:
Allow a device to have 2 activity (ON or OFF) times, but limit actual device activation to the EARLIER of the 2 times, or to the LATER of the 2 times.
Example: I have a set of lights that I want to have turn ON at the earlier of 7:30PM or sunset.
Right now, I code those triggers into a rule outside of Schedule Manager using the trick taught here by @bravenel: Feature Request- RM Trigger Earlier of Two Times - #3 by bravenel
I'd like to keep the "dashboard"-like characteristics provided by Schedule Manager and bring those lights (or a Rule) into SM.
That's a good feature and I actually have a use for it as well. I'll add it to my backlog - Allow schedules to configure the earlier/later of two times · Issue #9 · evcallia/hubitat · GitHub
Yet another feature creep request {YAFCR?)
It would be great to be able to use Hub Variables for the dimmer value.
Have several Hub Variables for different shade heights that I used in multiple RM rules. A rule for all the shades in a room. 5 rooms with shades. Made sense to use Hub Variables so one change would update each rule. No rule updates needed.
@evcallia Think I've found a bug, or perhaps more accurately an edge case. I've got a schedule set up like this:
Randomly, the front porch light doesn't come on at 1am, and/or the porch string lights don't turn off at 1am.
I commented out the logsoff function so debug logging would remain on, and I think I know what the problem is. At line 1654 you have: schedule("0 0 1 ? * * *", updated)
but there's also two scheduled jobs that call switchHandler() at 1am. So there's three scheduled jobs for 1am and the order they are called in is random. If the one that calls updated() runs first, the other jobs are either unscheduled or somehow interfered with, and one or both of the lights that should turn on or off at 1am does not occur.
I'd probably check to see if there's anything scheduled for 1am and if there is, back off the time by a few minutes and keep checking until there's no conflict. But there's probably several ways you could handle this.
For now, I'll just change the time to 12:50 am instead.
Also, there probably should be a way to allow debug logging to remain on until manually turned off.
Anyhow, thanks for the great app. I'm trying to move away from RM for things that just need fairly simple scheduling. Seeing everything in a single interface is much clearer than having things spread out across a lot of different rules.
I can see this being a useful feature, I'll add this to the backlog
Glad you're enjoying the app!
Definitely a race condition here depending on which 1am schedule gets run first. I like your proposed solution of backing off the refresh until it doesn't conflict. I'll get a fix out for that and include the logging suggestion as well.
cc @dcaton1220
Has this bubbled up near to the top of your list?
Yes, I have a version of this I'm testing now. Seems to be running well for me. Need to find time to do a little clean up and get a release together but I'm happy to push what I have if you'd like to test it out as well.
Sure, I’d be happy to try it out!
Awesome, here's the updated branch - https://raw.githubusercontent.com/evcallia/hubitat/refs/heads/codex/add-earlier-or-later-option-to-schedule-manager-66ry1b/apps/schedule-manager/schedule-manager-child.groovy
@evcallia I have something I'd like to move into Schedule Manager, but not sure it's possible.
I have a bunch of various lights on a schedule, but I only want that schedule to run when mode is Home. If mode is Away or Sleep, I want the lights off (and turned off if they're on). Is this possible?
I created two schedules, one for home and the other for away and sleep. The away/sleep schedule has all the devices and the desired state is 'off' but there's no run time selected. I don't know if this is allowed, but there weren't any error messages when I saved the schedule. But it didn't have the desired effect of turning everything off, regardless of time. I'm assuming device states are restored on mode changes. Maybe that's not the case.
Would it make sense to have an option under "Only run schedules during a selected mode" like "Turn off all devices in unselected modes"?
The goal here is to only have the lights on during the desired times if mode is home. If mode is away/sleep and changes to home during the scheduled time, I'd like the lights to come back on as long as the time is between the on and off times.
I can (and already am) doing this in Room Lighting, but RL is a bit ornery and I like your interface better.
Thanks.
If your only modes are Home, Away and Sleep, then my suggestion is to:
The Hub Variable must be date/time so it will only act once. A time-only variable will act every day at the variable time.
You need a 2 minute offset.
ps: agree about the interface
Thanks, but that's way too many moving parts to move something I already have set up in RL to Schedule Manager. RL does exactly what I want and has been working fine for a long time, I'm just not a fan of its UI. I probably ought to leave well enough alone, but I like the simplicity of Schedule Manager's UI.
@dcaton1220 This isn't currently possible without some work arounds. I'll respond to a few things below, but we could add two features to this app that I think would make it works for you.
I've got a couple things in flight so probably wouldn't get to that for a little bit, but let me know if that seems like it'd satisfy your use case.
The away/sleep schedule has all the devices and the desired state is 'off' but there's no run time selected
It is possible to save a schedule in this state, but if there are no times set then they are ignored.
I'm assuming device states are restored on mode changes.
This is not the case, but is something that could be added. The 'restore' functionality exists, but the app does not currently subscribe to mode changes (only checks for mode before taking action on a switch).
Perhaps. The key functionality is that on a mode change, the devices have to sync to whatever state they would have been in, had the mode been active when the triggers fired.
Download the Hubitat app
