Nuki Smart Lock Pro 4.0 suddenly cannot connect

[DarthSonic]

The problem

Nuki Smart Lock Pro 4.0 suddenly cannot connect. It worked for over 3 months without any issues. Suddenly yesterday it disconnected and cannot be reconnected. Several other matter devices work. One of them (door sensor) is under one meter away positioned from Nuki Smart Lock and still working. So, it cannot be a bad signal strength.

I removed Nuki from Matter integration and removed Matter in Nuki config. Adding to HA after that does not work with "No connection to thread-network "home-assistant" possible". So network is seen, but connection is not established.

What version of Home Assistant Core has the issue?

core-2024.5.5

What was the last working version of Home Assistant Core?

core-2024.5.5

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Matter (BETA)

Link to integration documentation on our website

https://www.home-assistant.io/integrations/matter/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2024-06-03 12:27:15.044 (MainThread) INFO [matter_server.server.device_controller.node_4] Re-Subscription succeeded
2024-06-03 12:36:32.147 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:128639958 on exchange 9648i with Node: <0000000000000004, 1> sendCount: 4 max retries: 4
2024-06-03 12:36:36.810 (MainThread) ERROR [matter_server.server.client_handler] [140633460942928] Error while handling: device_command (node 4): src/app/CommandSender.cpp:328: CHIP Error 0x00000032: Timeout
2024-06-03 12:58:59.618 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0x9a451bd6, Peer = 01:0000000000000004
2024-06-03 12:58:59.619 (MainThread) INFO [matter_server.server.device_controller.node_4] Previous subscription failed with Error: 50, re-subscribing in 0 ms...
2024-06-03 12:59:12.649 (MainThread) INFO [root] Re-subscription succeeded!
2024-06-03 12:59:12.649 (MainThread) INFO [matter_server.server.device_controller.node_4] Re-Subscription succeeded
2024-06-03 13:24:16.873 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0x7b1f981e, Peer = 01:0000000000000004
2024-06-03 13:24:16.874 (MainThread) INFO [matter_server.server.device_controller.node_4] Previous subscription failed with Error: 50, re-subscribing in 0 ms...
2024-06-03 13:24:28.859 (MainThread) INFO [root] Re-subscription succeeded!
2024-06-03 13:24:28.860 (MainThread) INFO [matter_server.server.device_controller.node_4] Re-Subscription succeeded
2024-06-03 13:49:33.084 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0x67c57365, Peer = 01:0000000000000004
2024-06-03 13:49:33.085 (MainThread) INFO [matter_server.server.device_controller.node_4] Previous subscription failed with Error: 50, re-subscribing in 0 ms...
2024-06-03 13:50:30.978 (Dummy-2) CHIP_ERROR [chip.native.DMG] Time out! failed to receive report data from Exchange: 9654i with Node: <0000000000000004, 1>
2024-06-03 13:50:30.980 (MainThread) INFO [matter_server.server.device_controller.node_4] Previous subscription failed with Error: 50, re-subscribing in 4834 ms...
2024-06-03 13:51:08.688 (Dummy-2) CHIP_ERROR [chip.native.DMG] Time out! failed to receive report data from Exchange: 9655i with Node: <0000000000000004, 1>
2024-06-03 13:51:08.690 (MainThread) INFO [matter_server.server.device_controller.node_4] Previous subscription failed with Error: 50, re-subscribing in 4055 ms...
2024-06-03 13:51:08.691 (MainThread) INFO [matter_server.server.device_controller] Marked node 4 as unavailable
2024-06-03 13:51:44.602 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:90930241 on exchange 9657i with Node: <0000000000000004, 1> sendCount: 4 max retries: 4
2024-06-03 13:51:51.901 (Dummy-2) CHIP_ERROR [chip.native.DMG] Time out! failed to receive report data from Exchange: 9657i with Node: <0000000000000004, 1>
2024-06-03 13:51:51.903 (MainThread) INFO [matter_server.server.device_controller.node_4] Previous subscription failed with Error: 50, re-subscribing in 17589 ms...
2024-06-03 13:52:42.805 (Dummy-2) CHIP_ERROR [chip.native.DMG] Time out! failed to receive report data from Exchange: 9659i with Node: <0000000000000004, 1>
2024-06-03 13:52:42.809 (MainThread) INFO [matter_server.server.device_controller.node_4] Previous subscription failed with Error: 50, re-subscribing in 20333 ms...
2024-06-03 13:53:30.412 (Dummy-2) CHIP_ERROR [chip.native.DMG] Time out! failed to receive report data from Exchange: 9661i with Node: <0000000000000004, 1>
2024-06-03 13:53:30.414 (MainThread) INFO [matter_server.server.device_controller.node_4] Previous subscription failed with Error: 50, re-subscribing in 33224 ms...
2024-06-03 13:54:57.000 (Dummy-2) CHIP_ERROR [chip.native.DMG] Time out! failed to receive report data from Exchange: 9663i with Node: <0000000000000004, 1>
2024-06-03 13:54:57.002 (MainThread) INFO [matter_server.server.device_controller.node_4] Previous subscription failed with Error: 50, re-subscribing in 42558 ms...
2024-06-03 13:55:49.941 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:64315276 on exchange 9664i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-03 13:55:56.578 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 4
2024-06-03 13:56:27.119 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:64315277 on exchange 9665i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-03 13:56:31.003 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 4
2024-06-03 13:57:00.218 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:64315278 on exchange 9666i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-03 13:57:05.435 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 4
2024-06-03 13:57:35.776 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:64315279 on exchange 9667i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-03 13:57:39.864 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 4
2024-06-03 13:58:10.373 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:64315280 on exchange 9668i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-03 13:58:14.295 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 4
2024-06-03 13:58:14.295 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/protocols/secure_channel/CASESession.cpp:560: CHIP Error 0x00000032: Timeout'
2024-06-03 13:58:14.296 (MainThread) INFO [matter_server.server.device_controller.node_4] Previous subscription failed with Error: 50, re-subscribing in 82506 ms...
2024-06-03 14:00:29.314 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:64315281 on exchange 9669i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-03 14:00:32.922 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 4
2024-06-03 14:01:02.386 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:64315282 on exchange 9670i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-03 14:01:07.349 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 4
2024-06-03 14:01:36.362 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:64315283 on exchange 9671i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-03 14:01:41.774 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 4
2024-06-03 14:02:10.903 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:64315284 on exchange 9672i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-03 14:02:16.203 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 4
2024-06-03 14:02:44.651 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:64315285 on exchange 9673i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-03 14:02:50.635 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 4
2024-06-03 14:02:50.636 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/protocols/secure_channel/CASESession.cpp:560: CHIP Error 0x00000032: Timeout'
2024-06-03 14:02:50.637 (MainThread) INFO [matter_server.server.device_controller.node_4] Previous subscription failed with Error: 50, re-subscribing in 82829 ms...
2024-06-03 14:03:56.854 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:202878636 on exchange 16438r with Node: <0000000000000001, 1> sendCount: 4 max retries: 4
2024-06-03 14:06:13.620 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:64315286 on exchange 9674i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-03 14:06:18.439 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 4
2024-06-03 14:06:46.859 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:64315287 on exchange 9675i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-03 14:06:52.869 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 4
2024-06-03 14:07:21.673 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:64315288 on exchange 9676i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-03 14:07:27.295 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 4
2024-06-03 14:07:57.164 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:64315289 on exchange 9677i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-03 14:08:01.723 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 4
2024-06-03 14:08:29.862 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:64315290 on exchange 9678i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-03 14:08:36.152 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 4
2024-06-03 14:08:36.152 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/protocols/secure_channel/CASESession.cpp:560: CHIP Error 0x00000032: Timeout'
2024-06-03 14:08:36.154 (MainThread) INFO [matter_server.server.device_controller.node_4] Previous subscription failed with Error: 50, re-subscribing in 299924 ms...
2024-06-03 14:11:02.929 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:64315291 on exchange 9679i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-03 14:11:08.815 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 4
2024-06-03 14:11:39.671 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:64315292 on exchange 9680i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-03 14:11:43.244 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 4
2024-06-03 14:12:10.969 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:64315293 on exchange 9681i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-03 14:12:17.672 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 4
2024-06-03 14:12:47.347 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:64315294 on exchange 9682i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-03 14:12:52.104 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 4
2024-06-03 14:13:21.374 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:64315295 on exchange 9683i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-03 14:13:26.537 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 4
2024-06-03 14:13:26.538 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/protocols/secure_channel/CASESession.cpp:560: CHIP Error 0x00000032: Timeout'
2024-06-03 14:13:26.540 (MainThread) INFO [matter_server.server.device_controller.node_4] Previous subscription failed with Error: 50, re-subscribing in 470100 ms...
2024-06-03 14:19:08.666 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:64315296 on exchange 9684i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-03 14:19:13.668 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 4
2024-06-03 14:19:41.702 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:64315297 on exchange 9685i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-03 14:19:48.096 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 4
2024-06-03 14:20:18.549 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:64315298 on exchange 9686i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-03 14:20:22.528 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 4
2024-06-03 14:20:53.452 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:64315299 on exchange 9687i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-03 14:20:56.954 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 4
2024-06-03 14:21:26.123 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:64315300 on exchange 9688i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-03 14:21:31.380 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 4
2024-06-03 14:21:31.381 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/protocols/secure_channel/CASESession.cpp:560: CHIP Error 0x00000032: Timeout'
2024-06-03 14:21:31.384 (MainThread) INFO [matter_server.server.device_controller.node_4] Previous subscription failed with Error: 50, re-subscribing in 339176 ms...
2024-06-03 14:27:00.725 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:64315301 on exchange 9689i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-03 14:27:04.435 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 4
2024-06-03 14:27:31.345 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:64315302 on exchange 9690i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-03 14:27:38.862 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 4
2024-06-03 14:28:09.308 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:64315303 on exchange 9691i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-03 14:28:13.290 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 4
2024-06-03 14:28:43.179 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:64315304 on exchange 9692i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-03 14:28:47.716 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 4
2024-06-03 14:28:50.032 (MainThread) INFO [matter_server.server.device_controller] Removing Node ID 4.
2024-06-03 14:28:50.055 (MainThread) INFO [matter_server.server.device_controller] Node ID 4 successfully removed from Matter server.
2024-06-03 14:29:17.136 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:64315305 on exchange 9693i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-03 14:29:22.148 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 4
2024-06-03 14:29:22.149 (MainThread) WARNING [matter_server.server.device_controller] Removing current fabric from device failed: src/protocols/secure_channel/CASESession.cpp:560: CHIP Error 0x00000032: Timeout

