---
title: Add and manage an IP or KNX monitor in Boss’nX network health
description: "Have a Kloud’nX gateway test whether a camera, a UPS or a KNX participant is reachable: addresses, probe interval, suspension, duplication and deletion."
canonical: https://wiki.can-nx.com/en/guides/boss-health-manage/
language: en
product: Boss’nX
audience:
  - administrateur
  - installateur
context: "Boss’nX, building supervision: Network health page, with the Manage network health capability"
---

# Add and manage an IP or KNX monitor in Boss’nX network health

Context: Boss’nX, building supervision: Network health page, with the Manage network health capability

A network health monitor has a Kloud’nX gateway periodically test whether an IP device (camera, UPS) or a KNX participant is reachable. From the **Network health** page in Boss’nX, you can add a monitor, edit it, suspend it, duplicate it or delete it.

Intended for administrators and installers. A monitor creates no measurement or command datapoint: for that, use [the component editor](https://wiki.can-nx.com/en/guides/boss-component-edit/). To add the participants of a KNX line in one go, follow [the KNX scan](https://wiki.can-nx.com/en/guides/boss-health-scan/).

## Before you start

- Your role has **View network health** for the navigation entry and **Manage network health** for the actions. Being able to view the table does not grant these actions; see [a role’s capabilities](https://wiki.can-nx.com/en/guides/boss-role-capabilities/).
- You are working in the relevant supervision.
- The device’s address and the gateway that must test it are confirmed for the installation. The examples in this guide are fictitious.

## Add a monitor

1. Open **Menu → Network health**, then click **Add a device**, at the top of the page or in the empty box.
2. At the top of the window, choose **IP device**, offered initially, or **KNX**.
3. Enter a recognizable **Name**, which is required. **Description** is optional.
4. Enter the addresses for the chosen type, then the interval and the gateway, as shown in the next section.
5. If necessary, choose **Location — floor**, then **Location — zone**. Changing the floor clears the chosen zone: check it again. Without a floor, all the zones are offered; **None** leaves these locations empty.
6. Check **Monitoring enabled**, which is checked on a new monitor. Uncheck it if monitoring must stay suspended.
7. Review the fields, then click **Add** and wait for the window to close.

To give up before saving, click **Cancel** or the cross at the top right.

## Enter the addresses and the interval

| Type or field | Expected value |
| --- | --- |
| **IP device → IP address** | A complete IPv4 address, for example **192.168.1.45**, with no domain name, protocol, port or added space. |
| **KNX → Physical address** | area.line.device format: area and line from 0 to 15, device from 0 to 255. Example: **1.1.5**. |
| **KNX → Group address** | main/middle/subgroup format: main from 0 to 31, middle from 0 to 7, subgroup from 0 to 255. Example: **1/2/3**. **0/0/0** is not accepted. |
| **Probe interval (s)** | An integer from **10 to 3600** for IP, from **30 to 3600** for KNX. Initial value: **60** seconds. |
| **KloudnX gateway** | The gateway that runs the test. Check the choice offered automatically and the **online / offline** indication when it appears. For KNX, the test runs on this gateway’s bus. |

For KNX, enter at least one address, physical or group, with no leading zeros in its parts. If you enter both, **both must answer** to get **Online**. Reading a group address requires the **Read flag (R)** to be active on the participant that carries this address. Have this configuration confirmed by the installer rather than changing the addresses to get a favorable state.

## Edit or suspend a monitor

1. Click the pencil **Edit**, on the right of the row, and check the name and the address.
2. Change the relevant fields. The **IP device / KNX** choice is fixed at creation and stays greyed out.
3. To suspend the monitor, uncheck **Monitoring enabled**; to resume it, check it again.
4. Click **Save** and wait for the window to close.

A suspended monitor shows **Disabled — monitoring suspended**. Suspending stops the test, not the device’s power supply.

## Duplicate a monitor

To monitor another device with the same settings:

1. Click the two-sheet **Duplicate** icon, on the right of the source row.
2. Check **Duplicate device** and the name completed with **(Copy)**.
3. Give a distinct name and enter the address of the new target. Also check the type, the gateway, the location, the interval and **Monitoring enabled**: the copied choices do not necessarily match the new target.
4. Click **Add**, then check both rows.

The source is kept and the copy is a new monitor. If a copied gateway or location is no longer available, choose only a confirmed reference. Do not rely on duplication to copy the history.

## Delete a monitor

1. Find the right row and check whether a simple suspension would better meet the need.
2. Click the **Delete** trash can, on the right.
3. Read the confirmation **Delete “…”? Its uptime history will be lost.**, then cancel to keep the monitor or confirm the deletion.

Deleting removes the network health monitor, without deleting or shutting down the physical device. The page offers no restore: if you need the history, contact support before deleting.

## Check the result

1. After **Add** or **Save**, wait for the result: closing the window does not cancel an operation already started.
2. Find the row in **Monitored devices** with the **All** filter. After a deletion, check that the row has disappeared.
3. Reopen the pencil **Edit** to review the stored parameters.
4. Then wait for a monitoring result. A new monitor may first show **awaiting first test**; see [the meaning of the states](https://wiki.can-nx.com/en/guides/boss-health/).

## Troubleshooting

**Add a device**, the row actions or **Scan the KNX bus** are missing: have **Manage network health** checked on your role.

| Message | Action |
| --- | --- |
| **Name is required.** | Fill in **Name**. |
| **Invalid IPv4 address.** | Enter four numbers from 0 to 255 separated by dots, with no port or space. |
| **Enter at least one address (physical or group).** | Enter the physical address, the group address or both. |
| **Invalid physical address — area.line.device format (e.g. 1.1.5).** | Correct the format; a group address does not fit in this field. |
| **Invalid group address — main/middle/sub format (e.g. 1/2/3).** | Correct the format; a physical address does not fit in this field. |
| **The interval must be an integer between 10 and 3600 seconds.** or **The interval must be an integer between 30 and 3600 seconds for KNX.** | Enter a whole number of seconds within the indicated range. |
| **Select a KloudnX gateway.** | Choose the confirmed gateway. |
| **Saving failed. Check the fields and try again.** | Review the fields. If the result remains uncertain, close and reopen the monitor, or check the list, before trying again: this avoids creating a duplicate. |
| **Deletion failed. Try again.** | First check whether the row is still present. |

Do not delete a monitor to get around an edit error.

## Contact support

If the parameters are confirmed and the failure persists, write to support@can-nx.com with the displayed message and the attempts made.

French labels: **Ajouter un équipement**, **Équipement IP / KNX**, **Nom**, **Description**, **Adresse IP**, **Adresse physique**, **Adresse de groupe**, **Intervalle de test (s)**, **Passerelle KloudnX**, **Emplacement — étage / Emplacement — zone**, **Surveillance active**, **Ajouter / Enregistrer / Annuler**, **Modifier / Dupliquer / Supprimer**, **Dupliquer l'équipement**, **(Copie)**.