Examples library

Nine automations that cover most of what a house actually asks for. Each one is built from blocks that already exist in Flows — nothing here needs custom code.

1.How to read these

Every example follows the same shape, and every one is built on the Flows page of Installer Studio.

  • Blocks are dragged from the menu at the top of the Flows canvas, then wired by dragging from an output dot to an input dot.
  • Device trigger blocks watch one property of one device. Device action blocks write to one.
  • Nothing runs until you press Deploy. After that the flow lives on the server and keeps working with the internet unplugged.
  • Blocks that hold a state — flip-flops, delayed on/off, the alarm, the lighting and fan-coil controllers — have a Rem switch. Rem on means the block comes back after a reboot exactly as it was; Rem off means it starts fresh.
Build one example, deploy it, and watch the block values update live on the canvas while you trigger it by hand. That is the fastest way to learn the editor.

2.Corridor light on motion, only after dark

The classic. Motion turns the light on, but only in the evening and at night — during the day the corridor has enough daylight and the customer finds it annoying.

What you need

  • A motion sensor device with a motion property.
  • A light the server can switch.
  • The site location set, so the server knows when sunset is.

How to build it

  1. Add a Device trigger: the motion sensor, property motion, trigger equals true.
  2. Add a Time condition: reference solar, event sunset, operator after. Leave the offset at 0, or set −30 to start half an hour before sunset.
  3. Add a Logic AND and wire both of the above into it.
  4. Add a Delayed on/off block. Wire the AND output into its Tr input. Set Doff to 120 seconds — how long the light stays on after the last motion.
  5. Add a Device action: the light, action set, value from connection. Wire the delayed block's O output into it.
  6. Press Deploy.
Leave Rem off on the delayed block. After a power cut you want the corridor dark, not stuck on because it was on when the power failed.

3.Staircase light with a timeout

A push button lights the staircase for two minutes, and any further press restarts the two minutes rather than switching it off.

What you need

  • A push button as a device with a boolean property.
  • A light.

How to build it

  1. Add a Device trigger on the button, trigger changed — it emits a short pulse on every press.
  2. Add a Delayed on/off block, Don 0 and Doff 120 seconds. Wire the pulse into Tr.
  3. Wire its O output into a Device action on the light.
  4. Deploy.
  • Each new press re-triggers the block, so the two minutes start again — exactly what a staircase needs.
  • To let a long press force it off, wire a second trigger into the block's Off input.

4.A room with moods and a central off

One room with several light circuits, a few saved moods (Bright, Dinner, TV), and a single button in the hall that switches every room off when leaving.

What you need

  • Two or more light circuits in the room — switched, dimmed or RGB.
  • A wall button for the room, and one for the hall.

How to build it

  1. Add a Lighting Controller block. Set Circuits to how many lights the room has.
  2. Wire each circuit output Lc1, Lc2… to a Device action on the matching light.
  3. Add moods with + in the block. For each mood set what every circuit should do — a level for dimmers, a colour for RGB, on/off for switched lights.
  4. Wire the room button into Mood to step through moods, or into On and Off for plain control.
  5. Add a Lighting Controller Central block, open it and select every room controller it should command.
  6. Wire the hall button into the central block's Off input.
  7. Deploy.
The lighting controller also has P (presence) and Mo (motion) inputs with their own timeouts, so the same block can do the corridor example for a whole room. Every input, output and parameter is listed in the Lighting Controller reference.

5.Fan-coil room with a window contact

A room kept at temperature by a fan coil, which stops when a window is opened and resumes when it is closed.

What you need

  • A room temperature sensor.
  • A fan-coil unit — on/off, fan speed and heat/cool mode.
  • A window contact.

How to build it

  1. Add a Fan Coil (AC) block.
  2. Wire the temperature sensor into Tc.
  3. Set Setpoint to the target temperature and Deadband to how far it may drift before the unit reacts (0.5 °C is a sensible start).
  4. Leave Mode on Auto so it heats or cools depending on which side of the setpoint the room is.
  5. Wire the window contact into Win. While that input is active the block holds the unit off.
  6. Wire the outputs: OnOff, Fan, Mode and Ts each to a Device action on the fan coil.
  7. Deploy.
Turn Rem on for this block. After a power cut the room should come back to the same setpoint and mode the customer left it at, not to the factory default. Every input, output and parameter is listed in the Fan Coil reference.

