About Matter's Network Commissioning

RE: About Matter's Network Commissioning

Marte Myrvold — Mon, 17 Feb 2025 09:20:57 GMT

Hi Hiroki,

The developers confirmed that you are providing it correctly and that the logs are correct.

Best regards,
Marte

RE: About Matter's Network Commissioning

Marte Myrvold — Thu, 13 Feb 2025 14:24:47 GMT

Hi Hiroki,

I have asked the developers to verify if this is correct. As you say, the log is successful with these changes. However, one difference I see with your previous logs is that the TH does not send any connect-network command before the remove-network command. I do not know if this matters, but I have asked the developers to make sure. I will get back to you when I get a reply.

Best regards,
Marte

RE: About Matter's Network Commissioning

H-ogawa — Wed, 12 Feb 2025 01:12:42 GMT

Hi, Matre

I added the following test parameters and tested successfully.

Is this the correct way to set the value of PIXIT.CNET.THREAD_2ND_OPERATIONALDATASET that you are pointing out?

The log when successful is below.

devzone.nordicsemi.com/.../TC_2D00_CNET_2D00_4_5F00_16_5F00_2025_5F00_02_5F00_12_5F00_01_5F00_05_5F00_31.log

Best regards,

Hiroki

RE: About Matter's Network Commissioning

Marte Myrvold — Fri, 07 Feb 2025 12:32:55 GMT

Hi Hiroki,

It seems like the connect-network command was sent to the same network ID as the remove-network command (1111111122222222). So, the behavior of the DUT is as expected since you are trying to remove a network that the DUT is commissioned to. Most likely the wrong PIXIT.CNET.THREAD_2ND_OPERATIONALDATASET was given to the test harness, or no operational dataset was given at all, making it default to 1111111122222222. Providing any other value should work.

CHIPTOOL   | 2025-02-04 23:54:39.856806 | CHIP:TOO Command: networkcommissioning connect-network hex:1111111122222222 0x785f8dda442de7f7 0 --Breadcrumb 1

CHIPTOOL   | 2025-02-04 23:54:39.261810 | CHIP:TOO Command: networkcommissioning remove-network hex:1111111122222222 0x785f8dda442de7f7 0 --Breadcrumb 1

Best regards,
Marte

RE: About Matter's Network Commissioning

H-ogawa — Thu, 06 Feb 2025 23:38:55 GMT

Hi,Marte

Thank you for your reply.
We look forward to hearing from you.

Best regards,

Hiroki

RE: About Matter's Network Commissioning

Marte Myrvold — Thu, 06 Feb 2025 13:40:18 GMT

Hi Hiroki,

I missed that it failed in step 2 in the log you attached, but looking at the logs again, I see that it returns Success instead of NetworkIDNotFound in the NetworkConfigResponse command.

I will forward this to the developers and get back to you tomorrow or early next week.

Best regards,
Marte

RE: About Matter's Network Commissioning

H-ogawa — Thu, 06 Feb 2025 09:57:18 GMT

[quote userid="51257" url="~/f/nordic-q-a/118628/about-matter-s-network-commissioning/521644"]Have you tested TC-CNET-2.16 alone?[/quote]

I made a mistake.
TC-CNET-4.16.

RE: About Matter's Network Commissioning

H-ogawa — Thu, 06 Feb 2025 01:04:49 GMT

Hi,Marte

Thank you for your reply.
I haven't stopped it manually during testing.

Have you tested TC-CNET-2.16 alone?

I get an error in step2.

For some reason, networkcommissioning remove-network is responding successfully.

Also, when I run the chip tool using the same steps as the TC-CNET-2.16 test, I still get the error.
However, when sending networkcommissioning remove-network a second time, NetworkIDNotFound is returned.

The log of the command sent with chip-tool is below.

If there is any mistake in the settings, please let me know.

devzone.nordicsemi.com/.../TC_2D00_CNET_2D00_4.16_5F00_chip_2D00_tool_5F00_log.txt

Best regards,

Hiroki

RE: About Matter's Network Commissioning

Marte Myrvold — Wed, 05 Feb 2025 13:20:38 GMT

Hi Hiroki,

Based on the logs the DUT passes steps 1, 2 and 3 of the test, but fails at uploading the log due to it being cancelled:

INFO       | 2025-02-04 23:54:40.036716 | Test Step Completed [PASSED]: Step 3: TH sends ConnectNetwork Command to the DUT with NetworkID value as the extended PAN ID of PIXIT.CNET.THREAD_2ND_OPERATIONALDATASET, which does not match the commissioned network, and Breadcrumb field set to 1
INFO       | 2025-02-04 23:54:40.040422 | --------------------------------------------------------------------------------
INFO       | 2025-02-04 23:54:40.051778 | --------------------------------------------------------------------------------
INFO       | 2025-02-04 23:54:40.053056 | Executing Test Step: Prompt Manual Log Upload
INFO       | 2025-02-04 23:54:40.305008 | Test Step Completed [PASSED]: Prompt Manual Log Upload
INFO       | 2025-02-04 23:54:40.306201 | --------------------------------------------------------------------------------
WARNING    | 2025-02-04 23:54:42.449801 | Test Failure: User cancelled log upload prompt.
INFO       | 2025-02-04 23:54:42.451645 | Test Case Completed [FAILED]: TC-CNET-4.16 (Semi-automated)
INFO       | 2025-02-04 23:54:42.452700 | ================================================================================
INFO       | 2025-02-04 23:54:42.455250 | Unpairing DUT from server

Are you manually cancelling the log upload or test in some way during this step?

Best regards,
Marte