Matter Test Harness: tests hang or fail to commission (rPI5 + nRF52840 RCP, NCS 3.0.2)

Question

Hi, 
 I’m having trouble getting the Matter Test Harness to run. 
 Environment

rPi 5 set up per Matter Test-Harness User Manual.pdf (using project-chip/certification-tool at v2.13+summer2025 ).

nRF52840 Dongle as the RCP.

NCS 3.0.2 Door Lock sample (no modifications).

Test Harness project configured with:

Fullscreen 
 TH_project_config.txt 
 Download 
 
 {
 "config": {
 "test_parameters": null,
 "network": {
 "wifi": {
 "ssid": "testharness",
 "password": "wifi-password"
 },
 "thread": {
 "rcp_serial_path": "/dev/ttyACM0",
 "rcp_baudrate": 115200,
 "on_mesh_prefix": "fd11:22::/64",
 "network_interface": "eth0",
 "dataset": {
 "channel": "15",
 "panid": "0x1234",
 "extpanid": "1111111122222222",
 "networkkey": "00112233445566778899aabbccddeeff",
 "networkname": "DEMO"
 },
 "otbr_docker_image": null
 }
 },
 "dut_config": {
 "discriminator": "3840",
 "setup_code": "20202021",
 "pairing_mode": "ble-thread",
 "chip_timeout": null,
 "chip_use_paa_certs": false,
 "trace_log": true,
 "enhanced_setup_flow": null
 }
 },
 "pics": {
 "clusters": {
 "Basic Information Cluster Test Plan": {
 "name": "Basic Information Cluster Test Plan",
 "items": {
 "BINFO.S": {
 "number": "BINFO.S",
 "enabled": true
 },
 "BINFO.S.A0000": {
 "number": "BINFO.S.A0000",
 "enabled": true
 },
 "BINFO.S.A0001": {
 "number": "BINFO.S.A0001",
 "enabled": true
 },
 "BINFO.S.A0002": {
 "number": "BINFO.S.A0002",
 "enabled": true
 },
 "BINFO.S.A0003": {
 "number": "BINFO.S.A0003",
 "enabled": true
 },
 "BINFO.S.A0004": {
 "number": "BINFO.S.A0004",
 "enabled": true
 },
 "BINFO.S.A0005": {
 "number": "BINFO.S.A0005",
 "enabled": true
 },
 "BINFO.S.A0006": {
 "number": "BINFO.S.A0006",
 "enabled": true
 },
 "BINFO.S.A0007": {
 "number": "BINFO.S.A0007",
 "enabled": true
 },
 "BINFO.S.A0008": {
 "number": "BINFO.S.A0008",
 "enabled": true
 },
 "BINFO.S.A0009": {
 "number": "BINFO.S.A0009",
 "enabled": true
 },
 "BINFO.S.A000a": {
 "number": "BINFO.S.A000a",
 "enabled": true
 },
 "BINFO.S.A000b": {
 "number": "BINFO.S.A000b",
 "enabled": false
 },
 "BINFO.S.A000c": {
 "number": "BINFO.S.A000c",
 "enabled": false
 },
 "BINFO.S.A000d": {
 "number": "BINFO.S.A000d",
 "enabled": false
 },
 "BINFO.S.A000e": {
 "number": "BINFO.S.A000e",
 "enabled": false
 },
 "BINFO.S.A000f": {
 "number": "BINFO.S.A000f",
 "enabled": true
 },
 "BINFO.S.A0010": {
 "number": "BINFO.S.A0010",
 "enabled": false
 },
 "BINFO.S.A0011": {
 "number": "BINFO.S.A0011",
 "enabled": false
 },
 "BINFO.S.A0012": {
 "number": "BINFO.S.A0012",
 "enabled": true
 },
 "BINFO.S.A0013": {
 "number": "BINFO.S.A0013",
 "enabled": true
 },
 "BINFO.S.A0014": {
 "number": "BINFO.S.A0014",
 "enabled": false
 },
 "BINFO.S.A0015": {
 "number": "BINFO.S.A0015",
 "enabled": true
 },
 "BINFO.S.A0016": {
 "number": "BINFO.S.A0016",
 "enabled": true
 },
 "BINFO.S.A0017": {
 "number": "BINFO.S.A0017",
 "enabled": false
 },
 "BINFO.S.E00": {
 "number": "BINFO.S.E00",
 "enabled": true
 },
 "BINFO.S.E01": {
 "number": "BINFO.S.E01",
 "enabled": false
 },
 "BINFO.S.E02": {
 "number": "BINFO.S.E02",
 "enabled": false
 },
 "BINFO.S.E03": {
 "number": "BINFO.S.E03",
 "enabled": false
 },
 "BINFO.C.A0005": {
 "number": "BINFO.C.A0005",
 "enabled": false
 }
 }
 }
 }
 }
}

Issue

When I start a test, the UI often gets stuck in a loading loop, or the run fails at commissioning.

UI_Test_Run_2025_09_01_15_09_08.log 
 Could someone advise what might be wrong or what to check next? 
 Thanks, 
 Lukasz

LukaWer · Accepted Answer

Elfving I&rsquo;ve got the setup working, but only by running OTBR on a separate Raspberry Pi. With the Test Harness (TH) configuration where OTBR runs in Docker on the same host, there appear to be networking/visibility issues between containers: the container with chip-tool doesn&rsquo;t see traffic from the OTBR container. Commissioning starts but times out right after the DUT connects to OTBR. 
 I observed the same behavior when running the nRF Matter Lock sample (SDK 3.1.0) with TH v2.13 + Summer 2025 with connected nRF Dongle as RCP. Using 9.1.3.b solved issue with communication to DUT.

Matter Test Harness: tests hang or fail to commission (rPI5 + nRF52840 RCP, NCS 3.0.2)

Top Replies