DoorBird KNX integration with Link’nX: Cloud and local
Link’nX connects a DoorBird intercom to the KNX bus and to scenarios in two connection modes. DoorBird (local) talks to the intercom on the local network: relay opening, switching the light on, reacting to the doorbell and to motion. DoorBird Cloud goes through a DoorBird authorization; it lets you create or delete keypad codes from KNX and prepare access control bookings. This page sums up what each mode does and the commissioning order.
What the DoorBird integration does
Section titled “What the DoorBird integration does”| Need | Where to configure it | Guide |
|---|---|---|
| Open a door or switch the light on in a scenario | DoorBird (local) actions | Local DoorBird automations |
| Start a scenario on a doorbell press or on motion | DoorBird (local) triggers | Local DoorBird automations |
| Open a relay or switch the light on from a KNX button | DoorBird (local) gateway table, Actions tab | Local DoorBird automations |
| Receive doorbell, motion and reachability on the bus | Gateway table, second tab | Local DoorBird automations |
| Connect a DoorBird Cloud and follow its status | Devices → Security & Access → DoorBird Cloud | Connect a DoorBird Cloud |
| Create or delete a keypad code from KNX | DoorBird Cloud gateway table | DoorBird Cloud code commands and KNX |
Step-by-step commissioning
Section titled “Step-by-step commissioning”Local DoorBird
Section titled “Local DoorBird”- Declare the intercom with its IP address and an API user that has the watch always permission, then find or enter its relays.
- Prepare the actions, triggers and KNX associations.
- Add the actions and triggers to the scenario concerned, then check its activation and conditions.
DoorBird Cloud
Section titled “DoorBird Cloud”- Declare and connect the device with the DoorBird administrator account, then check the Connected status and the Keypad.
- Associate the code commands with KNX group addresses if codes are to be created from the bus.
- For bookings, continue with declaring an access control device.
Good to know
Section titled “Good to know”- Local doorbell and motion events require the intercom to be on the same network broadcast domain as Link’nX, with firmware from November 2023 or later.
- In local mode, the KNX opening and light commands use DPT 1.017: 1 requests the action, 0 neither closes the door nor switches the light off. Doorbell and Motion (DPT 1.001) are pulses that return to 0 about two seconds later; Reachable (DPT 1.011) does not confirm that a relay opened.
- Without a declared relay, no opening row appears in the KNX table. Internal relays have the identifiers 1 or 2; a paired DoorController can use a compound identifier.
- With DoorBird Cloud, each code command receives a six-digit PIN in DPT 15.000. Delete a code only removes codes created by Link’nX, and the table provides no status feedback.
- A Connection expired status prevents creating or deleting codes until the device is reconnected with Reconnect DoorBird.
For other intercoms and access equipment, see Access control and Security and video surveillance.