Smart Lock (4th generation) Firmware Beta 4.4.x

Are you using the UniFi integration in Home Assistant as well and it’s the Nuki added as device tracker under this integration? Or do you have any specific config in the UniFi controller or HA that could keep the device from going to sleep (and thus continuously draining the battery)?

There is no UniFi integration in my home assistant and I removed the device tracker instance which is useless since the nuki is not moving

Hi all.
I have tried reporting the following bug in the app (iOS) however the app just sits there ‘Gathering device information’ and doesnt seem to send the log. I am guessing this is the best place to log issues?

So I got a Nuki 4 (non Pro) delivered last Friday. I have set the lock up on Matter (via Home Assistant SkyConnect USB stick) and it all seems to be connected fine. I applied for beta and had that approved Saturday - I have updated to beta 4.4.1.

My door is a eurocylinder with lift handle (UK front door) to lock the door. I have a split spindle installed behind the handle (it was just a straight bar on my previous Yale Conexis L2 lock however split spindle is more secure for the property).
The issue I am seeing since installing the beta is when I pull up on the app and choose ‘Open door’ it takes around 20+ seconds to hold back the latch especially when being stood next to the lock from the point of opening the app. The app shows ‘connecting…’ for the 20 seconds. If however I choose Unlock or Lock the app takes about 1 to 2 seconds (and still shows ‘connecting…’ for that 1 to 2 seconds). As I recall, the delay between sending command and it being actioned was much faster pre beta - almost instant, certainly not 20 seconds for an unlatch/open request.

I did try terminating the app on the phone and then going through the procedure again but it is still taking 20 odd seconds to perform the open.

Also, I think the status displayed in the app isnt quite right with this type of setup. It shows ‘locked’ when technically the Nuki isnt locked, it is unlocked but not open. This could be confusing to some people, thinking the door is locked when it is unlocked but not open. I think the status’s should be ‘locked’ (for when the handle is lifted/dead bolts engaged), ‘unlocked’ for when the handle has not been pulled up/dead bolts engaged, ‘open’ for when hold back latch is being performed.

Hi, I experienced (with 4.3.11 non-pro with Matter integration) the following at least weird behavior:

  • I clicked “open door” in the Nuki App (+ confirmation) but door doesn’t open for some seconds which is unusual
  • clicked again and confirmed, after some seconds the door opens as expected
  • I closed the door
  • a few seconds later (I was already in my apartment) the door opens again

So both clicks were somehow very delayed and the second “open” command doesn’t cancel the first one.

With previous firmware and without Matter integration I never experienced such behavior before.

and here the timing with a 3rd party sensor

I am experiencing a recurring issue with my Nuki lock becoming “Unavailable” and unresponsive in Home Assistant.

Screenshot 2024-09-25 080740

Here’s my setup:

  • The lock is connected via Thread through a HomePod.
  • The lock is integrated into Home Assistant using Matter.

When the issue occurs, restarting both Home Assistant and the HomePod does not solve the problem. I have to restart the lock itself to regain control.

Sounds like slow or unreliable remote access for the Nuki App. If your Matter integration supports “Remote Access”, you might want to turn it off and use WIFI instead. See also the FAQ for selecting through which channel the Smart Lock should communicate: Smart Lock WiFi/Thread/MQTT connection troubleshooting / FAQ - #3 by Stefan_Reiterer

Is the lock reachable in Apple Home at that time or is offline there as well?

I installed 4.3.11 the other day and had the same experience. After the update it has dropped 20-30% next day it said it was critical. It’s powered 24/7 via USB so not sure what’s going on.

Unplugged the USB and re powered it and today it’s back to 100%

What’s the advantages of 4.4 looks like just more logging currently?

1 Like

I noticed that the Nuki lock was still accessible in Apple Home, so I initially thought that restarting the lock had solved the problem. However, I eventually had to re-pair the lock in Home Assistant.

Firmware 4.4.4 is online…

@Stefan_Reiterer After update to 4.4.4 I got

on a non-pro lock which has no wifi support anyway… so I should not get this warning.

Additionally, the Door Sensor status is not transferred by Matter anymore?! see


and after Lock’n’Go the lock locks in the same moment as the door is closed, not the 2 seconds mentioned in the change log.

Edit:

Door Sensor is available via Matter again as it seems:

… and still the same problem with Matter via AmazonEcho for Remote connection
It was working for 30min, now again no connection anymore.

(I know this was mentioned a couple of times, but please, please support your beta-testers as we support you by giving us the possibility to switch back to the latest official firmware, like it is done for every other gadget I know. I am really happy to help and give feedback to your beta firmware but I want to switch back if the experience with the beta is worse than before.)

4 Likes

