Smart Lock Beta 4.5.0
(13.11.2024)
If you have problems with the WiFi connection of your Smart Lock, please follow the advice in the FAQ before you post here in the forum.
Just adding this here. I have installed beta firmware 4.5.0 and still see the same incorrect lock status (Nuki shows status as locked) if the handle has not been pulled up when Nuki attempts locking (therefore door is unlocked)
As per Smart Lock (4th generation) Firmware Beta 4.4.x - #84 by townsmcp
Adding a new bug that I have discovered, for me anyways.
Background - last week I bought and added the door sensor. Yesterday I replaced my split spindle to a straight bar for lock opening in the handle. This means that the eurocylinder can always be opened from outside unless the lock is locked. The previous split spindle detaches the unlatching (and therefore opening) from outside without using a key to hold back the latch (or using ‘Open’ setting in Nuki).
I have the lock set to auto lock immediately after closing the door (door sensor seems to work well with this feature). ‘Lock after’ is also set to 5 minutes.
I also have the optimize locking set to ‘Reduced locking distance’. I will be honest, I dont really know how to use ‘Custom’ (there needs to be a guide). I did used to have locking set to ‘Significantly reduced locking distance’ which I was happy with (faster lock/unlock) however lock status was not reported correctly with that setting 50% of the time…even though that setting did lock/unlock the Nuki correctly (so it was just status reporting that was the issue).
So the lock is on beta 4.5.0. App is on beta ios 2024.11.1 (2595).
So, on to the issue:
When performing tests today, I:
During this scenario I would expect to get a notification on the phone stating the Nuki failed to lock and then in the app I would expect to see lock status as unlocked/failed locking. I believe this is a major flaw at the moment as the Nuki status is completely incorrect. My previous locks (Yale Connexis v2 and Danalock) would report the correct status - failed to lock.
This is why I put the split spindle in to the door handle previously - if someone forgets to lift the handle when leaving (yes this is a user education piece however human nature forgetting etc etc) then at least the door cannot be opened from outside - with the straight bar anyone has access to the property and being as Nuki has failed to flag the correct lock status I cannot take action to return home/contact neighbours to ask them to lift the handle to ensure the door is locked properly.
Thanks @thebadboyltz i will give that a try. I know on previous app and firmware when I tried to use customised locking the settings were not being saved but I haven’t tried on this new versions
I also have a problem with this version and the problem already existed with previous versions.
My NUKI is connected to MATTER with my APPLE TV or my HOMEPOD, then to MQTT to go back to HOME ASSISTANT.
It happens regularly that the lock disconnects from MATTER, at this time even if I change HUB (APPLETV OR HOMEPOD), the connection is not remade.
If I restart the NUKI by removing the batteries, the connection is remade instantly.
Is it possible to implement an option in the nuki firmware so that after 3 minutes of MATTER disconnection the NUKI restarts?.
My brother has the same problem with his NUKI and MATTER with the official firmware.
indeed, I have the same behaviour with my Nuki 4.0 Pro, with all firmwares. Removing the battery-pack does the trick to “reconnect” via Matter. This “disconnecting” from Matter in the Apple Home app happens around every 6 to max 10 days, while my other Matter devices never “disconnect”. I have said it before and will say it again: the Nuki Matter implementation is not reliable.
This version 4.5.0 is the worst of all, Matter disconnects every day and the only way out is to remove the batteries.
Release a patch as soon as possible because it is unmanageable.
Is it possible to see the lock logs?
The 4.5.0 firmware version still does not generate a “battery-overview”.
It wonders me that Nuki does not solve this for months know problem.
Suggestion: temporary remove this function from the app until it is fixed.
Seba: what device do you use as Matter bridge?
either my APPLE-TV or my HOMEPOD, whatever the device used NUKI disconnects constantly, with the previous versions this happened from time to time but with this version it is every day and several times a day. sometimes it manages to reconnect and sometimes you have to remove the batteries
@thebadboyltz @Cornelis NukiHub 9.02 beta allows you to reboot your Nuki device over MQTT (e.g. HomeAssistant → MQTT → NukiHub → BLE → Nuki lock). You could create an automation in HomeAssistant to trigger the Nuki device reboot when the official MQTT implemention connection state is offline for a set amount of time. You can also use NukiHub Hybrid mode to combine all the added functionality of NukiHub in combination with the official MQTT implementation over Thread.
NukiHub will also support automated Nuki lock reboot on official MQTT implementation connection loss while in Hybrid mode in the near feature without the need for an automation in your smart home system.
Not a real fix for the Nuki WiFi/Thread issues, but at least a usable automated mitigation that does not require pulling the batteries.
your answer is good, I received my esp32 ETH01 today, I installed version 9.01 and configured in rj45 but not yet configured my NUKI because I take the time to read on github the many parameters.
Can you advise me if it is better to choose the hybrid mode to continue using mqtt from the NUKI firmware or simply in BLE? Is the hybrid mode faster to send information back to HA?
in hybrid mode how does it work?
NUKI-mqtt–>BLE esp32–>LAN–>HA.
I know we are off topic but if this can help other people like me who have problems with matter.
Let’s continue this on our discussions section.
Just wanted to point out here that there are automated ways to reboot your Nuki device on MQTT connection loss while Nuki devs work on improving Thread/Wifi/MQTT reliability.
