Automations

Automations

An automation is a rule the house follows on its own: When something happens, If the circumstances are right, Then do these actions. Open them from Configuration → Automations.

The rule model

• When — the triggers. If there are several, any one of them starts the rule (OR).
• If — the conditions, checked before the actions run. Optional: "without conditions, the automation runs on every trigger". Under All conditions must be: you choose whether all conditions must be true (AND) or any one of them (OR).
• Then — the actions, executed in order.

Triggers — what starts the automation

Tap Add a trigger and choose:

📘 Note: The Weather Forecast and Energy Price triggers appear only when the corresponding service is enabled on the server (see “Weather Service”, “Energy Price Service”).

Conditions — checked before the actions run

Tap Add a condition and choose:

• Device State — a device's current value compared to a threshold.
• Time Range — only between a start and end time, optionally on selected days.
• Date range — a period of the year ("a season — from 15 June to 15 Sept."). If the end date comes before the start date, the range crosses into the next year. Choose Repeat every year or limit it to one year.
• Astronomical — only between two sun events, for example after sunset and before dawn (select a start and a stop event). The builder shows today's times.
• Weather Forecast — a forecast check over a window (Current, Next 1/3/6/12/24 hours, Tomorrow) with an Aggregation (Average, Minimum, Maximum, Any, All).
• Energy Price — the price over a window (Current Hour, next hours, Today, Tomorrow), either Absolute (above/below/between a value) or Statistical (Below Average, In Cheapest N Hours, percentile…).

Actions — what the automation does

Tap Add an action and choose:

• Device Control — set a device parameter to a value. On a thermostat, the Boost parameter starts a boost of 30 min, 1 h, 2 h or 3 h (or Stop boost).
• Scenario — run an existing scenario.
• Global Command — lights or shutters of a whole Room or Category at once.
• Notification — send a push notification to the app.
• E-mail — send an e-mail with a custom subject and message to HyperVisu users. Requires the Email service (see “Email Service”) — the option is greyed out until it is configured. You choose the recipients, the channel (push or e-mail) and a priority.

Every action has an optional Delay before execution in seconds, shown as a chip on the action ("delays this action after the previous one").

Managing automations

From the Automations list:

• Active toggle — enable or disable a rule without deleting it.
• Trigger Automation — a test run: "This will execute only the actions and bypass all conditions."
• Duplicate — copy a rule to build a variant.
• Each row shows its trigger/condition/action counts, its next run (for time-based triggers) and its last run.
• Every automation can have its own icon (Choose an icon).

---

Automation & scenario vocabulary reference

The complete vocabulary of the rule editor and scenario schedules (see “Scenarios”), as compact tables.

Triggers (WHEN)

A rule fires when any one of its triggers fires — multiple triggers combine as OR.

Conditions (IF)

Conditions are checked after a trigger fires; the rule runs only if they pass. Conditions combine with AND / OR operators.

Actions (THEN)

Every action can carry an optional delay in seconds before it executes.

Astronomical events

The 13 sun events, computed daily from the server's coordinates (see “Network & Time Settings”). Every astronomical trigger accepts a ± offset in minutes.

Scenario schedules