Condition

🚀 Available since Core version 2026.1.

The Condition smart rule links triggers to actions: while a trigger applies, its actions are in effect. For example, when the motion sensor in the hallway detects movement, the first trigger turns on the light, and when motion stops, the second trigger turns it off. It is triggered by a device value (temperature, motion, a button press) or by time (at 23:00, at sunset, on workdays). It can have several triggers, and their order is their priority: at any moment, the actions of only one of them are in effect.

How the Condition smart rule works#

On every change — a new value of an input device, or the start or end of a time trigger — the smart rule goes through the triggers in the order they have on its page, and the first trigger that applies wins. The smart rule cancels the actions of the other triggers, even if their condition is true as well.

The trigger condition decides the kind of trigger:

• State triggers (Value equals, Value is less than, a time trigger in Interval mode) apply as long as their condition is true.
• Event triggers (Value changed to, a button press, a time trigger in Instant mode) happen at a single moment. They take part in the order like any other trigger: an event below a state trigger that applies is not executed at all; an event above it wins, and the actions of the state trigger are applied again only at the next change.

When no trigger applies, the smart rule releases its devices and writes nothing to them. The device is then controlled by a smart rule with a lower priority or by its Default values; with the default value set to Do not change, the device stays as the smart rule left it. If the smart rule should turn a device off, it needs a trigger of its own for that. The priority between smart rules that control the same device is set by their order in the device’s detail, in the Affected by section; you change it with the Edit button.

One-time actions and the notification are executed only on a new activation of the trigger — when its condition becomes true. When a trigger takes over from a trigger higher up, after the control unit starts or after the smart rule is saved, only its hold actions are applied.

How to read the charts on this page: grey lanes are the input — the temperature (height of the area, 16 to 24 °C), the trigger condition and what another smart rule wants; blue lanes are the result — when the trigger’s actions are in effect and when the light is on. A dashed outline means that the trigger condition is true, but a trigger higher in the order wins. The time axis is not to scale.

The chart shows a smart rule with three triggers on one temperature, in this order: heating at full power below 18 °C, at reduced power below 20 °C, and off from 21 °C.

1. Below 18 °C, trigger 1 wins and the smart rule cancels the actions of trigger 2.
2. Above 18 °C, trigger 2 takes over without a new activation: only its hold actions are applied.
3. At 20 °C, no trigger applies: the smart rule releases the heater, it does not turn it off.

So order the triggers from the narrowest condition: if the “below 20 °C” trigger were first, the “below 18 °C” trigger below it would never win.

Hold action vs One-time action#

Every device action has a type, which you choose in the Action type section on the action page (in the simplified view, tap Show more first to reveal it). The app explains there:

A hold action holds the value until the smart rule's condition is no longer met. A one-time action is applied only at the moment of the event and then releases the device, so a smart rule with a lower priority can take over. It is not applied again if this smart rule takes control later without a new event.

In the chart, the trigger Motion = Motion spotted turns the light on, and a second Condition smart rule with a lower priority holds it off from point 1:

1. The smart rule with a lower priority wants to turn the light off: a hold action does not let it, a one-time action does.

Actions of an event trigger are always one-time. Actions of a state trigger are hold actions by default, except for those that can only be one-time, such as Toggle.

Examples and scenarios#

Temperature control with hysteresis#

Goal: Turn on the heater below 20 °C without switching it on and off at every fluctuation around 20 °C.

• Device value mode, input device: a temperature sensor.
• Trigger 1: Value is less than 20 °C, Hysteresis 1 °C in + mode → turn on the heater (Hold action).
• Trigger 2: Value is greater than or equal to 21 °C → turn off the heater.

Behavior: The heater turns on below 20 °C, and thanks to hysteresis, trigger 1 keeps it on until the temperature rises above 21 °C; then trigger 2 turns it off. When the temperature falls again, no trigger applies between 21 and 20 °C: the smart rule releases the heater, and it stays off unless a smart rule with a lower priority or the Default values change it. Keep the actions of the trigger with hysteresis as hold actions — the app usually does not count this trigger switching on as a new activation, so one-time actions and the notification would not be executed. The hysteresis modes are described on the Triggers page.

Motion light with minimum duration#

Goal: The hallway light turns on when motion is detected and stays on for at least 10 minutes from the start of the motion.

• Trigger 1: Motion Value equals Motion spotted, Minimum duration 10 minutes → turn on the light.
• Trigger 2: Motion Value equals Motion cleared → turn off the light (Hold action).

Behavior: Trigger 1 stays active for at least 10 minutes from the start of the motion, even if the motion ends sooner; new motion during that time starts the count again. If there is no motion after that, trigger 2 takes over. Keep the turn-off as a hold action — a one-time action would not be executed when trigger 2 takes over without a new activation.

