Skip to content

Link’nX access control: declare a KNX lock or a DoorBird

Link’nXAdministratorInstaller

Link’nX web: Access Control section, declaration of an access point

Before creating bookings in Access Control, each access point is declared in Link’nX: a Zenio or Blumotix BX-E-AK12 KNX lock with its group addresses, or a DoorBird device connected through DoorBird Cloud with the relay to trigger. A visitor’s booking is then managed in Access Control.

Intended for the authorized installer or administrator of the project.

  • For a KNX lock: the hardware type and the group addresses validated for its objects.
  • For DoorBird: a device already declared and available in the DoorBird Cloud integration.
  • If KNX scenes must accompany the access: their addresses, DPTs and values.
  1. Check the project and the gateway in Link’nX, then open Devices → Security & Access → Access Control, typing Access in Search a device… if needed. On mobile, first open the three-line menu. The navigation guide covers missing or locked cards.
  2. Click Add. The form is titled Create Access Code; the fields of this step nevertheless define the hardware and its links.
  3. Fill in Name, required, with a name that lets you find the access point. Fictitious example: “Reception door”.
  4. Choose Hardware type before filling in its addresses, then complete the corresponding section below.
  5. If KNX scenes are planned, complete the scene commands and the end delay. Otherwise, leave these optional settings blank.
  6. Click Save, at the bottom of the form, then wait for Saved successfully and the return to the list. Avoid repeated clicks while waiting.

In KNX Configuration, use the group addresses established for the hardware:

Hardware typeRequired fields
Zenio (legacy simple lock)Write PIN Address (DPT 16.001) and Delete PIN Address (DPT 16.001).
Blumotix BX-E-AK12Write PIN Address (CO 54, DPT 15.000), Delete PIN Address (CO 55, DPT 15.000) and Feedback Address (CO 58, DPT 15.000).

The DPTs and objects shown in these labels identify the expected function. The examples visible in the fields are not the addresses of your installation. Enter a group address, never a visitor’s PIN code. For an unknown address or another model, contact the installer or support before configuring.

  1. Choose DoorBird Cloud in Hardware type.
  2. Under DoorBird device, open Device and select the desired declaration. The name may be accompanied by the device’s title.
  3. In Relay triggered by the access codes, select the relay wired for access: Relay 1 or Relay 2, depending on the choices offered. Relay 2 does not appear when the device is identified as having only one relay. Reread this choice after changing device.
  4. Continue with Save.

For a new declaration, the list offers the devices that are connected and available for code management: a device without a keypad or without support for access schedules may not appear. When editing, the device already associated remains visible even if it is no longer connected, with its status, for example an expired connection: then check its connection in DoorBird Cloud.

  1. Find the row by its Name and its Hardware type.
  2. Click its Edit pencil and reread the saved settings.
  3. The declaration does not program any code in the lock: codes are created with Access Control bookings. Try the first code on site.
  • The Edit pencil opens Edit Access Code. The validation button becomes Update, followed by Updated successfully and the return to the list.
  • Changing Hardware type clears, in the form, the fields specific to the other type.
  • To abandon a change, use the back arrow at the top left. If Unsaved changes appears, Cancel stays on the form, Don’t save leaves and discards the entry and Save tries to keep it before leaving. Then reopen the row to check the settings retained.
  • If you stayed on the form after Cancel and finally want to leave it, select the Access Control card in the sidebar, then Don’t save in the exit dialog.
  • Before deleting a declaration used by bookings, have the procedure and its consequences for their codes confirmed by support.
  • Saving stays on the form: check the name, the required fields of the selected type and any scenes filled in. Required flags a mandatory field. The form checks the entry, not whether the addresses match the hardware.
  • The DoorBird device list is empty: first check the device’s declaration and its connection with the DoorBird Cloud guide. Do not choose another device just to be able to save.
  • A save or update error appears: check the list before creating the declaration again, to avoid a duplicate.
  • The declaration is present, but access does not work: check the access point and the booking concerned with the Access Control troubleshooting.

If the result remains uncertain or the DoorBird status remains unavailable after these checks, write to support@can-nx.com with the declaration name, the hardware type, the model, the message displayed and the attempts made.

French labels: Contrôle d’accès → Ajouter → Créer un code d’accès, Nom, Type de matériel, Configuration KNX, Sauvegarder; when editing, Éditer → Modifier le code d’accès → Mettre à jour. For DoorBird: Appareil, Relais déclenché par les codes, Relais 1 / Relais 2. The exit dialog offers Annuler, Ne pas enregistrer and Enregistrer.