Matter commissioning fails at step 8 : AttestationVerification

[abollaert]

Hi,

I'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):

[1668776330.043644][85437:85442] CHIP:CTL: Failed in verifying 'Attestation Information' command received from the device: err 601. Look at AttestationVerificationResult enum to understand the errors
[1668776330.043662][85437:85442] CHIP:CTL: Error on commissioning step 'AttestationVerification': '../examples/chip-tool/third_party/connectedhomeip/src/controller/CHIPDeviceController.cpp:1031: CHIP Error 0x000000AC: Internal error'
[1668776330.043666][85437:85442] CHIP:CTL: Failed to perform commissioning step 8

I also tried with one of the samples (the light_bulb) shipped with the SDK and that also yields this error (it's also using the ExampleDACProvider).

Am I missing something here?

Kind regards,

-Alex

PS. Sort of related: is it possible that the samples use a version for their zap file (82) that isn't supported by the zap-tool shipped with the matter module? I had to pick up an older version of the zap file in order to be able to edit it.

 

[Maria Gilje]

Hello Alex,

Sorry for the delay.

The error code 601 means that no certificate is found. All error codes for Attestation Verification related errors are found in an enum here.

Are you using test certificates or your own?

Kind Regards

[abollaert]

Hi Maria,

I'm just using the same code as the examples:

SetDeviceAttestationCredentialsProvider(Examples::GetExampleDACProvider());

So I'm assuming these are test certificates.

Then I just try to do a BLE pairing (with OTBR):

./chip-tool pairing ble-thread 100 hex:0e080000000000010000000300000f35060004001fffe0020811111111222222220708fd87dbd714786b2b051000112233445566778899aabbccddeeff030e4f70656e54687265616444656d6f010212340410445f2b5ca6f2a93a55ce570a70efeecb0c0402a0f7f8 20202021 3840

And it fails with error 601 (on 2.1.1 and 2.1.2, using the same code compiled with 2.1.0 works).

I was planning on using development certs first, and add in my own certificates later.

Kind regards and thanks,

-Alex

[abollaert]

Update : this problem seems to have been caused by a version conflict. I used a chip-tool built from the official repo (https://github.com/project-chip) with device firmware build from NCS v2.1.2, and it would seem that the certs used differ (also see https://github.com/google-home/sample-app-for-matter-android/issues/29).

I've now built a chip-tool from the Nordic fork of the CHIP codebase (https://github.com/nrfconnect/sdk-connectedhomeip, tag v2.1.2) and that fixed the problem.

[abollaert]

https://github.com/project-chip/connectedhomeip/commit/faad9e179293775110f09692cd1c28e0d71b792f 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).