So on 4.4.4 lock status is still incorrect when ‘Open door’ has been selected. I have the lock setup with a lift to lock door type. I also do not have auto lock enabled - I don’t need this as I have a split spindle (can’t open the door from the outside without a key/Nuki to hold back latch.

Here is a recording from opening the app to selecting Open Door and showing the door status goes back to ‘Locked’ when all that has happened is the latch has been opened and then released - the door is not locked. This status really needs fixing as downstream actions are severely impacted due to incorrect status reporting via the app and other systems (Home Assistant for myself)

IMG_8718

IMG_8719

Hi,

this seems odd, please provide us more details by creating a ticket via Menu → Help → Contact customer support and write them a hint to forward it to me.

BR
Zoran

The new Beta 4.4.4 update introduces two features to the Smart Lock Pro (4th generation) designed to enhance WiFi stability and integrity. To use those features make sure that the most recent App Beta is installed (see list of Prerequisites below).

1.) WiFi Modes

From now onwards it is possible to choose between two different WiFi modes.

  • Automatic
    This mode is enabled by default by the Nuki App, designed to provide the optimal balance between battery life, response time, and WiFi stability. The WiFi-related settings remain consistent with previous beta versions.

  • Compatibility
    This mode can be manually enabled by the user through the Nuki App and is primarily intended for situations where the Smart Lock Pro cannot establish or maintain a stable WiFi connection. As the focus of this mode is ensuring maximum compatibility, it results in increased power consumption and should therefore be used with caution.

2.) WiFi Expert Settings

In case the above mentioned modes are not sufficient to achieve a stable WiFi connection there is now also the possibility to manually adjust internal WiFi related settings.

  1. Enter the “Built-in Wi-Fi” screen (via Settings > Features & Configuration > Built-in Wi-Fi)
  2. Tap 7x onto the NETWORK to display the hidden information and settings
  3. Scroll down and enter the WiFi Expert Settings
  4. Adjust the settings according to your requirements

List of adjustable settings

  • Broadcastfilter: This filter defines how many Broadcasts are handled by the Smart Lock Pro, the more packages which are let through the more often the Smart Lock wakes up and the more battery power is drained
  • DTIM skip interval: The DTIM interval is defined by the WiFi router and defines how often a package is transferred to the WiFi client. According to the WiFi specification it is possible to skip certain DTIM packages without getting ignored by the WiFi router, thus skipping DTIMs is a nice way to improve the power consumption as the (passive) device wakes up less frequent
  • Server signal skip: This setting defines the keep alive handling between the Smart Lock Pro and the Nuki server. Again, the more frequent the Smart Lock Pro wakes up, the more battery power is drained.
  • Power Saving Mode: Allows to choose the highest power saving mode of the integrated WiFi module, which supports Performance (UAPSD) and Power saving (FAST-PS).
    Note: If the selected power mode is not supported by the WiFi router the firmware will automatically fall-back to the next lower power saving mode. In the “automatic” mode the firmware will always apply UAPSD (with the fallback option), while in the “compatibility” mode it will always apply FAST-PS per default.
  • Server Signal Response: With this setting the Smart Lock Pro is actively sending a keep-alive package to the Nuki server to ensure the connection is kept online even if single packages are lost.

Important note🚨

Only change the expert settings if the WiFi connection is unstable as any change will impact the Battery consumption and thus lead to shorter Battery lifetime‼️


Prerequisites


Annotation

Until now the Energy mode (Settings > Features & Configuration > Battery) was re-used to change WiFi related settings in the background. This controversal UX has now been cleaned up by introducing the above described WiFi Energy Modes and Expert Settings. Resulting the original Energy mode is now mainly reliant to the Bluetooth advertising intervals (again):

  1. With 4.4.1 suddenly lost bridge connection to smartlock.
    Then updated to 4.4.4 and reboot, still no bridge connection.
    The bridge showed the correct connection to Smartlock and after managing bridge device, bridge was rebooting and bridge connection to smartlock was re-established.


  2. beta 4.4.4 and 4.4.1 and before - NO BATTERY REPORT possible
    See screenshot. Seems like I am not the only one with this problem.

Hope this information helps to look for further bugs.
Any more information necessary, please do not hesitate to ask.
Send troubleshoot report via Nuki App regarding lost smartlock-bridge connection.

1 Like

Same here - I have lost Matter link from Nuki v4 (non pro 4.4.4) and cant access the lock remotely but can access locally via matter (in Home Assistant). I dont really want to deselect matter on the lock in case I cant get it back (I have SkyConnect on HA and Google Hub Max) - I do also have the latest ios beta app installed

2 Likes

I’ve just updated to 4.4.4 on a 4th generation (non pro) to try and fix issues with the button either not responding or having delayed responses. It looked like it had fixed things at first, but actually the issue still seems to be present. Others have mentioned the same thing on this thread - is this a known issue or should I be reporting this separately somewhere?

This might not be relavent, but the device is also picking up on the wrong battery type. It says it is on a power pack and is charging, whereas it is using regular alkaline batteries. I turned off automoatic detection and it still incorrectly says that it is charging.

1 Like

Smart Lock Beta 4.4.4
Smart Lock now waits 2s after door has been closed before executing the “lock immediately after closed”

This new 2 second pause was never necessary for me.
When i’m going to leave the house, i do not want to wait for extra 2 seconds until i can be sure that lock’n’go worked!
So please make it configurable, maybe so:
Number of seconds to wait (0…5) before executing “lock immediately after closed”