Configuring steps

Double-click a step, or click its gear, to open its options. The dialog is generated from the step's catalog entry, so every step is documented the same way on the step reference.

Reading the cardCopy Anchor Link

After configuring, the card's subtitle becomes a sentence (Front door → unlocked, Weekdays 07:00). State-dependent steps also show a Now: line with the device's current reading, so you can see whether a condition would pass right now.

PickersCopy Anchor Link

• Device pickers are filtered to the domains the step supports; state pickers list that device's possible states by their friendly labels and store the raw token. If you type a state instead (imports, test values, the AI builder), any spelling of the label or the token is accepted and normalised on save; a value the device never reports shows an unknown state warning naming the valid options.
• Days, time, duration and schedule blocks have dedicated editors (a schedule block can start or end at a clock time or at sunrise / sunset with an offset; an end before the start runs overnight).
• Recipients depends on the channel: account users for push, phone numbers or addresses for SMS and email.
• Device action (in Control devices) is three pickers: device type, action, then that action's parameters, all from the hub's catalog.
• Integration action lists the services integrations have reported, with their parameters.

Text with placeholdersCopy Anchor Link

Fields marked as supporting templates show a placeholder table beside them. Type or click a token:

{{trigger.name}} changed to {{trigger.friendlyState}} at {{var.lastTime}}

trigger.friendlyState is the human form of the state (Open, 74°F) in the home's units. The full list is on Template placeholders.

VariablesCopy Anchor Link

Set variable writes a name (lastTime, count); operations include set, increment, decrement, now, from device state, from attribute and clear. Tick shared to make it visible to every flow in the location. Variable is compares it (equals, one of, above, below, is set, older than, …) or reads a trigger.* path directly.

Validation inside the dialogCopy Anchor Link

Options are checked live against the same rules the hub applies. A step with a config problem shows the message in the issues strip (entityId is required.), and Publish stays blocked until it is fixed.