Steps
Device changes
A device turns on, opens, unlocks…
When step — What starts the flow. Step type when-entity-state.
How it works
Starts the flow when a device changes state. Pick the device, then optionally the state it changes to and / or from; leave both empty for any change. Going offline or coming back (unavailable / unknown) does not count unless ticked at the bottom. Text steps can use {{trigger.name}}, {{trigger.state}}, {{trigger.oldState}} and {{trigger.attribute.<name>}}.
Example
Device changes: Front door → Unlocked → Send notificationA push each time the front door unlocks.
Options
| Option | Key | Kind | Required | Notes |
|---|---|---|---|---|
| Device | entityId | entity | yes | domains: light, switch, input_boolean, lock, cover, fan, binary_sensor, climate, presence, siren, media_player, camera, valve, mode, timer |
| Changes to | to | state | no | — |
| Changes from | from | state | no | — |
| Also when the device becomes or stops being unavailable | includeUnavailable | boolean | no | — |
| Also when the state becomes or stops being unknown | includeUnknown | boolean | no | — |
Exits
One exit. Triggers have no incoming connection.
Wire format
What the step stores in the flow definition's data bag (JSON schema).