Additional information

I restarted Home Assistant server with all integrations, with no success.

[home-assistant[bot]]

Hey there @home-assistant/matter, mind taking a look at this issue as it has been labeled with an integration (matter) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `matter` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign matter` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

matter documentation matter source _{^{(message by IssueLinks)}}

[cnelsonsc]

Same issue, I downgraded back to 5.3 and it started working again.

[DarthSonic]

Same issue, I downgraded back to 5.3 and it started working again.

What did you downgrade?

[cnelsonsc]

Home assistant core, stopped working with 5.4 & 5.5 but 5.3 works great.

[DarthSonic]

Home assistant core, stopped working with 5.4 & 5.5 but 5.3 works great.

Mmh... It worked for me with 5.4 without any issues. 5.5 worked until yesterday.

[DarthSonic]

no changes for 2024.6. still not working.

[Lucky-Strike1695]

Same setup, same issue, same logs... Stopped working this afternoon after matter integration & HA core update.

Edit : no idea why but after putting the lock in maintenance mode and failing to reset it back to default (error 506), then restarting the lock in normal mode, it started working again...

[cnelsonsc]

How do you put the lock in maintenance mode?

[mtdern]

same issue here on 2024.6.1. the lock worked fine even after the latest matter update until last night it just decided to drop off the network. will try to add the lock again later in the day to see if I can get it back online.

[Bucky2k]

Happy to see I am not alone - spent 3 hours installing/ deinstalling matter/thread/border router, etc... No success, cannot get the Nuki 4.0 to connect to HA via SkyConnect When using matter code, it starts searching device, exchanging matter access data and then starts "checking network connection". There it's then stuck...

Maybe the issue is with Nuki Firmware not fully resetting Matter connection when doing a new setup? Eager to hear more about the potential workaround via "Nuki maintenance mode"...

[cnelsonsc]

I don’t think it’s the Nuki firmware, it only started lllsing connection after I updated HA core to 2024.5.5. Does anyone have the lock connected via MQTT as well? Just curious if it continues to work that way.

[max-t-d]

Core 2024.6.2 / Matter server 6.1.2 + Factory reset / maintenance mode (same thing afaik, triggered through the app, (nuki FW 4.2.8)), Apple TV as thread border router. Pairing still fails. Funnily enough... it also fails when trying to connect in Apple Home, so this may be an issue with the Apple side of thread/matter? This is mentioned in the nuki FAQ as a potential issue (there it says that reduced thread coverage is observed while streaming on aTV, so not quite fitting this, since I'm not streaming either). I'll try putting a HomePod mini right next to the lock and see whether that changes anything. Since I only have the non-pro version of the lock, having an active thread/matter connection is precondition for me using MQTT - so can't try that, sadly.

[DarthSonic]

It's not issue with Apple. I have no matter hub beside HA. I'm using SkyConnect stick. Also I'm using Android to add device.

[agners]

I removed Nuki from Matter integration and removed Matter in Nuki config. Adding to HA after that does not work with "No connection to thread-network "home-assistant" possible". So network is seen, but connection is not established.

Hm, that sounds as if the Nuki lock really has troubles to connect to the Thread network then :thinking:

Did maybe something change in the Thread configuration panel (e.g. is the OTBR still listed to be part of the home-assistant network?

Can you try to restart the OTBR before an attempt, maybe this helps?

Do you know what Nuki Lock firmare you are using and when you updated last?

@max-t-d did it ever work for you on Apple or HA?

I don’t think it’s the Nuki firmware, it only started lllsing connection after I updated HA core to 2024.5.5. Does anyone have the lock connected via MQTT as well? Just curious if it continues to work that way.

That just upgrading/downgrading Core changes things is rather weird. Matter is largely controlled by the Matter Server add-on, and the Core essentially just displays what it can communicate with.

@cnelsonsc Do you have other Matter devices? Do those work with the non-working 2024.5.5 setup? :thinking:

[DarthSonic]

Did maybe something change in the Thread configuration panel (e.g. is the OTBR still listed to be part of the home-assistant network?

I cannot really tell you that, but it seems to be configured as expected:

[DarthSonic]

Can you try to restart the OTBR before an attempt, maybe this helps?

I started whole HA server before trying without success.

Reloading OTBR before adding device did help. But I also update HA core (2024.6.2) and Matter Server (6.1.2)

Do you know what Nuki Lock firmare you are using and when you updated last?

4.1.0 but do not know when it was updated. I did not update it manually.

For now it is working again.

[cnelsonsc2]

@cnelsonsc Do you have other Matter devices? Do those work with the non-working 2024.5.5 setup? 🤔

Yeah I have a couple other matter devices and they are fine, seems you are right, this might be an issue that needs to be raised with Nuki.

[max-t-d]

@agners

did it ever work for you on Apple or HA?

It worked flawlessly on HA with the atv as Thread border router for about three months. I was honestly surprised, paired on first try and quickly (for a matter device). I only tried to pair it to Apple home today as a workaround for the current issue, never even tried that before - thought I could get it back through that… :(

[Bucky2k]

Not working on my side - even after reload of OTBR, Matter an Thread. Stuck at this screen after exchange of Matter credentials

[Bucky2k]

So... How did you all get it running again?

[max-t-d]

Still not connecting for me. No solution/workaround here, sorry.

[cnelsonsc]

No solution here unfortunately.

[marcelveldt]

From my experience testing a fair bit with the Nuki Lock, it is a tiny bit picky on the RF signals. Try to move the border router closer to the device.

In any way, this is not a bug in the HA Matter implementation but rather a device specific (or setup specific) issue. I think the discord server (matter channel) would be a better location to troubleshoot that.