9.14 Invalid Keypad Fingerprint reporting as "undefined" completionstatus

[sjors-lemniscap]

PROBLEM DESCRIPTION

In the rolling authorization log a invalid (not registered) fingerprint has the completionStatus "undefined". If we compare this when a invalid keypad code is entered the completionStatus is "invalidcode" hence I would expect the completionStatus for a invalid (not registered) fingerprint to report "invalidfingerprint" or something similar.

Obviously I can filter on "undefined" and trigger "fingerprint" but for the sake of reporting correct statuses I think defining this status makes sense.

REQUESTED INFORMATION

Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!

• Read the Contributing Guide and Policy and the Code of Conduct
• Searched the problem in issues
• Searched the problem in discussions
• Searched the problem in the docs
• Searched the problem in the chat
• Device used (e.g., ESP32-S3): ESP32-S3 (Octal PSRAM)
• Nuki Hub binary firmware version number used: 20552619151.19.1
  • Pre-compiled
  • Self-compiled
• Provide the output of http://nukihubIP/get?page=info:

------------ NUKI HUB ------------
Device: ESP32-S3 (Octal PSRAM)
Version: 9.14
Build: 20552619151.19.1
Build type: Release
Build date: 2025-12-28
Updater version: 9.14
Updater build: 20552619151.19.1
Updater build date: 2025-11-24
Uptime (min): 575
Config version: 914
Last restart reason FW: RequestedViaMqtt
Last restart reason ESP: ESP_RST_SW: Software reset via esp_restart.
Free internal heap: 135863
Total internal heap: 405363
PSRAM Available: Yes
Free usable PSRAM: 8311976
Total usable PSRAM: 8388608
Total PSRAM: 8388608
Total free heap: 8397876
Network task stack high watermark: 27632
Nuki task stack high watermark: 29344

------------ SPIFFS ------------
SPIFFS Total Bytes: 233681
SPIFFS Used Bytes: 60240
SPIFFS Free Bytes: 173441

------------ GENERAL SETTINGS ------------
Network task stack size: 32768
Nuki task stack size: 32768
Check for updates: Yes
Latest version: 9.14
Allow update from MQTT: No
Update Nuki Hub and Nuki devices time using NTP: Yes
Web configurator username: Not set
Web configurator password: Not set
Web configurator bypass for proxy IP: Not set
Web configurator authentication: Basic
Session validity (in seconds): 3600
Session validity remember (in hours): 720
Duo Push MFA enabled: No
TOTP MFA enabled: No
Web configurator enabled: Yes
HTTP SSL: Disabled
Nuki Hub FQDN for HTTP redirect: Not set
Advanced menu enabled: Yes
Publish free heap over MQTT: Yes
Nuki connect debug logging enabled: No
Nuki communication debug logging enabled: No
Nuki readable data debug logging enabled: No
Nuki hex data debug logging enabled: No
Nuki command debug logging enabled: No
MQTT log enabled: Yes
Webserial enabled: No
Bootloop protection enabled: Yes

------------ NETWORK ------------
Network device: Built-in Wi-Fi
Network connected: Yes
Internet connected: Yes
IP Address: ***
SSID: ***
BSSID of AP: ***
ESP32 MAC address: ***

------------ NETWORK SETTINGS ------------
Nuki Hub hostname: nukihub_front_door_opener
DHCP enabled: No
Static IP address: ***
Static IP subnet: ***
Static IP gateway: ***
Static IP DNS server: ***
RSSI Publish interval (s): 60
Find WiFi AP with strongest signal: Yes
Restart ESP32 on network disconnect enabled: Yes
Disable Network if not connected within 60s: No
MQTT Timeout until restart (s): 60

------------ MQTT ------------
MQTT connected: Yes
MQTT broker address: ***
MQTT broker port: ***
MQTT username: ***
MQTT password: ***
MQTT base topic: front_door_opener
MQTT SSL: Disabled

------------ BLUETOOTH ------------
Bluetooth TX power (dB): 9
Bluetooth command nr of retries: 3
Bluetooth command retry delay (ms): 100
Seconds until reboot when no BLE beacons received: 60

------------ QUERY / PUBLISH SETTINGS ------------
Lock/Opener state query interval (s): 1800
Publish Nuki device authorization log: Yes
Max authorization log entries to retrieve: 50
Battery state query interval (s): 1800
Most non-JSON MQTT topics disabled: No
Publish Nuki device config: Yes
Config query interval (s): 3600
Publish Keypad info: Yes
Keypad query interval (s): 1800
Enable Keypad control: Yes
Publish Keypad topic per entry: Yes
Publish Keypad codes: Yes
Allow checking Keypad codes: Yes
Max keypad entries to retrieve: 100
Publish timecontrol info: Yes
Keypad query interval (s): 1800
Enable timecontrol control: Yes
Publish timecontrol topic per entry: Yes
Max timecontrol entries to retrieve: 50
Enable authorization control: Yes
Publish authorization topic per entry: Yes
Max authorization entries to retrieve: 50

