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
Section titled “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 |
| Unlock a door, apply a lock rule or an emergency | UniFi Access actions | Create a UniFi Access action |
| 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 |
| Block a client, enable a WLAN, restart a device or a PoE port | UniFi Network actions | Control a client, a WLAN or a device |
| 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 |
| Change a camera’s recording mode or react to a detection | unifi_protect actions and triggers | Control UniFi Protect and react to events |
| Map Protect commands and feedback to KNX | The Protect device’s gateway | Associate UniFi Protect with KNX |
Step-by-step commissioning
Section titled “Step-by-step commissioning”- Declare the target: a UniFi Access door or a UniFi Network console, or a UniFi Protect device with its controller’s address, its identifier and its kind.
- Prepare the range’s actions: Access, Network or Protect.
- Create the triggers you need, then add triggers and actions to a saved scenario.
- Map the KNX points in the gateway table: Access, Network or Protect.
- Check each result on the installation: saving an action does not prove its execution.
Good to know
Section titled “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; for cameras and sensors, Security and video surveillance.
All UniFi guides
Section titled “All UniFi guides”Access and getting started
Section titled “Access and getting started”Devices and integrations
Section titled “Devices and integrations”- Add a Hikvision, Reolink or UniFi Protect camera in Link’nX
- Declare a UniFi Access door or a UniFi Network controller
- UniFi Network action in Link’nX: client, WLAN, restart and PoE
- UniFi Protect: scenario commands and triggers in Link’nX
- UniFi Protect and KNX: map commands and feedback to group addresses