Define Actions

The actions determine what an automation does when it triggers and all conditions are met. In the editor they are listed under THEN the following actions are executed. Scenes use the same editor for their actions.

Steps to define an action:

1. Add action:
   • Click "Add your first Action". The Actions window opens. Add every further action with AND below the list.
2. Grouping and search:
   • As with the triggers, the dropdown at the top of the window determines how devices are grouped (Platform, Device Type, Room or Zone). The search field next to it finds devices, group addresses and variables.
3. Select the action:
   • The actions are listed under KNX Group Addresses, Platforms, System and Variables (see the table below). Clicking an entry adds it and closes the window. With Multiple Selection enabled, the window stays open so you can add several actions in a row.
4. Set the value:
   • Set the value on the right of the action's row, e.g. On or Off, a number, a text or a scene from the list. For numbers, the field shows the permitted range as a placeholder if the device specifies one. As long as a value is invalid, Save is disabled.
5. Change the order:
   • Drag an action to another position with the mouse. On narrow screens (up to 768 pixels wide) dragging is turned off.
6. Remove an action:
   • The × on the right of the row removes the action.

Action types

Entry in the window	What the action does	Setting
Platforms → device	Sets a property of the device, e.g. switching, brightness or position.	Depending on the property On/Off, a number, a text, a colour picker or a selection list. Commands without a value have no field.
KNX Group Addresses → group address	Sends a value to the KNX group address.	Field matching the datapoint type, e.g. time, date or a selection.
System → Delay	Waits before the following actions are executed.	½ Second to 60 Minutes; the default is 3 Seconds.
System → Wake On LAN	Sends a Wake-on-LAN packet as a broadcast to the local network to switch on a computer.	MAC address of the computer (12 hex digits, separators are ignored).
System → Services → Enable / Disable	Switches a service of the Controller on or off.	Cloud, Remote Access or Support VPN – only the services the Controller offers.
System → Scene	Runs a scene.	Scene from the list, split into Visible and Hidden.
System → Automation → Enable / Disable	Switches an automation on or off.	Automation from the list.
System → Schedules → Enable / Disable	Switches a schedule on or off.	Schedule from the list.
System → Notification	Sends a notification.	Notification from the list, split into E-Mail, Push Notification and Log Message.
Variables → variable	Sets the value of a variable.	On/Off for On/Off variables, a date or time field for Date and Time, otherwise a text field.

Scene, Automation, Schedules and Notification only appear once at least one scene, automation, schedule or notification exists. Add New Variable at the end of the variables asks for a name and a value, creates the variable straight away and adds the action.

Taking the value from another device

For numbers and texts, a + (Add Reference) sits next to the field. With it, the action sets the value of another device, a KNX group address or a variable instead of a fixed value. The × in the reference removes it again. In scenes, only variables are offered as a reference.

Order and delay

The actions are executed from top to bottom. A Delay pauses the sequence: the actions below it only follow once the time has elapsed.

• Example ventilation: action "Ventilation On", Delay 10 Minutes, action "Ventilation Off". The ventilation runs for ten minutes and then switches off.

The Delay only works within the actions. If the actions should only start after a waiting time, or only when a state lasts long enough, use the conditions Run-on time and Minimum duration.

Negative actions

Negative actions are executed when the automation is evaluated but the triggers or conditions are not met. An automation is evaluated as soon as one of its triggers reports.

1. Turn on negative actions:
   • Below the actions, click Enable Negative Actions. The section ELSE as a result of a failed condition, the following actions are executed. appears below.
2. Add a negative action:
   • Click "Add your first Negative Action"; add further ones with AND. The same types are available as for the actions; here the Delay defaults to 1 Second.
3. Turn them off again:
   • Disable Negative Actions hides the section. The negative actions are then discarded when you save.

• Example motion light: trigger "Motion detected", action "Light On", negative action "Light Off". When the motion detector no longer reports motion, the light goes off.

WARNING

Good to know:

• If Only trigger if the reported values are different. is enabled, the negative actions only run when the result changes from "met" to "not met". Without this option they can run again on every report of a trigger as long as the result is not met.
• As soon as the automation has a trigger under Time (e.g. Daily or Interval), Enable Negative Actions is hidden. A time trigger drops back right after it fires, so the negative actions would run every time.
• With a Minimum duration, the negative actions are executed as soon as the state ends, even if the minimum duration was not reached.
• If a saved automation has negative actions, the section is visible when you open it and the button is hidden. To remove the negative actions, delete them one by one with ×.
• Scenes have no negative actions.

Deleted devices

If a device was deleted or no longer has the property, the row shows This device no longer exists. or This function is no longer available. The action stays in the list until you remove it with ×.