Matter Demo - Instructions to get the discriminator code - missing a command?

RE: Matter Demo - Instructions to get the discriminator code - missing a command?

HeneryH — Fri, 11 Mar 2022 16:32:38 GMT

Thank you. I did notice on the benchtop lab I have that the light bulb sample did print out the commissioning data but the light switch did not.

I must have missed that note.

I'll try the lock demo too.

Thank you.

RE: Matter Demo - Instructions to get the discriminator code - missing a command?

Jørgen Holmefjord — Fri, 11 Mar 2022 15:59:49 GMT

Hi,

Most likely you are not able to get the commissioning data from the shell because of the reason mentioned in the "Test mode" section in the sample documentation for the Matter Light Switch:

"Unlike other samples, such as Matter door lock, this sample does not support Matter commissioning over Bluetooth® LE. To enable communication between the light switch and the light bulb devices, they must be initialized with the same static Thread network parameters and static Matter cryptographic keys."

I tested the Matter door lock sample, and there I can get the output from the onboardingcodes command.

Best regards,
Jørgen

RE: Matter Demo - Instructions to get the discriminator code - missing a command?

HeneryH — Tue, 08 Mar 2022 15:12:22 GMT

Using the Matter-Specific commands, I can only seem to get some of the data items to print out. The hardware and vendor IDs are OK but all of the pairing data is blank.

Is there some operational prerequisite after flashing the demos to get the CLI to spit out the pairing data (ie qrcodes, pins etc)?

RE: Matter Demo - Instructions to get the discriminator code - missing a command?

HeneryH — Tue, 08 Mar 2022 13:44:16 GMT

Not sure where the output shown above is coming from but I did find the commands to query the data separately.

Using Matter-specific commands

The nRF Connect examples let you use several Matter-specific CLI commands.

These commands are not available by default and to enable using them, set the CONFIG_CHIP_LIB_SHELL=y Kconfig option in the prj.conf file of the given example.

Every invoked command must be preceded by the matter prefix.

See the following subsections for the description of each Matter-specific command.

device

Handles a group of commands that are used to manage the device. You must use this command together with one of the additional subcommands listed below.

factoryreset

Performs device factory reset that is hardware reset preceded by erasing of the whole Matter settings stored in a non-volatile memory.

uart:~$ matter device factoryreset
Performing factory reset ...

onboardingcodes

Handles a group of commands that are used to view information about device onboarding codes. The onboardingcodes command takes one required parameter for the rendezvous type, then an optional parameter for printing a specific type of onboarding code.

The full format of the command is:

onboardingcodes none|softap|ble|onnetwork [qrcode|qrcodeurl|manualpairingcode]

To print all the onboardingcodes:

uart:~$ matter onboardingcodes none
QRCode:             MT:W0GU2OTB00KA0648G00
QRCodeUrl:          dhrishi.github.io/.../qrcode.html=MT%3AW0GU2OTB00KA0648G00
ManualPairingCode:  34970112332