[CC2652R7] The example for end device and support OpenThread CLI

Hi Mike,

It sounds like you want to have a Matter End Device with added OpenThread CLI?

If yes, you are correct, currently the Matter examples do not do this.

Can you help us understand what the purpose of this is? Which specific features of CLI do you need?

Note it is possible to have the application layer receive notifications from the OpenThread Stack: https://github.com/TexasInstruments/matter/blob/v1.0-ti-branch/examples/pump-app/cc13x2x7_26x2x7/main/DeviceCallbacks.cpp

Thanks,
Toby

Hi Toby,

Thanks for your reply.

Yes, we want to have a Matter End Device with added OpenThread CLI.

The purpose is for getting some information from end devices, e.g., status , ipaddr

Thanks,

Mike

CLI is usually used on its own, but it should be possible to add in. However, this is not something I've evaluated before, so there could be some limitations (e.g. Flash/RAM).

I would recommend first trying with the DeviceCallbacks I referenced in previous reply, and see if that fits the needs. It should at least provide the application information including:

1. Thread network state changes (joined network, disconnected from network):
   https://github.com/TexasInstruments/matter/blob/8a3ca52165e54701bac483c37d83f6da79c63e16/examples/pump-app/cc13x2x7_26x2x7/main/DeviceCallbacks.cpp#L66
2. Thread IP addr changes or updates:
   https://github.com/TexasInstruments/matter/blob/v1.0-ti-branch/examples/pump-app/cc13x2x7_26x2x7/main/DeviceCallbacks.cpp#L86

The Active Dataset for the Thread network could also be printed from here: https://github.com/TexasInstruments/matter/blob/v1.0-ti-branch/src/platform/OpenThread/OpenThreadUtils.cpp#L95

Other CLI related info can also be retrieved with the ot API, such as: otDatasetGetActive

Thanks,
Toby