Id
The number under which the trigger is stored internally. This field is read-only and empty when you create a new trigger.
Name
The name of the trigger.
Comment
The comment field is available for free use by the integrator/system administrator. It serves solely to document the configuration. You can enter information here, e.g. the purpose of the element, notes on the connected hardware, room/floor and other special features. The content of this field has no significance for X2.
Dead Time
A period of time during which re-triggering of this trigger is suppressed after it has fired. The dead time allows you to suppress multiple triggering if the triggering event occurs again within this time.
One example is when you trigger an action, e.g. when a doorbell is pressed, and do not want this action to occur multiple times if the visitor rings repeatedly. In this example, the dead time determines the minimum time that must elapse after the first ring before the system responds to ringing again.
ekey Interface
Select the interface that receives the ekey messages here. This field is mandatory. Only ekey interfaces are permitted.
ekey Message Settings
These settings control which messages this ekey trigger responds to.
Recognized/Permitted: General message type to respond to.
ekey device: Id of the device the message comes from. This field can be left empty; in that case the device is not taken into account and the trigger responds to messages from all devices.
ekey user: Id of the user in ekey. This field should be filled in if 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 or should not be specified. The field should be empty if the trigger is to respond to "Not recognized".
Detail: A detail code generated by ekey that 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 respond in a fine-grained manner to very specific errors; for most use cases, the detail code can be ignored.