The minimum duration is not a turn-off delay: when the motion lasts longer than 10 minutes, the light goes off as soon as the motion stops. Nor does a Delay of 5 minutes on trigger 2 keep the light on while it waits — no trigger applies, the smart rule releases the light, and a smart rule with a lower priority or the Default values can change it right away. For a light that should stay on for some time after the last motion, use the Delay smart rule.

Blinds and lights following the sun#

Goal: Open the blinds after sunrise, close them and turn on the lights before sunset, and turn off the lights at 23:00.

Time mode, three triggers with the Day time frame and Instant mode:

Behavior: Each action fires once at the specified time, so between the triggers you control both the blinds and the lights manually or with another smart rule.

Workday vs weekend schedule#

Goal: Heat to 22 °C from 06:00 to 08:00 on workdays and from 08:00 to 10:00 on weekends.

Time mode, Workday/Weekend time frame, Interval mode:

• Trigger 1: 06:00 – 08:00 on a workday → thermostat 22 °C.
• Trigger 2: 08:00 – 10:00 on the weekend → thermostat 22 °C.

Behavior: An interval starts and ends either on a workday or on the weekend, so two schedules need two triggers. At the end of the interval, the smart rule only releases the thermostat, and the setpoint stays at 22 °C until a smart rule with a lower priority or the thermostat’s Default values change it. Returning to a lower temperature needs a trigger of its own.

Getting started#

Below the common attributes, the smart rule page has three sections: trigger mode, input devices and triggers.

Condition

Trigger mode

Device value

Time

Input devices

Motion sensor

Add Device

1

Triggers

1

MotionMotion spotted

Turn on

2

MotionMotion cleared

Turn off

Add trigger

1. The number in the circle is the trigger’s position in the order; you change it by dragging the row. A state trigger has a filled circle, an event trigger an outlined one. Tapping the row opens the trigger configuration; the three dots open a menu in which Duplicate actions copies the trigger’s actions into other triggers in the same smart rule. It is offered only when the trigger has actions and the smart rule has another trigger.

Basic example#

You want to turn on the hallway light when the motion sensor detects movement, and turn it off when motion stops.

1. In the detail of the motion sensor, tap Add new smart rule and select Condition as a smart rule that the sensor triggers. The sensor is then the input device, and the triggers Motion = Motion spotted and Motion = Motion cleared are pre-filled. A smart rule added from the detail of a controlled device has one trigger without a condition instead, with an action for that device, and one added from the list of smart rules starts empty: add the sensor with Add Device and the triggers with Add trigger.
2. Tap trigger 1. In the Actions section, tap Add New Action, select the hallway light and set it to On.
3. In the same way, add the Off action to trigger 2.
4. Tap Save.

Trigger mode#

The smart rule always operates in one of two modes:

• Device value (default) — the triggers watch the input devices.
• Time — the triggers are time triggers, and instead of the input devices, the page has the Timeline section, which the app describes as “Shows when each trigger will be active.” The page remembers the triggers for each mode separately; when you save in Time mode, it discards the input devices and the triggers of the Device value mode.

Input devices#

The input devices are shared by all triggers and must be of the same type: once you select the first one, devices of other types are unavailable. A device cannot be both an input device and an action target in the same smart rule.

With several devices, a state trigger applies when any of them meets the condition or, with the All devices must fulfill the state option turned on, when all of them do (Triggers). An event is evaluated on the device that is reporting it.

Triggers#

For trigger conditions, value types and the other trigger settings — delay, minimum and maximum duration, hysteresis and time triggers — see Triggers.

Actions#

You add actions on the trigger configuration page: in the Actions section, tap Add New Action, select a target device, then configure what the device should do. In the action menu (three dots), Rename renames the target device, not the action.

Notifications#

Tap the bell icon in the Actions section header to add a notification to the trigger — at most one. It sends a push notification to the recipients you pick in its Groups, Users and Client devices sections, and only on a new activation of the trigger.

A script-type notification message can use the script constants SmartRuleName (the name of this smart rule), LocationName (your installation name) and DeviceName (the device that triggered the smart rule; empty in Time mode).

Limiting condition#

The Limiting condition row among the common attributes of the page controls when the smart rule is allowed to run, depending on the condition type: Formula, Time, Digital output or Multi-Value Switch. The Time type divides the selected period (day, week, workdays and weekend, month, year) into intervals in which the smart rule alternately runs and is limited. To limit it by presence mode, use the Multi-Value Switch type with the presence device. All types, the time intervals and what the smart rule does while it is limited are described on the Limiting condition page.

While the smart rule is limited, it sends no action and no notification to its devices, and in the list of smart rules in the device’s detail it shows the status Limited. It does not turn the devices off by itself — a smart rule with a lower priority or their Default values take them over. A one-time action that falls into the limited time is lost; the hold action of the active trigger is applied once the limitation ends.

Replaces older smart rules#

When you update to version 2026.1, these smart rules are converted to Condition and keep their priority. Some of them are split into several smart rules in the process.