> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/~/changes/vPSzQFfkdJCVWGT5AL1m/inbound-integrations/kentix-am.md).
# Kentix AlarmManager
## In ilert: Create a Kentix AlarmManager alert source
1. Go to **Alert sources** --> **Alert sources** and click on **Create new alert source**
2. Search for **Kentix AlarmManager** in the search field, click on the Kentix AlarmManager tile and click on **Next**.
3. Give your alert source a name, optionally assign teams and click **Next**.
4. Select an **escalation policy** by creating a new one or assigning an existing one.
5. Select you [Alert grouping](/~/changes/vPSzQFfkdJCVWGT5AL1m/alerting/alert-sources.md#alert-grouping) preference and click **Continue setup**. You may click **Do not group alerts** for now and change it later.
6. The next page show additional settings such as customer alert templates or notification prioritiy. Click on **Finish setup** for now.
7. On the final page, an API key and / or webhook URL will be generated that you will need later in this guide.
## Configuring Webhook in the AlarmManager
Login to your AlarmManager (*default:* *admin:password*)
### Creating a Webhook
On the side menu click on **Configuration** and choose the **Webhooks** tab.\
Click on the **plus icon** to create a new webhook.
Fill out all required fields as shown in the screenshot, paste your copied url from your ilert Kentix AlarmManager alert source, as well as the provided data payload template below:
```
{
"time": "$TIME$",
"building": "$BUILDING_NAME$",
"alarmzone": "$ALARMZONE_NAME$",
"alarmzone-state": "$ALARMZONE_STATE$",
"device": "$DEVICE_NAME$",
"address": "$DEVICE_ADDRESS$",
"temperature": "$TEMPERATURE_VALUE$",
"temperature-alarm": "$TEMPERATURE_ALARM$",
"humidity": "$HUMIDITY_VALUE$",
"humidity-alarm": "$HUMIDITY_ALARM$",
"dewpoint": "$DEWPOINT_VALUE$",
"dewpoint-alarm": "$DEWPOINT_ALARM$",
"fire": "$CO_VALUE$",
"fire-alarm": "$CO_ALARM$",
"intrusion": "$MOTION_VALUE$",
"intrusion-alarm": "$MOTION_ALARM$",
"vibration": "$VIBRATION_VALUE$",
"vibration-alarm": "$VIBRATION_ALARM$",
"input1": "$INPUT_VALUE[1]$",
"input1-alarm": "$INPUT_ALARM[1]$",
"input2": "$INPUT_VALUE[2]$",
"input2-alarm": "$INPUT_ALARM[2]$",
"connection": "$CONNECTION_VALUE$",
"connection-alarm": "$CONNECTION_ALARM$",
"latency": "$LATENCY_VALUE$",
"latency-alarm": "$LATENCY_ALARM$",
"extpower": "$EXTPOWER_VALUE$",
"extpower-alarm": "$EXTPOWER_ALARM$"
}
```
Click on the save icon in the top right.
### Assigning Webhook to Alarmzone
Navigate to the root **dashboard** view (top left item in sidebar), choose the Alarmzone which you want to connecto to your ilert alert source. Click on the **cog** and and select **Edit**.
Scroll all the way down to the Alarmzone's **Webhooks** configuration.\
And click on the **plus icon** to create a new assignment.
It is important to choose **Alarmstate change** as alarm assignment otherwise the connection wont work properly.
## A word on the Kentix device <-> ilert alert relation
Each ilert alert source is connected to a Kentix AlarmManager Webhook.\
Which in fact are assigned to Alarmzones. You might created multiple alert sources and assign them to as many Alarmzones as you like.
Each device in a alarmzone will create its own alert for its alarms.\
However ilert will not create a new alert per alarm type if an ongoing alert of the same device is already open, instead the additional alarms are appended to the existing alert.
When all alarms of the device fall back to normal state, ilert will automatically resolve the opened alert.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.ilert.com/~/changes/vPSzQFfkdJCVWGT5AL1m/inbound-integrations/kentix-am.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.