forked from project-chip/connectedhomeip
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathTest_TC_CADMIN_1_1.yaml
600 lines (487 loc) · 35.3 KB
/
Test_TC_CADMIN_1_1.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
# Copyright (c) 2021 Project CHIP Authors
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# Auto-generated scripts for harness use only, please review before automation. The endpoints and cluster names are currently set to default
name:
4.1.1. [TC-CADMIN-1.1] Administrator Behavior using ECM [DUT - Commissioner]
PICS:
- CADMIN.C
- CADMIN.C.C00.Tx
config:
nodeId: 0x12344321
cluster: "Basic Information"
endpoint: 0
tests:
- label: "Note"
verification: |
For DUT as comissioner test cases, Chip-tool command used below are an example to verify the functionality. For certification test, we expect DUT should have a capability or way to run the equivalent command.
disabled: true
- label: "Precondition"
verification: |
Reset Devices to factory defaults
disabled: true
- label: "Step 1: TH_CR1 starts a commissioning process with TH_CE"
PICS: CADMIN.C
verification: |
"1. Provision the TH_CE (all-cluster-app) device using TH_CR1 (chip-tool ) on the raspi"
disabled: true
- label:
"Step 2: TH_CR1 sends command to TH_CE to open a commissioning window
with a commissioning timeout of PIXIT.CADMIN.CwDuration seconds using
ECM (Enhanced Commissioning Method)."
PICS: CADMIN.C.C00.Tx
verification: |
Below are the example command for using single RPI as multiple controller. Vendor should have the provision to use the equivalent command in their DUT or use multiple commissioners/controllers
On TH_CR1 send the below command
./chip-tool pairing open-commissioning-window 1 1 400 2000 3841
Verify the Open commisioning window on the TH_CE(all-cluster-app) Log:
[1660901022.112296][3045:3045] CHIP:DIS: mDNS service published: _matterc._udp
[1660901022.112389][3045:3045] CHIP:ZCL: Commissioning window is now open
[1660901022.112474][3045:3045] CHIP:DMG: Command handler moving to [ Preparing]
disabled: true
- label:
"Step 3a: TH_CR1 sends command to TH_CE to read the list of Fabrics"
PICS: OPCREDS.C.A0001
verification: |
Below are the example command for using single RPI as multiple controller. Vendor should have the provision to use the equivalent command with their all-cluster-app and for the second and third commissioners.
On TH_CR1 send the below command
./chip-tool operationalcredentials read fabrics 1 0 --fabric-filtered 0
Verify 1 entry in the Fabrics list attributeOn TH_CR1(CHIP-TOOL) Log
Verify TH_CE reports 1 entry in fabrics list
[1676355303.608991][997145:997145] CHIP:IM: Received Read request
[1676355303.609044][997145:997145] CHIP:DMG: ReadRequestMessage =
[1676355303.609054][997145:997145] CHIP:DMG: {
[1676355303.609062][997145:997145] CHIP:DMG: AttributePathIBs =
[1676355303.609072][997145:997145] CHIP:DMG: [
[1676355303.609080][997145:997145] CHIP:DMG: AttributePathIB =
[1676355303.609090][997145:997145] CHIP:DMG: {
[1676355303.609129][997145:997145] CHIP:DMG: Endpoint = 0x0,
[1676355303.609141][997145:997145] CHIP:DMG: Cluster = 0x3e,
[1676355303.609150][997145:997145] CHIP:DMG: Attribute = 0x0000_0001,
[1676355303.609158][997145:997145] CHIP:DMG: }
[1676355303.609168][997145:997145] CHIP:DMG:
[1676355303.609175][997145:997145] CHIP:DMG: ],
[1676355303.609186][997145:997145] CHIP:DMG:
[1676355303.609196][997145:997145] CHIP:DMG: isFabricFiltered = false,
[1676355303.609206][997145:997145] CHIP:DMG: InteractionModelRevision = 1
[1676355303.609214][997145:997145] CHIP:DMG: },
[1676355303.609271][997145:997145] CHIP:DMG: IM RH moving to [GeneratingReports]
[1676355303.609309][997145:997145] CHIP:DMG: Building Reports for ReadHandler with LastReportGeneration = 0 DirtyGeneration = 0
If the DUT has to provision to verify the logs, verify that TH all-clusters-app sent 1 entry in the Fabrics list attribute reports and that this entry matches the first commissioning’s information.
[1676355303.610452][997160:997162] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_003E Attribute 0x0000_0001 DataVersion: 784275529
[1676355303.610499][997160:997162] CHIP:TOO: Fabrics: 1 entries
[1676355303.610525][997160:997162] CHIP:TOO: [1]: {
[1676355303.610538][997160:997162] CHIP:TOO: RootPublicKey: 04E8581EC896E1F4C0C460F03B20B5F785669CEA9C950487F564F8AFEDD6414F92B47F7B3EF810454DFC8D912C77A8F477378207908941C5E1225609DF4E7751C7
[1676355303.610557][997160:997162] CHIP:TOO: VendorID: 65521
[1676355303.610563][997160:997162] CHIP:TOO: FabricID: 1
[1676355303.610569][997160:997162] CHIP:TOO: NodeID: 1
[1676355303.610576][997160:997162] CHIP:TOO: Label:
[1676355303.610582][997160:997162] CHIP:TOO: FabricIndex: 1
[1676355303.610588][997160:997162] CHIP:TOO: }
[1676355303.610660][997160:997162] CHIP:EM: <<< [E:41653i S:27265 M:61334885 (Ack:214003320)] (S) Msg TX to 1:0000000000000001 [6193] --- Type 0000:10 (SecureChannel:StandaloneAck)
disabled: true
- label:
"Step 3b: Introduce dashes and spaces into the 11 digit Manual Code
provided in step 2 and enter it in the userinterfacedisplay of DUT_CR2"
PICS: CADMIN.M.UserInterfaceDisplay
verification: |
Vendor specific test step that should be manually verified using the requirements in the Expected Outcome.
disabled: true
- label: "Step 4.a: DUT_CR2 starts a commissioning process with TH_CE"
PICS: CADMIN.C
verification: |
Below are the example command for using single RPI as multiple controller. Vendor should have the provision to use the equivalent command in their DUT or use multiple commissioners/controllers
On DUT_CR2 send the below command
Below is the example when using chip tool as controller (considering 35998938564 as the manual code generated by 1st controller)
./chip-tool pairing code 2 35998938564 --commissioner-name beta
Verify TH_CE logs for
Commissioning completed successfully
disabled: true
- label:
"Step 4.b: Verify TH_CE is now discoverable over DNS-SD with two SRV
Records"
verification: |
Below are the example command for using single RPI as multiple controller. Vendor should have the provision to use the equivalent command in their DUT or use multiple commissioners/controllers
On the raspi , Verify if the TH_CE(All-cluster-app) is broadcasting
On TH_CR1 send the below command
avahi-browse -rt _matter._tcp
If the DUT has to provision to verify the logs, verify that TH all-clusters-app is now discoverable over DNS-SD with two SRV Records commissioning’s information.
+ wlp0s20f3 IPv6 3767A62E3306BE7C-0000000000000002 _matter._tcp local
+ wlp0s20f3 IPv6 B64553F058906CB3-0000000000000001 _matter._tcp local
= wlp0s20f3 IPv6 3767A62E3306BE7C-0000000000000002 _matter._tcp local
hostname = [8C1D96786A130000.local]
address = [fe80::73a0:f1da:5228:b4be]
port = [5540]
txt = ["T=1"]
= wlp0s20f3 IPv6 B64553F058906CB3-0000000000000001 _matter._tcp local
hostname = [8C1D96786A130000.local]
address = [fe80::73a0:f1da:5228:b4be]
port = [5540]
txt = ["T=1"]
disabled: true
- label:
"Step 4.c: DUT_CR2 sends command to TH_CE to write and read the Basic
Information Clusters NodeLabel mandatory attribute"
PICS: BINFO.C.A0005
verification: |
Below are the example command for using single RPI as multiple controller. Vendor should have the provision to use the equivalent command with their all-cluster-app and for the second and third commissioners.
On DUT_CR2 send the below command
./chip-tool basicinformation write node-label te5new 2 0 --commissioner-name beta
Verify Write request on TH_CE(all-clusters-app) Log
[1660894021.901330][2871:2871] CHIP:EM: Handling via exchange: 9616r, Delegate: 0xaaaada21ffc0
[1660894021.901426][2871:2871] CHIP:IM: Received Write request
[1660894021.901484][2871:2871] CHIP:DMG: IM WH moving to [Initialized]
[1660894021.901613][2871:2871] CHIP:DMG: WriteRequestMessage =
[1660894021.901676][2871:2871] CHIP:DMG: {
[1660894021.901735][2871:2871] CHIP:DMG: suppressResponse = false,
[1660894021.901802][2871:2871] CHIP:DMG: timedRequest = false,
[1660894021.901864][2871:2871] CHIP:DMG: AttributeDataIBs =
[1660894021.901940][2871:2871] CHIP:DMG: [
[1660894021.902001][2871:2871] CHIP:DMG: AttributeDataIB =
[1660894021.902071][2871:2871] CHIP:DMG: {
[1660894021.902136][2871:2871] CHIP:DMG: AttributePathIB =
[1660894021.902219][2871:2871] CHIP:DMG: {
[1660894021.902302][2871:2871] CHIP:DMG: Endpoint = 0x0,
[1660894021.902394][2871:2871] CHIP:DMG: Cluster = 0x28,
[1660894021.902488][2871:2871] CHIP:DMG: Attribute = 0x0000_0005,
[1660894021.902574][2871:2871] CHIP:DMG: }
[1660894021.902827][2871:2871] CHIP:DMG:
[1660894021.902912][2871:2871] CHIP:DMG: Data = "te5new" (6 chars),
[1660894021.902985][2871:2871] CHIP:DMG: },
./chip-tool basicinformation read node-label 2 0 --commissioner-name beta
Verify read request on TH_CE(all-clusters-app) Log
[1660894142.828718][2871:2871] CHIP:EM: Handling via exchange: 62454r, Delegate: 0xaaaada21ffc0
[1660894142.828834][2871:2871] CHIP:IM: Received Read request
[1660894142.829023][2871:2871] CHIP:DMG: ReadRequestMessage =
[1660894142.829097][2871:2871] CHIP:DMG: {
[1660894142.829153][2871:2871] CHIP:DMG: AttributePathIBs =
[1660894142.829235][2871:2871] CHIP:DMG: [
[1660894142.829306][2871:2871] CHIP:DMG: AttributePathIB =
[1660894142.829376][2871:2871] CHIP:DMG: {
[1660894142.829449][2871:2871] CHIP:DMG: Endpoint = 0x0,
[1660894142.829532][2871:2871] CHIP:DMG: Cluster = 0x28,
[1660894142.829627][2871:2871] CHIP:DMG: Attribute = 0x0000_0005,
[1660894142.829703][2871:2871] CHIP:DMG: }
[1660894142.829777][2871:2871] CHIP:DMG:
disabled: true
- label:
"Step 5: DUT_CR2 sends command to TH_CE to read the list of Fabrics"
PICS: OPCREDS.C.A0001
verification: |
Below are the example command for using single RPI as multiple controller. Vendor should have the provision to use the equivalent command in their DUT or use multiple commissioners/controllers
On DUT_CR2 send the below command
./chip-tool operationalcredentials read fabrics 2 0 --fabric-filtered 0 --commissioner-name beta
[1676355937.247133][997283:997283] CHIP:IM: Received Read request
[1676355937.247187][997283:997283] CHIP:DMG: ReadRequestMessage =
[1676355937.247196][997283:997283] CHIP:DMG: {
[1676355937.247202][997283:997283] CHIP:DMG: AttributePathIBs =
[1676355937.247210][997283:997283] CHIP:DMG: [
[1676355937.247215][997283:997283] CHIP:DMG: AttributePathIB =
[1676355937.247223][997283:997283] CHIP:DMG: {
[1676355937.247230][997283:997283] CHIP:DMG: Endpoint = 0x0,
[1676355937.247238][997283:997283] CHIP:DMG: Cluster = 0x3e,
[1676355937.247245][997283:997283] CHIP:DMG: Attribute = 0x0000_0001,
[1676355937.247251][997283:997283] CHIP:DMG: }
[1676355937.247259][997283:997283] CHIP:DMG:
[1676355937.247264][997283:997283] CHIP:DMG: ],
[1676355937.247273][997283:997283] CHIP:DMG:
[1676355937.247279][997283:997283] CHIP:DMG: isFabricFiltered = false,
[1676355937.247285][997283:997283] CHIP:DMG: InteractionModelRevision = 1
[1676355937.247291][997283:997283] CHIP:DMG: },
[1676355937.247324][997283:997283] CHIP:DMG: IM RH moving to [GeneratingReports]
[1676355937.247353][997283:997283] CHIP:DMG: Building Reports for ReadHandler with LastReportGeneration = 0 DirtyGeneration = 0
If the DUT has to provision to verify the logs, verify that TH all-clusters-app sent 1 entry in the Fabrics list attribute reports andand that these entries match the commissioning state to date.
[1676355937.249107][997381:997383] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_003E Attribute 0x0000_0001 DataVersion: 3110912421
[1676355937.249126][997381:997383] CHIP:TOO: Fabrics: 2 entries
[1676355937.249137][997381:997383] CHIP:TOO: [1]: {
[1676355937.249141][997381:997383] CHIP:TOO: RootPublicKey: 04CE05E675BAE5E141A6FF8412C01E7A418005EE3B3CDBAE730DAB3354F58B4F5DB4F4093E2C0DF28068817D24E9EB9A65A5D64DC776BE90D2B663A5EFFFB11636
[1676355937.249150][997381:997383] CHIP:TOO: VendorID: 65521
[1676355937.249152][997381:997383] CHIP:TOO: FabricID: 1
[1676355937.249154][997381:997383] CHIP:TOO: NodeID: 1
[1676355937.249156][997381:997383] CHIP:TOO: Label:
[1676355937.249158][997381:997383] CHIP:TOO: FabricIndex: 1
[1676355937.249160][997381:997383] CHIP:TOO: }
[1676355937.249163][997381:997383] CHIP:TOO: [2]: {
[1676355937.249166][997381:997383] CHIP:TOO: RootPublicKey: 04068A95301585A6EF6D23575F863B7C2DDA71D69E1AD58590CFEB34B18A31C54FCC5CF1ABBB889BCBE2EE9D8EBB5435EC8DABB8ADC0E203A59F801BD1ACDBB835
[1676355937.249168][997381:997383] CHIP:TOO: VendorID: 65521
[1676355937.249170][997381:997383] CHIP:TOO: FabricID: 2
[1676355937.249172][997381:997383] CHIP:TOO: NodeID: 2
[1676355937.249173][997381:997383] CHIP:TOO: Label:
[1676355937.249175][997381:997383] CHIP:TOO: FabricIndex: 2
[1676355937.249176][997381:997383] CHIP:TOO: }
[1676355937.249199][997381:997383] CHIP:EM: <<< [E:40732i S:56928 M:242798967 (Ack:118300610)] (S) Msg TX to 2:0000000000000002 [BE7C] --- Type 0000:10 (SecureChannel:StandaloneAck)
disabled: true
- label:
"Step 6: TH_CR1 sends command to TH_CE to write and read the Basic
Information Clusters NodeLabel mandatory attribute"
PICS: BINFO.C.A0005
verification: |
Below are the example command for using single RPI as multiple controller. Vendor should have the provision to use the equivalent command in their DUT or use multiple commissioners/controllers
On TH_CR1 send the below command
./chip-tool basicinformation write node-label te8 1 0
Verify the Write request On TH_CE(all-clusters-app) Log
[1660894538.804578][2871:2871] CHIP:EM: Handling via exchange: 64932r, Delegate: 0xaaaada21ffc0
[1660894538.804677][2871:2871] CHIP:IM: Received Write request
[1660894538.804737][2871:2871] CHIP:DMG: IM WH moving to [Initialized]
[1660894538.804867][2871:2871] CHIP:DMG: WriteRequestMessage =
[1660894538.804933][2871:2871] CHIP:DMG: {
[1660894538.804993][2871:2871] CHIP:DMG: suppressResponse = false,
[1660894538.805059][2871:2871] CHIP:DMG: timedRequest = false,
[1660894538.805120][2871:2871] CHIP:DMG: AttributeDataIBs =
[1660894538.805196][2871:2871] CHIP:DMG: [
[1660894538.805258][2871:2871] CHIP:DMG: AttributeDataIB =
[1660894538.805346][2871:2871] CHIP:DMG: {
[1660894538.805412][2871:2871] CHIP:DMG: AttributePathIB =
[1660894538.805493][2871:2871] CHIP:DMG: {
[1660894538.805575][2871:2871] CHIP:DMG: Endpoint = 0x0,
[1660894538.805661][2871:2871] CHIP:DMG: Cluster = 0x28,
[1660894538.805752][2871:2871] CHIP:DMG: Attribute = 0x0000_0005,
[1660894538.805840][2871:2871] CHIP:DMG: }
[1660894538.805922][2871:2871] CHIP:DMG:
[1660894538.806010][2871:2871] CHIP:DMG: Data = "te8" (3 chars),
[1660894538.806082][2871:2871] CHIP:DMG: },
./chip-tool basicinformation read node-label 1 0
Verify the Read request On TH_CE(all-clusters-app) Log
[1660894686.511690][2871:2871] CHIP:EM: Received message of type 0x2 with protocolId (0, 1) and MessageCounter:155836021 on exchange 25703r
[1660894686.511817][2871:2871] CHIP:EM: Handling via exchange: 25703r, Delegate: 0xaaaada21ffc0
[1660894686.511920][2871:2871] CHIP:IM: Received Read request
[1660894686.512190][2871:2871] CHIP:DMG: ReadRequestMessage =
[1660894686.512259][2871:2871] CHIP:DMG: {
[1660894686.512314][2871:2871] CHIP:DMG: AttributePathIBs =
[1660894686.512380][2871:2871] CHIP:DMG: [
[1660894686.512441][2871:2871] CHIP:DMG: AttributePathIB =
[1660894686.512526][2871:2871] CHIP:DMG: {
[1660894686.512599][2871:2871] CHIP:DMG: Endpoint = 0x0,
[1660894686.512683][2871:2871] CHIP:DMG: Cluster = 0x28,
[1660894686.512772][2871:2871] CHIP:DMG: Attribute = 0x0000_0005,
disabled: true
- label:
"Step 7: DUT_CR2 sends command to TH_CE to read, write and then read
the Basic Information Clusters NodeLabel mandatory attribute"
PICS: BINFO.C.A0005
verification: |
Below are the example command for using single RPI as multiple controller. Vendor should have the provision to use the equivalent command in their DUT or use multiple commissioners/controllers
On DUT_CR2 send the below command
./chip-tool basicinformation read node-label 2 0 --commissioner-name beta
Verify the Read request On TH_CE(all-clusters-app) Log
[1660902253.379018][3045:3045] CHIP:EM: Handling via exchange: 3197r, Delegate: 0xaaaaadbeffc0
[1660902253.379122][3045:3045] CHIP:IM: Received Read request
[1660902253.379306][3045:3045] CHIP:DMG: ReadRequestMessage =
[1660902253.379373][3045:3045] CHIP:DMG: {
[1660902253.379430][3045:3045] CHIP:DMG: AttributePathIBs =
[1660902253.379496][3045:3045] CHIP:DMG: [
[1660902253.379557][3045:3045] CHIP:DMG: AttributePathIB =
[1660902253.379634][3045:3045] CHIP:DMG: {
[1660902253.379703][3045:3045] CHIP:DMG: Endpoint = 0x0,
[1660902253.379782][3045:3045] CHIP:DMG: Cluster = 0x28,
[1660902253.379871][3045:3045] CHIP:DMG: Attribute = 0x0000_0005,
[1660902253.379935][3045:3045] CHIP:DMG: }
[1660902253.380141][3045:3045] CHIP:DMG:
[1660902253.380208][3045:3045] CHIP:DMG: ],
./chip-tool basicinformation write node-label te5new 2 0 --commissioner-name beta
Verify the Write request On TH_CE(all-clusters-app) Log
[1660900144.090077][3045:3045] CHIP:EM: Handling via exchange: 23950r, Delegate: 0xaaaaadbeffc0
[1660900144.090167][3045:3045] CHIP:IM: Received Write request
[1660900144.090226][3045:3045] CHIP:DMG: IM WH moving to [Initialized]
[1660900144.090347][3045:3045] CHIP:DMG: WriteRequestMessage =
[1660900144.090411][3045:3045] CHIP:DMG: {
[1660900144.090470][3045:3045] CHIP:DMG: suppressResponse = false,
[1660900144.090537][3045:3045] CHIP:DMG: timedRequest = false,
[1660900144.090598][3045:3045] CHIP:DMG: AttributeDataIBs =
[1660900144.090677][3045:3045] CHIP:DMG: [
[1660900144.090739][3045:3045] CHIP:DMG: AttributeDataIB =
[1660900144.090816][3045:3045] CHIP:DMG: {
[1660900144.090887][3045:3045] CHIP:DMG: AttributePathIB =
[1660900144.090976][3045:3045] CHIP:DMG: {
[1660900144.091061][3045:3045] CHIP:DMG: Endpoint = 0x0,
[1660900144.091150][3045:3045] CHIP:DMG: Cluster = 0x28,
[1660900144.091247][3045:3045] CHIP:DMG: Attribute = 0x0000_0005,
[1660900144.091344][3045:3045] CHIP:DMG: }
[1660900144.091432][3045:3045] CHIP:DMG:
[1660900144.091560][3045:3045] CHIP:DMG: Data = "te5new" (6 chars),
[1660900144.091655][3045:3045] CHIP:DMG: },
Verify read attribute returns the updated value written
./chip-tool basicinformation read node-label 2 0 --commissioner-name beta
Verify the Read request On TH_CE(all-clusters-app) Log
[1660900360.861128][3045:3045] CHIP:EM: Handling via exchange: 17574r, Delegate: 0xaaaaadbeffc0
[1660900360.861223][3045:3045] CHIP:IM: Received Read request
[1660900360.861402][3045:3045] CHIP:DMG: ReadRequestMessage =
[1660900360.861471][3045:3045] CHIP:DMG: {
[1660900360.861527][3045:3045] CHIP:DMG: AttributePathIBs =
[1660900360.861591][3045:3045] CHIP:DMG: [
[1660900360.861651][3045:3045] CHIP:DMG: AttributePathIB =
[1660900360.861727][3045:3045] CHIP:DMG: {
[1660900360.861798][3045:3045] CHIP:DMG: Endpoint = 0x0,
[1660900360.861871][3045:3045] CHIP:DMG: Cluster = 0x28,
[1660900360.861939][3045:3045] CHIP:DMG: Attribute = 0x0000_0005,
[1660900360.862012][3045:3045] CHIP:DMG: }
[1660900360.862088][3045:3045] CHIP:DMG:
[1660900360.862158][3045:3045] CHIP:DMG: ],
disabled: true
- label: "Step 8: Turn off TH_CR1"
verification: |
No need to do anything as chip-tool process exits after each command
disabled: true
- label:
"Step 9: DUT_CR2 sends command to TH_CE to open a commissioning window
using a commissioning timeout of PIXIT.CADMIN.CwDuration seconds using
ECM (Enhanced Commissioning Method)"
PICS: CADMIN.C.C00.Tx
verification: |
Below are the example command for using single RPI as multiple controller. Vendor should have the provision to use the equivalent command in their DUT or use multiple commissioners/controllers
On DUT_CR2 send the below command
./chip-tool pairing open-commissioning-window 2 1 400 2000 3841 --commissioner-name beta
Verify the Commissioning window is opened in TH_CE(all-clusters-app) Log
[1660901022.112296][3045:3045] CHIP:DIS: mDNS service published: _matterc._udp
[1660901022.112389][3045:3045] CHIP:ZCL: Commissioning window is now open
[1660901022.112474][3045:3045] CHIP:DMG: Command handler moving to [ Preparing]
disabled: true
- label:
"Step 10: DUT_CR2 sends command to TH_CE to revoke the commissioning
window using the Revoke Commissioning command"
PICS: CADMIN.C.C02.Tx
verification: |
Below are the example command for using single RPI as multiple controller. Vendor should have the provision to use the equivalent command in their DUT or use multiple commissioners/controllers
On DUT_CR2 send the below command
./chip-tool administratorcommissioning revoke-commissioning 2 0 --timedInteractionTimeoutMs 1000 --commissioner-name beta
Verify the Commissioning window is closed in TH_CE(all-clusters-app) Log
[1661485834.635244][6993:6993] CHIP:DIS: mDNS service published: _matter._tcp
[1661485834.635293][6993:6993] CHIP:ZCL: Commissioning window is now closed
[1661485834.635328][6993:6993] CHIP:DMG: Command handler moving to [ Preparing]
disabled: true
- label:
"Step 11: TH_CR3 attempts to execute a PASE to starts a commissioning
process with TH_CE"
PICS: CADMIN.C
verification: |
Below are the example command for using single RPI as multiple controller. Vendor should have the provision to use the equivalent command with their all-cluster-app and for the second and third commissioners.
On TH_CR3 send the below command
./chip-tool pairing code 3 34995354639 --commissioner-name gamma
verify you got the following message in the TH_CR3(all-clusters-app) log
If the DUT has to provision to verify the logs, Verify that either no _matterc._udp commissionable records exist matching the previously obtained discriminator, or that TH_CE refuses to allow a PASE with the provided passcode from the onboarding payload.
[1689719618872] [29136:5163326] [DIS] Browsing for: _matterc._udp,_S15
[1689719648874] [29136:5163326] [CTL] Discovery timed out
[1689719648874] [29136:5163326] [CTL] Stopping commissioning discovery over DNS-SD
[1689719648874] [29136:5163320] [CTL] Shutting down the commissioner
[1689719648874] [29136:5163320] [CTL] Stopping commissioning discovery over DNS-SD
[1689719648874] [29136:5163320] [CTL] Shutting down the controller
disabled: true
- label:
"Step 12: DUT_CR2 sends command to TH_CE to write and read the Basic
Information Clusters NodeLabel mandatory attribute"
PICS: BINFO.C.A0005
verification: |
Below are the example command for using single RPI as multiple controller. Vendor should have the provision to use the equivalent command in their DUT or use multiple commissioners/controllers
On DUT_CR2 send the below command
./chip-tool basicinformation write node-label te5new 2 0 --commissioner-name beta
Verify the Write request On TH_CE(all-clusters-app) Log
[1660902144.913634][3045:3045] CHIP:EM: Handling via exchange: 22257r, Delegate: 0xaaaaadbeffc0
[1660902144.913728][3045:3045] CHIP:IM: Received Write request
[1660902144.913785][3045:3045] CHIP:DMG: IM WH moving to [Initialized]
[1660902144.913912][3045:3045] CHIP:DMG: WriteRequestMessage =
[1660902144.913977][3045:3045] CHIP:DMG: {
[1660902144.914038][3045:3045] CHIP:DMG: suppressResponse = false,
[1660902144.914106][3045:3045] CHIP:DMG: timedRequest = false,
[1660902144.914168][3045:3045] CHIP:DMG: AttributeDataIBs =
[1660902144.914244][3045:3045] CHIP:DMG: [
[1660902144.914305][3045:3045] CHIP:DMG: AttributeDataIB =
[1660902144.914375][3045:3045] CHIP:DMG: {
[1660902144.914440][3045:3045] CHIP:DMG: AttributePathIB =
[1660902144.914522][3045:3045] CHIP:DMG: {
[1660902144.914602][3045:3045] CHIP:DMG: Endpoint = 0x0,
[1660902144.914691][3045:3045] CHIP:DMG: Cluster = 0x28,
[1660902144.914940][3045:3045] CHIP:DMG: Attribute = 0x0000_0005,
[1660902144.915025][3045:3045] CHIP:DMG: }
[1660902144.915109][3045:3045] CHIP:DMG:
[1660902144.915208][3045:3045] CHIP:DMG: Data = "te5new" (6 chars),
[1660902144.915292][3045:3045] CHIP:DMG: },
[1660902144.915374][3045:3045] CHIP:DMG:
./chip-tool basicinformation read node-label 2 0 --commissioner-name beta
Verify the Read request On TH_CE(all-clusters-app) Log
[1660902253.379018][3045:3045] CHIP:EM: Handling via exchange: 3197r, Delegate: 0xaaaaadbeffc0
[1660902253.379122][3045:3045] CHIP:IM: Received Read request
[1660902253.379306][3045:3045] CHIP:DMG: ReadRequestMessage =
[1660902253.379373][3045:3045] CHIP:DMG: {
[1660902253.379430][3045:3045] CHIP:DMG: AttributePathIBs =
[1660902253.379496][3045:3045] CHIP:DMG: [
[1660902253.379557][3045:3045] CHIP:DMG: AttributePathIB =
[1660902253.379634][3045:3045] CHIP:DMG: {
[1660902253.379703][3045:3045] CHIP:DMG: Endpoint = 0x0,
[1660902253.379782][3045:3045] CHIP:DMG: Cluster = 0x28,
[1660902253.379871][3045:3045] CHIP:DMG: Attribute = 0x0000_0005,
[1660902253.379935][3045:3045] CHIP:DMG: }
[1660902253.380141][3045:3045] CHIP:DMG:
[1660902253.380208][3045:3045] CHIP:DMG: ],
disabled: true
- label:
"Step 13: DUT_CR2 sends command to TH_CE to open a commissioning
window using ECM"
PICS: CADMIN.C.C00.Tx
verification: |
Below are the example command for using single RPI as multiple controller. Vendor should have the provision to use the equivalent command in their DUT or use multiple commissioners/controllers
On DUT_CR2 send the below command
./chip-tool pairing open-commissioning-window 2 1 180 1000 3840 --commissioner-name beta
Verify the Commissioning window is opened in TH_CE(all-clusters-app) Log
[1660902413.357922][3045:3045] CHIP:DIS: mDNS service published: _matterc._udp
[1660902413.358025][3045:3045] CHIP:ZCL: Commissioning window is now open
[1660902413.358116][3045:3045] CHIP:DMG: Command handler moving to [ Preparing]
disabled: true
- label:
"Step 14: Wait for commissioning window that was opened in step 13 to
timeout"
verification: |
Wait for the timeout of commissioning window in the above step
disabled: true
- label:
"Step 15: DUT_CR2 sends command to TH_CE to open a commissioning
window using ECM"
PICS: CADMIN.C.C00.Tx
verification: |
Below are the example command for using single RPI as multiple controller. Vendor should have the provision to use the equivalent command in their DUT or use multiple commissioners/controllers
On DUT_CR2 send the below command
./chip-tool pairing open-commissioning-window 2 1 300 1000 3840 --commissioner-name beta
Verify the Commissioning window is opened in TH_CE(all-clusters-app) Log
[1660902623.744448][3045:3045] CHIP:DIS: mDNS service published: _matterc._udp
[1660902623.744550][3045:3045] CHIP:ZCL: Commissioning window is now open
[1660902623.744634][3045:3045] CHIP:DMG: Command handler moving to [ Preparing]
disabled: true
- label:
"Step 16: TH_CR1 starts a commissioning process with TH_CE before the
timeout from step 15"
PICS: CADMIN.C
verification: |
Below are the example command for using single RPI as multiple controller. Vendor should have the provision to use the equivalent command in their DUT or use multiple commissioners/controllers
On TH_CR1 send the below command
(considering 34995354639 as the manual code generated by DUT)
./chip-tool pairing code 1 34995354639
[1676358083.879096][997283:997283] CHIP:SVR: Failsafe timer expired
[1676358083.879098][997283:997283] CHIP:IN: SecureSession[0x563d5294d7b0]: MarkForEviction Type:1 LSID:55630
[1676358083.879100][997283:997283] CHIP:SC: SecureSession[0x563d5294d7b0]: Moving from state 'kActive' --> 'kPendingEviction'
[1676358083.879109][997283:997283] CHIP:IN: SecureSession[0x563d5294d7b0]: Released - Type:1 LSID:55630
[1676358083.879113][997283:997283] CHIP:SVR: Commissioning failed (attempt 1): ../../third_party/connectedhomeip/src/app/server/CommissioningWindowManager.cpp:77: CHIP Error 0x00000032: Timeout
[1676358083.879123][997283:997283] CHIP:IN: SecureSession[0x563d5294d7b0]: Allocated Type:1 LSID:55631
[1676358083.879127][997283:997283] CHIP:SC: Assigned local session key ID 55631
[1676358083.879129][997283:997283] CHIP:SC: Waiting for PBKDF param request
[1676358083.879131][997283:997283] CHIP:DIS: Updating services using commissioning mode 2
[1676358083.879233][997283:997283] CHIP:DIS: CHIP minimal mDNS started advertising.
[1676358083.880559][997283:997283] CHIP:DL: Using wifi MAC for hostname
If the DUT has to provision to verify the logs, Verify the OperationalCert error 9 in TH_CE(all-clusters-app) Log
[1676358083.879250][998226:998228] CHIP:DMG: Received Command Response Data, Endpoint=0 Cluster=0x0000_0030 Command=0x0000_0001
[1676358083.879258][998226:998228] CHIP:CTL: Failsafe disarmed
[1676358083.879264][998226:998228] CHIP:CTL: Successfully finished commissioning step 'Cleanup'
[1676358083.879274][998226:998228] CHIP:TOO: Device commissioning Failure: ../../third_party/connectedhomeip/src/controller/CHIPDeviceController.cpp:1365: CHIP Error 0x0000007E: Trying to add a NOC for a fabric that already exists) with OperationalCert error 9
[1676358083.879284][998226:998228] CHIP:IN: SecureSession[0x7fe26000eec0]: MarkForEviction Type:1 LSID:21508
[1676358083.879287][998226:998228] CHIP:SC: SecureSession[0x7fe26000eec0]: Moving from state 'kActive' --> 'kPendingEviction'
[1676358083.879312][998226:998228] CHIP:EM: Failed to send Solitary ack for MessageCounter:80598822 on exchange 54053i:../../third_party/connectedhomeip/src/messaging/ExchangeContext.cpp:144: CHIP Error 0x00000002: Connection aborted
[1676358083.879325][998226:998228] CHIP:DMG: ICR moving to [AwaitingDe]
disabled: true