Adding a Matter device always fails.

[oyajizap]

iOS device model, version and app version

Model Name: iPhone 14
Software Version: 26.1
App version: 2025.11.2

Home Assistant Core Version

2025.11.1

Describe the bug
Adding a Matter device always fails.
It seems Matter commissioning process does not work. As I am using Matter Code Example on Nordic for debug as a Matter device, I can see the log on the device side. It shows the device is on BLE advertising but no BLE connection was established.

It worked well a few weeks ago so I suspect any app change might cause the issue.

To Reproduce
Add to Home Assistant -> Add Device -> Add Matter device -> No. It's new.
Then, scan QR code of the device. and Click "Add to "Home Assistant""

Expected behavior
A Matter device should be commissioned and added to "Home Assistant".

Screenshots

Additional context

[bgoncal]

No changes related to matter lately, try rebooting your phone, this flow on your screenshot is managed by Apple.

[oyajizap]

Thanks. I confirmed making BLE connection just after iPhone reboot but found the BLE connection was not made the second or later trials. So, I need to reboot iPhone every commissioning trial.
Is it expected? I have not see such problems before.

[bgoncal]

To be honest, I dont face those problems, and the connection is handled by Apple so, not much I can contirbute in terms of data.

Do you see any errors or warnings in the App?

[oyajizap]

No. No error message was shown but just "Connecting.." was see for several minutes. Then, finally, commissioning error was informed.
I've also noticed the failure was not seen if previous commissioning worked fine. So, the failure only happens when the latest commission failed by another reason. Now, I would say the issue is no longer critical.

[bgoncal]

Please keep me posted if you notice something App related, for now it sounds like some issue on your thread network, matter comissioning has been stable for a while and the code hasn't received changes lately. Let me know in case you think this issue should be reopened