How to Improve the Commissioning Speed of Matter over Thread？

[biubiubiubiu]

Background : To set up a Matter ICD (Internet Connectivity Device) and Thread as a SSD (Sleepy End Device). Here are the detailed settings：

CONFIG_OPENTHREAD_NORDIC_LIBRARY_MTD=y
CONFIG_OPENTHREAD_MTD=y
CONFIG_OPENTHREAD_FTD=n
CONFIG_CHIP_ENABLE_ICD_SUPPORT=y
CONFIG_CHIP_THREAD_SSED=
CONFIG_CHIP_ICD_SLOW_POLL_INTERVAL=30000
CONFIG_CHIP_ICD_FAST_POLLING_INTERVAL=500
CONFIG_CHIP_ICD_ACTIVE_MODE_THRESHOLD=2000

Currently, the Matter over Thread network commissioning has been tested 100 times, with a typical time of 65 seconds.

The following is my question：

1.I would like to set a macro definition during the Matter over Thread network commissioning phase, temporarily disabling the low - power limits of Matter ICD and SSED to boost the Matter over Thread commissioning speed. Is there such a macro definition?

2.After setting Matter ICD slow poll to 30000, the first Matter over Thread commissioning succeeded. But when I clicked "identify" in the Matter app, I found that the nRF54L15 took up to 30 seconds to receive the identify command, which is too long. How can I reduce this 30 - second delay while keeping the slow poll time at 30000?

Looking forward to your reply.

[Maria Gilje]

Hello, 

I didn't have the time to find all the needed information for you today, but I had some time to give my initial thoughts. I'll get back to you on Friday at the latest. 

1.I would like to set a macro definition during the Matter over Thread network commissioning phase, temporarily disabling the low - power limits of Matter ICD and SSED to boost the Matter over Thread commissioning speed. Is there such a macro definition?

I'm not sure, but I'll check this tomorrow. 

2.After setting Matter ICD slow poll to 30000, the first Matter over Thread commissioning succeeded. But when I clicked "identify" in the Matter app, I found that the nRF54L15 took up to 30 seconds to receive the identify command, which is too long. How can I reduce this 30 - second delay while keeping the slow poll time at 30000?

Pardon me if I misremember, but this is my understanding of the ICD from memory. The ICD is supposed to be low power and wake up to poll for commands. If the slow polling rate is set to 30000 ms, 30 seconds delay is the expected worst case delay. That is, you click identify in the Matter app very early in the polling interval and the device does not wake until ~30 seconds later.  

Best regards,

Maria

[biubiubiubiu]

Thank you for your prompt reply. I have one more question. After the Matter over Thread connection is established, when I reboot the nrf54l15, the device prints"[IN]Data received on an unknown session (LSID=12774). Dropping it!".How to enable the session resumption feature on nrf54l15?

[biubiubiubiu]

Yes, I saw this post before asking the question and followed the steps, but it still prompts me to enter the network key. I guess it might be because my device hasn't been Matter-certified?

[Maria Gilje]

It's difficult to say at this point what the reason for this behaviour is. 

Did this happen before you implemented the UAT behaviour as well? 

[biubiubiubiu]

It is not related to UAT. When attempting to set up the network connection on HomePod, there is no need to enter the network key.

[biubiubiubiu]

By the way, for the Time Sync Cluster with nRF54L15, should I choose server or client? And how should the nRF54L15 trigger the time update?

[Maria Gilje]

biubiubiubiu said:

By the way, for the Time Sync Cluster with nRF54L15, should I choose server or client? And how should the nRF54L15 trigger the time update?

The Matter v1.4 core specification ch. 11.17.15 Acting as an NTP Server states that NTP Server is suited for nodes with always-on power source (and a good enough accuracy). ICDs does not fall into the "always-on power" category. So your nRF54L15 is not suited for the server as far as I can tell. Please see the time syncronization cluster specification for details (ch. 11.17). 

biubiubiubiu said:

It is not related to UAT. When attempting to set up the network connection on HomePod, there is no need to enter the network key.

My apologies, I have not been able to find anything more on this at this point.