General
The basic settings for each device include the activation status (on/off) and a name under which all alarms and warnings reported by this device are displayed. This should be as clearly descriptive as possible in order to distinguish the devices.
By selecting the higher-level alarm group, the device is assigned to the system hierarchy.
Alarms are signaled in the higher-level alarm group.
The OID and SNMP host specified when adding can be edited, as well as the cycle in which data is retrieved.
The alarm delay specifies how long a device should delay the signaling of an alarm after it has been detected. E.g.: With an alarm delay of 30s, the device waits 30 seconds until the alarm is signaled and reported.
Alarm evaluation
The alarm evaluation differs depending on the type of sensor:
- Threshold values can be specified for Min, Max and Min/Max, above which alarms/warnings are triggered. The unit of the value, the conversion factor and the number of decimal places displayed can also be set
- For logic, you can specify whether an alarm should be triggered if the result is open or closed
- A list of values that trigger an alarm/warning can be specified for Alarm-if
An alarm assignment is always selected regardless of the type.
Depending on the alarm assignment set, a monitored value can always or only trigger an alarm when armed and then sends an alarm to all users who have authorization for the device (the assignment is made via the alarm groups) and notifications for the alarm type. In principle, all alarm assignments can always trigger alarms. The only exceptions to this are “Arm-active” (alarm only if the higher-level alarm group has been armed) and “Display only” (no alarm evaluation takes place).
| Name | API value | Description |
|---|---|---|
| From | off | The alarm is deactivated for this input and the status/measured value is not updated. |
| Sharp-Active | armed-active | If the higher-level alarm group has been armed, alarms can be triggered. The status/measured value of the input is updated. |
| Permanently active | always-active | Alarms can be triggered independently of the switching status of the alarm group. The status/measured value of the input is updated. |
| fire | fire | Alarms can always be triggered. These are reported as fire alarms. |
| Sabotage | sabotage | Alarms can always be triggered. These are reported as sabotage/intrusion alarms. |
| System message | system | Alarms can always be triggered. These are reported as a system message. |
Webhooks
Webhooks in KentixONE offer the option of sending an HTTP request to an external server when an event occurs. Each webhook can be assigned the types of alarms or warnings for which it should be sent.
Webhooks also offer the option of mapping functions via the KentixONE SmartAPI that are not available via the standard configuration.
For example, if a fire alarm occurs, the switching outputs of an AccessManager could be activated to unlock the connected motorized locks.