TapHome

Condition

The Condition smart rule lets you create custom automations by combining triggers (conditions that start the smart rule) with actions (what happens when the condition is met). You can trigger actions based on device values (temperature, motion, button presses, etc.) or based on time schedules.

Think of it as a customizable cause-and-effect smart rule: “If the temperature drops below 20 degrees, then turn on the heater.” You define the “if” (trigger) and the “then” (action).

When to use this smart rule

Use the Condition smart rule when you want to:

  • React to device changes — turn on lights when motion is detected, send a notification when a door opens, activate ventilation when CO2 is too high.
  • React to time events — turn on garden lights at sunset, switch off heating at 23:00, run different schedules on weekdays and weekends.
  • Combine conditions with actions — set up multiple triggers, each with its own set of actions.

A single Condition smart rule can contain multiple triggers. Each trigger has its own condition and its own set of actions. The first trigger whose condition is met “wins” — its actions are executed. This lets you build smart rules like: “If temperature < 18, turn on heater at high; if temperature < 20, turn on heater at low; otherwise, turn off heater.”

Getting started

Basic example

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

  1. Create a new Condition smart rule.
  2. The smart rule starts in Device value mode (the default).
  3. In the Input devices section, tap Add Device and select your motion sensor.
  4. In the Triggers section, tap Add trigger to create the first trigger.
  5. On the trigger configuration page:
    • Triggered by: select Motion.
    • When: select Value equals.
    • Value: select Motion spotted.
    • In the Actions section, tap Add New Action, select the hallway light, and set the action to turn it on.
  6. Go back and tap Add trigger for the second trigger.
  7. Configure it the same way, but select Motion cleared as the value and set the action to turn the light off.
  8. Tap Save.

The hallway light now turns on when motion is detected and turns off when motion stops.

Trigger modes

Every Condition smart rule operates in one of two modes:

Device value mode

The smart rule monitors one or more devices and triggers actions based on their values. You select which devices to monitor and configure trigger conditions for specific device values (temperature, humidity, digital output, etc.).

This is the default mode when creating a new smart rule.

Time mode

The smart rule triggers actions at specific times or during time intervals. No input devices are needed — the schedule itself is the trigger.

You can switch modes using the radio buttons at the top of the smart rule configuration page.

Device value triggers

When in Device value mode, you first select one or more input devices, then create triggers that monitor those devices.

Selecting input devices

Tap Add Device to add one or more devices you want to monitor (all devices you add must be of the same type). All triggers in this smart rule will evaluate against these devices. You can choose whether it is enough for any one device to satisfy the condition or all of them must satisfy it at the same time (see “All devices must fulfill the state” below).

Configuring a trigger

Tap Add trigger or tap an existing trigger to open the trigger configuration page. The page has several sections:

Value type

Select which device value to monitor. The available options depend on your selected devices. Common value types include:

Value typeExample use
TemperatureMonitor room temperature
HumidityMonitor humidity levels
MotionDetect movement
BrightnessReact to light levels
Reed ContactDetect door/window open/close
CO2Monitor air quality
Button pressedReact to button presses
ValueMonitor blinds or dimmer level

The full list depends on the devices you have selected.

Trigger type

Select how the value should be evaluated. Trigger types fall into two categories: State triggers and Event triggers.

  • State triggers remain active as long as the condition is true.
  • Event triggers fire instantly and do not have a duration.

Only State triggers can use Hold actions.

State triggers

State triggers remain active as long as the condition is true. They are re-evaluated every time the device value changes.

Comparison:

Trigger typeMeaning
Value equalsValue is exactly equal to the threshold
Value doesn't equalValue is anything except the threshold
Value is greater thanValue is above the threshold
Value is greater than or equalsValue is at or above the threshold
Value is less thanValue is below the threshold
Value is less than or equalsValue is at or below the threshold

Range:

Trigger typeMeaning
Value is within intervalValue is between two endpoints
Value is outside of intervalValue is outside two endpoints

Presence and error status:

Trigger typeMeaning
Has valueDevice is reporting a value
Has no valueDevice value is unknown/unavailable
Has warningDevice has a warning
Has errorDevice has an error
Has warning or errorDevice has a warning or error
Has no warningDevice has no warning
Has no errorDevice has no error
Has no warning or errorDevice has no warning or error

