Automations
Automations are if-this-then-that rules: when a sensor crosses a threshold, an actuator action runs.
Path: left nav → Automations
List tools
- Search
- Filters: All · Active · Paused
- Create automation (guided form)
- Advanced workflow builder (same rule idea, fuller editor under Settings workflows)
Empty state: “No automations yet. Create a rule to react to sensor readings.”
Create an automation
- Open Automations → Create automation.
- Fill in the form:
Rule details
- Automation name (required)
When (trigger)
| Field | Meaning |
|---|---|
| Sensor | Which sensor to watch |
| Reading type | Numeric (raw/value) compares ADC/count or numeric readings; ON/OFF compares digital state |
| Condition | For example Greater than (>), or other comparisons offered in the picker |
| Threshold value | Number that fires the rule |
| Unit | Optional label (for example °C, %) |
Then (action)
| Field | Meaning |
|---|---|
| Actuator | Which output to drive |
| Action | For example Turn actuator ON / OFF |
Notifications & UI
Optional toggles:
- Notify when rule matches
- Notify when action succeeds
- Notify when action fails
- Show badge on actuator
- Log executions (server)
- Queue when device is offline
- Flush queue after long offline / restart
- Tap Create automation.
Tips
- Prefer a clear name (“High humidity → turn fan on”) so filters and alerts stay readable.
- Pair with Alerts to learn when rules fire or fail.
- For clock-based behavior, use Schedules instead.
- For one-tap multi-actuator presets, use Scenes.
note
Who can create automations depends on your space role and plan. Viewers typically cannot.