nuki_hub: 8.35: config changes triggered in Home Assistant triggers complete MQTT reload for that device (renders all entities unavailable)
PROBLEM DESCRIPTION
After updating NH from v8.26 to v8.35, when one config (e. g. switch.lock_door_b_led_enabled) is changed, first the switch immediately turns back and after few seconds all entities are unavailable - it takes 30 seconds for them to come back. Nuki Hub seems to NOT restart during that time according to the sensor.lock_door_b_uptime_nukihub sensor.
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 (LOLIN32 Lite Board V1.0 ESP-32 Rev1)
- 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: 9596430697.1135.1 (release)
run: true
confVersion: 835
deviceId: [MASKED]
deviceIdOp: [MASKED]
nukiId: ***
nukidOp:
mqttbroker: [MASKED]
mqttport: 1883
mqttuser: ***
mqttpass: ***
mqttlog: false
checkupdates: true
websrvena: false
lockena: true
lockpin: 1
mqttpath: nuki_door_b
openerena: false
openerpin:
openercont: false
mqttoppath:
maxkpad:
opmaxkpad:
maxtc:
opmaxtc:
enabtlprst: false
mqttca:
mqttcrt:
mqttkey:
hassdiscovery: homeassistant
hassConfigUrl:
buffsize:
dhcpena: true
ipaddr: [MASKED]
ipsub: 255.255.255.0
ipgtw: [MASKED]
dnssrv: [MASKED]
nwhw: 1
nwwififb: false
rssipb: -1
hostname: ESP-Nuki-Hub-Door-B
nwbestrssi: true
nettmout: -1
restdisc: true
rstbcn: 60
lockStInterval: 3600
tcPerEntry: false
kpPerEntry: false
configInterval: 3600
batInterval: 7200
kpInterval: 1800
kpCntrlEnabled: true
kpInfoEnabled: false
kpPubCode: false
tcCntrlEnabled: false
tcInfoEnabled: false
cnfInfoEnabled: true
regAsApp: false
regOpnAsApp: false
nrRetry: 10
rtryDelay: 100
crdusr: ***
crdpass: ***
disnonjson: false
pubAuth: true
pubdbg: false
prdtimeout: 60
offHybrid: false
hybridTimer: 600
hybridAct: false
hybridRtry: false
hasmac: true
macb0: -41
macb1: 80
macb2: 112
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): Allowed
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): Allowed
Lock config ACL (Single button press action): Allowed
Lock config ACL (Double button press action): Allowed
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): Allowed
Lock config ACL (Auto lock timeout): Disallowed
Lock config ACL (Auto unlock disabled): Disallowed
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): Disallowed
Lock config ACL (Immediate auto lock enabled): Disallowed
Lock config ACL (Auto update enabled): Disallowed
Network device: Built-in Wi-Fi
BSSID of AP: [MASKED]
Uptime: 0 minutes
Heap: 76228
Stack watermarks: nw: 7096, nuki: 5536, pd: 7096
Restart reason FW: RestartOnDisconnectWatchdog
Restart reason ESP: ESP_RST_SW: Software reset via esp_restart.
TO REPRODUCE
Update NH to 8.35. Make a config change through any Home Assistant configuration entity.
EXPECTED BEHAVIOUR
Change is performed immediately and the changed entity updates within few seconds, all other entities are not affected and no entity renders unavailable for 30 seconds.
SCREENSHOTS
https://github.com/user-attachments/assets/bd7a78b1-d7bb-4636-8eb1-9f5f2d8165e8
ADDITIONAL CONTEXT
This makes controlling a Nuki lock from Home Assistant using Nuki Hub pretty useless.
- I can directly compare the behaviour to another Nuki Hub still running NH v8.26 - which works flawlessly when doing config changes.
- I enabled MQTT integration debug logging and performed a config change for that Nuki Hub device and had an intensive look at the log afterwards but can’t really find anything suspicious.
(Please, remember to close the issue when the problem has been addressed)
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 27 (16 by maintainers)
I’d say remain on 8.34 and use webflash when 9.0 is released.
9.0 will be released when we feel it is done, could be in a week, could be in a month depending on how many bugs are found.
@bcutter Please acknowledge that everyone here is doing their best to help you. What Nuki Hub does is complex on many levels, and problems can occur. HA auto discovery in itself is complicated enough already to potentially cause problems. Every release is tested as much as we can without being a commercial project. I know it can be frustrating if things don’t work, but that’s in the nature of setting up your own smart home.
I can’t be all that helpful since I’m not a HA user, but maybe deleting the MQTT nodes related to Nuki Hub sounds reasonable, since a fresh Nuki Hub setup doesn’t show these problems. Maybe export customizations you made before so it’s easy to add them later.
Maybe don’t label things as “unacceptable” or “worst update experience” then?
Yes.
If you want to make sure that HA does not lose any entity customizations, you can shut down HA or disable the MQTT integration while you clean up the retained messages. It’s unlikely to be necessary, but if you want to go really sure, that’s the way to ensure that HA can’t do anything funky.
Anyway, MQTT messages (even retained ones) are only a kind of message bus, so they are always ephemeral.