PROBLEM DESCRIPTION
When a series of events occur in quick succession, then some of the events might get lost/ are skipped in the rolling log (due to BLE latency?). The long log (/lock/log) contains 2 new entries on the next update.
example:
/lock/log:
[
{"action": "DoorOpened", "authorizationId": "XXXXXXXXXX", "authorizationName": "", "index": 16962, "timeDay": 13, "timeHour": 13, "timeMinute": 40, "timeMonth": 4, "timeSecond": 33, "timeYear": 2026, "type": "DoorSensor"},
{"action": "DoorClosed", "authorizationId": "XXXXXXXXXX", "authorizationName": "", "index": 16963, "timeDay": 13, "timeHour": 13, "timeMinute": 42, "timeMonth": 4, "timeSecond": 54, "timeYear": 2026, "type": "DoorSensor"},
{"action": "DoorOpened", "authorizationId": "XXXXXXXXXX", "authorizationName": "", "index": 16964, "timeDay": 13, "timeHour": 13, "timeMinute": 46, "timeMonth": 4, "timeSecond": 58, "timeYear": 2026, "type": "DoorSensor"},
{"action": "Lock", "authorizationId": "XXXXXXXXXX", "authorizationName": "", "completionStatus": "success", "index": 16965, "timeDay": 13, "timeHour": 13, "timeMinute": 48, "timeMonth": 4, "timeSecond": 14, "timeYear": 2026, "trigger": "manual", "type": "LockAction"}, <-- missing in rolling log
{"action": "DoorClosed", "authorizationId": "XXXXXXXXXX", "authorizationName": "", "index": 16966, "timeDay": 13, "timeHour": 13, "timeMinute": 48, "timeMonth": 4, "timeSecond": 14, "timeYear": 2026, "type": "DoorSensor"}
]
/lock/rollingLog:
2026/04/13 17:52:11:238: {"index":16962,"authorizationId":"XXXXXXXXXX","authorizationName":"","timeYear":2026,"timeMonth":4,"timeDay":13,"timeHour":13,"timeMinute":40,"timeSecond":33,"type":"DoorSensor","action":"DoorOpened"}
2026/04/13 17:54:31:020: {"index":16963,"authorizationId":"XXXXXXXXXX","authorizationName":"","timeYear":2026,"timeMonth":4,"timeDay":13,"timeHour":13,"timeMinute":42,"timeSecond":54,"type":"DoorSensor","action":"DoorClosed"}
2026/04/13 17:58:35:467: {"index":16964,"authorizationId":"XXXXXXXXXX","authorizationName":"","timeYear":2026,"timeMonth":4,"timeDay":13,"timeHour":13,"timeMinute":46,"timeSecond":58,"type":"DoorSensor","action":"DoorOpened"}
2026/04/13 17:59:51:228: {"index":16966,"authorizationId":"XXXXXXXXXX","authorizationName":"","timeYear":2026,"timeMonth":4,"timeDay":13,"timeHour":13,"timeMinute":48,"timeSecond":14,"type":"DoorSensor","action":"DoorClosed"}
It would be great, if Nukihub could make sure, that no event is skipped and thus missed.
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
------------ NUKI HUB ------------
Device: ESP32
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): 2964
Config version: 914
Last restart reason FW: RequestedViaWebServer
Last restart reason ESP: ESP_RST_SW: Software reset via esp_restart.
Free internal heap: 67300
Total internal heap: 268552
PSRAM Available: No
Network task stack high watermark: 7796
Nuki task stack high watermark: 5068
------------ SPIFFS ------------
SPIFFS Total Bytes: 233681
SPIFFS Used Bytes: 36646
SPIFFS Free Bytes: 197035
------------ GENERAL SETTINGS ------------
Network task stack size: 12288
Nuki task stack size: 8192
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: ***
Web configurator password: ***
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
Advanced menu enabled: No
Publish free heap over MQTT: No
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: No
------------ 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
DHCP enabled: Yes
RSSI Publish interval (s): 60
Find WiFi AP with strongest signal: No
Restart ESP32 on network disconnect enabled: No
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: sea2-lock
MQTT SSL: Enabled
MQTT SSL CA: ***
MQTT SSL CRT: Not set
MQTT SSL Key: Not set
------------ BLUETOOTH ------------
Bluetooth TX power (dB): 9
Bluetooth command nr of retries: 5
Bluetooth command retry delay (ms): 500
Seconds until reboot when no BLE beacons received: 600
------------ QUERY / PUBLISH SETTINGS ------------
Lock/Opener state query interval (s): 1800
Publish Nuki device authorization log: Yes
Max authorization log entries to retrieve: 5
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: No
Publish Keypad codes: No
Allow checking Keypad codes: No
Max keypad entries to retrieve: 10
Publish timecontrol info: No
Keypad query interval (s): 1800
Enable timecontrol control: No
Publish timecontrol topic per entry: No
Max timecontrol entries to retrieve: 10
Enable authorization control: Yes
Publish authorization topic per entry: No
Max authorization entries to retrieve: 5
------------ HOME ASSISTANT ------------
Home Assistant auto discovery enabled: No
------------ NUKI LOCK ------------
Lock enabled: Yes
Lock Ultra/Go/5th gen enabled: No
Paired: Yes
Nuki Hub device ID: 3474819996
Nuki device ID: ***
Firmware version: 3.10.7
Hardware version: 6.11
Valid PIN set: Yes
Has door sensor: Yes
Has keypad: Yes
Keypad highest entries count: 0
Timecontrol highest entries count: 0
Authorizations highest entries count: 0
Register as: Bridge
Force Lock ID: No
Force Lock Keypad: No
Force Lock Doorsensor: No
------------ HYBRID MODE ------------
Hybrid mode enabled: No
------------ NUKI LOCK ACL ------------
Lock: Allowed
Unlock: Allowed
Unlatch: Allowed
Lock N Go: Allowed
Lock N Go Unlatch: Allowed
Full Lock: Allowed
Fob Action 1: Allowed
Fob Action 2: Allowed
Fob Action 3: Allowed
------------ NUKI LOCK CONFIG ACL ------------
Name: Disallowed
Latitude: Disallowed
Longitude: Disallowed
Auto Unlatch: Disallowed
Pairing enabled: Disallowed
Button enabled: Disallowed
LED flash enabled: Disallowed
LED brightness: Disallowed
Timezone offset: Disallowed
DST mode: Disallowed
Fob Action 1: Disallowed
Fob Action 2: Disallowed
Fob Action 3: Disallowed
Single Lock: Disallowed
Advertising Mode: Disallowed
Timezone ID: Disallowed
Unlocked Position Offset Degrees: Disallowed
Locked Position Offset Degrees: Disallowed
Single Locked Position Offset Degrees: Disallowed
Unlocked To Locked Transition Offset Degrees: Disallowed
Lock n Go timeout: Disallowed
Single button press action: Disallowed
Double button press action: Disallowed
Detached cylinder: Disallowed
Battery type: Disallowed
Automatic battery type detection: Disallowed
Unlatch duration: Disallowed
Auto lock timeout: Disallowed
Auto unlock disabled: Disallowed
Nightmode enabled: Disallowed
Nightmode start time: Disallowed
Nightmode end time: Disallowed
Nightmode auto lock enabled: Disallowed
Nightmode auto unlock disabled: Disallowed
Nightmode immediate lock on start: Disallowed
Auto lock enabled: Disallowed
Immediate auto lock enabled: Disallowed
Auto update enabled: Disallowed
Reboot Nuki: Allowed
Motor speed: Allowed
Enable slow speed during nightmode: Allowed
Recalibrate Nuki: Allowed
------------ NUKI OPENER ------------
Opener enabled: No
------------ GPIO ------------
Retain Input GPIO MQTT state: No
TO REPRODUCE
This behavior can be easily reproduced with a door sensor installed: Unlatch (event 1/ source: lock) and then immediately open (event 2/ source: door sensor) the door. The first event might get lost.
EXPECTED BEHAVIOUR
No event should be skipped/ get lost in the rolling log
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
ADDITIONAL CONTEXT
Add any other context about the problem here.
(Please, remember to close the issue when the problem has been addressed)
PROBLEM DESCRIPTION
When a series of events occur in quick succession, then some of the events might get lost/ are skipped in the rolling log (due to BLE latency?). The long log (
/lock/log) contains 2 new entries on the next update.example:
/lock/log:/lock/rollingLog:It would be great, if Nukihub could make sure, that no event is skipped and thus missed.
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
TO REPRODUCE
This behavior can be easily reproduced with a door sensor installed: Unlatch (event 1/ source: lock) and then immediately open (event 2/ source: door sensor) the door. The first event might get lost.
EXPECTED BEHAVIOUR
No event should be skipped/ get lost in the rolling log
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
ADDITIONAL CONTEXT
Add any other context about the problem here.
(Please, remember to close the issue when the problem has been addressed)