Event triggers

Event triggers fire once when a specific change occurs. They do not remain active — they detect transitions.

Value changes:

Trigger typeMeaning
Value changedAny value change occurred
Value changed toValue changed to a specific value
Value changed fromValue changed from a specific value

Threshold crossings:

Trigger typeMeaning
Value rose aboveValue increased past the threshold
Value rose above or equalsValue increased to or past the threshold
Value fell belowValue decreased past the threshold
Value fell below or equalsValue decreased to or past the threshold

Range transitions:

Trigger typeMeaning
Value fell within intervalValue entered the range
Value fell outside of intervalValue left the range

Presence transitions:

Trigger typeMeaning
Got valueDevice started reporting a value
Lost valueDevice stopped reporting a value
Got warningDevice entered warning state
Got errorDevice entered error state
Got warning or errorDevice entered warning or error state
Lost all warningsDevice exited warning state
Lost all errorsDevice exited error state
Lost all warnings or errorsDevice exited all warning/error states

Device-specific events:

Trigger typeMeaning
Value isA device-specific event occurred (e.g., button pressed)

Value / value interval

Depending on the trigger type, you will see a field to enter either a single threshold value or a range (start and end values).

Additional settings (device value triggers)

The trigger configuration page includes an Additional settings section with advanced options. Which settings appear depends on the trigger type and your setup.

All devices must fulfill the state

Visible when you have more than one input device selected and the trigger is a State trigger.

  • Off (default): The trigger fires when any of the selected devices meets the condition.
  • On: The trigger fires only when all selected devices simultaneously meet the condition.

Delay

Postpones the action by a specified time after the trigger condition is met. The delay behaves very differently depending on the trigger type:

  • State trigger + delay = the condition must remain continuously true for the entire delay period. If the condition becomes false during the delay, the delay is cancelled and the action never fires. Use this to filter out brief fluctuations.
  • Event trigger + delay = the event is queued and the action fires after the delay expires, no matter what. The delay simply postpones execution.

Delay queue (Event triggers only)

When using delay with Event triggers, a queue stores pending events. You can set the queue size from 1 to 10.

  • Events are processed in order (first in, first out).
  • If the queue is full, new events are silently dropped.

If events arrive faster than the delay period allows them to be processed, and the queue is full, additional events will be lost. Increase the queue size or reduce the delay if this is a concern.

Minimum duration (State triggers only)

Once the action fires, it stays active for at least this duration — even if the trigger condition becomes false before the timer expires. When the minimum duration elapses, the smart rule re-evaluates the condition. If it is still false, the action is removed. If the condition is true again, the action continues normally.

Use this to guarantee a minimum action time. For example, “when motion is detected, keep the light on for at least 5 minutes” — even if the motion sensor goes back to idle after 30 seconds, the light will stay on for the full 5 minutes.

Maximum duration (State triggers only)

After the action has been active for this duration, it automatically deactivates. The trigger returns to an inactive state regardless of whether the condition is still true. Use this for time-limited actions — for example, “keep the fan running for a maximum of 30 minutes.”

Hysteresis (comparison triggers only)

Available for Value is greater than, Value is greater than or equals, Value is less than, and Value is less than or equals trigger types. Prevents rapid on/off switching when a value fluctuates around the threshold.

Hysteresis creates a “dead band” around the threshold. The trigger will not switch off until the value moves past the dead band in the opposite direction.

Modes:

ModeDead band placementUse case
+/-Equally above and below the thresholdGeneral purpose
+Above the threshold onlyHeating control
-Below the threshold onlyCooling control

Example: Threshold = 22 degrees, Hysteresis = 1 degree, Mode = +/-

  • Trigger turns ON when value drops below 21 degrees (threshold minus hysteresis).
  • Trigger turns OFF when value rises above 23 degrees (threshold plus hysteresis).
  • Between 21 and 23 degrees, the trigger maintains its current state.

Time triggers

When in Time mode, you configure time-based triggers instead of device-based ones.

Configuring a time trigger

Tap Add trigger to create a time trigger. The trigger configuration page shows:

Time frame

Select the time period that defines when the trigger repeats:

