nuki_hub: [Solution Provided] Nuki Lock state undefined since version 8.35
PROBLEM DESCRIPTION
With the update to the new 8.35 FW, the Nuki Lock state is undefined. Repairing the lock did not solve the problem. Power cycling the ESP32 Board did not solve the problem.
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
- [x ] Read the Contributing Guide and Policy and the Code of Conduct
- [ x] Searched the problem in issues
- [ x] Searched the problem in discussions
- [ x] Searched the problem in the docs
- Searched the problem in the chat
- Device used (e.g., ESP32-S3): ESP32 D1 mini
- Nuki Hub binary firmware version number used: 8.35
- Pre-compiled
- Self-compiled
- Provide the output of http://nukihubIP/info:
System Information
Nuki Hub version: 8.35
Nuki Hub build: 9596492875.1136.1 (release)
run: true
confVersion: 835
deviceId: 4178833015
deviceIdOp: 2209271902
nukiId: ***
nukidOp:
mqttbroker: 192.168.1.2
mqttport: 1883
mqttuser: ***
mqttpass: ***
mqttlog: false
checkupdates: true
websrvena: false
lockena: true
lockpin: 1
mqttpath: nuki
openerena: false
openerpin:
openercont: false
mqttoppath:
maxkpad:
opmaxkpad:
maxtc:
opmaxtc:
enabtlprst: false
mqttca:
mqttcrt:
mqttkey:
hassdiscovery: homeassistant
hassConfigUrl:
buffsize:
dhcpena: true
ipaddr:
ipsub:
ipgtw:
dnssrv:
nwhw: 1
nwwififb: false
rssipb: 60
hostname: NukiHub
nwbestrssi: false
nettmout: -1
restdisc: true
rstbcn: 120
lockStInterval: 1800
tcPerEntry: false
kpPerEntry: false
configInterval: 3600
batInterval: 1800
kpInterval: 1800
kpCntrlEnabled: true
kpInfoEnabled: false
kpPubCode: false
tcCntrlEnabled: false
tcInfoEnabled: false
cnfInfoEnabled: true
regAsApp: false
regOpnAsApp: false
nrRetry: 0
rtryDelay: 100
crdusr: ***
crdpass: ***
disnonjson: false
pubAuth: false
pubdbg: false
prdtimeout: 60
offHybrid: false
hybridTimer: 600
hybridAct: false
hybridRtry: false
hasmac: false
macb0:
macb1:
macb2:
latest: 8.35
tsksznetw:
tsksznuki:
authmaxentry:
kpmaxentry:
tcmaxentry:
MQTT connected: Yes
Lock firmware version:
Lock hardware version:
Lock paired: Yes
Lock valid PIN set: Yes
Lock has door sensor: No
Lock has keypad: No
Lock ACL (Lock): Allowed
Lock ACL (Unlock): Allowed
Lock ACL (Unlatch): Allowed
Lock ACL (Lock N Go): Allowed
Lock ACL (Lock N Go Unlatch): Allowed
Lock ACL (Full Lock): Allowed
Lock ACL (Fob Action 1): Allowed
Lock ACL (Fob Action 2): Allowed
Lock ACL (Fob Action 3): Allowed
Lock config ACL (Name): Disallowed
Lock config ACL (Latitude): Disallowed
Lock config ACL (Longitude): Disallowed
Lock config ACL (Auto Unlatch): Disallowed
Lock config ACL (Pairing enabled): Allowed
Lock config ACL (Button enabled): Allowed
Lock config ACL (LED flash enabled): Allowed
Lock config ACL (LED brightness): Disallowed
Lock config ACL (Timezone offset): Disallowed
Lock config ACL (DST mode): Disallowed
Lock config ACL (Fob Action 1): Disallowed
Lock config ACL (Fob Action 2): Disallowed
Lock config ACL (Fob Action 3): Disallowed
Lock config ACL (Single Lock): Allowed
Lock config ACL (Advertising Mode): Disallowed
Lock config ACL (Timezone ID): Disallowed
Lock config ACL (Unlocked Position Offset Degrees): Disallowed
Lock config ACL (Locked Position Offset Degrees): Disallowed
Lock config ACL (Single Locked Position Offset Degrees): Disallowed
Lock config ACL (Unlocked To Locked Transition Offset Degrees): Disallowed
Lock config ACL (Lock n Go timeout): Disallowed
Lock config ACL (Single button press action): Disallowed
Lock config ACL (Double button press action): Disallowed
Lock config ACL (Detached cylinder): Disallowed
Lock config ACL (Battery type): Disallowed
Lock config ACL (Automatic battery type detection): Disallowed
Lock config ACL (Unlatch duration): Disallowed
Lock config ACL (Auto lock timeout): Disallowed
Lock config ACL (Auto unlock disabled): Allowed
Lock config ACL (Nightmode enabled): Disallowed
Lock config ACL (Nightmode start time): Disallowed
Lock config ACL (Nightmode end time): Disallowed
Lock config ACL (Nightmode auto lock enabled): Disallowed
Lock config ACL (Nightmode auto unlock disabled): Disallowed
Lock config ACL (Nightmode immediate lock on start): Disallowed
Lock config ACL (Auto lock enabled): Allowed
Lock config ACL (Immediate auto lock enabled): Disallowed
Lock config ACL (Auto update enabled): Disallowed
Network device: Built-in Wi-Fi
BSSID of AP: C2:09:D0:1E:F7:A1
Uptime: 3 minutes
Heap: 76664
Stack watermarks: nw: 7092, nuki: 5420, pd: 7092
Restart reason FW: RestartOnDisconnectWatchdog
Restart reason ESP: ESP_RST_SW: Software reset via esp_restart.
TO REPRODUCE
Steps to reproduce the behavior: Update to the new firmware via the OTA interface from the board.
EXPECTED BEHAVIOUR
A clear and concise description of what you expected to happen. Nuki lock state should be locked, unlocked, locking, or unlocking, based on the situation. However, it remains in undefined state.
SCREENSHOTS
ADDITIONAL CONTEXT
I have rolled back to the 8.34 version, and it started working again. Post downgrade screenshot:
(Please, remember to close the issue when the problem has been addressed)
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 1
- Comments: 17 (1 by maintainers)
That was the solution! Setting nrRetry to 3 solved the problem. THANKS a lot!!!
I can confirm this works. Posted a new info page above, but somehow the formatting ended up weird. it is perfectly working as expected with the value “3”.
LE: When 8.36 rolls out, should I set it back to 0, or should I leave it at 3? What is the best practice there?
I may have found the issue in the info page supplied by @MihaiKrieger.
nrRetry is set to 0.
There was a change in 8.35 with how this value is used. Setting this to 0 will mean that most commands are never sent.
This setting is basically not named correctly as of this time as it is not interpreted as number of retries but as maximum number of total tries of a command.
I’ll make a PR to fix this.
Please check the value or
nrRetryon your info page and if this is 0 set it to at least 1 on the “Nuki configuration” page with the setting “Number of retries if command failed” (default is 3)