Add a "No Action" option for Keypad 2 access codes and fingerprints

Feature requests
1

Product name

Nuki Smart Lock Ultra + Keypad 2 NFC

Summary

Add a new “No Action” option under

Settings → Keypad → Settings → Actions → Access Code / Fingerprint

that generates a regular lockActionEvent MQTT event for valid access codes and fingerprints, but does not perform any action on the Smart Lock itself.

Features

Currently, access codes and fingerprints configured on the Keypad 2 must always be associated with one of the available Smart Lock actions:

  • Intelligent
  • Unlock
  • Lock
  • Open Door
  • Lock’n’Go

Please add an additional option:

  • No Action

When selected, a valid access code or fingerprint should:

  • authenticate successfully
  • generate and publish a regular lockActionEvent via MQTT
  • publish the corresponding authId and codeId within the MQTT payload
  • not perform any lock action on the Smart Lock

Example:

Current behaviour:

Access Code
↓
Action = Lock
↓
MQTT publishes: lockActionEvent like 2,0,xxxxx,yyyy,1
↓
Smart Lock locks

Proposed behaviour:

Access Code
↓
Action = No Action
↓
MQTT publishes: lockActionEvent like 6,0,xxxxx,yyyy,1
↓
No movement of the Smart Lock

This feature should work exactly like the existing actions and should support:

  • Access Codes
  • Fingerprints

Reason

This would unlock a huge amount of new use cases while requiring only minimal implementation effort.

Many users already consume MQTT events locally and integrate Nuki with systems such as:

  • Home Assistant
  • Loxone
  • openHAB
  • ioBroker
  • Node-RED

With this feature, Keypad 2 could become a fully customizable input device.
Since MQTT support already exists and lockActionEvent messages are already generated for the other keypad actions, this feature would only require introducing an additional action type that authenticates the user and publishes the MQTT event without moving the Smart Lock.

Users would be able to maintain all credentials directly inside the Nuki ecosystem and decide locally what should happen when a specific code or fingerprint is used.

This feature alone would make Keypad 2 one of the most versatile smart home keypads available on the market

Examples

Examples of possible use cases:

  • Access code 999999 → Open garage door
  • Access code 123456 → Open driveway gate
  • Access code 654321 → Enable guest mode
  • Access code 777777 → Disarm alarm system
  • Fingerprint #1 → Open garage and switch on lights
  • Fingerprint #2 → Execute “Coming Home” scene
  • Fingerprint #3 → Trigger vacation mode

This would allow users to keep all access credentials managed inside Nuki while delegating custom logic to their preferred smart home platform.

The implementation effort should be very small, since the firmware already supports generating lockActionEvent messages and only an additional action type without Smart Lock movement would be required.