KNX video surveillance with Link’nX: cameras and intercoms

Link’nX connects Hikvision, Reolink and UniFi Protect cameras, as well as DoorBird and 2N intercoms, to the installation’s scenarios and, depending on the brand, to the KNX bus. A detection, a doorbell press or an entered code can start a scenario; a KNX button or a scenario action can switch on a floodlight, change a camera’s recording mode or open a door. Each brand has its own path.

Solutions for your need

Need	Application	Guide
Declare a Hikvision or Reolink camera or a UniFi Protect device	Link’nX, Devices → Security & Access	Declare a camera or a Protect device
Start a scenario on a Hikvision event: motion, intrusion, license plate, face	Link’nX, HIKvision triggers	Forward the events from the camera, then use them in Link’nX
Switch on the floodlight, activate the siren or go to a Reolink PTZ position from a KNX button	Link’nX, Reolink gateway	Associate a Reolink camera with KNX
React to a Reolink motion, person, vehicle or pet detection	Link’nX, reolink triggers	Control a Reolink camera and use its detections
Change the recording mode, or react to a UniFi Protect doorbell, motion or leak	Link’nX, unifi_protect actions and triggers	Control UniFi Protect and react to events
Read a Protect device’s detections and measurements back on the bus	Link’nX, UniFi Protect gateway	Associate UniFi Protect with KNX
Open a door or react to the doorbell of a local DoorBird	Link’nX, DoorBird (local)	Declare the local DoorBird, then use its doorbell, motion and relays
Create or delete a DoorBird Cloud keypad code from KNX	Link’nX, DoorBird Cloud gateway	Connect the DoorBird Cloud, then associate its code commands
Control a 2N door switch or react to a call, a code or a card	Link’nX, 2N actions and triggers	Declare the 2N intercom, then use its commands and events

Triggers and actions are then used in a Link’nX scenario, on their own or with KNX actions.

Good to know

• A saved declaration does not confirm the connection to the hardware, and an offered command does not guarantee the model’s capability. Test each command and each detection on the device.
• Hikvision: the camera itself forwards its events to Link’nX. In the variant illustrated by the help, the destination is set in HTTP Data Transmission, with the URL /hik and port 4000, then Notify Surveillance Center is checked for each event.
• In a 2N or Hikvision trigger, all the criteria filled in must match the received event; an empty field or — ignores the criterion.
• Reolink: a trigger waits for a new detection. A detection that stays active does not restart the scenario.
• Local DoorBird: doorbell and motion events require an intercom on the same network broadcast domain as Link’nX, with firmware from November 2023 or later.

Brand pages: Hikvision, Reolink, UniFi, DoorBird and 2N. For doors, codes and bookings, see Access control.

All Security and video surveillance guides

Devices and integrations

• 2N intercom in Link’nX: switch actions and event triggers
• Add a 2N intercom in Link’nX: HTTP API account and XML import
• Add a Hikvision, Reolink or UniFi Protect camera in Link’nX
• Connect a DoorBird Cloud intercom to Link’nX: status and troubleshooting
• DoorBird Cloud and KNX: create and delete access codes
• Local DoorBird in Link’nX: declare the intercom and its relays
• Local DoorBird and KNX: doorbell, motion and door opening
• Hikvision in Link’nX: event triggers and privacy mask
• Hikvision Alarm Server: send camera events to Link’nX
• Reolink in Link’nX: control a camera and react to its detections
• Reolink and KNX: map commands and feedback to group addresses
• UniFi Protect: scenario commands and triggers in Link’nX
• UniFi Protect and KNX: map commands and feedback to group addresses