<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Matter Test Harness tests failing</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/123709/matter-test-harness-tests-failing</link><description>Hi, 
 I&amp;#39;m having trouble with the Matter Test Harness randomly failing tests and failing to commission my device. I have tried this with both my own Matter device and the Window Cover sample from the 3.0.1 SDK. I have the TH set up on a Pi 5 with the</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 02 Sep 2025 11:45:30 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/123709/matter-test-harness-tests-failing" /><item><title>RE: Matter Test Harness tests failing</title><link>https://devzone.nordicsemi.com/thread/547455?ContentTypeID=1</link><pubDate>Tue, 02 Sep 2025 11:45:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:363b5b5f-3ea7-4b9d-93bf-134790073044</guid><dc:creator>Elfving</dc:creator><description>&lt;p&gt;Yeah I agree that the process is cumbersome, though unfortunately this is currently the way it is.&lt;/p&gt;
&lt;p&gt;Did you have a look at the suggestion from another user here above? I interpreted your lack of response to that as it working to some degree?&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Elfving&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Matter Test Harness tests failing</title><link>https://devzone.nordicsemi.com/thread/546812?ContentTypeID=1</link><pubDate>Tue, 26 Aug 2025 18:43:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c8cbc6d7-6d8d-463f-b2bf-da2861b665ed</guid><dc:creator>hotbeefcurry</dc:creator><description>&lt;p&gt;Hey Tiit,&lt;/p&gt;
&lt;p&gt;Within your project configuration on the test harness, you should have a test parameters section. You can define the endpoint there. Kinda like this.&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;{
  &amp;quot;config&amp;quot;: {
    &amp;quot;test_parameters&amp;quot;: {
      &amp;quot;endpoint&amp;quot;: 1
    },
    &amp;quot;network&amp;quot;: {
      &amp;quot;wifi&amp;quot;: {
        &amp;quot;ssid&amp;quot;: &amp;quot;testharness&amp;quot;,
        &amp;quot;password&amp;quot;: &amp;quot;wifi-password&amp;quot;
      },&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Matter Test Harness tests failing</title><link>https://devzone.nordicsemi.com/thread/546427?ContentTypeID=1</link><pubDate>Fri, 22 Aug 2025 09:22:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4885717a-f1b1-44f4-9224-10d3615cd6ff</guid><dc:creator>Tiit</dc:creator><description>&lt;p&gt;I have tried to match the ZAP and PICS the best I can. That process is incredibly not user friendly though. Why can&amp;#39;t I just define the data model in one tool and have the other tool read/import that?&lt;/p&gt;
&lt;p&gt;I think one of the reason for all these failures is that I can&amp;#39;t seem to define the endpoint for each cluster anywhere. None of the guides show how to do this unfortunately. I have 3 endpoints defined in ZAP: endpoint 0 as the standard thing, endpoint 1 for the window cover and battery status, endpoint 2 for the environmental sensors. But the TH tried to run all sensor cluster tests on endpoint 1. I tried using the drop-down selector in PICS tool to define the endpoint, but that creates files that are identical to when I don&amp;#39;t use that. I tried manually editing the test configuration JSON think in the TH Project Config but that errors out whenever I tough the endpoint configuration. How can I tell the Matter TH to run a test on a specific endpoint?&lt;/p&gt;
&lt;p&gt;Tiit&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Matter Test Harness tests failing</title><link>https://devzone.nordicsemi.com/thread/546346?ContentTypeID=1</link><pubDate>Thu, 21 Aug 2025 13:19:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8db82333-c7a5-443b-8f8b-f46d35acc1f1</guid><dc:creator>Elfving</dc:creator><description>&lt;p&gt;&lt;span&gt;TC_IDM_10_2 seems to fail because FeatureMap attribute is a different data type than the TH expects and&amp;nbsp;TC_IDM_10_4 fails because the wildcard read returns incomplete TLV.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;I had a talk with someone who knows this a bit better than I do, who believes that both of these issues stem from the same problem. Maybe the&lt;span&gt;&amp;nbsp;PICS you provided to the TH are wrong/doesn&amp;#39;t correspond with what you actually have on the device. A customer with a similar problem in the past had ZAP files that didn&amp;#39;t match the PICS or that the ZAP files were generated with a version of the ZAP tool that used a different feature level than the SDK.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Here is a &lt;a href="https://picstool.csa-iot.org/"&gt;PICS tool&lt;/a&gt;&amp;nbsp;but I believe you have to do things manually there as well, and t&lt;a href="https://github.com/project-chip/certification-tool/blob/main/docs/Matter_TH_User_Guide/Matter_TH_User_Guide.adoc"&gt;&lt;span&gt;here is a user guide for TH here.&lt;/span&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Regards,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Elfving&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Matter Test Harness tests failing</title><link>https://devzone.nordicsemi.com/thread/546000?ContentTypeID=1</link><pubDate>Tue, 19 Aug 2025 07:22:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ffc72563-c24e-4514-92d4-aba2a6818f43</guid><dc:creator>Tiit</dc:creator><description>&lt;p&gt;Hi&amp;nbsp;Elfving,&lt;/p&gt;
&lt;p&gt;I did already read that and also much of the CSA documentation. But I&amp;#39;m still stuck with this. The error logs I attached show failures but I can&amp;#39;t tell from the logs why the tests are failing. I think it may be because my PICS files and the things my device report do not match up for some reason. But I can&amp;#39;t find a log or anything that would tell me where the issue is specifically. As far as I understand I have two separate tools where I need to define my device data model - PICS tool and ZAP tool. And I have to manually make sure they match exactly. Is this correct? Or is there a way I can do this in one tool and have the other import and use the same definition somehow? Also - can I somehow see the OTBR logs while the Test Harness is doing the automatic tests? And another question I have is how do I select which test I need to run in the Test Harness? Or more specifically - which tests will my ACL run on my device?&lt;/p&gt;
&lt;p&gt;Tiit&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Matter Test Harness tests failing</title><link>https://devzone.nordicsemi.com/thread/545776?ContentTypeID=1</link><pubDate>Fri, 15 Aug 2025 11:56:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:11f776bd-2868-489e-8cb5-2d07d712f303</guid><dc:creator>Elfving</dc:creator><description>&lt;p&gt;Hi Tiit,&lt;/p&gt;
&lt;p&gt;&lt;a href="https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/protocols/matter/end_product/certification.html"&gt;We do offer a lot of documentation on this&lt;/a&gt;,&amp;nbsp; which looks like a good idea to read up on. Let me know if this doesn&amp;#39;t help answering your questions. I am not that knowledgeable about this myself, though I&amp;#39;d be happy to ask someone if run into any issues.&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Elfving&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>