Schedules
A Schedule is a named set of time-of-day rules that resolve, at any moment, to a single state: Active or Inactive. On its own a schedule commands nothing — its value comes from binding each state to a set of scene modes. While the schedule is active it applies its active modes; while inactive, its inactive modes.
A schedule is the when; a scene is the what.
Together they form the standard occupancy automation — flipping a
building’s scenes between operating states on a calendar, with no manual
action. A schedule is referenced by its scoped id
sch.<n> (e.g. sch.1).
Schedule Rules
A schedule’s time rules are written as a comma-separated list of
items, each in the form [days] hh:mm-hh:mm using a 24-hour
clock:
| Example | Meaning |
|---|---|
weekdays 8:00-17:00 |
Mon–Fri, 8:00 AM to 5:00 PM |
sat 9:00-12:00 |
Saturday only, 9:00 AM to noon |
mon-fri 6:00-22:00 |
A day range, Mon through Fri |
weekdays 8:00-17:00, sat 9:00-12:00 |
Two rules combined |
Days —
weekdays(Mon–Fri), a single day (sat), or a range (mon-fri). Day names are the lowercase three-letter abbreviations:mon tue wed thu fri sat sun.Times —
start-endinh:mm24-hour format. The start is inclusive, the end is exclusive. There is no AM/PM. Times are always relative to the project timezone.
The schedule is Active whenever the current time falls within any of its rules, and Inactive otherwise. All times are evaluated in the project’s timezone.
Scene Bindings
Each schedule carries two lists of scene modes — one applied while active, one while inactive:
| List | Applied when… | Example |
|---|---|---|
| Active Modes | the schedule is Active | sn.1.1, sn.2.1 |
| Inactive Modes | the schedule is Inactive | sn.1.2, sn.2.2 |
Each entry references one mode of one scene as
sn.<scene>.<mode> — the scene’s id plus the
mode’s stable id. Because the reference
binds to the stable mode id, renaming or reordering a scene’s modes
never breaks a schedule.
A scene typically appears in both lists with a
different mode in each — for example a comfort scene set to its
occupied mode while active and unoccupied
while inactive. A scene may be listed in at most one mode per state.
Both lists are optional. An empty list means the schedule applies nothing in that state, and the affected scenes simply hold whatever they were last set to.
How It Runs
Schedules are evaluated automatically on a recurring cycle — no action is needed once the rules and bindings are set. On each cycle the schedule re-applies the modes for its current state, so the building stays in the intended state even after a restart.
Applying a mode is an ordinary scene batch write at level
10. Because scene writes hold until something overwrites
them, a manual point override (which takes a higher priority level) wins
over the schedule, and the schedule resumes once that override is
released. Deleting a schedule stops future changes but does not undo
modes it has already applied.
Schedules may activate up to 5 minutes before the start time, and may toggle to inactive up to 5 minutes after the ending time.