<?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 commissioning fails at step 8 : AttestationVerification</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/94029/matter-commissioning-fails-at-step-8-attestationverification</link><description>Hi, 
 I&amp;#39;m in the process of developing a new Matter device, using the Matter template as starting point. 
 When trying to commission the device it fails at step 8 (AttestationVerification): 
 I also tried with one of the samples (the light_bulb) shipped</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 29 Nov 2022 13:24:21 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/94029/matter-commissioning-fails-at-step-8-attestationverification" /><item><title>RE: Matter commissioning fails at step 8 : AttestationVerification</title><link>https://devzone.nordicsemi.com/thread/398120?ContentTypeID=1</link><pubDate>Tue, 29 Nov 2022 13:24:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5f71ca07-4d33-4248-b52e-480925bbedd2</guid><dc:creator>abollaert</dc:creator><description>&lt;p&gt;&lt;a id="" href="https://github.com/project-chip/connectedhomeip/commit/faad9e179293775110f09692cd1c28e0d71b792f"&gt;https://github.com/project-chip/connectedhomeip/commit/faad9e179293775110f09692cd1c28e0d71b792f&lt;/a&gt;&amp;nbsp;is the commit that updates the certs (if you build your chip-tool using a version that follows this commit it will fail to commission your device).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Matter commissioning fails at step 8 : AttestationVerification</title><link>https://devzone.nordicsemi.com/thread/398118?ContentTypeID=1</link><pubDate>Tue, 29 Nov 2022 13:22:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3c3c09e2-6224-44a3-b118-fd5ccc1ddcf2</guid><dc:creator>abollaert</dc:creator><description>&lt;p&gt;Update : this problem seems to have been caused by a version conflict. I used a chip-tool built from the official repo (&lt;a id="" href="https://github.com/project-chip"&gt;https://github.com/project-chip&lt;/a&gt;) with device firmware build from NCS v2.1.2, and it would seem that the certs used differ (also see&amp;nbsp;&lt;a id="" href="https://github.com/google-home/sample-app-for-matter-android/issues/29"&gt;https://github.com/google-home/sample-app-for-matter-android/issues/29&lt;/a&gt;).&lt;br /&gt;&lt;br /&gt;I&amp;#39;ve now built a chip-tool from the Nordic fork of the CHIP codebase (&lt;a id="" href="https://github.com/nrfconnect/sdk-connectedhomeip,"&gt;https://github.com/nrfconnect/sdk-connectedhomeip,&lt;/a&gt; tag v2.1.2) and that fixed the problem.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Matter commissioning fails at step 8 : AttestationVerification</title><link>https://devzone.nordicsemi.com/thread/397335?ContentTypeID=1</link><pubDate>Thu, 24 Nov 2022 09:01:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:99974041-7cc3-4c62-89f4-3ab0528f875f</guid><dc:creator>abollaert</dc:creator><description>&lt;p&gt;Hi Maria,&lt;/p&gt;
&lt;p&gt;I&amp;#39;m just using the same code as the examples:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;SetDeviceAttestationCredentialsProvider(Examples::GetExampleDACProvider());&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;So I&amp;#39;m assuming these are test certificates.&lt;/p&gt;
&lt;p&gt;Then I just try to do a BLE pairing (with OTBR):&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;./chip-tool pairing ble-thread 100 hex:0e080000000000010000000300000f35060004001fffe0020811111111222222220708fd87dbd714786b2b051000112233445566778899aabbccddeeff030e4f70656e54687265616444656d6f010212340410445f2b5ca6f2a93a55ce570a70efeecb0c0402a0f7f8 20202021 3840&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;And it fails with error 601 (on 2.1.1 and 2.1.2, using the same code compiled with 2.1.0 works).&lt;/p&gt;
&lt;p&gt;I was planning on using development certs first, and add in my own certificates later.&lt;/p&gt;
&lt;p&gt;Kind regards and thanks,&lt;/p&gt;
&lt;p&gt;-Alex&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Matter commissioning fails at step 8 : AttestationVerification</title><link>https://devzone.nordicsemi.com/thread/397167?ContentTypeID=1</link><pubDate>Wed, 23 Nov 2022 12:34:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:47679874-68c6-4141-85a1-bee38d0edf21</guid><dc:creator>Maria Gilje</dc:creator><description>&lt;p&gt;Hello Alex,&lt;/p&gt;
&lt;p&gt;Sorry for the delay.&lt;/p&gt;
&lt;p&gt;The error code 601 means that no certificate is found. All error codes for Attestation Verification related errors are found in an enum &lt;a href="https://github.com/project-chip/connectedhomeip/blob/v1.0.0/src/credentials/attestation_verifier/DeviceAttestationVerifier.h#L30"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Are you using test certificates or your own?&lt;/p&gt;
&lt;p&gt;Kind Regards&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Matter commissioning fails at step 8 : AttestationVerification</title><link>https://devzone.nordicsemi.com/thread/396438?ContentTypeID=1</link><pubDate>Fri, 18 Nov 2022 14:03:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4f85f132-3f30-4a4a-acaa-89eb98dc9e58</guid><dc:creator>abollaert</dc:creator><description>&lt;p&gt;Update : if I revert NCS back to v2.1.0) commissioning works. Starting from v2.1.1 something was broken it seems.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>