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

[SchmuFoo (Jan S.)]

SL4P MQTT Problems since Nuki FW Update 4.1.8

FYI that I have installed firmware 4.2.4 beta on 22.03.2024 and since then I see a bunch reconnects after the Nuki has closed the TCP Connection to the Broker. root@loxberry:/opt/loxberry# grep -i Nuki /var/log/mosquitto/mosquitto.log 2024-03-19T16:10:59: New client connected from 192.168.1.103:52442 as Nuki_39C748EC (p2, c1, k300, u'loxberry'). 2024-03-19T19:32:02: Client Nuki_39C748EC already connected, closing old connection. 2024-03-19T19:32:02: New client connected from 192.168.1.103:5244…

[Toni_CB (Toni Cerdà)]

This last update seems to break matter in HA, when I try to lock or unlock I get the following error:

Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/commands.py:239
integration: Home Assistant WebSocket API(documentation, issues)
First occurred: 21:24:11 (3 occurrences)
Last logged: 21:29:16

• [140153390413248] InteractionModelError: UnsupportedAccess (0x7e)
• [140153477776448] InteractionModelError: UnsupportedAccess (0x7e)

Also mqtt is responding very slow, before it was instantaneous.

[cso (Csowada)]

With 4.2.3 and Nuki Hub (BLE API) the activity log worked. Now with 4.2.4 I receive again not the last 5 entries, it looks like the wrong order. Also the authorization data is not correct.

[FabioF (Fabio Fiorina)]

Poor Wifi connection Nuki 4th gen Pro

Hi all, with version 4.2.4 beta and battery set to “fast” I have the same behavior as before: when the SL4P is connected to the router’s weak signal the Wifi connection is stable and also the connection to the Nuki server is stable. When the SL4P is connected to the NETGEAR repeater’s strong signal the Wifi connection is stable but the connection to Nuki server is DOWN and UP every 3-4 minutes (looking at the MQTT messages) and the APP shows an “offline” for the 95% of the time. Best regards…

[Toni_CB (Toni Cerdà)]

Is matter actions like open/close working for you? With this last firmware I can not operate the lock using home assistant.

[Toni_CB (Toni Cerdà)]

Is it possible to downgrade to 4.2.3? I am going on vacation some days and last fw broke so many things:

• not able to open/close using matter with HA
• very slow response from mqtt
• battery draining very fast
• sometimes door is open later when 2 persons are in the entrance, much late, when you are already inside home. I had to deactivate Auto Unlock for security reasons.

4.2.3 was working perfect in my case.

[Stefan_Reiterer]

Original post has been updated with release notes for the Smart Lock Beta 4.2.5

This Beta includes improvements on the MQTT connection (adjusted internal settings and optimized timeout handling) as well as further optimizations on the power consumption due to an adapted handling of unlatch actions.

Please install this build and provide feedback via this channel - thank you

[828 (Dan)]

I can confirm with 4.2.5 . mqtt is more stable than previous (4.2.4 release)

[paolo1983]

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?

[Stephan87 (Stephan)]

@Toni_CB

break matter

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

[Toni_CB (Toni Cerdà)]

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.

[LookedPath (Simone de Blasiis)]

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

[SchmuFoo (Jan S.)]

@Stephan87

3- very slow response from mqtt.

With regards to this I have the following questions also for you:

SL4P MQTT Problems since Nuki FW Update 4.1.8

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)

[Stephan87 (Stephan)]

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

[Toni_CB (Toni Cerdà)]

I have it in medium and no problems so far, it is a non pro version.

[Stephan87 (Stephan)]

Did you receive notification when you used Button on smart lock 4 ( in apple home or Home assistant)

[Toni_CB (Toni Cerdà)]

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.

[Toni_CB (Toni Cerdà)]

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

[Stephan87 (Stephan)]

Can you send me additional steps? to Add mqtt in home assistant

[Toni_CB (Toni Cerdà)]

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.