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". With one condition there is nothing to choose. From the second condition on, a control appears at the top of IF: All true requires every condition (AND), Any true requires one of them (OR).
• Then — the actions, executed in order.

The triggers, conditions and actions you add are only a draft until you tap Save. The button stays dimmed while the rule has no name, no trigger or no action. A new rule is created with Enabled on.

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”).

📘 Note: The Weather Forecast and Energy Price triggers fire on the change, not for as long as the check stays true. A trigger set to In Cheapest N Hours with 3 fires at the moment the current hour becomes one of the three cheapest: once if the three hours follow each other, up to three times a day if they are apart. The first check after you save or edit the rule, and after a server restart, only records the situation and runs nothing — a rule saved in the middle of a cheap hour waits for the next time a cheap hour begins.

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, with a Title and a message, to the HyperVisu app of the users you select.
• E-mail — send an e-mail with a custom Subject and Message to HyperVisu users. Requires the Email service (see “Email Service”): the E-mail action is absent from the list until that service is switched on.

Only administrators choose the recipients; a notification or an e-mail created by another user is sent to that user alone.

⚠️ Warning: Always select the recipients. An E-mail action with no recipient selected is sent to every user who has an e-mail address.

Every action has an optional Delay before execution in seconds, shown as a chip on the action. The delay is counted from the moment the automation runs, not from the previous action: two actions with delays of 10 s and 30 s run 10 and 30 seconds after the start.

Managing automations

The Automations list counts the rules and the active ones in its header. Each row shows the rule's name, a one-line summary of its first trigger, a copy icon and a switch. Tap a row to open the rule.

• Pause a rule — turn off the switch on its row. This is saved at once and the rule stays in the list. The Enabled switch inside a rule does the same, but only once you tap Save.
• Trigger — a button in the editor of a saved rule. It runs the saved actions at once, without confirmation, and skips every condition: "This will execute only the actions and bypass all conditions". If you changed the rule, tap Save and reopen it first.
• Duplicate — tap the copy icon on the row. The copy is saved at once, named with "(copy)", and arrives switched off.
• Delete — open the rule, tap the bin in its header and confirm. A deleted rule cannot be restored.
• Every automation can have its own icon (Choose an icon).

⚠️ Warning: Trigger is not a simulation: devices move, scenarios run, notifications and e-mails are sent. It tests the actions only — only the real trigger checks the conditions. A rule that is switched off is not run, although the app still shows "Automation triggered".

📘 Note: A rule with a Manual trigger that you run from the home screen's Manual Automations section or from a view still checks its conditions, unlike Trigger in the editor.

The list shows neither a last run nor a next run, and the app has no run history per rule. The "last run" line under a rule's name in the editor is not reliable. To see what a rule did, an administrator opens the Activity of a device the rule controls in the admin panel (see “Device Activity Log”).

---

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. From the second condition on, All true (AND) or Any true (OR) applies to the whole list.

Actions (THEN)

Every action can carry an optional delay in seconds before it executes. The delay is counted from the start of the run, not from the previous action.

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