Steps
Schedule starts / ends
Two exits: when a weekly schedule becomes active, and when it becomes inactive
When step — What starts the flow. Step type when-schedule.
How it works
Fires at the boundaries of a weekly schedule of time blocks, through two exits: Active when a block starts, Inactive when it ends. Blocks can start or end at a clock time or at sunrise / sunset with an offset; an end before the start runs overnight.
Example
Schedule starts / ends (weekdays 9–5) → Active: Control devices (thermostat comfort) → Inactive: Control devices (thermostat eco)Comfort during work hours, eco outside them.
Options
| Option | Key | Kind | Required | Notes |
|---|---|---|---|---|
| Active during | blocks | scheduleBlocks | yes | — |
Exits
Two exits: active (the default connection) and inactive (drawn dashed). Connect a step to the second exit to handle the other case.
Wire format
What the step stores in the flow definition's data bag (JSON schema).