Which is why there was a firmware 4.3.11 released which did most likely also solve this issues.
It is known and we are planning improvements for the next beta.
1 Like
Well, itās clear that it wasnāt resolved and with 4.4.4 itās still happening. Do you have this in mind or should I report it somewhere else?
2 Likes
If you put your phone into flight mode, turn on BLE and open the Nuki App. How long does it take until you get the status when you are in front of the door? Do you have Android or iOS?
1 Like
Iām away from home these days, Iāll do it when I get back. In the meantime, letās see if any other colleague who suffers from these failures can try it.
Sorry but I canāt get anything, I donāt get any messages, maybe the test should be different.
I think I have managed to narrow down the issue for the lock not reporting the correct status and a significant delay when sending open command to the lock - I had Optimize locking set to Significantly reduced locking distance as this works for my lock and has the benefit of reducing battery usage and speeding up locking/unlocking. I have set the option back to Normal (default) and now the lock reports the correct status at all times and the delay when choosing to open the door is a second - the app still shows connecting however the lock now reacts almost instantly.
@Juergen do you want me to test and report back Reduced locking distance option in Optomize locking settings?
Lets follow up in a private conversation. Itās most likely not a general problem but specific do your setup (lift up handle & adjusted lock distance).
Original post has been updated with release notes for the Smart Lock (4th generation) Beta 4.4.5
This Beta includes an important fix for the physical button, ensuring that any manual input is recognized and handled properly. Next to that the motor strength has been adjusted to ensure that the latch stays pulled during an unlatch operation. Lastly adaptions have been made to the LED handling as several users reported that the LED behaved strange in random cases.
Please report your findings within this channel.
Thank you for your provided feedback! 
Hi, before to update to 4.4.5 the battery level was 40% and now after update is 60%. Any reason? I have the setting in NUKI POWER PACK.
EDIT: after 5 minutes the battery shows critical
There are two different versions of the Nuki Power Pack. The Smart Lock needs to perform a lock action in order to properly differentiate which PowerPack is inserted and adjust the battery percentage calculation accordingly. Therefore the battery % might not be accurate until a lock action has been executed after a reboot.
1 Like
Hello,
Since the last official version I have a bug with my smart-lock 4 pro.
I decided to upgrade to the beta version (4.4.5) hoping that the problem is fixed because I have a lot of problems with my HOME ASSISTANT automations.
Here is a description of the bug, visible from the NUKI IOS application, or from mqtt, thread or matter.
When I unlock the lock, the state is unlocked for 2 seconds then the state goes directly back to locked while the lock is still unlocked.
Just checked and had lost Matter Connection on iPhone and checked on IPad it is available. Rebooted the iPhone still same issue even After update to 4.4.5.
Connection via Matter to HomeKit and MQTT to Home
Not sure what you mean by this. If your Smart Lock is not reachable in Apple Home on the iPhone, but reachable on the iPad, this is not something that Nuki has under control. Itās an Apple thing.
You are right just checked again and somehow itās okay now on all devices.
4.4.5 has fixed my issue with the front button intermittently not responding.
Hi
I received a notification about new beta 4.4.6. what are the improvments ?
I just installed 4.4.6 and I still have a problem. I canāt adjust the closing limit, whatever setting I put, the lock always goes all the way (the opening adjustment works).
If you have an idea Iām interested because in the old official version it worked
@stefan reiterer,
Here is a link to the video that describes the problem.
Whatever setting is made, the lock closes fully, I tried to reset it but it doesnāt change anything.
We donāt see it in the video but even by changing the āunlocked transitionā setting it doesnāt change anything.
The opening setting works but at the time of making the video it no longer worked.
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.4.6. App is on beta ios 2024.10.1 (2585).
So, on to the issue:
When performing tests today, I:
- Unlock Nuki
- Open the door
- Close the door
- Do not lift the handle
- Wait for door sensor to lock the Nuki (still with the handle not lifted so door locking bolts are not engaged and therefore the door can be opened from outside)
- Nuki then starts to lock (as expected)
- Nuki sounds like it is attempting to retry locking as it cannot complete locking (handle not lifted)
- Nuki status changes to locked but it is definitely not locked and now the status is incorrect and no notifications received stating failed to lock.
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.
1 Like