Handle Matter network status from ChipEventHandler()

[Yuelin.Li]

Hi there

I've been using Nordic nRF Connect SDK v2.4.1 for my Matter application development. I've been working on features to report Matter network status correctly and I have few questions wanted to get some clarification.

The ChipEventHandler() provides status change of BLE and thread, but from the enum provided in code for ChipEventHandler() and observation from the debug log, network status could not be concluded solely based on one status change, it has to be determined with a sequential updates from ChipEventHandler(). For example, after a device being committed to a network, ChipEventHandler() returns kThreadStateChange then kThreadConnectivityChange. However after a device being removed from the network, the ChipEventHandler only reports kThreadStateChange  without any update about kThreadConnectivityChange. 

So I'm trying to clarify the expected event return for following cases, might as well as the order of the possible event, as I was able to observe ChipEventHandler() return event in different order for one same network state.

1. Start BLE commissioning 
2. Timeout BLE commissioning
3. Transition to Thread commissioning
4. Timeout Thread commissioning
5. Complete Commission to Matter network
6. Matter Boarder Router become offline and no Matter communication as ICD
7. Matter Boarder router get back online

Thanks for looking into this.

Regards,

Yuelin 

[Simonr]

Hi Yuelin

The ChipEventHandler() was replaced in the app_task.cpp file as of NCS 2.6.0 with some updates that should improve this functionality I think. Please check out the NCS 2.6.0 migration guide for details on how it is/should be replaced: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.6.0/nrf/releases_and_maturity/migration/migration_guide_2.6.html 

Let me know if you're not in a position to migrate to a newer SDK version, and I'll do some digging on what can be done for NCS 2.4.1.

Best regards,

Simon