Inquiry About Matter Certification Test Failure on TC-S-2.2, Step 8g

[paper555]

I am writing to seek your assistance regarding an issue we encountered during the Matter certification testing. Our product failed to pass test case TC-S-2.2, specifically at Step 8g.

Issue Description:

• Expected Behavior: The TH sends an AddScene command and should receive a response with Status = 133.

• Actual Behavior: The system returns Status = 0 instead.

We are currently using SDK version 3.0.1. For your reference, we have attached the detailed process logs to this email.

Could you please help us investigate the root cause of this discrepancy? We would greatly appreciate any insights or suggestions to resolve this issue.

Thank you for your time and support. We look forward to your response.

TC-S-2.2_TH.txt

[Marte Myrvold]

Hi,

I have reported this internally and am waiting for a response from the developers. I will get back to you in a couple of days.

Best regards,
Marte

[Marte Myrvold]

Hi,

Please make sure you are using a test harness version that corresponds with the Matter version used in the nRF Connect SDK version you use.

The Scenes Management cluster is provisional in Matter 1.4.1, the version used in nRF Connect SDK v3.0.1. Provisional means that something is not certifiable at this stage.

The cluster is no longer provisional in Matter 1.4.2, so if you want to use Scenes Management and certify it, you should use nRF Connect SDK v3.1.0 or later, which uses Matter 1.4.2.

The developers recommend creating an issue in the connectedhomeip repository: https://github.com/project-chip/connectedhomeip/.

Best regards,
Marte

[paper555]

I've also encountered the same issue with the NCS SDK versions 2.9.1 and 3.0.0.

[Marte Myrvold]

The cluster is provisional in nRF Connect SDK v2.9.1 and v3.0.0 as well.

[paper555]

Does the Matter Light Bulb sample project mention enabling the BDX transfer protocol feature?

[Marte Myrvold]

Can you clarify what you mean by enabling BDX?

BDX is used for OTA, among other things, and the Light Bulb sample has the OTA Requestor device type on endpoint 0, so it does support BDX. There is some information in our documentation (Matter OTA - Bulk Data Exchange Protocol (BDX)), but not about enabling BDX specifically.