certification-tool icon indicating copy to clipboard operation
certification-tool copied to clipboard

[Bug] Matter 1.5 TE1 - unable to do on-network commissioning

Open plauric opened this issue 11 months ago • 2 comments

Describe the bug

Using a DUT as server, unable to run TC-ACL-2.1 from the TH web interface: on-network commissioning fails.

Steps to reproduce the behavior

Using v2.13-beta2+summer2025 and a DUT as server:

  1. Create a project using the default settings and select the Base and Access Control PICS.
  2. Select a single test: TC-ACL-2.1
  3. The DUT server is on the network. Put it in commissioning mode.
  4. The RasPI is connected using Ethernet.
  5. Try running the test and confirm when prompted that the DUT is in commissioning mode. The test fails:

Test Suite Error: Error occurred during setup of test suite.FirstChipToolSuite. Connecting to ws://172.19.0.1:9002 failed.

While the DUT server is in commissioning mode, running this command from the RasPI confirms that the DUT can be discovered on the network:

ubuntu@ubuntu:~$ avahi-browse -d local _matterc._udp --resolve

eth0 IPv4 69D2FBD61AE58D09 _matterc._udp local = eth0 IPv4 69D2FBD61AE58D09 _matterc._udp local hostname = [A788AF55E58B8ED7.local] address = [192.168.2.21] port = [5540] txt = ["PI=" "PH=33" "CM=1" "D=3840" "VP=5398+4"]

Also, I can commission the DUT just fine when using chip-tool on a development machine.

Expected behavior

No response

Log files

UI_Test_Run_2025_03_04_18_59_30.log

PICS file

No response

Screenshots

No response

Environment

No response

Additional Information

No response

plauric avatar Mar 05 '25 00:03 plauric

Hi @plauric,

I'm not able to reproduce this issue but I noticed from the log that you used a PICS file. Can you share the PICS here so I may try a similar execution from my side?

Also, any more details on the environment used would be helpful.

antonio-amjr avatar Mar 18 '25 17:03 antonio-amjr

@plauric Could you please try again with v2.13-beta3.3+summer2025 version?

rquidute avatar May 06 '25 21:05 rquidute

@rquidute This was a user error - the mDNS packets didn't include the IPv6 address of the DUT.

Thank you for looking into this.

plauric avatar May 14 '25 15:05 plauric