Time frameMeaning
DayRepeats daily
WeekRepeats on selected days of the week
Workday/WeekendSeparate schedules for workdays and weekends
MonthRepeats on selected days of the month
YearRepeats on selected dates of the year

Mode

Choose between two modes:

Instant: The trigger fires at a specific point in time. Use this for one-shot actions like “turn on lights at sunset.”

Interval: The trigger is active during a time range (from start to end). Actions are applied when the interval begins and removed when it ends. Use this for actions that should last for a period, like “keep porch lights on from 18:00 to 23:00.”

Start time (and end time)

Tap the time picker to configure the exact time. For intervals, you configure both start and end times.

The time configuration sub-page offers additional options depending on the selected time frame:

  • Day: Set a clock time, or use Sunrise/Sunset with an offset.
  • Week: Choose which day of the week plus the time.
  • Workday/Weekend: Automatically selects workdays or weekend days.
  • Month: Choose which day of the month plus the time.
  • Year: Choose which month and day plus the time.

When using Sunrise or Sunset, you can add an offset from -4 hours to +4 hours. This is useful for triggers like “30 minutes before sunset” or “1 hour after sunrise.”

Actions

Each trigger has its own list of actions that execute when the trigger’s condition is met. Actions define what happens — which devices to control and how.

Hold action vs One-time action

Actions come in two types:

  • A Hold action continuously controls the target device as long as the trigger is active.
  • A One-time action only affects the target device at the moment when the trigger is activated.

If your action is “turn on the light”, Hold action would override any attempt of lower priority smart rules to turn the light off until the trigger expires, while a One-time action would turn the light on once but allow other smart rules to freely change its state later.

Which type is available depends on the trigger:

  • Event trigger actions are always One-time action. Since the event fires instantly, there is nothing to “hold.”
  • State trigger actions default to Hold action, but you can switch to One-time action. By default the action configuration shows a simplified view. Tap the Show more button to reveal the Action type section, where you can choose between Hold action and One-time action.

Use a One-time action on a State trigger when you want the trigger condition to start something without locking the device. For example, a State trigger “temperature above 25 degrees” with a One-time action “turn on fan” will turn the fan on once when the temperature exceeds 25, but will not prevent other smart rules (even with lower priority) from turning the fan off while the temperature is still above 25.

Adding actions

On the trigger configuration page, tap Add New Action in the Actions section. Select a target device, then configure what the device should do (turn on, turn off, set to a specific value, etc.).

You can add multiple actions to a single trigger. For example, a single “motion detected” trigger could turn on a light, set a thermostat to 22 degrees, and close the blinds.

Notifications

Tap the bell icon in the Actions section header to add a notification action. Notifications are sent as push messages to selected users or user groups when the trigger fires.

Notification messages can include dynamic content using script constants:

  • SmartRuleName — the name of this smart rule.
  • LocationName — your installation name.
  • DeviceName — the name of the device that triggered the smart rule (Device value mode only).

Managing actions

Each action in the list shows the target device name and a summary of the configured action. Tap the three-dot menu on any action to:

  • Edit — modify the action configuration.
  • Remove — delete the action.
  • Rename — rename the action.

Multiple triggers

A single Condition smart rule can have multiple triggers. Each trigger has its own condition and its own actions. This is how priority works:

  1. All triggers are evaluated every time a device value changes (or a time event occurs).
  2. The first trigger whose condition is currently true “wins.”
  3. Only the winning trigger’s actions are executed.
  4. Other triggers still update their internal state, but their actions are not applied.

This first-match-wins behavior means trigger order matters. The trigger listed first has the highest priority.

Triggers are displayed with numbered icons (1, 2, 3, …). State triggers show a filled circle, Event triggers show an outlined circle.

Tap the three-dot menu on any trigger to:

  • Edit — open the trigger configuration.
  • Duplicate actions — copy this trigger’s actions into one or more other triggers in the same smart rule.
  • Remove — delete the trigger.

Examples and scenarios

Temperature control with hysteresis

Goal: Turn on a heater when the room gets cold, with hysteresis to prevent rapid cycling.

ParameterValue
ModeDevice value
Input deviceTemperature sensor
Trigger 1 typeValue is less than
Trigger 1 value20 degrees
Trigger 1 hysteresis1 degree, Mode: +
Trigger 1 actionTurn on heater (Hold action)
Trigger 2 typeValue is greater than or equals
Trigger 2 value21 degrees
Trigger 2 actionTurn off heater

