---
title: "Boss’nX alarm rules: create KNX alarms in bulk by tag"
description: "Create alarms at once on all the KNX datapoints that carry the same tag in Boss’nX: choosing datapoints, naming, confirmation and the creation report."
canonical: https://wiki.can-nx.com/en/guides/boss-tag-alarms-create/
language: en
product: Boss’nX
audience:
  - administrateur
  - installateur
context: "Boss’nX, supervision: Menu → Alarm rules, Create view, with the rights to manage components"
---

# Boss’nX alarm rules: create KNX alarms in bulk by tag

Context: Boss’nX, supervision: Menu → Alarm rules, Create view, with the rights to manage components

The **Alarm rules** page in Boss’nX creates, in a single operation, alarm datapoints for all the KNX datapoints that carry the same tag, for example all the supply temperatures of a supervision. The new datapoints are added to existing components, based on KNX datapoints that are already filled in: existing alarms and their parameters remain unchanged.

Intended for the administrator or installer authorized to manage components. To set up the alarm of a single datapoint, follow the [threshold or value alarm of a component](https://wiki.can-nx.com/en/guides/boss-point-alarm/) instead.

## Before you start

- The chosen tag is carried by the source datapoints themselves. If needed, use [targeted tag assignment](https://wiki.can-nx.com/en/guides/boss-tags-assign/) beforehand.
- These source datapoints are KNX datapoints that have a read address. A KNX datapoint without a read address does not appear; BACnet or Modbus datapoints are hidden, with a counter when they carry this tag.
- The tag of the source datapoints and the expected condition are prepared with the person responsible for the installation.

## Choose the tag and the source datapoints

1. In the supervision concerned, open **Menu → Alarm rules**, in the **Alarms** family. From the **Alarms** page, this page is also offered in the row of tabs under the header.
2. Check the **Alarm rules** title and the supervision’s name.
3. At the top of the page, open the **Tag** field, search for the label you want and click its row in the list.
4. Check that the **Create** view is selected. **Measure points** groups the results by location and component.
5. First choose the **Trigger type** in **Generic definition**, then fill in its condition: [threshold, boolean or list of values](https://wiki.can-nx.com/en/guides/boss-tag-alarms-definition/), or [comparison of two tags](https://wiki.can-nx.com/en/guides/boss-tag-alarms-comparison/).
6. Check the boxes on the right. Eligible datapoints are checked by default: uncheck those that should not receive any new alarm, and check that the datapoints kept really represent the measurements to monitor.

## Browse the tree without losing the selection

- **Collapse all** and **Expand all** only act on the display. Clicking a location banner opens or closes its branch.
- The boxes remain selected in a collapsed branch; its counter helps you locate them.
- Beyond forty datapoints, the first display may collapse location levels. Your collapse choices may be kept when you return to this page in the same browser tab.
- The box of a banner or a component acts on all its eligible datapoints, including in collapsed branches. When they are all checked, it unchecks them; when some are missing, it checks them.
- Check the **selected** and **eligible** totals, or **paired** in comparison mode.

## Name and classify the new alarms

1. In **Naming**, fill in **Alarm names**. **Alarm {point}** is suggested at first: **{point}** will be replaced by the label of each source datapoint.
2. Use a name that is not empty and is recognizable. Fictional example: **Workshop monitoring {point}**.
3. In **Tag of created alarms**, choose a tag to impose their classification. Otherwise, **Auto — suggested from the name** indicates a suggestion taken from the name of each new alarm.
4. Note the planned tag: it may differ from the measurement tag chosen at the top of the page, and it is the one that lets you find the new datapoints in **Existing alarms**.

Scroll inside the **Generic definition** panel to reach these fields at the bottom. If the list of tags extends beyond the visible part, scroll this panel or the list to the row you want before selecting it.

## Confirm the creation

1. Check **Apply to selection (…)**. The button remains unavailable if the selection is empty, if the definition is incomplete or if more than five hundred datapoints are selected. In the latter case, **Selection too large: … alarms for a maximum of 500. Uncheck some points.** is shown: uncheck datapoints to prepare a smaller batch.
2. Click **Apply to selection (…)**.
3. In **Confirm creation**, check the number of alarms and components, then the previewed names and conditions. Only the first five rows are detailed; a counter represents the following ones.
4. Click **Back** to correct the selection or the fields, or **Confirm** to send the request.
5. Wait for **Report** before any other operation.

Nothing is saved when you choose the datapoints, or when you go back with **Back** before sending. After **Confirm**, returning to editing does not cancel the request: wait for the report.

## Check the result

1. In **Report**, read the number of alarms created and any errors. Note the rejected components and datapoints before clicking **Close**.
2. The page returns to the choice of a tag, with the definition reset, including after a partial result.
3. Choose the tag of the created alarms, then open [Existing alarms](https://wiki.can-nx.com/en/guides/boss-tag-alarms-existing/) to check the new datapoints.
4. The report describes how the configuration was taken into account: then test the behavior on the installation. The events produced by the alarms are viewed in [the alarm history](https://wiki.can-nx.com/en/guides/boss-alarms-consult/).

## Troubleshooting

- **Partial result**: errors in a batch do not cancel the creations that succeeded. Running the same configuration again adds new datapoints, including duplicates: first check the datapoints already present, then limit any new attempt to the items actually missing.
- **Failed request**: if **Report** indicates that the request failed, still check the result after reopening before trying again.

For a persistent rejection, an uncertain result or a setting whose effect is not established, contact support@can-nx.com with the supervision, the tag, the components, the requested conditions and the report’s message.

French labels: **Règles d'alarme**, **Créer**, **Définition générique**, **Points de mesure**, **Appliquer à la sélection (…)**, **Confirmer la création**, **Retour**, **Confirmer**, **Rapport**, **Fermer**. The names of the standard tags remain in French in the English interface.