TC-CNET-4.10 Test step 11 timeout.

[hoorii-zzy]

Hi,

      Our product is about to undergo Matter certification. However, in the testing of TC-CNET-4.10, during the 11th step " ./chip-tool generalcommissioning arm-fail-safe 0 0 1 0", there is a timeout error indicating that the command is not responding. However, when executing it immediately for the second time, it succeeds. This phenomenon is consistently reproducible. Can you provide any guidance on how to resolve this issue? We are anxious to proceed with the product testing.

      I'm urgently looking forward to your reply.

      Jerry.

      22/8/2023

[hoorii-zzy]

Charlie said:

Just want to confirm the latest test is based on the original NCS\v2.2.0\nrf\samples\matter\lock, correct?

Yes, correct

[hoorii-zzy]

Hi Charlie,

I have some new discoveries:

1. If I execute the command "./chip-tool generalcommissioning arm-fail-safe 900 1 1 0" and then directly execute "./chip-tool generalcommissioning arm-fail-safe 0 0 1 0", it will be successful.
2. If I execute the command "./chip-tool generalcommissioning arm-fail-safe 900 1 1 0" , then
   "./chip-tool networkcommissioning  remove-network "and "./chip-tool networkcommissioning connect-network", then execute "./chip-tool generalcommissioning arm-fail-safe 0 0 1 0", the first time will fail and the second time will be successful.
   
3. If I change 900 to 60 based on 2, remove and reconnect the network, wait for 60s, and then execute "./chip-tool generalcommissioning arm-fail-safe 0 0 1 0", it will be successful on the first attempt.

Hope these can help you.

 Jerry.

[hoorii-zzy]

Hi Charlie,

Is there any progress that can be shared with me right now? We are in urgent need of a result or solution.

BR,

Jerry.

[Charlie]

Hi Jerry,

Thanks for keeping sharing your discovery.

Our development team had some delays due to other high-priority tasks, but they are working on reproducing this issue now and will have results quite soon.

I will keep monitoring the process and provide you an update later.

Best regards,

Charlie

[Charlie]

Hi Jerry,

Just got confirmation that we are able to reproduce the issue with the release configuration of door lock sample (NCS 2.2.0).

steps needed to reproduce:

1. commission door lock
2. run ./chip-tool
3. run ./chip-tool remove-network hex:<extended pan id e.g. 1111111122222222> 1 0
4. run ./chip-tool arm-fail-safe 0 0 1 0

It seems that the issue is with some race condition connected with CASE session because while we ran above steps within interactive controller, the 4th step successfully passed

1. commission device
2. run chip-tool interactive by ./chip-tool interactive start
3. generalcommissioning arm-fail-safe 900 1 1 0
4. remove-network hex:<extended pan id e.g. 1111111122222222> 1 0
5. arm-fail-safe 0 0 1 0

To find the root cause, We need more time to investigate.

Best regards,

Charlie