6.Blinds that follow the sun

South-facing blinds go down when the afternoon sun hits the glass, and come back up in the evening.

What you need

  • A blind with a position property.
  • Ideally a weather station or outdoor brightness sensor; without one, time alone works.

How to build it

  1. Add a Time condition: solar, event noon, operator after — the sun is on that façade from midday.
  2. If you have a brightness sensor, add a Device trigger on it with trigger above and a threshold in lux, and combine both with a Logic AND.
  3. Wire the result into a Device action on the blind: action position, value 30 — down far enough to shade, not so far the room goes dark.
  4. Add a second Time condition: solar, sunset, after, wired to another Device action setting position 100.
  5. Deploy.
Wind is the one case worth wiring first: if the site has a wind sensor, give it its own flow that drives every blind to a safe position and deploy that before the sun logic. Sun comfort is optional, storm damage is not.

7.Alarm with entry and exit delay

Arming gives 30 seconds to leave; coming home gives time to disarm before the siren sounds. Interior sensors are bypassed when armed in stay mode so the family can move around at night.

What you need

  • An alarm device.
  • Motion sensors and window/door contacts.
  • A siren output.

How to build it

  1. Add an Alarm block and pick the alarm device.
  2. Add a point for each sensor with Add motion sensor and Add window/door sensor, then wire each physical sensor into the matching input.
  3. Set Exit delay to 30 seconds — the grace period after arming.
  4. Set Entry delay to the seconds the customer needs to reach the keypad. Leave it at 0 if the siren should sound immediately.
  5. Wire the Siren output to the siren device, and Notify to a Notification block so the panel shows what happened.
  6. Deploy.
  • Stay vs away: arming to stay bypasses the motion sensors and watches only doors and windows. Arming to away watches everything.
  • Rem: turn it on if the system must still be armed after a power cut. With Rem off the alarm comes back disarmed — safer for commissioning, wrong for a finished site.
  • During the exit delay, sensor activity is ignored on purpose — the customer walking out of their own front door must not start anything.
  • Every input, output and parameter is listed in the Alarm reference.

8.Water leak shut-off

A leak sensor under the sink closes the main valve and tells everyone, immediately and without conditions.

What you need

  • A leak sensor.
  • A motorised valve the server can close.

How to build it

  1. Add a Device trigger on the leak sensor, trigger equals true.
  2. Wire it to a Device action that closes the valve.
  3. Wire the same trigger to a Notification block with a message like "Water leak detected — main valve closed" and severity set to the highest level.
  4. Deploy.
Keep this flow on its own, with no time conditions and no AND gates. Every condition you add is another way for it not to fire on the night it matters.

9.Holiday presence simulation

While the family is away, a few lights come on in the evening so the house does not look empty.

What you need

  • Two or three lights in rooms visible from the street.
  • A way to say "we are away" — a scene, a button, or the alarm being armed to away.

How to build it

  1. Add a Memory flag set block with a key such as holiday, driven by the button or scene that starts holiday mode.
  2. Add a Time condition: solar, dusk, after.
  3. Add a Memory flag get on holiday and combine it with the time condition in a Logic AND.
  4. Wire the result to the living-room light, and through a Delay block of a few minutes to a second light, so they do not all switch together.
  5. Add a second time condition for the hour the lights should go off, wired to actions that switch them off.
  6. Deploy.
Memory flags are shared across every flow on the server, so the same holiday flag can also lower the heating setpoint and arm the alarm.

10.Tell the customer something happened

Anything worth knowing — a door left open, a freezer warming up, a failed automation — shows up on the panel instead of being discovered later.

What you need

  • Whatever sensor the message is about.

How to build it

  1. Add the Device trigger for the condition — for example a freezer temperature with trigger above −15.
  2. Add a Delayed on/off with Don of 600 seconds, so a door opened for a minute does not raise an alarm.
  3. Wire it to a Notification block. Write the message in the customer's language and set a cooldown so it cannot repeat every few seconds.
  4. Deploy.
There is also an Error monitor block that fires when any flow on the server fails. Wire one to a notification and you will hear about a broken automation from the system rather than from the customer.
Need one of these adapted to a site? Send us the layout — or read the device reference to see which properties each block can drive.