Matter commission and multiple fabric issues on nRF54L15.

[simon3panda]

Hi Nordic,

We are develop a multiple switch button device based on nRF54L15. We've two issues now while developing.

1. Matter Network Commissioning Issue with nRF54L15 DK

Using the nRF54L15 DK, we have implemented a multi-switch functionality. However, the DK behaves inconsistently in different testing environments. Even when using the official unmodified demo applications (such as light_bulb and light_switch), the issue persists.

We have submitted a support case on the SmartThings community website, which includes a detailed description of the issue and log outputs. However, the feedback so far has not resolved the issue.
Case link:
https://community.smartthings.com/t/matter-device-pairing-issue-with-smartthings-app-on-iphone-april-2025/298534/6

2. Multiple Fabric Issue

The multiple fabric feature also shows inconsistent behavior depending on the environment. This issue also occurs when using the official unmodified demo applications (light_bulb, light_switch).

We would greatly appreciate any help in analyzing the root cause of these issues or any suggestions you may have. Thank you in advance for your support.

[Marte Myrvold]

Hi,

1. Matter Network Commissioning Issue with nRF54L15 DK

Based on the logs, the SmartThings Hub does not send a Case Sigma1 message to set up the CASE connection after the operational discovery. Instead, several BLE messages are sent between the device and the iPhone. It seems like it gets stuck when adding the device to iCloud. Have you tried reaching out to Apple for support? Have you tried with another iPhone?

Android:

I: 3268149 [DL]advertising srp service: A82B8EF5C959FAE5-C2032ACD15199E15._matter._tcp
I: 3268159 [SWU]Stopping the watchdog timer
I: 3268163 [SWU]Starting the periodic query timer, timeout: 86400 seconds
D: 3269697 [DL]SRP update succeeded
I: 3270233 [EM]>>> [E:22172r S:0 M:220016613] (U) Msg RX from 0:798752CD8D53BDE5 [0000] to 0000000000000000 --- Type 0000:30 (SecureChannel:CASE_Sigma1) (B:196)
I: 3270247 [IN]CASE Server received Sigma1 message . Starting handshake. EC 0x20006668
I: 3270255 [EM]<<< [E:22172r S:0 M:172498957 (Ack:220016613)] (U) Msg TX from 0000000000000000 to 0:798752CD8D53BDE5 [0000] [UDP:[fd41:8102:3c8a:1:3040:80ff:1261:2b27]:54369] --- Type 0000:10 (SecureChannel:StandaloneAck) (B:26)
I: 3270276 [SC]Received Sigma1 msg
I: 3270283 [SC]CASE matched destination ID: fabricIndex 1, NodeID 0xC2032ACD15199E15
I: 3270305 [EM]<<< [E:22172r S:0 M:172498958 (Ack:220016613)] (U) Msg TX from 0000000000000000 to 0:798752CD8D53BDE5 [0000] [UDP:[fd41:8102:3c8a:1:3040:80ff:1261:2b27]:54369] --- Type 0000:31 (SecureChannel:CASE_Sigma2) (B:822)
I: 3270327 [EM]??1 [E:22172r S:0 M:172498958] (U) Msg Retransmission to 0:0000000000000000 in 1893ms [State:Active II:500 AI:300 AT:4000]
I: 3270339 [SC]Sent Sigma2 msg
D: 3270630 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 3271050 [EM]>>> [E:22172r S:0 M:220016614 (Ack:172498958)] (U) Msg RX from 0:798752CD8D53BDE5 [0000] to 0000000000000000 --- Type 0000:32 (SecureChannel:CASE_Sigma3) (B:669)
I: 3271066 [EM]<<< [E:22172r S:0 M:172498959 (Ack:220016614)] (U) Msg TX from 0000000000000000 to 0:798752CD8D53BDE5 [0000] [UDP:[fd41:8102:3c8a:1:3040:80ff:1261:2b27]:54369] --- Type 0000:10 (SecureChannel:StandaloneAck) (B:26)
I: 3271086 [SC]Received Sigma3 msg
E: 3271092 [SC]The device does not support GetClock_RealTimeMS() API: 3.  Falling back to Last Known Good UTC Time
I: 3271376 [EM]<<< [E:22172r S:0 M:172498960 (Ack:220016614)] (U) Msg TX from 0000000000000000 to 0:798752CD8D53BDE5 [0000] [UDP:[fd41:8102:3c8a:1:3040:80ff:1261:2b27]:54369] --- Type 0000:40 (SecureChannel:StatusReport) (B:34)
I: 3271397 [EM]??1 [E:22172r S:0 M:172498960] (U) Msg Retransmission to 0:0000000000000000 in 1868ms [State:Active II:500 AI:300 AT:4000]
I: 3271410 [SC]SecureSession[0x200045d8, LSID:57612]: State change 'kEstablishing' --> 'kActive'
D: 3271419 [IN]SecureSession[0x200045d8]: Activated - Type:2 LSID:57612
D: 3271427 [IN]New secure session activated for device <042B599B7E1E363B, 1>, LSID:57612 PSID:30631!
I: 3271436 [IN]CASE Session established to peer: <042B599B7E1E363B, 1>

iPhone:

I: 3100769 [DL]advertising srp service: 5329CE4A2334A18B-000000001EAD6F46._matter._tcp
I: 3100779 [SWU]Stopping the watchdog timer
I: 3100783 [SWU]Starting the periodic query timer, timeout: 86400 seconds
D: 3102336 [DL]SRP update succeeded
D: 3102816 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
D: 3105324 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
D: 3105396 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 3107856 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
D: 3110364 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
D: 3110436 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 3112417 [DL]OpenThread State Changed (Flags: 0x00000064)
D: 3112422 [DL]   Device Role: ROUTER
D: 3112896 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
D: 3115404 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
D: 3115476 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 3117937 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
D: 3120444 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
D: 3120517 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 3122977 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
D: 3125484 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
D: 3125557 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 3128017 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
D: 3130524 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
D: 3130597 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)

2. Multiple Fabric Issue

Do you get any error messages in the apps?

Did you follow the guide here:  Matter: Testing the nRF Connect platform with Apple, Google and Samsung ecosystems ?

Best regards,
Marte

[simon3panda]

1. We tried with another iPhone, the same behaviour. Not connect to Apple yet.

2.We follow the exactly the same guide article. No any err message in the apps. It seems nothing happened after enter Setup code.