Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nuki Opener timeout after upgrade to 9.03-master8 #557

Closed
9 of 10 tasks
duhow opened this issue Dec 6, 2024 · 10 comments
Closed
9 of 10 tasks

Nuki Opener timeout after upgrade to 9.03-master8 #557

duhow opened this issue Dec 6, 2024 · 10 comments
Labels
bug Something isn't working fixed in master
Milestone

Comments

@duhow
Copy link
Contributor

duhow commented Dec 6, 2024

PROBLEM DESCRIPTION

Timeouts when attempting to open Nuki Opener.
Can't open the intercom door.
All 4 retry attempts appear within 1 second, expecting to delay a bit.

Noticed these errors couple of days after upgrading to #554 ...

nuki/opener/action electricStrikeActuation
nuki/opener/action ack
nuki/opener/commandResult error
nuki/opener/retry 1
nuki/opener/commandResult error
nuki/opener/retry 2
nuki/opener/commandResult error
nuki/opener/retry 3
nuki/opener/commandResult error
nuki/opener/retry 4
nuki/opener/retry failed

REQUESTED INFORMATION

------------ NUKI HUB ------------
Version: 9.03-master8
Build: 12148007889.169.1
Build type: Release
Build date: 2024-12-03
Updater version: 9.03-master8
Updater build: 12148007889.169.1
Updater build date: 2024-12-03
Uptime (min): 84
Config version: 1061194719
Last restart reason FW: NotApplicable
Last restart reason ESP: ESP_RST_BROWNOUT: Brownout reset (software or hardware)
Free internal heap: 61096
Total internal heap: 260360
PSRAM Available: No
Network task stack high watermark: 7148
Nuki task stack high watermark: 5072

------------ GENERAL SETTINGS ------------
Network task stack size: 12288
Nuki task stack size: 8192
Check for updates: No
Latest version: 9.03-master8
Allow update from MQTT: Yes
Web configurator username: Not set
Web configurator password: Not set
Web configurator enabled: Yes
Publish debug information enabled: No
MQTT log enabled: No
Webserial enabled: No
Bootloop protection enabled: Yes

------------ NETWORK ------------
Network device: Built-in Wi-Fi
Network connected: Yes
IP Address: 192.168.10.21
SSID: MOVISTAR_BD8C
BSSID of AP: 94:83:C4:4F:3D:8E
ESP32 MAC address: 24:6F:28:7C:6C:F8

------------ 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: Yes
MQTT Timeout until restart (s): Disabled

------------ MQTT ------------
MQTT connected: Yes
MQTT broker address: 192.168.10.4
MQTT broker port: 1883
MQTT username: ***
MQTT password: ***
MQTT base topic: nuki
MQTT SSL CA: Not set
MQTT SSL CRT: Not set
MQTT SSL Key: Not set

------------ 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: -1

------------ QUERY / PUBLISH SETTINGS ------------
Lock/Opener state query interval (s): 1800
Publish Nuki device authorization log: No
Max authorization log entries to retrieve: 5
Battery state query interval (s): 1800
Most non-JSON MQTT topics disabled: No
Publish Nuki device config: No
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: Yes
Allow checking Keypad codes: No
Max keypad entries to retrieve: 10
Publish timecontrol info: Yes
Keypad query interval (s): 1800
Enable timecontrol control: No
Publish timecontrol topic per entry: Yes
Max timecontrol entries to retrieve: 10

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

------------ NUKI LOCK ------------
Lock enabled: Yes
Paired: Yes
Nuki Hub device ID: 4268661439
Nuki device ID: ***
Firmware version: 4.4.9
Hardware version: 7.0
Valid PIN set: Yes
Has door sensor: No
Has keypad: No
Timecontrol highest entries count: 0
Register as: App

------------ HYBRID MODE ------------
Hybrid mode enabled: Yes
Hybrid mode connected: Yes
Sending actions through official MQTT enabled: Yes
Time between status updates when official MQTT is offline (s): 600

------------ NUKI LOCK ACL ------------
Lock: Allowed
Unlock: Allowed
Unlatch: Allowed
Lock N Go: Disallowed
Lock N Go Unlatch: Disallowed
Full Lock: Disallowed
Fob Action 1: Disallowed
Fob Action 2: Disallowed
Fob Action 3: Disallowed

------------ 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

------------ NUKI OPENER ------------
Opener enabled: Yes
Paired: Yes
Nuki Hub device ID: 4268661439
Nuki device ID: ***
Firmware version: 1.10.1
Hardware version: 4.17
Opener valid PIN set: Yes
Opener has keypad: No
Timecontrol highest entries count: 0
Register as: Bridge
Nuki Opener Lock/Unlock action set to Continuous mode in Home Assistant: 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: Disallowed
Fob Action 2: Disallowed
Fob Action 3: Disallowed

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

------------ GPIO ------------
@duhow
Copy link
Contributor Author

duhow commented Dec 6, 2024

I have opened via mobile app and now seems responsive.
Unless there's anything else to check, give me few days to see if this problem reocurrs again.

@iranl
Copy link
Collaborator

iranl commented Dec 6, 2024

With the updated libs I also changed the way nuki ble library reconnects with the lock/opener. It tries to do this faster than before by not querying services each time it connects. Might give some issues though when something in the connection goes wrong and then does not recover.

Maybe connecting to the opener through the app disconnected the esp32 and the opener in some way that allows the esp32 to recover the connection afterwards.

