Since 22.03.23 - 16:58
I have the same issue with 4.2.4: at the beginning It works well but after some days the lock doesnāt respond to home assistant. For example this morning i wasnāt able to open the door from home assistant. I opened the nuki app and by moving something in the mqqt sectionā¦the lock respond again from home assistant.
This issue Is very annoying.
I used for 10 months nuki 3 pro with mqqt and i havent any issue!!!
I assigned a static ip at the nuki lock in my router and i managed the Power saving from auto to medium.
My mqtt broker Is mosquitto
Help 
2 Likes
I think the same, is very annoying.
Every 3 or 5 days I have the same problems. You canāt trust this lock.
There are many people all over the world waiting for a solution that never comes. This product is not cheap.
1 Like
Well guys, Iām not affiliated to nuki in any way, but it seems that there is an issue with WiFi/MQTT and Matter integrated. What we all know so far, it does not happen with the 3 Pro. so thatās my logical conclusion. Iām not a developer and Iām sure they do their best and some solutions (if they exist) take time.
From my side the issue seems fixed sind 4.2.4, but Iām not using matter at all.
Keep your heards up, itās still the best lock I tried, keeping the 3 pro out of the comparrison.
I have Just reset the smart lock and reconfigured from 0. I Will tell if in the next days It Will disconnect from home assistantā¦
Fixed with 4.2.5 Beta
It seems to work with 4.2.5ā¦
In the last two days no issueā¦
I have the issue again with 4.2.5.
Can you explain this a bit more please? In this|my Thread various problems I had where discussed and also fixed all the time.
(From my side there is, BTW, only one last minor problem existing: Sometimes there is a delay of handling MQTT LockActions, which a) can be seen in an traffic capture and seems to be related with the MQTT KeepAlive process and b) is also already under investigation by Nuki)
still have MQTT trouble with 4.2.5 
What problem exactly?
ā
First problem, I have a raspberry PI 3B+ near to the nuki (~50cm) ; WiFi is perfect on my raspberry (RTT 5ms) but signal is medium/poor with my SL4 (RTT ~900ms).
I manage my SL4 via MQTT by sending the payload 1 or 2 to the topic nuki/XXXXXXXX/lockAction
Second problem, The SL4 randomly disconnects from the broker (mosquitto) and very often. Moreover, and there is a lag between the MQTT command and the lock action (sometimes my request is even lost).
After some days i can say that with 4.2.5 mqtt seems to work ā¦
RTT of a ping is not a proper measure of WiFi quality. The Smart Lock runs on batteries and RTT times >1.000ms are normal. If you have problems with frequent reconnects follow the steps described here: Smart Lock WiFi/Thread/MQTT connection troubleshooting / FAQ
Update from my side:
After the latest updates to 4.2.6 and the beta version 4.3.1 it is still not stable.
It is beter then before the update, but still not good enough.
Best regards,
Jacob
Give 4.3.2 a try:
Done, Letās hope it is the final fix, for this.
Since three days not a single delay - Seems to be fixed with 4.3.2
A possible new ātypeā of issue with 4.2.6 that I didnāt have with 4.1.8.
I can unlock via MQTT almost always, but locking almost never works. The lock blinks, indicating itās unlocked, I issue the MQTT command to lock it and it flashes white once, but doesnāt lock. After this, it doesnāt blink anymore, possibly indicating it āthinksā itās locked now?
If I rotate the lock manually (as to unlock it) it starts blinking again and I can then lock it with MQTT.
This doesnāt happen if I lock with the app, so pretty weird.
Looking forward to 4.3.2 (waiting for stable though). For me, 4.1.8 was better than 4.2.6.
Thanks everyone
Then please open a new thread for it and do not write in the 4.1.8 thread.
You could check what the Activity log of the Smart Lock says to this lock commands.