Matter test failure about TC-DESC-2.3

Question

Hi Nordic Support Team, 
 I have created an issue on GitHub regarding the device type ID error we encountered during testing. Here is the link to the issue: 
 github.com/.../838 
 Since I am unsure how long it will take to get a response, I would like to discuss this matter with your team as well. 
 Looking forward to your assistance. 
 Best regards, Xiongwei Wang

xiongwei.wang · Accepted Answer

Hi, 
 I believe the issue was caused by using a custom device type. The problem can be resolved by simply defining a custom cluster and assigning it to endpoint 1 (or any other endpoint). This should allow the test to pass. 
 Thanks, Xiongwei.Wang

xiongwei.wang · Answer

Hi, 
 Happy New Year! I almost forgot about it, haha. Sorry to bother you at the start of the new year. 
 I've now verified the issue I mentioned yesterday. 
 After adding some debug prints, I found that all events share the same variable. It's normal for the event number to jump if other events are emitted in the middle of the monitored sequence. 
 Here&rsquo;s what happens in TC-IDM-6.2:

The test expects to receive about 4 consecutive events of Event A .

The first Event A is emitted right after device boot.(Saved in the buffer)

However, when pairing with the Matter controller, the Thread Diagnostics Cluster emits an Event B .

This Event B increments the event counter, so the subsequent Event A instances no longer follow the expected consecutive numbering, causing the test to fail.

UL (the certification body) suggested I could temporarily remove the Thread Diagnostics Cluster and retest. 
 In esp-matter, their examples don&rsquo;t include this cluster, which is why their tests pass. Here is the issue: https://github.com/project-chip/connectedhomeip/issues/42559 
 
 However, there&rsquo;s still another issue to resolve: I'm not sure how to proceed with test case TC-DESC-2.3 . 
 Also, UL reported another problem, but I need to organize the details before sharing. 
 Best regards, Xiongwei.Wang

Matter test failure about TC-DESC-2.3

Top Replies