---
title: "UniFi KNX integration with Link’nX: Access, Network, Protect"
description: "Connect UniFi Access, Network and Protect to KNX with Link’nX: doors, network clients, cameras, scenario actions, triggers and DPTs."
canonical: https://wiki.can-nx.com/en/integrations/unifi/
language: en
---

# UniFi KNX integration with Link’nX: Access, Network, Protect

Link’nX integrates three UniFi ranges, each with its own declaration and path: UniFi Access for doors, UniFi Network for clients, WLANs and network devices, UniFi Protect for cameras, lights, sensors and chimes. Each range has scenario actions and triggers, as well as a gateway table that connects it to the KNX bus. Start by identifying the range concerned.

## What the UniFi integration does

| Need | Where to configure it | Guide |
| --- | --- | --- |
| Declare an Access door or a Network console | **Security & Access → UniFi Access** or **Smart Home → UniFi Network** | [Declare an Access door or a Network controller](https://wiki.can-nx.com/en/guides/link-unifi-devices/) |
| Unlock a door, apply a lock rule or an emergency | **UniFi Access** actions | [Create a UniFi Access action](https://wiki.can-nx.com/en/guides/link-unifi-access-actions/) |
| Start a scenario on an access or a doorbell, connect the door to KNX | **UniFi Access** triggers and the door’s gateway | [UniFi Access events and KNX points](https://wiki.can-nx.com/en/guides/link-unifi-access-events-knx/) |
| Block a client, enable a WLAN, restart a device or a PoE port | **UniFi Network** actions | [Control a client, a WLAN or a device](https://wiki.can-nx.com/en/guides/link-unifi-network-actions/) |
| React to a client connection and map its presence to a KNX address | **UniFi Network** triggers and the controller’s gateway | [Client presence and KNX table](https://wiki.can-nx.com/en/guides/link-unifi-network-presence-knx/) |
| Change a camera’s recording mode or react to a detection | **unifi_protect** actions and triggers | [Control UniFi Protect and react to events](https://wiki.can-nx.com/en/guides/link-unifi-protect-automation/) |
| Map Protect commands and feedback to KNX | The Protect device’s gateway | [Associate UniFi Protect with KNX](https://wiki.can-nx.com/en/guides/link-unifi-protect-gateway/) |

## Step-by-step commissioning

1. Declare the target: [a UniFi Access door or a UniFi Network console](https://wiki.can-nx.com/en/guides/link-unifi-devices/), or [a UniFi Protect device](https://wiki.can-nx.com/en/guides/link-camera-devices/) with its controller’s address, its identifier and its kind.
2. Prepare the range’s actions: [Access](https://wiki.can-nx.com/en/guides/link-unifi-access-actions/), [Network](https://wiki.can-nx.com/en/guides/link-unifi-network-actions/) or [Protect](https://wiki.can-nx.com/en/guides/link-unifi-protect-automation/).
3. Create the triggers you need, then add triggers and actions to a [saved scenario](https://wiki.can-nx.com/en/guides/link-scenario-save/).
4. Map the KNX points in the gateway table: [Access](https://wiki.can-nx.com/en/guides/link-unifi-access-events-knx/), [Network](https://wiki.can-nx.com/en/guides/link-unifi-network-presence-knx/) or [Protect](https://wiki.can-nx.com/en/guides/link-unifi-protect-gateway/).
5. Check each result on the installation: saving an action does not prove its execution.

## Good to know

- UniFi Access: one declaration per door, port prefilled with **12445**, API token, door chosen after **Detect doors**. **Emergency** (**Evacuation** or **Lockdown**) applies to all doors of the selected controller.
- UniFi Network: port prefilled with **443**, site prefilled with “default” and the controller’s local account, which an Access token does not replace. A client’s presence designates an associated device, not a person.
- The Access KNX points and the Network KNX commands use DPT 1.001. On the Network side, the value 0 on **Block client** requests unblocking, and **Active client count** uses DPT 7.001.
- UniFi Protect: in the KNX table, **Set recording** requests the **Always** mode with 1 and **Never** with 0; the feedback uses DPT 1.001, 5.001, 9.001, 9.004 or 9.007 depending on the measurement. Only activate the rows that the declared hardware can provide.

For door access, see [Access control](https://wiki.can-nx.com/en/usages/acces/); for cameras and sensors, [Security and video surveillance](https://wiki.can-nx.com/en/usages/videoprotection/).

## All UniFi guides

### Access and getting started

- [UniFi Access action in Link’nX: unlock, lock rules and emergency](https://wiki.can-nx.com/en/guides/link-unifi-access-actions/)

### Devices and integrations

- [Add a Hikvision, Reolink or UniFi Protect camera in Link’nX](https://wiki.can-nx.com/en/guides/link-camera-devices/)
- [Declare a UniFi Access door or a UniFi Network controller](https://wiki.can-nx.com/en/guides/link-unifi-devices/)
- [UniFi Network action in Link’nX: client, WLAN, restart and PoE](https://wiki.can-nx.com/en/guides/link-unifi-network-actions/)
- [UniFi Protect: scenario commands and triggers in Link’nX](https://wiki.can-nx.com/en/guides/link-unifi-protect-automation/)
- [UniFi Protect and KNX: map commands and feedback to group addresses](https://wiki.can-nx.com/en/guides/link-unifi-protect-gateway/)

### Protocols, imports and monitoring

- [UniFi Access: scenario triggers and KNX group addresses](https://wiki.can-nx.com/en/guides/link-unifi-access-events-knx/)
- [UniFi Network: client presence, triggers and KNX addresses](https://wiki.can-nx.com/en/guides/link-unifi-network-presence-knx/)