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
InputsNone — it is a source block.
OutputOne pin, labelled O.
FieldsDevice, Property, When (the trigger mode) and, for most modes, a Value to compare against.
The value editor matches the property: a switch for a boolean, a slider for a number, a list for an enum, a colour wheel for a colour. If a property looks wrong there, the device's property type is what needs fixing.

2.Trigger modes

Which modes you are offered depends on the kind of property.

ModeOffered forWhat it emits
ChangedEvery property typeA 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.
EqualsEvery property typeTrue while the property equals your value, false otherwise — re-evaluated on every report.
Above / BelowNumbers onlyTrue or false against your threshold.
On value (pass through)Every property typeThe 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.
Above and below only work on numbers. Pointing them at a colour or a text value gives a condition that is never true, with nothing to indicate why.

3.What happens at flow start

A detail worth knowing before you deploy a flow onto a live house.

Trigger modeOn deploy or restart
ChangedStays 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 / BelowWorks 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.
Deploying reads the house; it does not drive it. The first real report from a device after the flow is running is what actually commands anything, so you can deploy at any time of day without a room switching itself on.

4.Device action

Writes to one property of one device.

Detail
InputOne pin, I.
OutputO — the value that arrived, passed straight through so you can chain further blocks. It passes through whether or not the action actually fired.
FieldsDevice, 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.
Toggle works on blinds too: the current position decides the direction, so a blind standing open travels closed and anything else opens. If the position has never been reported it opens, which is the safer guess.

5.Fixed value or from connection

This setting changes when the action fires, not just what it sends.

Value sourceWhen it firesWhat it sends
Fixed valueOnly when the incoming value is true. The input is purely a trigger.The value you typed into the block.
From connectionOn every input — because 0 and false are legitimate values to send.Whatever arrived.
From connection, fed by a conditionOnly when the condition is true — the block recognises a conditional trigger wired directly to it and uses it as a gate.Whatever arrived.
The usual mistake is a fixed-value action wired to something that sends false — nothing happens and it looks broken. If the action must respond to both states, either use from connection, or add a NOT and a second action for the off case.

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.
The consequence to design around: a flow cannot usefully react to its own write within that window. If you need a confirmation step, read the state back a few seconds later with a Delay rather than expecting an immediate echo.

7.Notification

Puts a message in front of the customer.

FieldDescriptionDefault
MessageThe text. Write <v> anywhere in it to insert the incoming value — "Freezer is at <v> °C".—
SeverityInfo, 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.
The repeat guard is held in memory only, so a server restart clears it and the next event alerts immediately even if it is within the window. Use it to tame a chattering sensor, not as a guarantee of silence.
Keep the cooldown generous on anything sensor-driven. A door sensor with no cooldown can produce dozens of alerts in a minute, and a customer who turns notifications off will miss the one that mattered.

8.Flow error

A source block that fires when something in the flow engine goes wrong.

Detail
InputsNone.
OutputErr — carries the error text itself, so a Notification reading "Flow failed: <v>" shows the real message.
FieldsNone.
  • 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.
Put a Flow error block and a Notification in one small flow on every site. It costs two blocks and turns "the automation stopped working" from something the customer reports into something the system reports.

9.Subflows and saved blocks

Package a piece of logic once and drop it into other flows.

How to make one

  1. Build the logic in a normal flow.
  2. 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.
  3. 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.
Back to all function blocks, or see them wired together in the examples library.