------------ HOME ASSISTANT ------------
Home Assistant auto discovery enabled: Yes
Home Assistant auto discovery topic: homeassistant/
Nuki Hub configuration URL for HA: ***
Nuki Hub ID: ***

------------ NUKI LOCK ------------
Lock enabled: No

------------ NUKI OPENER ------------
Opener enabled: Yes
Paired: Yes
Nuki Hub device ID: 1108873984
Nuki device ID: ***
Firmware version: 1.11.0
Hardware version: 4.17
Opener valid PIN set: Yes
Opener has keypad: Yes
Keypad highest entries count: 0
Timecontrol highest entries count: 0
Authorizations highest entries count: 0
Register as: Bridge
Nuki Opener Lock/Unlock action set to Continuous mode in Home Assistant: No
Force Opener ID: No
Force Opener Keypad: No

------------ NUKI OPENER ACL ------------
Activate Ring-to-Open: Allowed
Deactivate Ring-to-Open: Allowed
Electric Strike Actuation: Allowed
Activate Continuous Mode: Allowed
Deactivate Continuous Mode: Allowed
Fob Action 1: Allowed
Fob Action 2: Allowed
Fob Action 3: Allowed

------------ NUKI OPENER CONFIG ACL ------------
Name: Allowed
Latitude: Allowed
Longitude: Allowed
Pairing enabled: Allowed
Button enabled: Allowed
LED flash enabled: Allowed
Timezone offset: Allowed
DST mode: Allowed
Fob Action 1: Allowed
Fob Action 2: Allowed
Fob Action 3: Allowed
Operating Mode: Allowed
Advertising Mode: Allowed
Timezone ID: Allowed
Intercom ID: Allowed
BUS mode Switch: Allowed
Short Circuit Duration: Allowed
Eletric Strike Delay: Allowed
Random Electric Strike Delay: Allowed
Electric Strike Duration: Allowed
Disable RTO after ring: Allowed
RTO timeout: Allowed
Doorbell suppression: Allowed
Doorbell suppression duration: Allowed
Sound Ring: Allowed
Sound Open: Allowed
Sound RTO: Allowed
Sound CM: Allowed
Sound confirmation: Allowed
Sound level: Allowed
Single button press action: Allowed
Double button press action: Allowed
Battery type: Allowed
Automatic battery type detection: Allowed
Reboot Nuki: Allowed
Recalibrate Nuki: Allowed

------------ GPIO ------------

Retain Input GPIO MQTT state: No

TO REPRODUCE

Steps to reproduce the behavior:

1. Run firmware 9.14
2. Use a finger on the keypad 2.0 fingerprint sensor that is NOT registered
3. Check the rolling authorization log and filter on: trigger: fingerprint, completionStatus: undefined

EXPECTED BEHAVIOUR

A clear and concise description of what you expected to happen.
The completionStatus should be defined as invalidfingerprint

SCREENSHOTS

If applicable, add screenshots to help explain your problem.

ADDITIONAL CONTEXT

Add any other context about the problem here.

DEBUG Front Door Auth state=32494 attrs={"action": "ActivateRTO", "authorizationId": 3431655, "authorizationName": "Keypad", "codeId": 0, "completionStatus": "undefined", "friendly_name": "Opener Front Door Rolling authorization log", "icon": "mdi:format-list-bulleted", "index": 32494, "timeDay": 9, "timeHour": 19, "timeMinute": 2, "timeMonth": 1, "timeSecond": 26, "timeYear": 2026, "trigger": "fingerprint", "type": "KeypadAction"} triggered by automation DEBUG front door auth – dump attributes triggered by state of Opener Front Door Rolling authorization log

(Please, remember to close the issue when the problem has been addressed)

[technyon]

It's probably a new code that they sent for fingerprints. Have to figure out what it is.

[technyon]

I've made some changes so instead of undefined the numeric value will be published. Please update to the latest version and let me know the value, so I can add it to the list of known codes.

[github-actions]

This issue has been automatically marked as stale because it hasn't had any activity in the last few weeks. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically marked as stale because it hasn't had any activity in the last few weeks. It will be closed if no further activity occurs. Thank you for your contributions.