Triggers, actions & notifications
How a flow sees the house and how it acts on it — plus the two blocks that talk to people, and the way to package logic for reuse.
1.Device trigger
Watches one property of one device. Every flow that reacts to the house starts with one of these.
| Detail | |
|---|---|
| Inputs | None — it is a source block. |
| Output | One pin, labelled O. |
| Fields | Device, Property, When (the trigger mode) and, for most modes, a Value to compare against. |
2.Trigger modes
Which modes you are offered depends on the kind of property.
| Mode | Offered for | What it emits |
|---|---|---|
| Changed | Every property type | A short pulse on every change of value: true, then false about a twentieth of a second later. This is the one to use for buttons. |
| Equals | Every property type | True while the property equals your value, false otherwise — re-evaluated on every report. |
| Above / Below | Numbers only | True or false against your threshold. |
| On value (pass through) | Every property type | The property's actual value, forwarded unchanged — a temperature, a level, a colour. |
- Changed is a pulse, not a state. Downstream blocks see true and then immediately false. Wire it to things that act on an edge — a flip-flop's toggle, a mood step, a timer — not to something expecting a level.
- Equals, above and below are levels. They hold their answer and re-send it on every report from the device, so they suit AND gates and conditions.
- On value is how you move a number from one device to another — a setpoint from a dial into a fan coil block, a lux reading into a Compare.
3.What happens at flow start
A detail worth knowing before you deploy a flow onto a live house.
| Trigger mode | On deploy or restart |
|---|---|
| Changed | Stays quiet. It records the current value as its baseline and waits for a real change, so deploying never fires a button-shaped trigger. |
| Equals / Above / Below | Works out its answer, but commands nothing. An "above 25 °C" trigger in a room already at 26 °C hands that true to the gates downstream, so an AND has a current value — but no device is written to while the flow is starting. |
4.Device action
Writes to one property of one device.
| Detail | |
|---|---|
| Input | One pin, I. |
| Output | O — the value that arrived, passed straight through so you can chain further blocks. It passes through whether or not the action actually fired. |
| Fields | Device, Property, Action, Value source and Value. |
- Set is available for every writable property. Toggle is offered only for on/off properties.
- Measurement properties — temperature, motion, power, humidity and the rest — are never offered as action targets. They can only ever be triggers.
5.Fixed value or from connection
This setting changes when the action fires, not just what it sends.
| Value source | When it fires | What it sends |
|---|---|---|
| Fixed value | Only when the incoming value is true. The input is purely a trigger. | The value you typed into the block. |
| From connection | On every input — because 0 and false are legitimate values to send. | Whatever arrived. |
| From connection, fed by a condition | Only when the condition is true — the block recognises a conditional trigger wired directly to it and uses it as a gate. | Whatever arrived. |
6.The feedback-loop guard
Why a device you just commanded does not immediately re-trigger the flow that commanded it.
When a Device action writes to a device, that device reports its new state back — and without protection, a trigger watching the same property would fire again, write again, and loop. The platform drops status reports for a property for about a second and a half after a flow has written to it.
- The guard applies to every trigger watching that device and property, in every flow — not only the one that wrote.
- Duplicate reports arriving within a fraction of a second of each other are also collapsed, so one physical change is one event even when the message arrives twice.
7.Notification
Puts a message in front of the customer.
| Field | Description | Default |
|---|---|---|
| Message | The text. Write <v> anywhere in it to insert the incoming value — "Freezer is at <v> °C". | — |
| Severity | Info, success, warning or error. | Info |
| Ignore repeats for (s) | The same message will not alert again within this time. 0 always shows. | 0 |
- The message appears in the notification bell on the panels and in the app. Repeated alerts from the same block update the same entry and mark it unread again rather than piling up.
- When a Device trigger feeds it directly, the notification fires once per event and
<v>shows the property's real value — not the true/false of the pulse. That is what makes "Temperature is<v>" work.
8.Flow error
A source block that fires when something in the flow engine goes wrong.
| Detail | |
|---|---|
| Inputs | None. |
| Output | Err — carries the error text itself, so a Notification reading "Flow failed: <v>" shows the real message. |
| Fields | None. |
- It is server-wide: one Flow error block reports faults from every flow, not only the one it sits in. You need one, not one per flow.
- It fires when a device action fails after its retries are exhausted, and when a block throws an unexpected error.
9.Subflows and saved blocks
Package a piece of logic once and drop it into other flows.
How to make one
- Build the logic in a normal flow.
- Add a Flow input for each value it should receive and a Flow output for each value it produces, and name them — those names become the block's pins.
- Use Save as block, give it a name, and it appears in the add menu under saved blocks.
At least one input and one output are required. Blocks may contain other blocks.
Blocks are stored on the server, so they are shared between installers, follow you to any machine that opens that server, and are covered by its backup. Blocks you had saved before this change are moved up automatically the first time you open the Flows page.
- Blocks are not parameterised per device. A device trigger or action inside a block keeps the device it was built with, so reusing it elsewhere means re-pointing those nodes by hand. Logic, timing and comparison blocks reuse cleanly; device-bound ones do not.
- The block editor deliberately offers only logic, timing and memory blocks. Build anything device-bound in a main flow first, then save it as a block.
- Deploying a flow expands every block into plain nodes before it runs, so the server never sees blocks — which is why a block is an editing convenience rather than a runtime feature.