Matter multi admin fails with nrf samples

[stlevkov]

Greetings,

I am trying to pair nRF52840 DK to second admin (controller) using the provided chip-tool and the switch app from the nrf samples.

Specs:

• nRF52840 DK                                                                                                       (DUT)
• nRF52840 Dongle (Radio Co-Processor)
• Raspberry Pi 4 (OpenThread Border Router)
• nRF Connect SDK v2.1.0
• Linux Chip-Tool x86 64
• Ubuntu 20.04 x86 64 VM Controller 1 (uart debug connected to nRF52840 DK) (C1)
• Ubuntu 20.04 x86 64 VM Controller 2                                                                    (C2)

Following the scenario for commissioning:

• C1: ./chip-tool-release pairing ble-thread 4369 hex:operational-data-set-here 20202021 3840     ,
  • Device commissioned successfully, visible in OpenThread Border Router, can be controlled by C1
• C1: ./chip-tool-debug pairing open-commissioning-window 4369 1 400 2000 3840
  • [1663682774.140445][29427:29432] CHIP:CTL: Successfully opened pairing window on the device
    [1663682774.140464][29427:29432] CHIP:CTL: Manual pairing code: [36434149637]
    [1663682774.140471][29427:29432] CHIP:CTL: SetupQRCode: [MT:4CT91AFN00A7NS7BR10]
• C2: ./chip-tool-debug pairing code 4444 36527152093                                                                    [timeout, unable to pair]
• C2: ./chip-tool-debug pairing onnetwork-long 4444 20202021 3840                                                [timeout, unable to pair]

Avahi is able to resolve the address.During the second pairing, both C2 and DUT are exchanging messages but fails to establish PASE.

Error which i received on chip-tool (C2):

[1663682901.400708][3380:3380] CHIP:TOO: Run command failure: ../../src/protocols/secure_channel/PASESession.cpp:245: CHIP Error 0x00000032: Timeout

Error which i received on nRF52840 (DUT):

E: 1565622 [SC]PASESession timed out while waiting for a response from the peer. Expected messa4
D: 1565632 [IN]SecureSession[0x20003788]: Released - Type:1 LSID:14348
E: 1565638 [SVR]Commissioning failed (attempt 1): 32

Expected scenario for DUT:

• Pair with ble-thread to join thread network
• opened commissioning window
• pair with onnetwork

Is there a multi admin (multi fabric) support in nrf samples?

Thanks in advance.

[stlevkov]

Hi,

I am unable to pair it using the ethernet or onnetwork, but using the qr-code, it is working fine.

I was placing an wrong code for which the device was brodcasting initially. After sending open-commissioning-window, the core is different and unique for this particular window. This was the reason for getting the error.

So far it is working fine to me i can continue with the integration.

[Marte Myrvold]

Hi,

That is great to hear!

I also heard back from the developers. You should use the --commissioner-name argument when commissioning to the second fabric. Without that the chip-tool will most likely attempt to commission to the first one again, which sounds like what you experienced. This has worked for the development team when testing recently:

./chip-tool pairing ble-thread 1 hex:<operational_dataset> 28073715 3654
./chip-tool administratorcommissioning open-basic-commissioning-window 300 1 0 --timedInteractionTimeoutMs 1000
./chip-tool pairing onnetwork 1 28073715 --commissioner-name beta

Best regards,

Marte

[stlevkov]

Hi,
I will give it a try, but so far, the commissioning is working fine with the qr code. No need to use different identity for the commissioner. The device is creating another fabric for the second commissioner on another index. Both has different root certificates, works the same as chip-all-clusters-app so far. Currently, the commissioner-name is not set for both commissioners, they are using alpha, which is by default.

I think using different identity (beta) will be valid, if both of the commissioners are started from the same host machine. In my case, i am using different machines, which can explain why it is working with the same identity.