4.25Automation

Automation runs a sequence when a trigger arrives on the KNX bus: a list of steps that either write a KNX value or pause. This page lists every field of the Configure Automations dialog, how it runs, and when to choose it over the Rule gateway or Logic Studio.

#What it does

Each automation has one trigger (a KNX group address and an optional value) and a list of steps. When the trigger arrives, the gateway runs the steps from top to bottom: Send KNX Value writes a value to a group address, Pause waits. Typical uses are a scene that switches several groups one after the other, a pulse that switches something on and off again after a time, and a sequence with delays between devices.

#Which service to use

Automation is the simplest way to run a fixed sequence with pauses. It has no conditions other than the trigger value.

#Before you enable it

• The service is Disabled by default. Turn Enabled on and deploy the project (see Deploying to a gateway). Each automation also has its own Enabled switch.
• The gateway listens to and writes the bus through its KNX connection, so the KNX engine must be working.

#Settings

#Automations Editor

The editor has two parts: the list of automations with their details at the top, and the steps of the selected automation below. Both lists have Add, Clone, Remove, Up and Down. Import and Export in the header save and load all automations as automations.json; importing replaces the whole list. Cancel and Save Changes only close the dialog.

#Rule Details

#Steps

A new automation has one step. Each step list entry reads Send 1 -> 1/1/5 or Pause 2 s.

#How it works on the gateway

• The gateway watches incoming KNX write telegrams. A response to a read request does not start an automation.
• A telegram starts an automation when its group matches Trigger Group and, unless Trigger Value is blank, its value equals the Trigger Value. Numbers are compared as numbers.
• The steps run one after another. Each write is sent to the bus before the next step starts. A Pause waits the set time.
• On Retrigger decides what a second trigger does to a running sequence. Restart from beginning stops the running one and starts again. A pause that is already waiting finishes its time first. Ignore while running leaves the running sequence alone. Cancel without restarting stops the running sequence and does not start a new one.
• If a step writes to the automation's own trigger group, the gateway ignores that echo for about 1.5 seconds so the automation does not start itself. Do not rely on this for other automations: a write to the trigger group of a different automation does start it.
• A sequence that is running when the gateway restarts is lost.

#Example

A "pulse" that switches a gate relay on for 2 seconds and then off:

1. Enable Automation and add an automation: Name Open gate, Trigger Group 4/1/1, Trigger Data Type DPT 1.001, Trigger Value 1, On Retrigger Ignore while running.
2. Step 1: Send KNX Value, Group Address 4/1/2, Data Type DPT 1.001, Value 1.
3. Step 2: Pause, Duration 2 s.
4. Step 3: Send KNX Value, Group Address 4/1/2, Data Type DPT 1.001, Value 0.
5. Deploy. A push button that writes 1 to 4/1/1 pulses 4/1/2 for 2 seconds. A second press during the pulse is ignored.

#Tips and common problems

• Nothing happens: the service or the automation is disabled, the Trigger Group is empty or different from the group on the bus, or the Trigger Value does not match the telegram. Clear the Trigger Value to test.
• The sequence starts twice: the trigger group is also written by one of your own steps or by another automation. Use a separate trigger group.
• A conditional action is needed: Automation has no conditions beyond the trigger value. Use the Rule gateway or Logic Studio.
• It must start at a set time: Automation has no time-of-day trigger of its own. It starts only from a KNX write telegram.

#See also

• Rule gateway
• Logic Studio
• Scene
• KNX engine