Leakage Sensor (Ethernet)
The Leakage Sensor is used for early detection of moisture or leaking water. Depending on the model, cable sensors (longer distances) and/or point sensors (specific locations) can be evaluated. The configuration areas are described below.
General
The basic settings of each device include the activation state (On/Off) as well as a name under which all alarms and warnings reported by this device are displayed. This should be chosen as uniquely descriptive as possible to be able to distinguish between devices.
Alarm Group
By selecting the parent alarm group, the device is integrated into the system hierarchy.
Alarms are signaled in the parent alarm group.
In the general settings, you assign the display name, enable/disable the device, and assign it to an alarm group. Optionally, you can add a description.
Connection
Connection monitoring enables alarming when the device is not reachable.
| Alarm Assignment | Selection of the alarm assignment |
| Output as Warning | Connection loss does not trigger an alarm and is only reported as a warning. |
Connection monitoring triggers a message in case of unreachability. Through the alarm assignment, you decide whether the connection loss is treated as an alarm or, with the "Output as warning" option enabled, only as a warning.
Tamper
Configure the device's response to vibrations or tilting and choose the mounting position. Excessive sensitivity can lead to false alarms – adjust the values to suit the installation situation.
Leakage Monitoring (1)
Set up the monitoring of measurement points. For each sensor cable, you can specify the operating mode (e.g., permanently active), adjust sensitivity, and define texts for OK and alarm statuses.
Leakage Monitoring (2)
In addition to Sensor Cable 2, a point sensor can be configured. Here as well, operating mode, sensitivity, and individual descriptions for OK/alarm are available.
Webhooks
Webhooks in KentixONE provide the ability to send an HTTP request to an external server when an event occurs. System-wide Webhooks can be created for this purpose. Such a webhook can be assigned to any number of events.
Webhooks also provide the possibility to implement functions via the KentixONE SmartAPI that are not available through the standard configuration.
For example, when a fire alarm occurs, the switching outputs of an AccessManager could be activated to unlock the connected motor locks.
Events
| Name | Description |
|---|---|
| All Alarms | The webhook is sent for every alarm that occurs. |
| Armed-Active Alarms | When an armed-active alarm occurs, the webhook is sent. |
| Always-Active Alarms | When an always-active alarm occurs, the webhook is sent. |
| Fire Alarms | When a fire alarm occurs, the webhook is sent. |
| Sabotage Alarms | When a sabotage alarm occurs, the webhook is sent. |
| System Messages | When a system message is triggered, the webhook is sent. |
| Before Arming | The webhook is sent when an alarm group is to be armed.(1) |
| After Arming | The webhook is sent after an alarm group has been armed. |
| Before Disarming | The webhook is sent when an alarm group is to be disarmed.(1) |
| After Disarming | The webhook is sent after an alarm group has been disarmed. |
| Change of Switching Status (Arming or Disarming) | When the alarm group is switched, the webhook is sent. |
| Cyclical (5 Min, 10 Min, 15 Min, 30 Min) | The webhook is sent cyclically. |
(1) The webhook is sent when a switching command is triggered either by a user or by automatic arming. Example: (Dis-)Arming command by user → Webhook is sent → (Dis-)Arming is executed
Using webhooks, HTTP requests can be sent to external systems for events (e.g., leakage alarm or warning).