| ← Settings | Manual |
The Automation section lets administrators define event-driven rules that automatically execute device commands when specific system events occur. Each rule has a trigger event, optional run-if conditions, and one or more action commands to execute. Rules sourced from built-in modules are read-only; only custom module rules can be edited or deleted.
Standard two-column settings layout:
automation:create).Clicking + opens the Add Automation Rule dialog:
| Field | Description |
|---|---|
| Display Name | Required |
| Description | Required, multiline |
| Enabled | Checkbox; defaults to enabled |
Select the Event Kind that triggers this rule (not all event kinds are available — internal system events, device commands, and object/scene lifecycle events are excluded). After choosing an event kind, optional Run-If Conditions appear.
Ordered list of commands to execute when the rule fires. Each command entry specifies:
Conditions are ANDed together. Each criterion specifies:
allowed, armState, tokenType)Conditions are stored as a SQL-like expression (e.g. (allowed = true) and (token in ("abc","def"))).
| Property | Editable | Notes |
|---|---|---|
| Display Name, Enabled, Description | Yes (custom rules only) | automation:update required |
| Module | No | Shows the module identifier (e.g. custom) |
| Rule Body (JSON) | Yes (custom rules only) | Opens the Body edit dialog |
| Button | Permission | Description |
|---|---|---|
| Enable Automation | automation:update |
Shown when rule is disabled; custom rules only |
| Disable Automation | automation:update |
Shown when rule is enabled; custom rules only |
| Delete Automation | automation:delete |
Requires confirmation; custom rules only |
| Action | Permission |
|---|---|
| View automation rules | /settings/automation route |
| Add new rule | automation:create |
| Edit rule info or body | automation:update |
| Enable / disable rule | automation:update |
| Delete rule | automation:delete |