Skip to content

Local DoorBird and KNX: doorbell, motion and door opening

Link’nXAdministratorInstaller

Link’nX web: actions, triggers and KNX gateway table of a declared DoorBird (local)

Once a DoorBird intercom is declared on the local network, Link’nX can open a door through one of its relays, switch its light on and react to a doorbell press or a detected motion. These functions are used in scenarios, with actions and triggers, or directly from the KNX bus through the gateway table.

Intended for the authorized installer or administrator. Start by declaring the intercom and its relays, in the right project and the right gateway.

  1. Open Actions → Add, then choose DoorBird (local) in Select an action type. Enter Name after choosing the type.
  2. In DoorBird intercom, select the relevant devices; several devices can be checked.
  3. In DoorBird command, choose Open the door or Switch the light on.
  4. For Open the door, select Relay to trigger. The list presents only the relay identifiers common to the selected devices. If it is empty, check their declarations or prepare separate actions for different relays.
  5. For Switch the light on, there is no relay to select, and the relay chosen for an opening is not kept for this command.
  6. Save with the floppy disk at the bottom right, wait for Success!, then reopen the action in the list to reread the devices and the command. When editing, follow the confirmation of the affected scenarios when it appears.

Switch the light on energizes the intercom’s light relay, which the intercom switches off by itself. The form offers neither a switch-off command nor an on-duration.

A prepared action does not run the equipment: to use it in an automation, add it to the planned scenario.

If Please select the relay to trigger appears, choose the relay again, especially after a change of device. Do not add an arbitrary identifier to a declaration to make this message disappear.

  1. Open Triggers → Add. Choose DoorBird (local) in Select a trigger type, then fill in Name.
  2. In DoorBird intercom, choose a device.
  3. In Event type, choose Doorbell pressed or Motion detected.
  4. For the doorbell, leave Call button (optional) empty to accept all buttons. To target a specific button, enter the button identifier or keypad code as reported by the intercom, eight characters maximum. The example 1 is not universal. If this filter involves a confidential code, enter it only in the interface.
  5. For Motion detected, the button filter is not used. Reread the settings after any change of event.
  6. Save with the floppy disk, wait for Success!, then find and reopen the trigger.
  7. Add it to the relevant scenario with the desired actions, then check this scenario’s activation and conditions.

For an edit, a duplication or the confirmation of affected scenarios, follow the triggers guide. If Please select an event type appears, explicitly choose the desired event.

In Devices → Security & Access → DoorBird (local), click the two opposite arrows Gateway mode configuration, to the left of the device’s pencil.

TabRow and functionDPT
ActionsSwitch the light on: energizes the light relay.1.017
ActionsOne row per declared relay, bearing the Relay name: requests this relay’s opening.1.017
Second tab, speech-bubble iconReachable: on while the intercom answers on the local network, checked every 30 seconds.1.011
Second tabDoorbell and Motion: pulse at 1 during the event, then return to 0 about two seconds later.1.001
  1. Fill in Address and check Active for the planned mappings.
  2. Save each tab with the floppy disk and wait for Succès (Success) and Données sauvegardées avec succès ! (Data saved successfully!).
  3. Reopen the gateway to reread the values. The KNX table guide details addresses, filters and saving.

For the commands in 1.017, the value 1 requests the action; the value 0 neither closes the door nor switches the light off. Reachable shows the intercom’s network availability, not the physical opening of a relay. Doorbell and Motion are event pulses: do not interpret them as permanent states or as an open door.

  • Run one command at a time, on the planned door, and watch the intercom or the door.
  • Press the doorbell or cause a motion, then check that the scenario reacts and that Doorbell or Motion goes to 1 on the bus.

The scenario does not react. First check the intercom concerned, the event type, then the button filter if it is filled in. Then check that the trigger is associated with the right scenario, that this scenario is enabled and that its conditions are met. Local events require the network and firmware prerequisites of the declaration guide.

The commands work, but the doorbell triggers nothing. Events arrive as UDP broadcasts and depend on their own network prerequisites: have them checked, along with the button filter.

A relay or a KNX row is missing. Reread the list of relays saved for this device: each declared relay produces a row.

The row exists, but the door does not open. Check the planned relay, the active mapping and the connection settings. Do not send repeated commands or commands to other doors to get around the blockage.

If the result remains uncertain, contact support@can-nx.com with the model, the scenario, the expected event or command and the attempts made, without a password or secret code.

French labels: Interphone DoorBird, Commande DoorBird, Ouvrir la porte, Allumer l’éclairage, Relais à déclencher, Type d’événement, Appui sur la sonnette, Mouvement détecté, Bouton d’appel (facultatif); feedback Joignable, Sonnette and Mouvement.