Thank you for the feedback. We’re looking into this.
Thanks Jürgen,
In my case:
Border router: sonoff zbdongle-e
Server: Nuc7 with proxmox, HA in a VM
Distance: 7-8 meters aprox.
Without “online” it is quite stable, maybe there are 1-2 resubscription shown in the matter addon logs.
With online enabled I got like 20 resubscription per day in the matter logs.
Thanks Jürgen,
let me know if you need some help or test with the smart lock
Hello @Juergen,
After upgraded my smart lock to beta version 4.2.1 I have the following issue:
The Smart Lock is no more reachable in HomeKit app:
and the Matter link seems not working anymore:
I have tried to:
- Deactivate/Activate the remote access link via Matter but after few minutes the error appear again
- Reboot the smart lock taking off the batteries
- Reboot my only border router (Apple HomePod mini)
- Delete the smart lock accessory to may Apple Home e add it again. It works for some times than is not reachable anymore
- Change the battery settings of the smart lock from “automatic” to “fast”
This has been happening to all of us for days, you have to remove the batteries from the smart lock and then deactivate the remote control from the Nuki app and reconnect and finally restart the smarthome completely. But it will come back if it fails in a few minutes.
1 Like
Selber Fehler. Seit homepod os17.4 ist das so. Die apple tv 17.4 ohne propleme als border router.
With latest beta firmware and battery set to fast at least in my case the online seems much more stable, only 2-3 re subscriptions per day and it is able to reconnect without pulling the batteries out.
There was an iOS app update a few days ago that “Improved usability for remote Access via Thread”.
Since updating the app, remote access via the Nuki app seems better - not perfect - but better.
However, I have noticed connectivity within the Apple Home app has suffered a lot since the update.
Previously, the connection in the Apple Home app was rock solid, whereas now it is reported as “No Response” every time I open the Home app.
If I select the tile in the Home app and maybe open the lock setting in the Home app, it might finally update and show the correct status. It worked perfectly every time before the update, so whatever has changed might have improved the Nuki app a little, but it made the Home app experience worse.
1 Like
The problem seems to stem not from a Nuki update, but the iOS 17.4 roll out of Apple. None of the recent Nuki updates did alter the Matter functionality. Can you please open up a seperate thread for this so that we can track that properly? Thank you.
1 Like
Es müsste der homepod mini bei mir sein. Wenn die ohne strom sind funktioniert es mit apple tv 3gfn ohne probleme
[quote=“Martins Mezavilks, post:31, topic:25402, full:true, username:Martins_Mezavilks”]
Same issue for me with Home Pod Mini updated to iOs 17.4
1 Like
I’m on Android 14 and using just simple wifi. I also have disconnection all the day from the lock to the WiFi since few versions.
It’s quite unusable when I’m away from home
Original post has been updated with release notes for the Smart Lock Beta 4.2.3
This Beta includes the update to Matter 1.2, which opens up the capabilities to differentiate between unlatch and unlock. For now the this new feature is only available in case Home Assistant is used as Matter Hub.
Next to that further improvements and bugfixes are included in terms of Auto Lock, the detection of manual unlatch actions as well as on the overall power consumption of the Pro version.
Additionally a fix is included which improves the overall reconnect behavior for the MQTT API.
As usual please install this beta and provide feedback and your findings through this channel.
Thank you! 
4 Likes
Many thanks for the update.
Tested and the unlock without unlatch works as expected 
Thank you I had been waiting for the Matter 1.2
Unbolt works fine !
My problems on beta 4.2.3 are :
- Battery level not reported correctly (both in Android app and Matter) : still reported as 100% always
- Following log comes predictably every 25 minutes. Only the node which is my Nuki lock. It has never lost connectivity permanently, but commands occasionally are not executed. The log seems to indicate some connection instability.
Mar 16 16:46:08 LivingPI python[448805]: 2024-03-16 16:46:08 LivingPI chip.DMG[448805] ERROR Subscription Liveness timeout with SubscriptionID = 0x5d130ee1, Peer = 01:0000000000000010
Mar 16 16:46:08 LivingPI python[448805]: 2024-03-16 16:46:08 LivingPI matter_server.server.device_controller.[node 16][448805] INFO Previous subscription failed with Error: 50, re-subscribing in 0 ms...
Mar 16 16:46:09 LivingPI python[448805]: 2024-03-16 16:46:09 LivingPI PersistentStorage[448805] INFO DeleteSdkKey: [redacted]
Mar 16 16:46:09 LivingPI python[448805]: 2024-03-16 16:46:09 LivingPI PersistentStorage[448805] INFO Committing...
Mar 16 16:46:09 LivingPI python[448805]: 2024-03-16 16:46:09 LivingPI PersistentStorage[448805] INFO SetSdkKey: f/1/s/0000000000000010 = [redacted]
Mar 16 16:46:09 LivingPI python[448805]: 2024-03-16 16:46:09 LivingPI PersistentStorage[448805] INFO Committing...
Mar 16 16:46:09 LivingPI python[448805]: 2024-03-16 16:46:09 LivingPI PersistentStorage[448805] INFO SetSdkKey: [redacted]
Mar 16 16:46:09 LivingPI python[448805]: 2024-03-16 16:46:09 LivingPI PersistentStorage[448805] INFO Committing...
Mar 16 16:46:10 LivingPI python[448805]: 2024-03-16 16:46:10 LivingPI root[448805] INFO Re-subscription succeeded!
Mar 16 16:46:10 LivingPI python[448805]: 2024-03-16 16:46:10 LivingPI matter_server.server.device_controller.[node 16][448805] INFO Re-Subscription succeeded
Same here, exactly every 25 minutes HA matter shows a Re-subscription:
2024-03-16 20:24:49 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0xc72d762d, Peer = 01:0000000000000008
2024-03-16 20:24:49 (MainThread) INFO [matter_server.server.device_controller.node_8] Previous subscription failed with Error: 50, re-subscribing in 0 ms...
2024-03-16 20:24:56 (MainThread) INFO [root] Re-subscription succeeded!
2024-03-16 20:24:56 (MainThread) INFO [matter_server.server.device_controller.node_8] Re-Subscription succeeded
2024-03-16 20:50:01 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0x987d9e31, Peer = 01:0000000000000008
2024-03-16 20:50:01 (MainThread) INFO [matter_server.server.device_controller.node_8] Previous subscription failed with Error: 50, re-subscribing in 0 ms...
2024-03-16 20:50:06 (MainThread) INFO [root] Re-subscription succeeded!
2024-03-16 20:50:06 (MainThread) INFO [matter_server.server.device_controller.node_8] Re-Subscription succeeded
2024-03-16 21:28:19 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0xe66a548d, Peer = 01:0000000000000008
2024-03-16 21:28:19 (MainThread) INFO [matter_server.server.device_controller.node_8] Previous subscription failed with Error: 50, re-subscribing in 0 ms...
2024-03-16 21:28:35 (MainThread) INFO [root] Re-subscription succeeded!
2024-03-16 21:28:35 (MainThread) INFO [matter_server.server.device_controller.node_8] Re-Subscription succeeded
2024-03-16 21:53:39 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0x188da957, Peer = 01:0000000000000008
2024-03-16 21:53:39 (MainThread) INFO [matter_server.server.device_controller.node_8] Previous subscription failed with Error: 50, re-subscribing in 0 ms...
2024-03-16 21:53:46 (MainThread) INFO [root] Re-subscription succeeded!
2024-03-16 21:53:46 (MainThread) INFO [matter_server.server.device_controller.node_8] Re-Subscription succeeded
The new unlatch feature with Matter 1.2 is quite nice and working as intended, just needed to reload the Matter integration in HA.
I am also having the re-subscription issue in HA every 25 minutes:
2024-03-19 12:40:33 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0xcd3adf88, Peer = 01:0000000000000006
2024-03-19 12:40:33 (MainThread) INFO [matter_server.server.device_controller.node_6] Previous subscription failed with Error: 50, re-subscribing in 0 ms...
2024-03-19 12:40:35 (MainThread) INFO [root] Re-subscription succeeded!
2024-03-19 12:40:35 (MainThread) INFO [matter_server.server.device_controller.node_6] Re-Subscription succeeded
2024-03-19 13:05:43 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0x6a013655, Peer = 01:0000000000000006
2024-03-19 13:05:43 (MainThread) INFO [matter_server.server.device_controller.node_6] Previous subscription failed with Error: 50, re-subscribing in 0 ms...
2024-03-19 13:05:46 (MainThread) INFO [root] Re-subscription succeeded!
2024-03-19 13:05:46 (MainThread) INFO [matter_server.server.device_controller.node_6] Re-Subscription succeeded
2024-03-19 13:30:54 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0xe24d2549, Peer = 01:0000000000000006
2024-03-19 13:30:54 (MainThread) INFO [matter_server.server.device_controller.node_6] Previous subscription failed with Error: 50, re-subscribing in 0 ms...
2024-03-19 13:30:57 (MainThread) INFO [root] Re-subscription succeeded!
2024-03-19 13:30:57 (MainThread) INFO [matter_server.server.device_controller.node_6] Re-Subscription succeeded
@Stefan_Reiterer is there any hope of seeing an added layer of security with the optional setting to require a PIN to unlock the Nuki over Matter?
Original post has been updated with release notes for the Smart Lock Beta 4.2.4
This Beta includes further improvements for the WiFi reconnect handling as well as the general WiFi connection. Furthermore the power consumption gets decreased with this build due to adaptations of the dynamic BLE advertising as well as improvements on the WiFi connection handling.
Please install this build and provide feedback via this channel - thank you
1 Like
I’ve been having connectivity problems for a while with the beta including current 4.2.4.
See my log which was taken from a recently power cycled Smart Lock 4.0 and newly started Matter server (over Thread). Node 23 is the Smart Lock. Other nodes are different products, other brands, working fine. Node 23 shows succesfully discovered on mdns , but fails the rest of the connection process.
I never had this sort of problems before I was on the beta firmware.
-- Journal begins at Sat 2024-03-23 16:19:09 CET, ends at Sat 2024-03-23 16:30:04 CET. --
Mar 23 16:19:38 LivingPI systemd[1]: Started Mijn Matter Server.
Mar 23 16:19:43 LivingPI python[1309]: 2024-03-23 16:19:43 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Logging...
Mar 23 16:19:43 LivingPI python[1309]: 2024-03-23 16:19:43 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Controller Stack...
Mar 23 16:19:43 LivingPI python[1309]: [1711207183.591846][1309:1309] CHIP:CTL: Setting attestation nonce to random value
Mar 23 16:19:43 LivingPI python[1309]: [1711207183.612406][1309:1309] CHIP:CTL: Setting CSR nonce to random value
Mar 23 16:19:43 LivingPI python[1309]: [1711207183.688300][1309:1309] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
Mar 23 16:19:43 LivingPI python[1309]: [1711207183.688563][1309:1309] CHIP:DL: writing settings to file (/tmp/chip_kvs-MZvsv9)
Mar 23 16:19:43 LivingPI python[1309]: [1711207183.688740][1309:1309] CHIP:DL: renamed tmp file to file (/tmp/chip_kvs)
Mar 23 16:19:43 LivingPI python[1309]: [1711207183.690649][1309:1309] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_factory.ini
Mar 23 16:19:43 LivingPI python[1309]: [1711207183.706435][1309:1309] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_config.ini
Mar 23 16:19:43 LivingPI python[1309]: [1711207183.707018][1309:1309] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_counters.ini
Mar 23 16:19:43 LivingPI python[1309]: [1711207183.711670][1309:1309] CHIP:DL: writing settings to file (/data/chip_counters.ini-aTY1Ba)
Mar 23 16:19:43 LivingPI python[1309]: [1711207183.712158][1309:1309] CHIP:DL: renamed tmp file to file (/data/chip_counters.ini)
Mar 23 16:19:43 LivingPI python[1309]: [1711207183.712204][1309:1309] CHIP:DL: NVS set: chip-counters/reboot-count = 94 (0x5E)
Mar 23 16:19:43 LivingPI python[1309]: [1711207183.712743][1309:1309] CHIP:DL: Got Ethernet interface: eth0
Mar 23 16:19:43 LivingPI python[1309]: [1711207183.713020][1309:1309] CHIP:DL: Found the primary Ethernet interface:eth0
Mar 23 16:19:43 LivingPI python[1309]: [1711207183.713300][1309:1309] CHIP:DL: Got WiFi interface: wlan0
Mar 23 16:19:43 LivingPI python[1309]: [1711207183.713354][1309:1309] CHIP:DL: Failed to reset WiFi statistic counts
Mar 23 16:19:43 LivingPI python[1309]: 2024-03-23 16:19:43 (MainThread) WARNING [PersistentStorage] Initializing persistent storage from file: /home/pi/.matter_server/chip.json
Mar 23 16:19:59 LivingPI python[1309]: 2024-03-23 16:19:59 (MainThread) WARNING [PersistentStorage] Loading configuration from /home/pi/.matter_server/chip.json...
Mar 23 16:19:59 LivingPI python[1309]: 2024-03-23 16:19:59 (MainThread) WARNING [CertificateAuthorityManager] Loading certificate authorities from storage...
Mar 23 16:19:59 LivingPI python[1309]: 2024-03-23 16:19:59 (MainThread) WARNING [CertificateAuthority] New CertificateAuthority at index 1
Mar 23 16:19:59 LivingPI python[1309]: 2024-03-23 16:19:59 (MainThread) WARNING [CertificateAuthority] Loading fabric admins from storage...
Mar 23 16:19:59 LivingPI python[1309]: 2024-03-23 16:19:59 (MainThread) WARNING [FabricAdmin] New FabricAdmin: FabricId: 0x0000000000000001, VendorId = 0xFFF1
Mar 23 16:19:59 LivingPI python[1309]: 2024-03-23 16:19:59 (MainThread) INFO [matter_server.server.stack] CHIP Controller Stack initialized.
Mar 23 16:19:59 LivingPI python[1309]: 2024-03-23 16:19:59 (MainThread) INFO [matter_server.server.server] Starting the Matter Server...
Mar 23 16:19:59 LivingPI python[1309]: 2024-03-23 16:19:59 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Skip fetching certificates (already fetched within the last 24h).
Mar 23 16:19:59 LivingPI python[1309]: 2024-03-23 16:19:59 (MainThread) WARNING [FabricAdmin] Allocating new controller with CaIndex: 1, FabricId: 0x0000000000000001, NodeId: 0x000000000001B669, CatTags: []
Mar 23 16:20:00 LivingPI python[1309]: 2024-03-23 16:20:00 (Dummy-2) CHIP_ERROR [chip.native.DL] Long dispatch time: 626 ms, for event type 2
Mar 23 16:20:00 LivingPI python[1309]: 2024-03-23 16:20:00 (MainThread) INFO [matter_server.server.device_controller] Loaded 6 nodes from stored configuration
Mar 23 16:20:00 LivingPI python[1309]: 2024-03-23 16:20:00 (MainThread) INFO [matter_server.server.vendor_info] Loading vendor info from storage.
Mar 23 16:20:00 LivingPI python[1309]: 2024-03-23 16:20:00 (MainThread) INFO [matter_server.server.vendor_info] Loaded 181 vendors from storage.
Mar 23 16:20:00 LivingPI python[1309]: 2024-03-23 16:20:00 (MainThread) INFO [matter_server.server.vendor_info] Fetching the latest vendor info from DCL.
Mar 23 16:20:00 LivingPI python[1309]: 2024-03-23 16:20:00 (MainThread) INFO [matter_server.server.vendor_info] Fetched 179 vendors from DCL.
Mar 23 16:20:00 LivingPI python[1309]: 2024-03-23 16:20:00 (MainThread) INFO [matter_server.server.vendor_info] Saving vendor info to storage.
Mar 23 16:20:01 LivingPI python[1309]: 2024-03-23 16:20:01 (MainThread) INFO [matter_server.server.device_controller.mdns] Node 1 discovered on MDNS
Mar 23 16:20:01 LivingPI python[1309]: 2024-03-23 16:20:01 (MainThread) INFO [matter_server.server.device_controller.mdns] Node 4 discovered on MDNS
Mar 23 16:20:01 LivingPI python[1309]: 2024-03-23 16:20:01 (MainThread) INFO [matter_server.server.device_controller.mdns] Node 22 discovered on MDNS
Mar 23 16:20:01 LivingPI python[1309]: 2024-03-23 16:20:01 (MainThread) INFO [matter_server.server.device_controller.mdns] Node 23 discovered on MDNS
Mar 23 16:20:01 LivingPI python[1309]: 2024-03-23 16:20:01 (MainThread) INFO [matter_server.server.device_controller.mdns] Node 10 discovered on MDNS
Mar 23 16:20:01 LivingPI python[1309]: 2024-03-23 16:20:01 (MainThread) INFO [matter_server.server.device_controller.node_1] Setting-up node...
Mar 23 16:20:01 LivingPI python[1309]: 2024-03-23 16:20:01 (MainThread) INFO [matter_server.server.device_controller.node_4] Setting-up node...
Mar 23 16:20:01 LivingPI python[1309]: 2024-03-23 16:20:01 (MainThread) INFO [matter_server.server.device_controller.node_22] Setting-up node...
Mar 23 16:20:01 LivingPI python[1309]: 2024-03-23 16:20:01 (MainThread) INFO [matter_server.server.device_controller.node_23] Setting-up node...
Mar 23 16:20:01 LivingPI python[1309]: 2024-03-23 16:20:01 (MainThread) INFO [matter_server.server.device_controller.node_10] Setting-up node...
Mar 23 16:20:01 LivingPI python[1309]: 2024-03-23 16:20:01 (MainThread) INFO [matter_server.server.device_controller.mdns] Node 17 discovered on MDNS
Mar 23 16:20:01 LivingPI python[1309]: 2024-03-23 16:20:01 (MainThread) INFO [matter_server.server.device_controller.node_17] Setting-up node...
Mar 23 16:20:02 LivingPI python[1309]: 2024-03-23 16:20:02 (MainThread) INFO [matter_server.server.device_controller.node_1] Setting up attributes and events subscription.
Mar 23 16:20:04 LivingPI python[1309]: 2024-03-23 16:20:04 (MainThread) INFO [matter_server.server.device_controller.node_4] Setting up attributes and events subscription.
Mar 23 16:20:05 LivingPI python[1309]: 2024-03-23 16:20:05 (MainThread) INFO [matter_server.server.device_controller.node_22] Setting up attributes and events subscription.
Mar 23 16:20:13 LivingPI python[1309]: 2024-03-23 16:20:13 (MainThread) INFO [matter_server.server.device_controller.node_1] Subscription succeeded
Mar 23 16:20:18 LivingPI python[1309]: 2024-03-23 16:20:18 (MainThread) INFO [matter_server.server.device_controller.node_22] Subscription succeeded
Mar 23 16:20:25 LivingPI python[1309]: 2024-03-23 16:20:25 (MainThread) INFO [matter_server.server.device_controller.node_4] Subscription succeeded
Mar 23 16:20:34 LivingPI python[1309]: 2024-03-23 16:20:34 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:220298590 on exchange 35192i sendCount: 4 max retries: 4
Mar 23 16:20:40 LivingPI python[1309]: 2024-03-23 16:20:40 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 1
Mar 23 16:20:42 LivingPI python[1309]: 2024-03-23 16:20:42 (MainThread) INFO [matter_server.server.device_controller.node_10] Setting up attributes and events subscription.
Mar 23 16:20:42 LivingPI python[1309]: 2024-03-23 16:20:42 (MainThread) INFO [matter_server.server.device_controller.node_17] Setting up attributes and events subscription.
Mar 23 16:20:43 LivingPI python[1309]: 2024-03-23 16:20:43 (MainThread) INFO [matter_server.server.device_controller] Attempting to resolve node 23... (attempt 2 of 2)
Mar 23 16:20:44 LivingPI python[1309]: 2024-03-23 16:20:44 (MainThread) INFO [matter_server.server.device_controller.node_17] Subscription succeeded
Mar 23 16:20:57 LivingPI python[1309]: 2024-03-23 16:20:57 (MainThread) INFO [matter_server.server.device_controller.node_10] Subscription succeeded
Mar 23 16:21:14 LivingPI python[1309]: 2024-03-23 16:21:14 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:220298597 on exchange 35197i sendCount: 4 max retries: 4
Mar 23 16:21:18 LivingPI python[1309]: 2024-03-23 16:21:18 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 1
Mar 23 16:21:18 LivingPI python[1309]: 2024-03-23 16:21:18 (MainThread) WARNING [matter_server.server.device_controller.node_23] Setup for node failed: Unable to resolve Node 23