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.
ekey interface #
The interface that receives the ekey messages must be selected here. This field must be filled in. Only ekey interfaces are permitted.
Settings for the ekey message #
These settings control which messages this ekey trigger responds to.
Recognized/approved: General message type to which the system reacts.
ekey device: Id of the device from which the message comes. This field can be empty, in which case the device is not taken into account and the trigger reacts to messages from all devices.
ekey user: Id of the user in ekey. This field should be filled in when a finger is selected. If no user is specified, the trigger applies to all users! The user is not used for digital inputs.
Finger/input: Finger that triggered the message or digital input. Depending on the selection here, a user should be specified or not. The field should be empty if “Not recognized” is to be responded to.
Detail: A detail code generated by ekey specifies an error reason more precisely. If the field is set to “Ignore”, the detail code is not taken into account. The detail code can be used to react to very specific errors in a fine-grained manner; for most use cases, the detail code can be ignored.
