Thank you very much for the information, I will do the same.
Good morning, I have updated to 4.3.10 and I have noticed that when the SL4P is locked it does not open manually by turning the knob. I donât know if this is normal as I had not tried it before, is it?
Forget what i said, it was a physical problem with my lock. It works fine, sorry.
I bought a Matter antenna because I had lot of issues with wifi and mqtt.
It worked well but since 4.4.0, sometimes it doesnât work and the button on the smart lock doesnât work immediately, sometimes I have to push 10 times to have an action.
Help me out: what is a Matter antenna?
Initial post has been updated with the release notes of the new Beta 4.4.1.
With this Beta a critical issue has been resolved, which lead to the effect that the Smart Lock was not reachable anymore via Bluetooth, which not only affects the availability via the Nuki Bridge but also via the Nuki App and other accessories.
If you are affected by the behavior mentioned in Nuki Bridge lost connection to Smartlock 4.0 the best way to update your device is as following:
-
Make sure that your Smart Lock is registered for the FW Beta
a. If not, send me your Smart Lock ID via PM and we will add it to the FW Beta -
Unplug your Nuki Bridge
-
Manually install the Beta FW via the Nuki App
-
Again plug in your Nuki Bridge
As usual we kindly ask you to install this version and provide feedback into this channel.
A radio antenna to be able to use matter through openthread and plugged to my home assistant box.
Hello.
Still the same problem than in version 4.4.0
Since I installed this Version I have problems with the Remote Access via Matter for Alexa.
I installed this Firmware and Matter was working for 1 day. Since yesterday I have no chance to connect remote via Matter, only via WiFi.
In the Alexa app itself I can open and close the Lock from Home, but not in the Nuki app via remote. Means the Matter itself is connected, only the Remote is switching off all the time if I try to switch it on.
In the previous Version I never had this problem.
The Beta releases 4.4.0 and 4.4.1 did not contain any change touching the implementation, thus the described behavior might also re-occur.
Iâll follow up with you individually.
I got a weird behaviour with the battery level:
within less than two days , the level dropped from 81 to 34% without any special reasons:
This is a known issue which Nuki canât send seem to reproduce. Itâs up to us (I have the same issue from time to time) to identify the source. Are you using UniFi hardware? And do you have the device integrated using MQTT or Matter for instance with Home Assistant?
Iâm controlling the lock only using MQTT commands. I removed the bluetooth interface from my home assistant in order to stop the ibeacon sensor which was interrogating the nuki sensor. Lets check now.
My wifi network is based on Unify hardware
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.
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?