I can confirm with 4.2.5 . mqtt is more stable than previous (4.2.4 release)
With 4.2.5 mqqt seems to work! In the last 2 days no issue!
A question: what Is the suggested Power saving setting? Auto or medium?
The Smart Lock Beta 4.2.5 update broke :
1-Button on Smart Lock 4 Pro ( when Button used to Unlock/Lock its work but notification not work ( notification are not sent to Nuki App or apple home ) To update the lock status.
2- lock status break only when used Button on smart Lock 4 pro ( lock / unlock ) .
3- very slow response from mqtt.
4- break matter
My issues with the slow response of MQTT and non working matter were resolved after removing a thread repeater I had between the Nuki and the router. With a direct connection now, it works correctly.
My Nuki is the only device in the Thread network and I only have a Thread Border Router, Home Assistant.
After the 4.2.5 update it seems that commands are more reliable to the Nuki but it won’t update it’s status.
If I send a command it will execute it but it won’t update its status to the Matter server, the older release would loose its connection completely and stop responding to commands and updating the Matter server on status changes.
With this new release I’ve seen a reduction in the re-subrscription logs in the Matter servers but I’ve also seen a surge in errors:
2024-03-31 07:15:13 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0x05277932, Peer = 01:0000000000000006
2024-03-31 07:15:13 (MainThread) INFO [matter_server.server.device_controller.node_6] Previous subscription failed with Error: 50, re-subscribing in 0 ms...
2024-03-31 07:15:16 (MainThread) INFO [root] Re-subscription succeeded!
2024-03-31 07:15:16 (MainThread) INFO [matter_server.server.device_controller.node_6] Re-Subscription succeeded
2024-03-31 07:40:23 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0x9ad297b3, Peer = 01:0000000000000006
2024-03-31 07:40:23 (MainThread) INFO [matter_server.server.device_controller.node_6] Previous subscription failed with Error: 50, re-subscribing in 0 ms...
2024-03-31 07:40:27 (MainThread) INFO [root] Re-subscription succeeded!
2024-03-31 07:40:27 (MainThread) INFO [matter_server.server.device_controller.node_6] Re-Subscription succeeded
2024-03-31 07:58:39 (MainThread) INFO [matter_server.server.device_controller.mdns] Node 6 re-discovered on MDNS
2024-03-31 07:58:39 (MainThread) INFO [matter_server.server.device_controller.node_6] Setting-up node...
2024-03-31 07:58:39 (MainThread) INFO [matter_server.server.device_controller.node_6] Unsubscribing from existing subscription.
2024-03-31 07:58:39 (MainThread) INFO [matter_server.server.device_controller.node_6] Setting up attributes and events subscription.
2024-03-31 07:58:39 (MainThread) WARNING [matter_server.server.device_controller.node_6] Unable to subscribe to Node: src/inet/UDPEndPointImplSockets.cpp:417: OS Error 0x02000013: No such device
2024-04-01 22:09:01 (MainThread) INFO [matter_server.server.device_controller.mdns] Node 6 discovered on MDNS
2024-04-01 22:09:01 (MainThread) INFO [matter_server.server.device_controller.node_6] Setting-up node...
2024-04-01 22:09:01 (MainThread) INFO [matter_server.server.device_controller.node_6] Setting up attributes and events subscription.
2024-04-01 22:09:01 (MainThread) WARNING [matter_server.server.device_controller.node_6] Unable to subscribe to Node: src/inet/UDPEndPointImplSockets.cpp:417: OS Error 0x02000013: No such device
2024-04-02 08:21:28 (MainThread) INFO [matter_server.server.device_controller.mdns] Node 6 discovered on MDNS
2024-04-02 08:21:28 (MainThread) INFO [matter_server.server.device_controller.node_6] Setting-up node...
2024-04-02 08:21:28 (MainThread) INFO [matter_server.server.device_controller.node_6] Setting up attributes and events subscription.
2024-04-02 08:21:28 (MainThread) WARNING [matter_server.server.device_controller.node_6] Unable to subscribe to Node: src/inet/UDPEndPointImplSockets.cpp:417: OS Error 0x02000013: No such device
With regards to this I have the following questions also for you:
I confirmed the same problem in an update 4.2.5 and
4.2.4
The Smart Lock Beta 4.2.5 update broke :
1-Button on Smart Lock 4 Pro ( when Button used to Unlock/Lock its work but notification not work ( notification are not sent to Nuki App or apple home ) To update the lock status.
2- lock status break only when used Button on smart Lock 4 pro ( lock / unlock ) .
3- break matter
4- Slow response to receiving alerts ( lock -unlock ) notification
I have it in medium and no problems so far, it is a non pro version.
Did you receive notification when you used Button on smart lock 4 ( in apple home or Home assistant)
Yes, both matter and mqtt report when button is used:
Nuki app:
mqtt:
matter:
The only difference is that mqtt also reports “is locking/unlocking”.
About notifications in nuki app I am not using them since my Nuki is offline.
mmm, checking the logs I can see that there is a open button action at 7:47 and auto lock at 7:57 not registered in matter but correct in mqtt 
Can you send me additional steps? to Add mqtt in home assistant
Hi, you have to install mqtt in HA, for example the mosquitto add-on. Then enable mqtt in Nuki App, in the Smart Home section → MQTT and add your server details (IP, user, password). Before Nuki should be connected either with wifi or with matter/thread OBTR with NAT64. There is already a post about HA in this forum, I suggest you check it.
Thanks Toni
it’s Possible to setup Mqtt withe Matter at the same time
1- MQTT Home Assistent
2 Matter Apple TV or matter in Home Assistent
What ist your setup ? Can you share
So far, 4.2.5 is working great for me with both Home-Assistant Matter/Thread and MQTT at the same time. I use both as MQTT provides more information about the lock, most importantly the battery level, but control the lock over Thread which is supposedly more energy efficient.
If battery level was available via Thread, I’d only use that.
Edit: turns out I now see a Battery entity via Matter/Thread after re-interviewing the lock:
Note: as already mentioned in this thread, actual firmware version is not updated in HA.
I’ll probably disable MQTT to save battery then.
MQTT still does show a bit more information about the lock state:
But just as I said this, it seems all of my Smartlock MQTT entities are unavailable now.
Lost them 1h ago…
Edit: and they came back only after a few hours:
First time it occurred over the course of several days (actually installed the lock on Saturday):
Hi all,
I’ve installed v.4.2.5 a few days ago, after having many problems with 4.1.8; I have set up both matter (using Apple Home) and MQTT. The lock is very inconsistent in its behavior: the MQTT entities regularly become unavailable and then go back online on their own a few hours later.
I have to say I’m very disappointed; a €350 smart lock should not have these issues.
1 Like
Hi, I only use a Sonoff Border Router plugged directly to HA (thread → matter) and MQTT enabled in Nuki. It is a non pro version, so I does not have WiFi.
I do not have Nuki online. The online causes a lot of unavailable issues in my case, without it is very stable.
4.2.6 installed this morning (CEST) ; it seems WiFi is more stable (only 2 ping lost rather than >300 for a same period)
I really look forward to be tomorrow to evaluate this release 