Local DoorBird in Link’nX: declare the intercom and its relays

Link’nX can control a DoorBird intercom directly on the local network, with its IP address and an API user. Once the intercom is declared with its door-opening relays, each relay gets its own row in the KNX table and can be used in scenarios, like the doorbell and motion detection.

Intended for the authorized installer or administrator. For an intercom linked through the DoorBird cloud, follow the DoorBird Cloud path instead, which uses a different connection.

Before you start

• The intercom’s IP address.
• An API user created in the DoorBird app with the watch always permission, and its password. The help gives the username form abcdef0001: use your own account.
• For doorbell and motion events, which arrive as UDP broadcasts: the intercom on the same network broadcast domain as Link’nX, with firmware from November 2023 or later. Have these prerequisites confirmed by the installer.

Declare the intercom

1. In Link’nX, check the project and the gateway. Open Devices → Security & Access → DoorBird (local), or search for DoorBird in Search a device…. On mobile, first open the three-line menu. For a padlock or a missing card, follow the navigation guide.
2. Click Add. DoorBird intercom declaration presents Name, IP address, API user and Password: these four fields are required. The name is limited to 64 characters, for example “Reception gate”.
3. Fill in the values of the device concerned. The examples shown in the fields are not a configuration to copy.
4. Under Door openers (relays), you can declare the relays whose identifiers you know, as described below. You can also save the intercom before discovering them.
5. Click the floppy disk at the bottom right. Wait for Success! and the return to the list, which shows Name, IP address and Relays.
6. Click the Edit pencil of the row. In DoorBird intercom modification, relay discovery starts when the saved record opens. Reread the connection and the relays.

Discover or enter the relays

Each declared relay gets its own door-opening row in the KNX table. Without a declared relay, no opening row is offered there.

In the saved record, Refresh, to the right of the Door openers (relays) title, restarts the search; the button may stay grayed out while waiting. The relays found complete the list, named after their identifier. A name already entered for a kept identifier is not replaced.

To enter a relay manually:

1. Click Add a relay.
2. Fill in Relay id with the exact identifier provided by the hardware, then Relay name, limited to 64 characters. Both fields are required for each added row.
3. Internal relays can have the identifiers 1 or 2. A paired DoorController can use a compound identifier such as gggaaa@1, a fictitious example to check before entering anything. Each identifier must be unique within the declaration.
4. To remove a row added by mistake, use its Delete trash can, after checking that no action or KNX mapping uses it.
5. Click the floppy disk, wait for Updated!, then reopen the record to reread the identifiers and the names.

After a successful discovery, also save to keep the new relays offered. If you remove a relay from the declaration, review the scenarios and tables that reference it without assuming an automatic update: see the local DoorBird automations.

Edit, abandon or delete the declaration

• To edit, use the pencil, then the floppy disk, and reread the record.
• To abandon an entry, leave the record; in Unsaved changes, Cancel stays on the form and Don’t save discards the changes.
• To delete the whole declaration, first check the automations that use it. If the consequences are not established, contact support before the operation.

Check the result

• The list shows the row with the right IP address and the expected number of Relays.
• When the record reopens, discovery queries the intercom: a search without an error message confirms that it answers on the network.
• Then test an opening from an action or the KNX table, described in the automations guide.

Troubleshooting

Message or symptom	Check and action
Duplicate relay identifiers	Correct the repeated identifiers; adding spaces around the same identifier does not create another relay. Also reread the name of each row.
The intercom did not respond.	Check the address, the device’s presence on the network, the API user and its password, then the watch always permission. Then click Refresh. Relays can still be entered manually if their identifiers are known; do not guess them.
The intercom returned no relay — the declared list is kept.	Keep the existing configuration. This empty reply can also indicate an unreachable intercom or a missing permission: check the device, then refresh.
The floppy disk is grayed out	Check the four connection fields and the two fields of each relay row: a row that was added but is incomplete prevents saving.
The password length seems different when editing	The field’s help text states that the password is not shown when editing and that the displayed length does not match its own. Do not replace it for this reason alone.

If the blockage persists, contact support@can-nx.com with the model, the context, the message and the attempts made, without a password or an export containing sensitive data.

French labels: DoorBird (local) → Ajouter → Déclaration d’un interphone DoorBird, Nom, Adresse IP, Utilisateur API, Mot de passe, Ouvre-portes (relais), Actualiser, Ajouter un relais, Identifiant du relais, Nom du relais. Saving displays Succès ! or Mis à jour !.