project-chip / project-chip/matter-test-scripts
TC-DGGEN-2.1 Matter 1.3 ble-thread commissioning failed
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 7
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 3
Description
I'm having a problem with the TC-DGGEN-2.1. Upon startup, the TC requests a factory reset. This is fine, but in the next step, it tries to perform commissioning with a default value as the payload (MT:-24J0AFN00KA0648G00).
My problem is this line in the TC because the payload is not correct:
CHIPTOOL | 2025-04-01 10:21:46.250219 | CHIP:TOO Command: pairing code 11667813817360817962 MT:-24J0AFN00KA0648G00
I added a screenshot from the yaml. There you can see the default value (same like the command).
With this problem I changed the payload in the yaml.
After the change of payload the TH tries a commissioning via DNS-SD (new Payload MT:8IXS1CEK01Y10648G00). But my DUT is a ble-thread device. (The commissioning in a Apple ecosystem works fine with this payload)
I use TH 2.10.1+spring2024 for Matter 1.3 test
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the attached UI_Test_Run_EP0_DGGEN_2_1_2025_04_07_14_14_51.log and the YAML shown in the screenshots. Trace the TC-DGGEN-2.1 commissioning flow from the default payload through the changed payload, then verify that a BLE-Thread DUT is commissioned using the intended transport rather than DNS-SD.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, yaml
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100