How to change matter example descriminator/setup pin code

[waqarrashid33]

I am trying to test the light switch and light bulb example with google home app and google nest device as a border router. I have flashed the bulb example into a nrf52840dk and the switch example onto another nrf52840dk.

The problem is that I was able to comission one of the device but when I try to comission the second device, the app says that device should have unique comiisioning data (descriminator and setup pin code). I was under the impression that it should work without being unique but I am new to all this so what do I know.

Can anyone help me out here and point in the direction where I can change these hardcoded values. I tried looking for them myself but haven't managed to figure it out.


Edit 1: docs.nordicsemi.com/.../nrfconnect_factory_data_configuration.html

Edit 2: There seems to be multiple ways to update this. In nRF Kconfig GUI:> Modules > Connecthomeip > Matter Prototcol Stack: You will find the following information that can be edited. But still there seems to be something missiing and I am getting the same QR code.



Edit 3: I am using nrf connect sdk 2.6.0 and the same tool chain. Still I try to change the values for descriminator and passcode. The descriminator change seems to take effect and I see the new value on uart of the device but the passcode remains the same and the QR-Code also remains the same.

[Marte Myrvold]

Hi,

Edit 1: docs.nordicsemi.com/.../nrfconnect_factory_data_configuration.html

This is the correct way to configure the discriminator and passcode.

The descriminator change seems to take effect and I see the new value on uart of the device but the passcode remains the same and the QR-Code also remains the same.

You can generate a new QR code using chip-tool:

./chip-tool payload generate-qrcode [--existing-payload] [--discriminator] [--setup-pin-code] [--version] [--vendor-id] [--product-id] [--commissioning-mode] [--allow-invalid-payload] [--rendezvous] [--tlvBytes]

For example:

$ ./chip-tool payload generate-qrcode --discriminator 1234 --setup-pin-code 13243546 --vendor-id 0x123 --product-id 0x123
[1723550244.756316][2136306:2136306] CHIP:TOO: QR Code: MT:GWQS0POG02A48B1OA00

So from this we get the manual pairing code MT:GWQS0POG02A48B1OA00, which corresponds to the QR code found here: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%GWQS0POG02A48B1OA00.

Best regards,
Marte

[waqarrashid33]

Thanks for the answer. So just changing these parameters in Kconfig or prj.conf files were not enough. Somehow it was not generating the new factory data. I deleted the build directory and was able to get the device have the new factory data, including the QR code which was visible on the uart.

Any idea how to do the ACL stuff in the google eco system. I now want to bind the switch and bulb.

[Marte Myrvold]

Hi,

Great to hear that you solved the issue with the QR code!

waqarrashid33 said:

Any idea how to do the ACL stuff in the google eco system. I now want to bind the switch and bulb.

Unfortunately, Google and many other commercial ecosystems do not currently support binding. Instead, you can set up an automation that controls the light when the light switch is pressed.

Best regards,
Marte