---
title: "UniFi Protect and KNX: map commands and feedback to group addresses"
description: "Control a UniFi Protect camera or light from the KNX bus with Link’nX: commands, status feedback and measurements, with the DPT for each group address."
canonical: https://wiki.can-nx.com/en/guides/link-unifi-protect-gateway/
language: en
product: Link’nX
audience:
  - administrateur
  - installateur
context: "Link’nX web: KNX gateway table of a declared UniFi Protect device"
---

# UniFi Protect and KNX: map commands and feedback to group addresses

Context: Link’nX web: KNX gateway table of a declared UniFi Protect device

The UniFi Protect gateway table in Link’nX maps the group addresses of your KNX project to the commands of a Protect device (status light, recording, privacy, light, chime) and to its status feedback (motion, door, leak, temperature, humidity, battery…). A KNX push button can then control a Protect camera or light without going through a scenario.

Intended for authorized installers and administrators. For the recording modes on detections or on schedule, the LCD message or a command in a scenario, use a [Protect action](https://wiki.can-nx.com/en/guides/link-unifi-protect-automation/) instead.

## Before you start

- The device is [declared in Link’nX](https://wiki.can-nx.com/en/guides/link-camera-devices/), with the right kind.
- You know the hardware’s functions: the table presents a common catalog, of which only some rows apply to each kind and model.
- The group addresses and their DPTs are defined in the KNX project.

## Open the device’s gateway table

In **Devices → Security & Access → UniFi Protect**, click the **two opposite arrows**, **Gateway mode configuration**, to the left of the device’s pencil. The common behavior of the table (address formats, filters) is described in the [KNX table guide](https://wiki.can-nx.com/en/guides/link-gateway-table/).

## Map the commands in the Actions tab

1. In the **Actions** tab, find the rows that apply to the hardware using the table below.
2. Fill in their **Address** and check **Active** for each intended association.
3. Review the DPT, the address and the hardware function.
4. Click the **floppy disk at the bottom right** and wait for **Succès** (Success) and **Données sauvegardées avec succès !** (Data saved successfully!). Save the tab before switching to another.

| Row | DPT | Use |
| --- | --- | --- |
| **Set status light** | 1.001 | Status light of a compatible camera or light: 1 activates, 0 deactivates. |
| **Set recording** | 1.001 | Camera: 1 requests the **Always** mode, 0 the **Never** mode. For the modes on detections or on schedule, use a Protect action. |
| **Set privacy mask** | 1.001 | Camera: 1 enables privacy, 0 disables it. Check the recording mode and the actual result separately. |
| **Set light** | 1.001 | Compatible light: 1 requests forced switch-on; 0 removes this forcing. Also check its detection mode. |
| **Set brightness** | 5.001 | Compatible light: percentage from 0 to 100. The available levels depend on the hardware; a positive level does not replace a switch-on command. |
| **Set motion-activated light** | 1.001 | Compatible light: 1 enables the on-motion mode, 0 disables it. This choice may change its operation compared with the planned schedule: confirm the goal with the installer. |
| **Play chime** | 1.001 | Chime declaration: 1 requests a ring; 0 does not trigger one. |

## Map the feedback in the second tab

1. Open the **second tab**, with the speech-bubble icon.
2. Map the feedback the hardware can provide: fill in **Address** and check **Active**.
3. Save this tab with the floppy disk.

| Feedback | DPT |
| --- | --- |
| **Motion state**, **Recording state**, **Smart detection state**, **Online state** | 1.001 |
| **Door state (1 = open)**, **Leak state**, **Light state** | 1.001 |
| **Brightness state**, **Battery level** | 5.001 |
| **Temperature** | 9.001 |
| **Humidity** | 9.007 |
| **Illuminance** | 9.004 |

A camera does not necessarily have a sensor’s measurements. In your KNX logic, do not treat missing feedback as a zero temperature, an empty battery or a closed door. **Recording state** indicates the reported activity, not the name of the configured mode.

**Leak state** reports a recent detection and returns to zero after about 30 seconds without a new detection. Zero therefore does not certify that the area is dry or that a leak has been repaired. For an alert to be kept until checked, have the installer define the expected behavior; this feedback alone is not a human acknowledgment.

## Check the result

1. Go back to the list, reopen the gateway and review the values saved in each tab. Commands and feedback are separate associations.
2. Send each command from the bus, for example with the ETS group monitor, and watch the device.
3. For feedback, check the value received on its address. The save message confirms that the associations are saved, not a KNX exchange, a physical command or the current availability of a measurement.

## Troubleshooting

- A row does not respond: check the active association, the DPT, the right declaration and the relevant capability, then follow the [Protect troubleshooting](https://wiki.can-nx.com/en/guides/link-unifi-protect-automation/).
- **Erreur lors de la sauvegarde des données.** (Error while saving the data.): the table has not been saved. Check the context and the values, then save again.

If the checks have already failed or if a value remains uncertain, write to support@can-nx.com with the context, the row concerned and the tests carried out.

French labels: **Définir l'enregistrement**, **Définir le masque de confidentialité**, **Définir l'éclairage**, **Définir la luminosité**, **Définir l'éclairage sur détection**, **Jouer le carillon**; **État de l'enregistrement**, **État en ligne**, **État de la porte (1 = ouverte)**, **État de fuite**, **Température**, **Humidité**, **Éclairement**, **Niveau de batterie**.