You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/app/tests/suites/certification/Test_TC_DD_2_2.yaml
+18
Original file line number
Diff line number
Diff line change
@@ -181,6 +181,24 @@ tests:
181
181
SoftAP commissioning not currently supported on TH=all-clusters-app
182
182
disabled: true
183
183
184
+
- label: "Step 3c: TH is configured with the default channel to be Channel 6 in 2.4GHz. If TH has a 5GHz Wi-Fi radio, TH is configured with an additional channel list that includes Channel 44 and the operating channel Wi-Fi network the DUT is on if it is operating in non-ETSI regulatory domains and includes Channel 149 if it is operating in ETSI regulatory domains."
185
+
PICS: MCORE.DD.DISCOVERY_PAF
186
+
verification: |
187
+
TH must start sending Wi-Fi PAF Publish Frames on the default channel and the channel list.
- label: "Step 2f: Using the DUT, parse the TH’s QR code and follow any steps needed for the Commissioner/Commissionee to complete the commissioning process using Wi-Fi PAF"
204
+
PICS: MCORE.DD.DISCOVERY_PAF
205
+
verification: |
206
+
1. DUT parses QR code and DUT commissions TH to the Matter network
Copy file name to clipboardExpand all lines: src/app/tests/suites/certification/Test_TC_DD_3_12.yaml
+46
Original file line number
Diff line number
Diff line change
@@ -169,6 +169,52 @@ tests:
169
169
[1657234324847] [31475:16824564] CHIP: [TOO] Device commissioning completed with success
170
170
disabled: true
171
171
172
+
- label:
173
+
"Step 2e: User-Intent Commissioning Flow: Use a Commissionee with a QR code that has the Custom Flow field set to 1 and supports Wi-Fi PAF for its Discovery Capability. "
"Step 2h: User should follow any TH-specific steps for putting the TH Commissionee device into commissioning mode and to complete the commissioning process using Wi-Fi PAF."
Copy file name to clipboardExpand all lines: src/app/tests/suites/certification/Test_TC_DD_3_13.yaml
+43
Original file line number
Diff line number
Diff line change
@@ -182,6 +182,49 @@ tests:
182
182
[1657235198856] [31506:16834043] CHIP: [TOO] Device commissioning completed with success
183
183
disabled: true
184
184
185
+
- label: "Step 2e: Custom Commissioning Flow: Use a Commissionee with a QR code that has the Custom Flow field set to 2 and supports Wi-Fi PAF for its Discovery Capability. Commissionee is NOT in commissioning mode. Ensure the Version bit string follows the current Matter spec. documentation."
- label: "Step 2h: User should follow any TH-specific steps, unless the DUT has alternative means to guide the user to successful commissioning, for putting the TH Commissionee into commissioning mode, for triggering the DUT Commissioner for commissioning, and for completing the commissioning process using BLE."
Copy file name to clipboardExpand all lines: src/app/tests/suites/certification/Test_TC_DD_3_14.yaml
+26
Original file line number
Diff line number
Diff line change
@@ -212,6 +212,32 @@ tests:
212
212
Run command failure: ../../third_party/connectedhomeip/src/controller/SetUpCodePairer.cpp:50: CHIP Error 0x0000002F: Invalid argument
213
213
disabled: true
214
214
215
+
- label: "Step 4c: Using the QR code from Step 1, ensure the TH’s Discovery Capability bit string is NOT set to Wi-Fi PAF for discovery (i.e. set to OnNetwork discovery capability)"
216
+
PICS: MCORE.DD.DISCOVERY_PAF
217
+
verification: |
218
+
User has a QR code generated to pass into DUT. Using the example provided above, the payload would be "MT:-24J029Q00KA0648G00".
- label: "Step 4d: Scan/read the QR code of the TH device using the DUT"
236
+
PICS: MCORE.DD.DISCOVERY_PAF
237
+
verification: |
238
+
If TH Commissionee’s Discovery Capabilities do not support Wi-Fi PAF, ensure that the DUT commissions the TH onto the Matter network over a capability that is NOT BLE. In this example, over OnNetwork.
239
+
disabled: true
240
+
215
241
- label:
216
242
"Step 5a: Prefix: Using the QR code from Step 1, generate a new QR
217
243
code but substituting out the current Prefix with an invalid Prefix
0 commit comments