@jeje My questions are the same too 
This is explained. Decided to tell my wife anyway to validate it wasnt here auto unlock. Turns out she left the house and had returned 8 minutes prior to the unlatching and left her phone downstairs. So it was a very much delayed auto unlock. This not being logged was probably due the forever unlatched bug crashing the lock. Hopefully that is fixed with 4.3.6.
Hi mate, I’ve reported this issue already two times to Nuki team, with log and screenshots of the history. However, they told me that it is linked to the phone since this is built up the Bluetooth connection to the Lock. I owned a version 3 lock before and have not witnessed such behaviour before. But since “upgrading” to SL4 this happen sometimes unexpectedly. It happens also with mi wife’s phone. So I have to deactivate one of the main feature of Nuki SL. 
If it’s any consolation I had this with my SL3 too - it’s not just isolated to the 4.
Best, Dave
Changelog is updated in the first post of the topic.
4.3.6 has stabilization improvements which aim at improving the problem that some people see where the lock remains in forever unlatched state during a lock action.
1 Like
I‘ve switched from MQTT to Matter-over-Thread to connect the Nuki with Home Assistant and avoid being locked out. It has everything I want except the state of the door sensor. Is it planned to expose that status also over Matter?
I know about https://support.nuki.io/hc/de/articles/19945508775953-Ist-der-Status-des-Door-Sensors-über-Matter-verfügbar and Expose Door Sensor state over Matter, but the situation has changed a bit: Home Assistant added support for Matter 1.3 (which includes the DPS feature attribute) in May.
-
We do not comment about planned features or our roadmap here in the forum.
-
There is already a feature request for this. Please make sure that you vote for it:
Expose Door Sensor state over Matter
I already did, thanks 
Thank you for this update 
Its great to hear that 4.3.6 includes stabilization improvements, especially addressing the issue with the lock remaining in an unlatched state.
thank you for this update that fixes unlatch, but wifi issues are still there. My smartlock pro can’t connect to wifi and it is very close to the router.
Good morning, my Nuki Smart 4 pro after update 4.3.6 stopped connecting both via wifi and via thread. How can I solve it? Is it possible to go back to the official firmware? THANK YOU
I joined the beta starting with version 4.3.5, and updated to 4.3.6 as soon as it was available.
Since joined my SL4 Pro doesn’t react to all button presses.
From the app it works fine, and so from HA using mqtt.
But pressing the button to lock or unlock a lot of times doesn’t do anything.
Is this a known issue?
There is one known issue around button press, which will be addressed in the next beta (4.3.7). Please report back once the beta is out if your problem is solved with it.
Your Smart Lock is connected perfectly fine (via Thread) since a few days. If you still have problems you might switch back to WIFI. Follow this instructions to do so: Smart Lock WiFi/Thread/MQTT connection troubleshooting / FAQ - #3 by Stefan_Reiterer
1 Like
Original post has been updated with release notes for the Smart Lock (4th generation) Beta 4.3.7
This Beta includes an adaption for the reconnect handling of the Smart Lock Pro in combination with the WiFi / Nuki Server / MQTT connection and shall improve the situation especially for users which are actively using the MQTT API.
Next to that slight improvements are included for the double-click detection as well as for the clutch handling, which is now assuring that the smart lock is properly disengaging the clutch even when the batteries run low.
Finally a stability improvement is also part of the Beta which ensures that the smart lock is not getting stuck unresponsive via Bluetooth / WiFi.
Please report your findings within this channel.
Thank you for your provided feedback! 
1 Like
Dear Stefan,
my Nuki is unable to install the newest Beta. It’s downloaded and transferred to the lock, but ends up with an error 23.
Edit: After putting out the battery for 5 Minutes, I was able to install the beta.
Hi there,
This firmware ( 4.3.6 beta ) seems to work nicely. I lost the MQTT connection, and it has been restored within 2 seconds
Let check now the 4.3.7 release.
Upgrading my SL4Pro from 4.3.6 to 4.3.7 fails with error code 23 too.
PS: 4.3.6 is working quite well for with Matter over Thread.
Same here. After battery removal and waiting a couple of minutes the SW 4.3.7 is uploaded and working so far.
1 Like
It did the trick, thanks!
Hi there. 4.3.7 installed fine with me, but it has not fixed the double click action. Intermittently failing to respond to double click on the button (we have ours as single click lock and double click unlock). So far single click seems to be fine. This behaviour was also a problem in 4.3.6, but fine before that.