Action Triggers
Action Triggers are direct event-to-action mappings. They are the quickest way to say: when this happens, do that.
UI path
- Open Configuration.
- Select Behavior.
- Expand Action Triggers.
- Click + Action Trigger.
- Choose the source type.
- Choose the source ID and expected event/value.
- Add one or more action steps.
- Add state guards if it should only function in certain States
- Test individual steps or the entire Action Trigger with the play/test buttons.
Controls
| Control | What it does |
|---|---|
| Action ID | Stable trigger name used to trigger and reference |
| Source type | Input, RFID, analog, sequence, collection, timer, operator, or integration source |
| Source ID | Specific configured source to watch |
| State/value | Event or value that fires the trigger |
| When states | Optional states where this trigger is allowed |
| Steps | Actions to run when fired |
Firmware 1.1 additions
Action Triggers can use runtime enable/disable gates so a trigger can be temporarily blocked without deleting its setup or relying only on state guards. This is useful for lockout periods, puzzle phases, reset flows, and service-mode behavior.
Action steps also support keyboard copy/paste, which makes it faster to duplicate tested action blocks across triggers or move them into reusable building blocks.
When to use it
Use Action Triggers for simple behavior. Use Logic Rules when multiple separate conditions must be true at the same time. Note that Action Trigger steps can fire other Action Triggers so you can create building blocks that have multiple things that would trigger them and have less places to re-define the same thing.