Behavior: The heater turns on when the temperature drops below 20 degrees. Thanks to hysteresis in + mode, trigger 1 stays active until the temperature rises above 21 degrees (20 + 1 = 21). The heater then turns off. It will not turn back on until the temperature drops below 20 again. This prevents the heater from cycling on and off when the temperature hovers around 20 degrees.

Motion-activated light with delay

Goal: Turn on lights when motion is detected, and turn them off 5 minutes after motion stops.

ParameterValue
ModeDevice value
Input deviceMotion sensor
Trigger 1 typeValue equals
Trigger 1 valueMotion spotted
Trigger 1 actionTurn on light (Hold action)
Trigger 2 typeValue equals
Trigger 2 valueMotion cleared
Trigger 2 delay5 minutes
Trigger 2 actionTurn off light

Behavior: When motion is detected, the light turns on immediately (trigger 1). When motion stops, trigger 2 starts a 5-minute delay. If motion is detected again during those 5 minutes, the delay is cancelled (the condition “no motion” becomes false) and trigger 1 takes over again. The light only turns off if no motion is detected for a full 5 minutes.

Motion light with minimum duration

Goal: Turn on lights when motion is detected, and keep them on for at least 10 minutes even if motion stops.

ParameterValue
ModeDevice value
Input deviceMotion sensor
Trigger 1 typeValue equals
Trigger 1 valueMotion spotted
Trigger 1 Minimum duration10 minutes
Trigger 1 actionTurn on light (Hold action)
Trigger 2 typeValue equals
Trigger 2 valueMotion cleared
Trigger 2 actionTurn off light

Behavior: When motion is detected, the light turns on immediately and the 10-minute minimum duration timer starts. If motion stops after 2 minutes, the light stays on — the minimum duration guarantees at least 10 minutes. When the timer expires, the smart rule re-evaluates. If there is still no motion, trigger 2 wins and the light turns off. If motion has resumed, trigger 1 continues and the light stays on.

Daily blinds and lights automation

Goal: Automatically manage blinds and lights throughout the day — open blinds after sunrise, close blinds and turn on lights near sunset, and turn off lights at bedtime.

ParameterValue
ModeTime
Trigger 1 time frameDay
Trigger 1 modeInstant
Trigger 1 start timeSunrise + 30 minutes
Trigger 1 action 1Open living room blinds
Trigger 1 action 2Open bedroom blinds
Trigger 2 time frameDay
Trigger 2 modeInstant
Trigger 2 start timeSunset - 15 minutes
Trigger 2 action 1Close living room blinds
Trigger 2 action 2Close bedroom blinds
Trigger 2 action 3Turn on living room lights
Trigger 3 time frameDay
Trigger 3 modeInstant
Trigger 3 start time23:00
Trigger 3 action 1Turn off living room lights

Behavior: Each morning, 30 minutes after sunrise, both sets of blinds open. Shortly before sunset, the blinds close and the living room lights turn on. At 23:00, the lights turn off. Since all triggers use Instant mode, each action fires once at the specified time (One-time action). The Sunrise and Sunset times adjust automatically throughout the year based on your location.

Weekday vs weekend schedule

Goal: Run different heating schedules on workdays and weekends.

ParameterValue
ModeTime
Trigger 1 time frameWorkday/Weekend
Trigger 1 modeInterval
Trigger 1 start06:00 (Workday)
Trigger 1 end08:00 (Workday)
Trigger 1 actionSet thermostat to 22 degrees
Trigger 2 time frameWorkday/Weekend
Trigger 2 modeInterval
Trigger 2 start08:00 (Weekend)
Trigger 2 end10:00 (Weekend)
Trigger 2 actionSet thermostat to 22 degrees

Behavior: On workdays, heating starts at 06:00. On weekends, it starts at 08:00. Both schedules turn off the heating boost after 2 hours.

Deleting a smart rule

To delete the smart rule, scroll to the bottom and tap the Uninstall button, or use the three-dot menu at the top and select Uninstall. A confirmation dialog will appear before the smart rule is permanently deleted.