Skip to content

Nuki lock and KNX integration with Link’nX

With Link’nX, a Nuki lock is controlled from the installation’s scenarios: unlock, lock, unlatch or run Lock ‘n’ go. The scenario can start on a KNX write, for example a press on a push button mapped to a group address. This page sums up what the integration does and the commissioning order.

NeedWhere to configure itGuide
Declare the lock with its identifier and API keyDevices → Security & Access → NukiDeclare a Nuki lock
Unlock or lock from a scenarioNuki action, Unlock and Lock commandsPrepare a Nuki action
Unlock and open the latchUnlatch commandPrepare a Nuki action
Lock again after a delayLock ‘n’ go command, with or without unlatch; delay set in the Nuki lock’s settingsPrepare a Nuki action
Run the command from the KNX busScenario with a KNX triggerCreate a KNX trigger
  1. In Nuki Web, note the lock’s identifier and generate an API token with the Manage devices right. Check that the Nuki entry is available in the project and the gateway (navigation and options).
  2. Declare the lock with a Name, its Lock ID and its API key.
  3. Prepare one Nuki action per useful command. Editing and duplication follow the common actions guide.
  4. Add the action to the scenario with its trigger, for example a KNX trigger on the button’s address.
  5. Check the lock and the command, then test the scenario on the door.

If something goes wrong, the last section of the Nuki guide covers a lock missing from the list and a command with no effect.

  • The declaration needs no IP address or port: only the name and the Lock ID, 64 characters maximum each, and the API key.
  • An action targets one lock. It has no Value field and no duration setting: the Lock ‘n’ go delay is set in the lock’s settings, from the Nuki app or Nuki Web.
  • Unlock alone does not request opening the latch: choose Unlatch. Opening the latch can allow the door to open.
  • Saving the declaration or the action runs no command and confirms neither the connection to the lock nor its status.
  • Enter the API key only in the form, never in an e-mail or a screenshot.

For other access solutions, see Access control.