Matter multi admin fails with nrf samples

RE: Matter multi admin fails with nrf samples

stlevkov — Wed, 21 Sep 2022 20:39:40 GMT

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.

RE: Matter multi admin fails with nrf samples

Marte Myrvold — Wed, 21 Sep 2022 14:17:02 GMT

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

RE: Matter multi admin fails with nrf samples

Marte Myrvold — Wed, 21 Sep 2022 13:53:21 GMT

Hi,

Matter multi-admin is supported, and is enabled by default in the samples.

I have asked the development team about this, but they need some more details. Can you share all executed commands from the CHIP Tool?

Best regards,

Marte

RE: Matter multi admin fails with nrf samples

stlevkov — Wed, 21 Sep 2022 12:55:53 GMT

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.