I have developed a low-power windowcovering product based on Matter 1.3, and currently, I'm conducting CSA certification testing. However, I've noticed that many test cases are experiencing timeouts during execution. Previously, I also developed a Matter 1.3 smoke detector, which has successfully passed the tests and obtained the CSA certification. Upon comparing the two products, I found that the windowcovering's message exchange speed with the gateway is significantly slower than that of the smoke detector, even though both operate in SED mode with ICD enabled and share similar configuration settings.
CONFIG_OPENTHREAD_MTD=y CONFIG_OPENTHREAD_FTD=n CONFIG_OPENTHREAD_MTD_SED=y CONFIG_OPENTHREAD_NORDIC_LIBRARY_MTD=y CONFIG_CHIP_ENABLE_ICD_SUPPORT=y CONFIG_CHIP_ICD_SLOW_POLL_INTERVAL=10000 CONFIG_CHIP_ICD_FAST_POLLING_INTERVAL=200 CONFIG_CHIP_ICD_IDLE_MODE_DURATION=120 CONFIG_CHIP_ICD_ACTIVE_MODE_DURATION=300 CONFIG_CHIP_ICD_ACTIVE_MODE_THRESHOLD=2000
I have developed a low-power windowcovering product based on Matter 1.3, and currently, I'm conducting CSA certification testing. However, I've noticed that many test cases are experiencing timeouts during execution. Previously, I also developed a Matter 1.3 smoke detector, which has successfully passed the tests and obtained the CSA certification. Upon comparing the two products, I found that the windowcovering's message exchange speed with the gateway is significantly slower than that of the smoke detector, even though both operate in SED mode with ICD enabled and share similar configuration settings.
The SDKs for the smoke detector and the windowcovering are different. When developing the smoke detector, NCS 2.5 was used since NCS did not yet support Matter 1.3 at that time. To work around this, I replaced the matter repository's commit with the Matter 1.3 tag. In contrast, the current low-power windowcovering development utilizes NCS 2.7, which already supports Matter 1.3.
Interestingly, when I ported the smoke detector code to NCS 2.7, it exhibited the same issue as the windowcovering, with slower message exchange speeds with the gateway, resulting in test case timeouts. Furthermore, using the NCS 2.7-provided window_covering sample directly also replicated the same phenomenon as my custom-developed windowcovering. I've attached two OLG comparison images from the testing process.
Additionally, I'm attaching a typical test case, ACE2.1, which iterates through all attributes and is required to complete within 5 minutes. While NCS 2.5 with Matter 1.3 meets this time requirement, NCS 2.7 consistently exceeds the time limit.
I would like to know if Nordic is aware of the above issues with ncs2.7 and if there are recommended configurations for ICDs in low-power devices
ACE-2.1-ncs2.7-window-sample.txtACE-2.1-ncs2.5+matter1.3-smoke.txt