Using the example

1. Testing the Matter device on first Thread instance

Like any other standart Matter device, you can provision and control the Matter device using the python controller, chip-tool (standalone or pre-built), Android, iOS app or the mattertool utility from the Matter Hub package provided by Silicon Labs. The pre-built chip-tool instance ships with the Matter Hub image. More information on using the Matter Hub can be found in the online Matter documentation here: Silicon Labs Matter Documentation

More information on using the chip-tool directly can be found here: CHIPTool

Here is an example with the CHIPTool:

chip-tool pairing ble-thread 1 hex:<operationalDataset> 20202021 3840

chip-tool onoff on 1 1

2. Testing the COAP communication on second Thread instance

At start-up, the MatterLightOverThread application automatically create a new Thread network if no network exists for the second Thread instance. Since console is connected to second Thread instance, you can retrieve the dataset by the following command:

matterCli> otcli dataset active -x

0e08000000000001000000030000104a0300001935060004001fffe00208e9ecaf1c444483960708fdea3dc3acbe3eb30510ba4e2f688d1df053dd6d807f3fffbb2e03064f544e414d45010227b904104d35cc1a04eeeb9cf2c90cd5da40df440c0402a0f7f8
Done

or

matterCli> otcli dataset active

Active Timestamp: 1
Channel: 16
Wake-up Channel: 25
Channel Mask: 0x07fff800
Ext PAN ID: e9ecaf1c44448396
Mesh Local Prefix: fdea:3dc3:acbe:3eb3::/64
Network Key: ba4e2f688d1df053dd6d807f3fffbb2e
Network Name: OTNAME
PAN ID: 0x27b9
PSKc: 4d35cc1a04eeeb9cf2c90cd5da40df44
Security Policy: 672 onrc 0
Done

Once you have retrieved the proprietary Thread network dataset, you can configure a COAP client to join your Thread network and then receive COAP commands sent by this client.

This is documented in the following example