Will see about forcing a full reconnect on errors.

@duhow
Copy link
Contributor Author

duhow commented Dec 12, 2024

The problem repeats after a while, despite I can open with the App and later with Nuki Hub, the same disconnect issue happens again (eg. the next day).

@technyon
Copy link
Owner

@duhow Is there any change with the 9.04 release?

@duhow
Copy link
Contributor Author

duhow commented Dec 18, 2024

Still having issues. Even after opening with the app, 2h later I would have issues with the device.
Right now I have unpaired and paired again the device, will report later how it goes...

@iranl
Copy link
Collaborator

iranl commented Dec 18, 2024

Please report if this is fixed in 9.05-master4

@kotylo
Copy link

kotylo commented Dec 19, 2024

Not sure if related, but i've updated to 9.05-master4 and after 4+ hours could not get in to the Opener or Lock:

Buzzer MQTT Log changed to nukiTask is running
8:50:43 AM - 1 minute ago
Buzzer MQTT Log changed to networkTask is running
8:50:17 AM - 1 minute ago
Buzzer MQTT Log changed to Result (attempt 1): Result (attempt 2): Result (attempt 3): Result (attempt 4): Query opener state failed
8:50:01 AM - 2 minutes ago
Buzzer MQTT Log changed to nukiTask is running
8:48:43 AM - 3 minutes ago
Buzzer MQTT Log changed to networkTask is running
8:48:17 AM - 3 minutes ago
Buzzer MQTT Log changed to Lock: Maximum number of retries exceeded, aborting.
8:47:24 AM - 4 minutes ago
Buzzer MQTT Log changed to Lock: Last command failed, retrying after 100 milliseconds. Retry 4 of 3
8:47:24 AM - 4 minutes ago
Buzzer MQTT Log changed to Lock action result: error
8:47:24 AM - 4 minutes ago
Buzzer MQTT Log changed to Lock: Last command failed, retrying after 100 milliseconds. Retry 3 of 3
8:47:24 AM - 4 minutes ago
Buzzer MQTT Log changed to Lock action result: error
8:47:24 AM - 4 minutes ago
Buzzer MQTT Log changed to Lock: Last command failed, retrying after 100 milliseconds. Retry 2 of 3
8:47:23 AM - 4 minutes ago
Buzzer MQTT Log changed to Lock action result: error
8:47:23 AM - 4 minutes ago
Buzzer MQTT Log changed to Lock: Last command failed, retrying after 100 milliseconds. Retry 1 of 3
8:47:23 AM - 4 minutes ago
Buzzer MQTT Log changed to Lock action result: error
8:47:23 AM - 4 minutes ago



Home Door MQTT Log changed to nukiTask is running
8:50:43 AM - 1 minute ago
Home Door MQTT Log changed to networkTask is running
8:50:17 AM - 2 minutes ago
Home Door MQTT Log changed to Result (attempt 1): Result (attempt 2): Result (attempt 3): Result (attempt 4): Query opener state failed
8:50:01 AM - 2 minutes ago
Home Door MQTT Log changed to nukiTask is running
8:48:43 AM - 3 minutes ago
Home Door MQTT Log changed to networkTask is running
8:48:17 AM - 4 minutes ago
Home Door MQTT Log changed to Lock: Maximum number of retries exceeded, aborting.
8:47:24 AM - 5 minutes ago
Home Door MQTT Log changed to Lock: Last command failed, retrying after 100 milliseconds. Retry 4 of 3
8:47:24 AM - 5 minutes ago
Home Door MQTT Log changed to Lock action result: error
8:47:24 AM - 5 minutes ago
Home Door MQTT Log changed to Lock: Last command failed, retrying after 100 milliseconds. Retry 3 of 3
8:47:24 AM - 5 minutes ago
Home Door MQTT Log changed to Lock action result: error
8:47:24 AM - 5 minutes ago
Home Door MQTT Log changed to Lock: Last command failed, retrying after 100 milliseconds. Retry 2 of 3
8:47:23 AM - 5 minutes ago
Home Door MQTT Log changed to Lock action result: error
8:47:23 AM - 5 minutes ago
Home Door MQTT Log changed to Lock: Last command failed, retrying after 100 milliseconds. Retry 1 of 3
8:47:23 AM - 5 minutes ago
Home Door MQTT Log changed to Lock action result: error
8:47:23 AM - 5 minutes ago
Home Door MQTT Log changed to Lock action received: lock
8:47:23 AM - 5 minutes ago

@iranl
Copy link
Collaborator

iranl commented Dec 19, 2024

Please report if this is fixed in 9.05-master5. I'm optimistic the issue has been found and addressed.

@kotylo
Copy link

kotylo commented Dec 20, 2024

No retries for me at least, so seems to work for now for both Opener and Lock.

@iranl iranl added bug Something isn't working fixed in master labels Dec 21, 2024
@iranl iranl added this to the 9.05 milestone Dec 21, 2024
@iranl iranl mentioned this issue Dec 21, 2024
5 tasks
@iranl
Copy link
Collaborator

iranl commented Dec 21, 2024

This seems fixed. Please re-open if issues persist on 9.05-master5/9.05-beta1 and up.
In that case please add serial logs

@iranl iranl closed this as completed Dec 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working fixed in master
Projects
None yet
Development

No branches or pull requests

4 participants