A trigger that reacts to the “age” of the value of one or more channels. If a value has not been updated for longer than the set time (whether by reading/writing), the trigger is activated. For example, you can monitor whether an operating mode is regularly reported or whether an interface regularly receives data.

Id #

The number under which the trigger is saved internally. This field is only for viewing and is empty when you create a new trigger.

Name #

The name of the trigger.

Comment #

The comment field is for free use by the integrator/system administrator. It is used exclusively to document the configuration. Information can be entered here, e.g. the purpose of the element, comments on the connected hardware, room/floor and other special features. The content of this field is irrelevant for X2.

Dead time #

A period of time that suppresses the re-triggering of this trigger after it has been triggered. You can use the dead time to suppress multiple triggering if the triggering event occurs again within this time.

An example would be if you trigger an action, e.g. when a doorbell is pressed, and do not want this action to take place several times if the visitor rings the doorbell several times. In this example, you use the dead time to determine the minimum time that must elapse after the first ring before the doorbell is answered again.

Max. age #

A maximum time for how old the value of a channel may be. If the value of a channel has not been updated for longer, the trigger is activated.
The minimum possible value is 1 second (smaller values are interpreted internally as 1 second). However, times >= 1 minute make sense in most applications.

Remarks #

This trigger only triggers on the first channel whose value exceeds the set age – in order for it to trigger again, the values of all channels must fall within the age limit again at the same time.
The trigger has a fixed, internal trigger lock that blocks triggering for approx. 1 minute after system start in order to prevent it from being triggered incorrectly during the initialization phase.