Matter TH failing CDOCONC-2.1

[Tiit]

Hi again,

I'm having trouble with the Matter Test Harness. I have been running tests in isolation one by one and fixing issues the TH finds. Now I have run into an issue I don't really know how to solve. I take the Matter Window Cover sample and add CO2 measurement cluster to that using the ZAP tool. In the ZAP tool I set MinMeasuredValue, MaxMeasuredValue and MeasuredValue to RAM Storage (as otherwise TH will fail to read them). If I now run the TH and have it test this cluster it will succeed in steps 1..3 (commission, read min and max) but fail in step 4 (read MeasuredValue). The logs are of no help as it seems TH doesn't even try to read that cluster.

Test Step Completed [PASSED]: Step 3: TH reads from the DUT the MaxMeasuredValue attribute.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Executing Test Step: Step 4: TH reads from the DUT the MeasuredValue attribute.
Test Step Error: Error occurred during execution of test case TC-CDOCONC-2.1. '>=' not supported between instances of 'float' and 'NoneType'
Test Case Completed [ERROR]: TC-CDOCONC-2.1
================================================================================
Unpairing DUT from server

I'm not sure why this is happening. We are very close to having to send our device out to certification and I don't really feel comfortable with the state of it as is. If I just use chip-tool I can successfully read that value so I'm not sure why the test would fail. 

To be honest this doesn't feel like a "Nordic" issue to me but more like a TH/CSA issue but I'm hoping maybe you guy shave seen this before and can help me move forward faster.

Tiit

[Elfving]

Hi Tiit,

Is this related to this previous case of yours? Was that problem solved?

I agree that it doesn't look like a Nordic issue but I'll forward this to the relevant team and see if they have any ideas.

Still using 3.0.1?

Regards,

Elfving

[Tiit]

Hi Elfving,

It is related in that I'm working on the same device. But the previous issue was resolved as a user posted a snippet of JSON i have to add to the TH conf that makes the tests run on the correct endpoint. I have also discussed this with the lab that will certify the device and they agree that this is how they would also do that.

I will also reach out to CSA and hope they have some input on this issue as well. But I think it wouldn't hurt to have the issue here in Devzone as well since this will be the most likely place the next person running into this will look for the solution.

Still using 3.0.1. But if you think it would change anything I can try the newest version as well.

TIit

[Elfving]

Hi again,

Which chip-tool command did you use to obtain value of MaxMeasuredValue? And what is then returned?

Regards,

Elfving

[Elfving]

Got help from the relevant team here:

This steps are defined as the following:

    - label: "Step 4: TH reads from the DUT the MeasuredValue attribute."
      PICS: CDOCONC.S.A0000
      command: "readAttribute"
      attribute: "MeasuredValue"
      response:
          constraints:
              type: single
              minValue: MinMeasuredValueValue
              maxValue: MaxMeasuredValueValue

Looking at the error:

Test Step Error: Error occurred during execution of test case TC-CDOCONC-2.1. '>=' not supported between instances of 'float' and 'NoneType'

This indicates that MeaseuredValue was not set NoneType. Alternatively one of the MinMeasuredValueValue or MaxMeasuredValueValue was of the NoneType. Have you set the MeasuredValue ?

Another thing: By default, this test case expects the Carbon Dioxide Concentration device type to be in Endpoint 1. Maybe this is the problem, as customer has this cluster on endpoint 2 and didn't configure Harness correctly? https://github.com/nrfconnect/sdk-connectedhomeip/blob/v3.0-branch/src/app/tests/suites/certification/Test_TC_CDOCONC_2_1.yaml#L23

https://github.com/project-chip/certification-tool/blob/main/docs/Matter_TH_User_Guide/Matter_TH_User_Guide.adoc#92-test-parameters

Regards,

Elfving