From 106535231cfe648a99da07f0d52f935aac04f2de Mon Sep 17 00:00:00 2001 From: kowsisoundhar12 <57476670+kowsisoundhar12@users.noreply.github.com> Date: Wed, 18 May 2022 18:41:25 +0530 Subject: [PATCH] Updated Manual Scripts (#18116) * Added updated manual scripts * Added Auto generated file * Restyled by whitespace * Added updated scripts * Restyled by whitespace * Restyled by clang-format Co-authored-by: Restyled.io --- .../suites/certification/Test_TC_DD_3_14.yaml | 498 +++++------ .../suites/certification/Test_TC_DD_3_7.yaml | 716 ++++++++++++++- .../suites/certification/Test_TC_DD_3_8.yaml | 700 ++++++++++++++- .../suites/certification/Test_TC_DM_1_2.yaml | 75 +- .../suites/certification/Test_TC_DM_2_3.yaml | 57 -- .../suites/certification/Test_TC_IDM_2_2.yaml | 825 ++++++++++++++++-- .../suites/certification/Test_TC_IDM_3_1.yaml | 284 +++++- .../suites/certification/Test_TC_IDM_3_2.yaml | 501 +++++++++-- .../suites/certification/Test_TC_IDM_4_1.yaml | 325 +++---- .../suites/certification/Test_TC_IDM_4_2.yaml | 187 +++- .../suites/certification/Test_TC_IDM_5_1.yaml | 178 ++-- .../suites/certification/Test_TC_IDM_5_2.yaml | 48 +- .../suites/certification/Test_TC_SC_4_5.yaml | 70 +- .../suites/certification/Test_TC_SC_4_9.yaml | 33 +- src/app/tests/suites/tests.js | 1 - .../chip-tool/zap-generated/test/Commands.h | 58 -- 16 files changed, 3605 insertions(+), 951 deletions(-) delete mode 100644 src/app/tests/suites/certification/Test_TC_DM_2_3.yaml diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_14.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_14.yaml index 437abe568b8719..3c1d6868129924 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_14.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_14.yaml @@ -14,8 +14,8 @@ # Auto-generated scripts for harness use only, please review before automation. The endpoints and cluster names are currently set to default name: - 7.3.14. [TC-DD-3.14] Commissioning Flow - Manual Pairing Code - Negative - scenario [DUT - Commissioner] + 3.3.14. [TC-DD-3.14] Commissioning Flow - QR Code - Negative Scenario [DUT - + Commissioner] config: nodeId: 0x12344321 @@ -23,354 +23,270 @@ config: endpoint: 0 tests: - - label: - "If (PICS_11_MANUAL_PC), Provide the 11 digit manual pairing code from - the Commissionee to the DUT in any format supported by DUT" - verification: - "Device TH: ./out/all-clusters-app/chip-all-clusters-app ... - [1645845935.798806][8925:8925] CHIP:DL: Device Configuration: - [1645845935.798853][8925:8925] CHIP:DL: Serial Number: TEST_SN - [1645845935.798875][8925:8925] CHIP:DL: Vendor Id: 65521 (0xFFF1) - [1645845935.798904][8925:8925] CHIP:DL: Product Id: 32769 (0x8001) - [1645845935.798929][8925:8925] CHIP:DL: Hardware Version: 0 - [1645845935.798960][8925:8925] CHIP:DL: Setup Pin Code: 20202021 - [1645845935.798984][8925:8925] CHIP:DL: Setup Discriminator: 3840 - (0xF00) [1645845935.799008][8925:8925] CHIP:DL: Manufacturing Date: - (not set) [1645845935.799038][8925:8925] CHIP:DL: Device Type: 65535 - (0xFFFF) [1645845935.799106][8925:8925] CHIP:SVR: SetupQRCode: - [MT:-24J042C00KA0648G00] [1645845935.799135][8925:8925] CHIP:SVR: - Copy/paste the below URL in a browser to see the QR Code: - [1645845935.799164][8925:8925] CHIP:SVR: - https://dhrishi.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J042C00KA0648G00 - [1645845935.799195][8925:8925] CHIP:SVR: Manual pairing code: - [34970112332] [1645845935.799236][8925:8925] CHIP:SVR: Long manual - pairing code: [749701123365521327694]" - disabled: true + - label: "Locate and scan/read the Commissionees QR code using DUT" + verification: | + Device TH: + ./out/all-clusters-app/chip-all-clusters-app - - label: - "If (PICS_21_MANUAL_PC), Provide the 21 digit manual pairing code from - the Commissionee to the DUT in any format supported by DUT" - verification: - "Device TH: ./out/all-clusters-app/chip-all-clusters-app ... - [1645845935.798806][8925:8925] CHIP:DL: Device Configuration: - [1645845935.798853][8925:8925] CHIP:DL: Serial Number: TEST_SN - [1645845935.798875][8925:8925] CHIP:DL: Vendor Id: 65521 (0xFFF1) - [1645845935.798904][8925:8925] CHIP:DL: Product Id: 32769 (0x8001) - [1645845935.798929][8925:8925] CHIP:DL: Hardware Version: 0 - [1645845935.798960][8925:8925] CHIP:DL: Setup Pin Code: 20202021 - [1645845935.798984][8925:8925] CHIP:DL: Setup Discriminator: 3840 - (0xF00) [1645845935.799008][8925:8925] CHIP:DL: Manufacturing Date: - (not set) [1645845935.799038][8925:8925] CHIP:DL: Device Type: 65535 - (0xFFFF) [1645845935.799106][8925:8925] CHIP:SVR: SetupQRCode: - [MT:-24J042C00KA0648G00] [1645845935.799135][8925:8925] CHIP:SVR: - Copy/paste the below URL in a browser to see the QR Code: - [1645845935.799164][8925:8925] CHIP:SVR: - https://dhrishi.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J042C00KA0648G00 - [1645845935.799195][8925:8925] CHIP:SVR: Manual pairing code: - [34970112332] [1645845935.799236][8925:8925] CHIP:SVR: Long manual - pairing code: [749701123365521327694]" + ...[1645845935.798806][8925:8925] CHIP:DL: Device Configuration: + [1645845935.798853][8925:8925] CHIP:DL: Serial Number: TEST_SN + [1645845935.798875][8925:8925] CHIP:DL: Vendor Id: 65521 (0xFFF1) + [1645845935.798904][8925:8925] CHIP:DL: Product Id: 32769 (0x8001) + [1645845935.798929][8925:8925] CHIP:DL: Hardware Version: 0 + [1645845935.798960][8925:8925] CHIP:DL: Setup Pin Code: 20202021 + [1645845935.798984][8925:8925] CHIP:DL: Setup Discriminator: 3840 (0xF00) + [1645845935.799008][8925:8925] CHIP:DL: Manufacturing Date: (not set) + [1645845935.799038][8925:8925] CHIP:DL: Device Type: 65535 (0xFFFF) + [1645845935.799106][8925:8925] CHIP:SVR: SetupQRCode: [MT:-24J042C00KA0648G00] + [1645845935.799135][8925:8925] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: + [1645845935.799164][8925:8925] CHIP:SVR: https://dhrishi.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J042C00KA0648G00 + [1645845935.799195][8925:8925] CHIP:SVR: Manual pairing code: [34970112332] + [1645845935.799236][8925:8925] CHIP:SVR: Long manual pairing code: [749701123365521327694] disabled: true - label: - "If (PICS_11_MANUAL_PC), VERSION: Using the manual code from Step 1.a, - generate a new manual code but substituting out the current VERSION - with an invalid VERSION: 1" - verification: - "BLOCKED chip-device-ctrl BUG: Generated pairing code does not change - when Version String is changed from 0 to, assuming it should - chip-device-ctrl > setup-payload generate -vr 1 -vi 65521 -pi 32769 - -cf 0 -dc 2 -dv 3840 -ps 20202021 2022-03-03 01:09:59 matter-te-6 - chip.SPL[333678] INFO Manual pairing code: [34970112332] 2022-03-03 - 01:09:59 matter-te-6 chip.SPL[333678] INFO SetupQRCode: - [MT:.24J042C00KA0648G00]" + "Version String: Using the QR code from Step 1, generate a new QR code + but substituting out the current Version String with an invalid + Version String (i.e. '010' or any non-zero 3-bit value)" + verification: | + ./chip-tool payload generate-qrcode --discriminator 3841 --setup-pin-code 20202021 --version 001 --vendor-id 65521 --product-id 0x8001 --commissioning-mode 2 --rendezvous 2 + [1649826848.599869][3121:3121] CHIP:TOO: QR Code: MT:.24J048N01KA0648G00 disabled: true - label: - "If (PICS_11_MANUAL_PC), Provide the manual pairing code, generated in - the previous step, to the DUT in any format supported by the DUT" - verification: - "BLOCKED chip-device-ctrl BUG: Generated pairing code does not change - when Version String is changed from 0 to, assuming it should" - disabled: true + "Scan/read the QR code, generated in the previous step, using the DUT" + verification: | + DUT Commissioner: + sudo ./examples/chip-tool/out/debug/chip-tool pairing qrcode 1234 MT:.24J0AFN00KA0648G00 + ... - - label: - "If (PICS_21_MANUAL_PC), VERSION: Using the manual code from Step 1.b, - generate a new manual code but substituting out the current VERSION - with an invalid VERSION: 1" - verification: "" + Device TH: + ./out/all-clusters-app/chip-all-clusters-app + ... + DUT has not commissioned the TH to the Matter network disabled: true - label: - "If (PICS_21_MANUAL_PC), Provide the manual pairing code, generated in - the previous step, to the DUT in any format supported by the DUT" - verification: - "DUT Commissioner: sudo ./examples/chip-tool/out/debug/chip-tool - pairing manualcode 1234 10054912339 ... Device TH: - ./out/all-clusters-app/chip-all-clusters-app ..." + "If (PICS_USER_INTENT_COMM_FLOW), Using the QR code from Step 1, + generate a new QR code using all the same Onboarding Payload + components except for the Custom Flow field, set it to 1: User-Intent + Commissioning Flow" + verification: | + chip-device-ctrl > setup-payload generate -vr 0 -vi 65522 -pi 32770 -cf 1 -dc 4 -dv 3840 -ps 20202021 + 2022-02-26 03:42:39 matter-te-6 chip.SPL[22108] INFO Manual pairing code: [34970112332] + 2022-02-26 03:42:39 matter-te-6 chip.SPL[22108] INFO SetupQRCode: [MT:86PS06VO00KA0648G00] disabled: true - label: - "If (PICS_11_MANUAL_PC), VID_PID_PRESENT: Using the manual code from - Step 1.a, generate a new manual code but substituting out the current - VID_PID_PRESENT with an invalid VID_PID_PRESENT set to 1" - verification: - "NEED SUPPORT: Unable to generate this manual code with - chip-device-ctrl: does not allow the option" - disabled: true + "If (PICS_USER_INTENT_COMM_FLOW), Scan/read the QR code, generated in + the previous step, using the DUT" + verification: | + chip-tool does not prevent commissioning because of invalid VID/PID values. This is handled after the commissioning process. + This test step is not valid and is addressed in PR#893 - - label: - "If (PICS_11_MANUAL_PC), Provide the manual pairing code, generated in - the previous step, to the DUT in any format supported by the DUT" - verification: - "NEED SUPPORT: Unable to generate manual code in previous step" - disabled: true + DUT Commissioner: + '' ./examples/chip-tool/out/debug/chip-tool pairing qrcode 1234 MT:86PS06VO00KA0648G00 + ... - - label: - "If (PICS_21_MANUAL_PC), VID_PID_PRESENT: Using the manual code from - Step 1.b, generate a new manual code but substituting out the current - VID_PID_PRESENT with an invalid VID_PID_PRESENT set to 0" - verification: - "NEED SUPPORT: Unable to generate this manual code with - chip-device-ctrl: does not allow the option" + Device TH: + ./out/all-clusters-app/chip-all-clusters-app + ... + DUT has not commissioned the TH to the Matter network disabled: true - label: - "If (PICS_21_MANUAL_PC), Provide the manual pairing code, generated in - the previous step, to the DUT in any format supported by the DUT" - verification: - "NEED SUPPORT: Unable to generate manual code in previous step" - disabled: true + "If (PICS_CUSTOM_COMM_FLOW), Using the QR code from Step 1, generate a + new QR code using all the same Onboarding Payload components except + for the Custom Flow field, set it to 2: Custom Commissioning Flow" + verification: | + INVALID TEST STEP - - label: - "If (PICS_11_MANUAL_PC), SHORT DISCRIMINATOR: Using the manual code - from Step 1.a, generate a new manual code but substituting out the - current SHORT DISCRIMINATOR string with one set to an invalid one - (i.e. Any different SHORT DISCRIMINATOR than the commissionees SHORT - DISCRIMINATOR while following section 5.1.1.5. 'Discriminator value')" - verification: - "chip-device-ctrl > setup-payload generate -vr 0 -vi 65521 -pi 32769 - -cf 0 -dc 2 -dv 1111 -ps 20202021 2022-03-03 01:56:46 matter-te-6 - chip.SPL[381013] INFO Manual pairing code: [10054912339] 2022-03-03 - 01:56:46 matter-te-6 chip.SPL[381013] INFO SetupQRCode: - [MT:-24J0MBW17K10648G00]" - disabled: true + This test step is not valid because the scenario here should always be supported for standard commissioning flow. This is addressed in PR#893 - - label: - "If (PICS_11_MANUAL_PC), Provide the manual pairing code, generated in - the previous step, to the DUT in any format supported by the DUT" - verification: - "DUT Commissioner: sudo ./examples/chip-tool/out/debug/chip-tool - pairing manualcode 1234 10054912339 ... [1646273075122] - [54299:29491292] CHIP: [BLE] NewConnection [1646273075150] - [54299:29491292] CHIP: [BLE] CBManagerState: ON [1646273075152] - [54299:29491293] CHIP: [BLE] CBManagerState: RESETTING [1646273076351] - [54299:29491293] CHIP: [BLE] CBManagerState: ON Illegal instruction: 4 - Device TH: ./out/all-clusters-app/chip-all-clusters-app ... DUT does - not commission the TH to the Matter network" - disabled: true - - label: - "If (PICS_21_MANUAL_PC), SHORT DISCRIMINATOR: Using the manual code - from Step 1.b, generate a new manual code but substituting out the - current SHORT DISCRIMINATOR string with one set to an invalid one - (i.e. Any different SHORT DISCRIMINATOR than the commissionees SHORT - DISCRIMINATOR while following section 5.1.1.5. Discriminator value)" - verification: - "NEED SUPPORT: Unable to generate this manual code with - chip-device-ctrl: does not generate 21-digit codes for every input" + chip-device-ctrl > setup-payload generate -vr 0 -vi 65521 -pi 32769 -cf 0 -dc 2 -dv 3840 -ps 20202021 + 2022-02-26 03:50:13 matter-te-6 chip.SPL[22108] INFO Manual pairing code: [34970112332] + 2022-02-26 03:50:13 matter-te-6 chip.SPL[22108] INFO SetupQRCode: [MT:-24J042C00KA0648G00] disabled: true - label: - "If (PICS_21_MANUAL_PC), Provide the manual pairing code, generated in - the previous step, to the DUT in any format supported by the DUT" - verification: - "NEED SUPPORT: Unable to generate manual code in previous step" + "If (PICS_CUSTOM_COMM_FLOW), Scan/read the QR code, generated in the + previous step, using the DUT" + verification: | + INVALID TEST STEP + + This test step is not valid because the scenario here should always be supported for standard commissioning flow. This is addressed in PR#893 + + DUT Commissioner: + '' ./examples/chip-tool/out/debug/chip-tool pairing qrcode 1234 MT:-24J042C00KA0648G00 + ... + + Device TH: + ./out/all-clusters-app/chip-all-clusters-app + ... + DUT has not commissioned the TH to the Matter network disabled: true - label: - "If (PICS_11_MANUAL_PC), Passcode: Using the manual code from Step - 1.a, generate a new manual code using all the same Onboarding Payload - components except for the Passcode. For each Passcode in the following - list, set the Passcode component to one of the invalid Passcode and - generate a new manual code using all the same Onboarding Payload - components and one Passcode from the list: 00000000, 11111111, - 22222222, 33333333, 44444444, 55555555, 66666666, 77777777, 88888888, - 99999999, 12345678, 87654321" - verification: - "NEED SUPPORT: Unable to generate false manual codes with - chip-device-ctrl chip-device-ctrl > setup-payload generate -vr 0 -vi - 65521 -pi 32769 -cf 1 -dc 4 -dv 3840 -ps 00000000 2022-03-03 00:11:58 - matter-te-6 chip.SPL[22108] ERROR Failed encoding invalid payload Chip - Stack Error 47 00000000: 11111111: 22222222: 33333333: 44444444: - 55555555: 66666666: 77777777: 88888888: 99999999: 12345678: 87654321" + "Commissioning Flow - Reserved: Using the QR code from Step 1, + generate a new QR code using all the same Onboarding Payload + components except for the Custom Flow field, set it to 3: Reserved" + verification: | + ./chip-tool payload generate-qrcode --discriminator 3841 --setup-pin-code 20202021 --version 000 --vendor-id 65521 --product-id 0x8001 --commissioning-mode 1 --rendezvous 2 + [1649827720.845213][3171:3171] CHIP:TOO: QR Code: MT:-24J08UL01KA0648G00 disabled: true - label: - "If (PICS_11_MANUAL_PC), Provide each of the manual pairing codes, - generated in the previous step, to the DUT in any format supported by - the DUT" - verification: - "NEED SUPPORT: Unable to generate manual code in previous step" + "Scan/read the QR code, generated in the previous step, using the DUT" + verification: | + DUT Commissioner: + '' ./examples/chip-tool/out/debug/chip-tool pairing qrcode 1234 MT:-24J08UL01KA0648G00 + ... + + Device TH: + ./out/all-clusters-app/chip-all-clusters-app + ... + DUT has not commissioned the TH to the Matter network disabled: true - label: - "If (PICS_21_MANUAL_PC), Passcode: Using the manual code from Step - 1.b, generate a new manual code using all the same Onboarding Payload - components except for the Passcode. For each Passcode in the following - list, set the Passcode component to one of the invalid Passcode and - generate a new manual code using all the same Onboarding Payload - components and one Passcode from the list: 00000000, 11111111, - 22222222, 33333333, 44444444, 55555555, 66666666, 77777777, 88888888, - 99999999, 12345678, 87654321" - verification: - "NEED SUPPORT: Unable to generate false manual codes with - chip-device-ctrl chip-device-ctrl > setup-payload generate -vr 0 -vi - 65521 -pi 32769 -cf 1 -dc 4 -dv 3840 -ps 00000000 2022-03-03 00:11:58 - matter-te-6 chip.SPL[22108] ERROR Failed encoding invalid payload Chip - Stack Error 47 00000000: 11111111: 22222222: 33333333: 44444444: - 55555555: 66666666: 77777777: 88888888: 99999999: 12345678: 87654321" + "If (PICS_DT_BLE), Using the QR code from Step 1, generate a new QR + code using all the same Onboarding Payload components except for the + Discovery Capability bit string, set it to BLE for discovery" + verification: | + ./chip-tool payload generate-qrcode --discriminator 3841 --setup-pin-code 20202021 --version 000 --vendor-id 65521 --product-id 0x8001 --commissioning-mode 2 --rendezvous 2 + [1649827755.759091][3173:3173] CHIP:TOO: QR Code: MT:-24J048N01KA0648G00 disabled: true - label: - "If (PICS_21_MANUAL_PC), Provide each of the manual pairing codes, - generated in the previous step, to the DUT in any format supported by - the DUT" - verification: - "NEED SUPPORT: Unable to generate manual code in previous step" + "If (PICS_DT_BLE), Scan/read the QR code, generated in the previous + step, using the DUT" + verification: | + DUT Commissioner: + '' ./examples/chip-tool/out/debug/chip-tool pairing qrcode 1234 MT:-24J048N01KA0648G00 + ... + + Device TH: + ./out/all-clusters-app/chip-all-clusters-app + ... + DUT has not commissioned the TH to the Matter network disabled: true - label: - "If (PICS_21_MANUAL_PC), VENDOR_ID: Using the manual code from Step - 1.b, generate a new manual code using all the same Onboarding Payload - components except for the VENDOR_ID. For each VENDOR_ID in the - following list, set the VENDOR_ID component to one of the invalid Test - VENDOR_IDs and generate a new manual code using all the same - Onboarding Payload components and one Test VENDOR_ID from the list: - 0xFFF1, 0xFFF2, 0xFFF3, 0xFFF4" - verification: - "16-MacBook-Pro:connectedhomeip liam$ sudo - ./examples/chip-tool/out/debug/chip-tool payload verhoeff-generate - 74970112336552132769 [1646274552600] [54458:29507435] CHIP: [SPL] - Generating Character for: 74970112336552132769 [1646274552601] - [54458:29507435] CHIP: [SPL] Generated Char: 4 0xFFF1: - 749701123365521327694 0xFFF2: 749701123365522327692 0xFFF3: - 749701123365523327697 0xFFF4: 749701123365524327693" + "If (PICS_DT_IP), Using the QR code from Step 1, generate a new QR + code using all the same Onboarding Payload components except for the + Discovery Capability bit string, set it to IP Network for discovery" + verification: | + ./chip-tool payload generate-qrcode --discriminator 3841 --setup-pin-code 20202021 --version 000 --vendor-id 65521 --product-id 0x8001 --commissioning-mode 3 --rendezvous 2 + [1649827827.266780][3178:3178] CHIP:TOO: QR Code: MT:-24J00OO01KA0648G00 disabled: true - label: - "If (PICS_21_MANUAL_PC), Provide each of the manual pairing codes, - generated in the previous step, to the DUT in any format supported by - the DUT" - verification: - "NOTE: chip-tool as a commissioner is meant to support these invalid - manual pairing codes but other commissioners SHALL NOT support them - without understanding the risks. chip-tool cannot be used as a - 'negative' case example for invalid Version ID manual codes. Run each - of the invalid manual codes in the previous step with the command - listed below 'DUT Commissioner' DUT Commissioner: sudo - ./examples/chip-tool/out/debug/chip-tool pairing manualcode 1234 - 749701123365521327694 ... Device TH: - ./out/all-clusters-app/chip-all-clusters-app ..." + "If (PICS_DT_IP), Scan/read the QR code, generated in the previous + step, using the DUT" + verification: | + DUT Commissioner: + '' ./examples/chip-tool/out/debug/chip-tool pairing qrcode 1234 MT:-24J00OO01KA0648G00 + ... + + Device TH: + ./out/all-clusters-app/chip-all-clusters-app + ... + DUT has not commissioned the TH to the Matter network disabled: true - label: - "If (PICS_21_MANUAL_PC), PRODUCT_ID: Using the manual code from Step - 1.b, generate a new manual code but substituting out the current - PRODUCT_ID with an invalid PRODUCT_ID of 0x0000(i.e. While following - section 2.5.3. Product Identifier)" - verification: - "16-MacBook-Pro:connectedhomeip liam$ sudo - ./examples/chip-tool/out/debug/chip-tool payload verhoeff-generate - 74970112336552100000 Password: [1646274432948] [54452:29506141] CHIP: - [SPL] Generating Character for: 74970112336552100000 [1646274432949] - [54452:29506141] CHIP: [SPL] Generated Char: 6 Manual Pairing code: - 749701123365521000006" + "Discovery Capability - Reserved: Using the QR code from Step 1, + generate a new QR code using all the same Onboarding Payload + components except for the Discovery Capability bit string, set it to + non-zeros" + verification: | + BLOCKED + + chip-all-clusters-app BUG: chip-all-clusters-app advertises over BLE when the discovery capability should not be advertising with capabilites set to '0' + + + chip-device-ctrl > setup-payload generate -vr 0 -vi 65521 -pi 32769 -cf 0 -dc 2 -dv 3840 -ps 20202021 + 2022-02-26 03:50:13 matter-te-6 chip.SPL[22108] INFO Manual pairing code: [34970112332] + 2022-02-26 03:50:13 matter-te-6 chip.SPL[22108] INFO SetupQRCode: [MT:-24J042C00KA0648G00] disabled: true - label: - "If (PICS_21_MANUAL_PC), Provide the manual pairing code, generated in - the previous step, to the DUT in any format supported by the DUT" - verification: - "BLOCKED chip-tool BUG: chip-tool is allowing the Product ID to be - '00000' when this should not be allowed. However, this check may not - be handled during the commissionning process. DUT Commissioner: sudo - ./examples/chip-tool/out/debug/chip-tool pairing manualcode 1234 - 749701123365521000006 ... [1646275242410] [54535:29515978] CHIP: [CTL] - Received CommissioningComplete response [1646275242410] - [54535:29515978] CHIP: [CTL] Rendezvous cleanup [1646275242410] - [54535:29515978] CHIP: [TOO] Device commissioning completed with - success Device TH: ./out/all-clusters-app/chip-all-clusters-app ... - [1646275242.549708][29139:29139] CHIP:SVR: Commissioning completed - successfully" + "Scan/read the QR code, generated in the previous step, using the DUT" + verification: | + BLOCKED + + chip-all-clusters-app BUG: chip-all-clusters-app advertises over BLE when the discovery capability should not be advertising with capabilites set to '0' + + DUT Commissioner: + sudo ./examples/chip-tool/out/debug/chip-tool pairing qrcode 1234 MT:-24J042C00KA0648G00 + ... + + Device TH: + ./out/all-clusters-app/chip-all-clusters-app + ... + DUT has not commissioned the TH to the Matter network disabled: true - label: - "If (PICS_11_MANUAL_PC), CHECK_DIGIT: Using the manual code from Step - 1.a, generate a new manual code but substituting out the current - CHECK_DIGIT with an invalid CHECK_DIGIT (i.e. Any different - CHECK_DIGIT than the commissionees CHECK_DIGIT while following Table - 38. Encoding Method without Vendor and Product IDs (VID_PID_Present == - 0))" - verification: - "16-MacBook-Pro:connectedhomeip liam$ sudo - ./examples/chip-tool/out/debug/chip-tool payload verhoeff-verify - 34970112331 10 [1646275789088] [54629:29523682] CHIP: [SPL] Verifying - Manual Code: 3497011233 [1646275789088] [54629:29523682] CHIP: [SPL] - 34970112331 is INVALID at position 10 Manual Pairing code: 3497011233" + "Passcode: Using the QR code from Step 1, generate a new QR code using + all the same Onboarding Payload components except for the Passcode. + For each passcode in the following list, set the Passcode component to + one of the invalid Passcodes and generate a new QR code using all the + same Onboarding Payload components and one Passcode from the list: + 00000000, 11111111, 22222222, 33333333, 44444444, 55555555, 66666666, + 77777777, 88888888, 99999999, 12345678, 87654321" + verification: | + BLOCKED + + chip-all-clusters-app BUG: chip-all-clusters-app advertises over IP when the discovery capability should not be advertising with capabilites set to '0' + + + chip-device-ctrl > setup-payload generate -vr 0 -vi 65521 -pi 32769 -cf 0 -dc 4 -dv 3840 -ps 20202021 + 2022-02-26 03:58:28 matter-te-6 chip.SPL[22108] INFO Manual pairing code: [34970112332] + 2022-02-26 03:58:28 matter-te-6 chip.SPL[22108] INFO SetupQRCode: [MT:-24J0AFN00KA0648G00] disabled: true - label: - "If (PICS_11_MANUAL_PC), Provide the manual pairing code, generated in - the previous step, to the DUT in any format supported by the DUT" - verification: - "DUT Commissioner: sudo ./examples/chip-tool/out/debug/chip-tool - pairing manualcode 1234 749701123365521327693 ... [1646275837642] - [54631:29524424] CHIP: [-] - ../../third_party/connectedhomeip/src/setup_payload/ManualSetupPayloadParser.cpp:49: - CHIP Error 0x00000013: Integrity check failed at - ../../commands/common/CHIPCommand.cpp:62 [1646275837642] - [54631:29524424] CHIP: [TOO] Run command failure: - ../../third_party/connectedhomeip/src/setup_payload/ManualSetupPayloadParser.cpp:49: - CHIP Error 0x00000013: Integrity check failed [1646275837649] - [54631:29524424] CHIP: [SPT] VerifyOrDie failure at - ../../third_party/connectedhomeip/src/lib/support/Pool.h:311: - Allocated() == 0 Abort trap: 6 Device TH: - ./out/all-clusters-app/chip-all-clusters-app ... DUT has not - commissioned the TH to the Matter network" + "Scan each of the generated QR codes from the previous step using DUT" + verification: | + BLOCKED + + chip-all-clusters-app BUG: chip-all-clusters-app advertises over IP when the discovery capability should not be advertising with capabilites set to '0' + + DUT Commissioner: + sudo ./examples/chip-tool/out/debug/chip-tool pairing qrcode 1234 MT:-24J0AFN00KA0648G00 + ... + + Device TH: + ./out/all-clusters-app/chip-all-clusters-app + ... + DUT has not commissioned the TH to the Matter network disabled: true - label: - "If (PICS_21_MANUAL_PC), Check Digit: Using the manual code from Step - 1.b, generate a new manual code but substituting out the current - CHECK_DIGIT with an invalid CHECK_DIGIT (i.e. Any different - CHECK_DIGIT than the commissionees CHECK_DIGIT while following Table - 39. Encoding Method with Vendor and Product IDs included - (VID_PID_Present == 1))" - verification: - "16-MacBook-Pro:connectedhomeip liam$ sudo - ./examples/chip-tool/out/debug/chip-tool payload verhoeff-verify - 749701123365521327693 20 [1646275504257] [54540:29518920] CHIP: [SPL] - Verifying Manual Code: 74970112336552132769 [1646275504258] - [54540:29518920] CHIP: [SPL] 749701123365521327693 is INVALID at - position 20 Manual Pairing code: 749701123365521327693" + "Prefix: Using the QR code from Step 1, generate a new QR code but + substituting out the current Prefix with an invalid Prefix that is not + 'MT:' (i.e. Prefix='AB:')" + verification: | + NEED SUPPORT + + Unable to generate fals QR codes with discovery capability set to an invalid number (i.e. 8 or above for chip-device-ctrl) + + chip-device-ctrl > setup-payload generate -vr 0 -vi 65521 -pi 32769 -cf 0 -dc 8 -dv 3840 -ps 20202021 + 2022-03-05 00:31:33 matter-te-6 chip.SPL[394173] INFO Manual pairing code: [34970112332] + Chip Stack Error 47 disabled: true - label: - "If (PICS_11_MANUAL_PC), Provide the manual pairing code, generated in - the previous step, to the DUT in any format supported by the DUT" - verification: - "DUT Commissioner: sudo ./examples/chip-tool/out/debug/chip-tool - pairing manualcode 1234 749701123365521327693 ... [1646275557755] - [54545:29519511] CHIP: [-] - ../../third_party/connectedhomeip/src/setup_payload/ManualSetupPayloadParser.cpp:49: - CHIP Error 0x00000013: Integrity check failed at - ../../commands/common/CHIPCommand.cpp:62 [1646275557755] - [54545:29519511] CHIP: [TOO] Run command failure: - ../../third_party/connectedhomeip/src/setup_payload/ManualSetupPayloadParser.cpp:49: - CHIP Error 0x00000013: Integrity check failed [1646275557761] - [54545:29519511] CHIP: [SPT] VerifyOrDie failure at - ../../third_party/connectedhomeip/src/lib/support/Pool.h:311: - Allocated() == 0 Abort trap: 6 Device TH: - ./out/all-clusters-app/chip-all-clusters-app ... DUT has not - commissioned the TH to the Matter network" + "Scan/read the QR code, generated in the previous step, using the DUT" + verification: | + NEED SUPPORT + + Unable to generate false QR codes with discovery capability set to an invalid number (i.e. 8 or above for chip-device-ctrl) + + Device TH: + ./out/all-clusters-app/chip-all-clusters-app + ... + DUT has not commissioned the TH to the Matter network disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_7.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_7.yaml index b2756d991b643d..6c4afdcb7f70f7 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_7.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_7.yaml @@ -14,7 +14,7 @@ # Auto-generated scripts for harness use only, please review before automation. The endpoints and cluster names are currently set to default name: - 3.3.7. [TC-DD-3.7] Commissioning Flow - Concurrent - Negative scenario [DUT + 3.3.7. [TC-DD-3.7] Commissioning Flow - Concurrent - Negative Scenario [DUT - Commissioner] config: @@ -24,15 +24,721 @@ config: tests: - label: - "Repeat steps 1.a-1.o from [TC-DD-3.5]. Force Fail any step between - 1.a and 1.j." + "Commissioner has regulatory and fabric information available and has + accurate date, time and timezone" verification: | + On DUT: sudo ./chip-all-clusters-app + + On Controller: ./chip-tool discover commissionables + + 1. Connect the device to Ethernet + 2. Disover the device using CHIP Tool . ./chip-tool discover commissionables + 3. connect -ip , + 4. Once device is provisioned, read 'Product Name' attribute from the Basic cluster. Example:./chip-tool basic read product-name 1 0 + + Reference : below Full log for the above commands (click on this cell if you like to see complete log) + + + controller > ./chip-tool discover commissionables + Waiting for device responses... + CHIP:CTL: Generating ICAC + CHIP:DL: AUDIT: ===== RANDOM NUMBER GENERATOR AUDIT START ==== + CHIP:DL: AUDIT: * Validate buf1 and buf2 are <<>> + CHIP:DL: AUDIT: * Validate r1 and r2 are <<>> + CHIP:DL: AUDIT: * buf1: 3BE3E264C0A0A053248E93609D22044A + CHIP:DL: AUDIT: * buf2: E69C8767AD6B60907AD3633E774F38EB + CHIP:DL: AUDIT: * r1: 0x2A0E6454 r2: 0x16315893 + CHIP:DL: AUDIT: ===== RANDOM NUMBER GENERATOR AUDIT END ==== + CHIP:DL: writing settings to file (/tmp/chip_counters.ini-9yXPat) + CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini) + CHIP:DL: NVS set: chip-counters/reboot-count = 23 (0x17) + CHIP:DL: Got Ethernet interface: eth0 + CHIP:DL: Found the primary Ethernet interface:eth0 + CHIP:DL: Got WiFi interface: wlan0 + CHIP:DL: Failed to reset WiFi statistic counts + CHIP:IN: UDP::Init bind&listen port=5541 + CHIP:IN: UDP::Init bound to port=5541 + CHIP:IN: UDP::Init bind&listen port=5541 + CHIP:IN: UDP::Init bound to port=5541 + CHIP:IN: TransportMgr initialized + CHIP:DIS: Init fabric pairing table with server storage + CHIP:DL: writing settings to file (/tmp/chip_counters.ini-zgCtZd) + CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini) + CHIP:DL: NVS set: chip-counters/GlobalMCTR = 25000 (0x61A8) + CHIP:CTL: System State Initialized... + CHIP:DL: MDNS failed to join multicast group on veth5731933 for address type IPv4: ../th + CHIP:DL: MDNS failed to join multicast group on vethbf7bfa6 for address type IPv4: ../th + CHIP:DL: MDNS failed to join multicast group on vethcf434e5 for address type IPv4: ../th + CHIP:ZCL: Using ZAP configuration... + CHIP:DIS: Verifying the received credentials + CHIP:IN: Generating compressed fabric ID using uncompressed fabric ID 0x0000000000000000 + CHIP:IN: 0x04, 0x66, 0xd6, 0xcf, 0x4c, 0x1e, 0x11, 0xc3, + CHIP:IN: 0x52, 0x4f, 0xa6, 0x8c, 0x6e, 0x65, 0x46, 0xdc, + CHIP:IN: 0x90, 0x1b, 0x5f, 0x42, 0x9f, 0x69, 0xd1, 0xb7, + CHIP:IN: 0x7d, 0xf3, 0x6b, 0x54, 0x12, 0x6c, 0x12, 0x59, + CHIP:IN: 0x5b, 0xc3, 0x07, 0x1c, 0x5c, 0xf4, 0x4e, 0x5f, + CHIP:IN: 0x71, 0x06, 0x9a, 0xbb, 0x2f, 0xef, 0x20, 0x0d, + CHIP:IN: 0x0e, 0x9b, 0x26, 0x3e, 0x8d, 0x46, 0x09, 0xd8, + CHIP:IN: 0xfd, 0xa1, 0xc0, 0x10, 0x4f, 0x05, 0x14, 0x99, + CHIP:IN: 0x22, + CHIP:IN: Generated compressed fabric ID + CHIP:IN: 0x4a, 0x53, 0x1e, 0x52, 0x06, 0xed, 0x06, 0xda, + CHIP:DIS: Added new fabric at index: 1, Initialized: 1 + CHIP:DIS: Assigned compressed fabric ID: 0x4A531E5206ED06DA, node ID: 0x000000000001B669 + CHIP:CTL: Joined the fabric at index 1. Compressed fabric ID is: 0x4A531E5206ED06DA + CHIP:DL: CHIP task running + CHIP:DIS: Attempt to mDNS broadcast failed: ../third_party/connectedhomeip/src/inet/UDP + CHIP:DIS: Attempt to mDNS broadcast failed: ../third_party/connectedhomeip/src/inet/UDP + CHIP:DIS: Attempt to mDNS broadcast failed: ../third_party/connectedhomeip/src/inet/UDP + CHIP:DIS: Attempt to mDNS broadcast failed: ../third_party/connectedhomeip/src/inet/UDP + CHIP:DIS: Discovered Node: + CHIP:DIS: Host name: EEAABADABAD0DDCA + CHIP:DIS: Port: 5540 + CHIP:DIS: Long discriminator: 3840 + CHIP:DIS: Vendor ID: 9050 + CHIP:DIS: Product ID: 65279 + CHIP:DIS: Commissioning Mode 1 + CHIP:DIS: Device Type 0 + CHIP:DIS: Device Name + CHIP:DIS: Rotating Id 00007C5F6E176CD40F68685D100A1CF8A98B + CHIP:DIS: Pairing Instruction + CHIP:DIS: Pairing Hint 0x21 + CHIP:DIS: Address 0: 2402:e280:2108:181:dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 1: fe80::dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 2: 192.168.1.12 + CHIP:DIS: Discovered Node: + CHIP:DIS: Host name: EEAABADABAD0DDCA + CHIP:DIS: Port: 5540 + CHIP:DIS: Long discriminator: 3840 + CHIP:DIS: Vendor ID: 9050 + CHIP:DIS: Product ID: 65279 + CHIP:DIS: Commissioning Mode 1 + CHIP:DIS: Device Type 0 + CHIP:DIS: Device Name + CHIP:DIS: Rotating Id 00007C5F6E176CD40F68685D100A1CF8A98B + CHIP:DIS: Pairing Instruction + CHIP:DIS: Pairing Hint 0x21 + CHIP:DIS: Address 0: 2402:e280:2108:181:dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 1: fe80::dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 2: 192.168.1.12 + CHIP:DIS: Discovered Node: + CHIP:DIS: Host name: EEAABADABAD0DDCA + CHIP:DIS: Port: 5540 + CHIP:DIS: Long discriminator: 3840 + CHIP:DIS: Vendor ID: 9050 + CHIP:DIS: Product ID: 65279 + CHIP:DIS: Commissioning Mode 1 + CHIP:DIS: Device Type 0 + CHIP:DIS: Device Name + CHIP:DIS: Rotating Id 00007C5F6E176CD40F68685D100A1CF8A98B + CHIP:DIS: Pairing Instruction + CHIP:DIS: Pairing Hint 0x21 + CHIP:DIS: Address 0: 2402:e280:2108:181:dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 1: fe80::dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 2: 192.168.1.12 + CHIP:DIS: Discovered Node: + CHIP:DIS: Host name: EEAABADABAD0DDCA + CHIP:DIS: Port: 5540 + CHIP:DIS: Long discriminator: 3840 + CHIP:DIS: Vendor ID: 9050 + CHIP:DIS: Product ID: 65279 + CHIP:DIS: Commissioning Mode 1 + CHIP:DIS: Device Type 0 + CHIP:DIS: Device Name + CHIP:DIS: Rotating Id 00007C5F6E176CD40F68685D100A1CF8A98B + CHIP:DIS: Pairing Instruction + CHIP:DIS: Pairing Hint 0x21 + CHIP:DIS: Address 0: 2402:e280:2108:181:dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 1: fe80::dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 2: 192.168.1.12 + CHIP:DIS: Discovered Node: + CHIP:DIS: Host name: EEAABADABAD0DDCA + CHIP:DIS: Port: 5540 + CHIP:DIS: Long discriminator: 3840 + CHIP:DIS: Vendor ID: 9050 + CHIP:DIS: Product ID: 65279 + CHIP:DIS: Commissioning Mode 1 + CHIP:DIS: Device Type 0 + CHIP:DIS: Device Name + CHIP:DIS: Rotating Id 00007C5F6E176CD40F68685D100A1CF8A98B + CHIP:DIS: Pairing Instruction + CHIP:DIS: Pairing Hint 0x21 + CHIP:DIS: Address 0: 2402:e280:2108:181:dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 1: fe80::dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 2: 192.168.1.12 + CHIP:DIS: Discovered Node: + CHIP:DIS: Host name: EEAABADABAD0DDCA + CHIP:DIS: Port: 5540 + CHIP:DIS: Long discriminator: 3840 + CHIP:DIS: Vendor ID: 9050 + CHIP:DIS: Product ID: 65279 + CHIP:DIS: Commissioning Mode 1 + CHIP:DIS: Device Type 0 + CHIP:DIS: Device Name + CHIP:DIS: Rotating Id 00007C5F6E176CD40F68685D100A1CF8A98B + CHIP:DIS: Pairing Instruction + CHIP:DIS: Pairing Hint 0x21 + CHIP:DIS: Address 0: 2402:e280:2108:181:dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 1: fe80::dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 2: 192.168.1.12 + + + controller> sudo ./chip-tool pairing ethernet 112233 20202021 3840 192.168.1.12 5540 + + Output of this command in cell number I6 and J6 due to cell constraint of maximum size. + + + + controller> sudo ./chip-tool basic read product-name 0x000000000001B669 0 + + ,, + disabled: true + + - label: + "Commissioner and Commissionee discover each other and connect via the + discovery mode applicable for the DUT." + verification: | + Verify on DUT: + + ./chip-tool discover commissionables + Waiting for device responses... + CHIP:CTL: Generating ICAC + CHIP:DL: AUDIT: ===== RANDOM NUMBER GENERATOR AUDIT START ==== + CHIP:DL: AUDIT: * Validate buf1 and buf2 are <<>> + CHIP:DL: AUDIT: * Validate r1 and r2 are <<>> + CHIP:DL: AUDIT: * buf1: 3BE3E264C0A0A053248E93609D22044A + CHIP:DL: AUDIT: * buf2: E69C8767AD6B60907AD3633E774F38EB + CHIP:DL: AUDIT: * r1: 0x2A0E6454 r2: 0x16315893 + CHIP:DL: AUDIT: ===== RANDOM NUMBER GENERATOR AUDIT END ==== + CHIP:DL: writing settings to file (/tmp/chip_counters.ini-9yXPat) + CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini) + CHIP:DL: NVS set: chip-counters/reboot-count = 23 (0x17) + CHIP:DL: Got Ethernet interface: eth0 + CHIP:DL: Found the primary Ethernet interface:eth0 + CHIP:DL: Got WiFi interface: wlan0 + CHIP:DL: Failed to reset WiFi statistic counts + CHIP:IN: UDP::Init bind&listen port=5541 + CHIP:IN: UDP::Init bound to port=5541 + CHIP:IN: UDP::Init bind&listen port=5541 + CHIP:IN: UDP::Init bound to port=5541 + CHIP:IN: TransportMgr initialized + CHIP:DIS: Init fabric pairing table with server storage + CHIP:DL: writing settings to file (/tmp/chip_counters.ini-zgCtZd) + CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini) + CHIP:DL: NVS set: chip-counters/GlobalMCTR = 25000 (0x61A8) + CHIP:CTL: System State Initialized... + CHIP:DL: MDNS failed to join multicast group on veth5731933 for address type IPv4: ../th + CHIP:DL: MDNS failed to join multicast group on vethbf7bfa6 for address type IPv4: ../th + CHIP:DL: MDNS failed to join multicast group on vethcf434e5 for address type IPv4: ../th + CHIP:ZCL: Using ZAP configuration... + CHIP:DIS: Verifying the received credentials + CHIP:IN: Generating compressed fabric ID using uncompressed fabric ID 0x0000000000000000 + CHIP:IN: 0x04, 0x66, 0xd6, 0xcf, 0x4c, 0x1e, 0x11, 0xc3, + CHIP:IN: 0x52, 0x4f, 0xa6, 0x8c, 0x6e, 0x65, 0x46, 0xdc, + CHIP:IN: 0x90, 0x1b, 0x5f, 0x42, 0x9f, 0x69, 0xd1, 0xb7, + CHIP:IN: 0x7d, 0xf3, 0x6b, 0x54, 0x12, 0x6c, 0x12, 0x59, + CHIP:IN: 0x5b, 0xc3, 0x07, 0x1c, 0x5c, 0xf4, 0x4e, 0x5f, + CHIP:IN: 0x71, 0x06, 0x9a, 0xbb, 0x2f, 0xef, 0x20, 0x0d, + CHIP:IN: 0x0e, 0x9b, 0x26, 0x3e, 0x8d, 0x46, 0x09, 0xd8, + CHIP:IN: 0xfd, 0xa1, 0xc0, 0x10, 0x4f, 0x05, 0x14, 0x99, + CHIP:IN: 0x22, + CHIP:IN: Generated compressed fabric ID + CHIP:IN: 0x4a, 0x53, 0x1e, 0x52, 0x06, 0xed, 0x06, 0xda, + CHIP:DIS: Added new fabric at index: 1, Initialized: 1 + CHIP:DIS: Assigned compressed fabric ID: 0x4A531E5206ED06DA, node ID: 0x000000000001B669 + CHIP:CTL: Joined the fabric at index 1. Compressed fabric ID is: 0x4A531E5206ED06DA + CHIP:DL: CHIP task running + CHIP:DIS: Attempt to mDNS broadcast failed: ../third_party/connectedhomeip/src/inet/UDP + CHIP:DIS: Attempt to mDNS broadcast failed: ../third_party/connectedhomeip/src/inet/UDP + CHIP:DIS: Attempt to mDNS broadcast failed: ../third_party/connectedhomeip/src/inet/UDP + CHIP:DIS: Attempt to mDNS broadcast failed: ../third_party/connectedhomeip/src/inet/UDP + CHIP:DIS: Discovered Node: + CHIP:DIS: Host name: EEAABADABAD0DDCA + CHIP:DIS: Port: 5540 + CHIP:DIS: Long discriminator: 3840 + CHIP:DIS: Vendor ID: 9050 + CHIP:DIS: Product ID: 65279 + CHIP:DIS: Commissioning Mode 1 + CHIP:DIS: Device Type 0 + CHIP:DIS: Device Name + CHIP:DIS: Rotating Id 00007C5F6E176CD40F68685D100A1CF8A98B + CHIP:DIS: Pairing Instruction + CHIP:DIS: Pairing Hint 0x21 + CHIP:DIS: Address 0: 2402:e280:2108:181:dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 1: fe80::dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 2: 192.168.1.12 + CHIP:DIS: Discovered Node: + CHIP:DIS: Host name: EEAABADABAD0DDCA + CHIP:DIS: Port: 5540 + CHIP:DIS: Long discriminator: 3840 + CHIP:DIS: Vendor ID: 9050 + CHIP:DIS: Product ID: 65279 + CHIP:DIS: Commissioning Mode 1 + CHIP:DIS: Device Type 0 + CHIP:DIS: Device Name + CHIP:DIS: Rotating Id 00007C5F6E176CD40F68685D100A1CF8A98B + CHIP:DIS: Pairing Instruction + CHIP:DIS: Pairing Hint 0x21 + CHIP:DIS: Address 0: 2402:e280:2108:181:dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 1: fe80::dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 2: 192.168.1.12 + CHIP:DIS: Discovered Node: + CHIP:DIS: Host name: EEAABADABAD0DDCA + CHIP:DIS: Port: 5540 + CHIP:DIS: Long discriminator: 3840 + CHIP:DIS: Vendor ID: 9050 + CHIP:DIS: Product ID: 65279 + CHIP:DIS: Commissioning Mode 1 + CHIP:DIS: Device Type 0 + CHIP:DIS: Device Name + CHIP:DIS: Rotating Id 00007C5F6E176CD40F68685D100A1CF8A98B + CHIP:DIS: Pairing Instruction + CHIP:DIS: Pairing Hint 0x21 + CHIP:DIS: Address 0: 2402:e280:2108:181:dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 1: fe80::dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 2: 192.168.1.12 + CHIP:DIS: Discovered Node: + CHIP:DIS: Host name: EEAABADABAD0DDCA + CHIP:DIS: Port: 5540 + CHIP:DIS: Long discriminator: 3840 + CHIP:DIS: Vendor ID: 9050 + CHIP:DIS: Product ID: 65279 + CHIP:DIS: Commissioning Mode 1 + CHIP:DIS: Device Type 0 + CHIP:DIS: Device Name + CHIP:DIS: Rotating Id 00007C5F6E176CD40F68685D100A1CF8A98B + CHIP:DIS: Pairing Instruction + CHIP:DIS: Pairing Hint 0x21 + CHIP:DIS: Address 0: 2402:e280:2108:181:dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 1: fe80::dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 2: 192.168.1.12 + CHIP:DIS: Discovered Node: + CHIP:DIS: Host name: EEAABADABAD0DDCA + CHIP:DIS: Port: 5540 + CHIP:DIS: Long discriminator: 3840 + CHIP:DIS: Vendor ID: 9050 + CHIP:DIS: Product ID: 65279 + CHIP:DIS: Commissioning Mode 1 + CHIP:DIS: Device Type 0 + CHIP:DIS: Device Name + CHIP:DIS: Rotating Id 00007C5F6E176CD40F68685D100A1CF8A98B + CHIP:DIS: Pairing Instruction + CHIP:DIS: Pairing Hint 0x21 + CHIP:DIS: Address 0: 2402:e280:2108:181:dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 1: fe80::dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 2: 192.168.1.12 + CHIP:DIS: Discovered Node: + CHIP:DIS: Host name: EEAABADABAD0DDCA + CHIP:DIS: Port: 5540 + CHIP:DIS: Long discriminator: 3840 + CHIP:DIS: Vendor ID: 9050 + CHIP:DIS: Product ID: 65279 + CHIP:DIS: Commissioning Mode 1 + CHIP:DIS: Device Type 0 + CHIP:DIS: Device Name + CHIP:DIS: Rotating Id 00007C5F6E176CD40F68685D100A1CF8A98B + CHIP:DIS: Pairing Instruction + CHIP:DIS: Pairing Hint 0x21 + CHIP:DIS: Address 0: 2402:e280:2108:181:dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 1: fe80::dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 2: 192.168.1.12 + disabled: true + + - label: + "Establish encryption keys with Password Authenticated Session + Establishment on the commissioning channel" + verification: | + Verify on DUT: + + CHIP:SC: Sent PBKDF param request + CHIP:CTL: Setting attestation nonce to random value + CHIP:CTL: Setting CSR nonce to random value + CHIP:CTL: Commission called for node ID 0x000000000001B669 + CHIP:EM: Received message of type 0x21 with protocolId (0, 0) and MessageCounter:1341084110 on exchange 63762i + CHIP:EM: Found matching exchange: 63762i, Delegate: 0xffff8c000bc0 + CHIP:EM: Rxd Ack; Removing MessageCounter:850320430 from Retrans Table on exchange 63762i + CHIP:EM: Removed CHIP MessageCounter:850320430 from RetransTable on exchange 63762i + CHIP:SC: Received PBKDF param response + disabled: true + + - label: + "Commissioner SHALL re-arm Fail-safe timer on Commissionee within 60s + (the autonomously Fail-safe timer length set by Commissionee)" + verification: | + Verify on DUT: + + CHIP:CTL: Commissioning stage next step: 'ReadCommissioningInfo' -> 'ArmFailSafe' + CHIP:CTL: Performing next commissioning step 'ArmFailSafe' + CHIP:CTL: Arming failsafe (60 seconds) + disabled: true + + - label: "Reboot TH and prepare for commissioning" + verification: | + 1. Using TH=all-clusters-app, exit the app, re-launch app + disabled: true + + - label: "Commissioner should return to step 2" + verification: | + Verify on DUT: + + ./chip-tool discover commissionables + Waiting for device responses... + CHIP:CTL: Generating ICAC + CHIP:DL: AUDIT: ===== RANDOM NUMBER GENERATOR AUDIT START ==== + CHIP:DL: AUDIT: * Validate buf1 and buf2 are <<>> + CHIP:DL: AUDIT: * Validate r1 and r2 are <<>> + CHIP:DL: AUDIT: * buf1: 3BE3E264C0A0A053248E93609D22044A + CHIP:DL: AUDIT: * buf2: E69C8767AD6B60907AD3633E774F38EB + CHIP:DL: AUDIT: * r1: 0x2A0E6454 r2: 0x16315893 + CHIP:DL: AUDIT: ===== RANDOM NUMBER GENERATOR AUDIT END ==== + CHIP:DL: writing settings to file (/tmp/chip_counters.ini-9yXPat) + CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini) + CHIP:DL: NVS set: chip-counters/reboot-count = 23 (0x17) + CHIP:DL: Got Ethernet interface: eth0 + CHIP:DL: Found the primary Ethernet interface:eth0 + CHIP:DL: Got WiFi interface: wlan0 + CHIP:DL: Failed to reset WiFi statistic counts + CHIP:IN: UDP::Init bind&listen port=5541 + CHIP:IN: UDP::Init bound to port=5541 + CHIP:IN: UDP::Init bind&listen port=5541 + CHIP:IN: UDP::Init bound to port=5541 + CHIP:IN: TransportMgr initialized + CHIP:DIS: Init fabric pairing table with server storage + CHIP:DL: writing settings to file (/tmp/chip_counters.ini-zgCtZd) + CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini) + CHIP:DL: NVS set: chip-counters/GlobalMCTR = 25000 (0x61A8) + CHIP:CTL: System State Initialized... + CHIP:DL: MDNS failed to join multicast group on veth5731933 for address type IPv4: ../th + CHIP:DL: MDNS failed to join multicast group on vethbf7bfa6 for address type IPv4: ../th + CHIP:DL: MDNS failed to join multicast group on vethcf434e5 for address type IPv4: ../th + CHIP:ZCL: Using ZAP configuration... + CHIP:DIS: Verifying the received credentials + CHIP:IN: Generating compressed fabric ID using uncompressed fabric ID 0x0000000000000000 + CHIP:IN: 0x04, 0x66, 0xd6, 0xcf, 0x4c, 0x1e, 0x11, 0xc3, + CHIP:IN: 0x52, 0x4f, 0xa6, 0x8c, 0x6e, 0x65, 0x46, 0xdc, + CHIP:IN: 0x90, 0x1b, 0x5f, 0x42, 0x9f, 0x69, 0xd1, 0xb7, + CHIP:IN: 0x7d, 0xf3, 0x6b, 0x54, 0x12, 0x6c, 0x12, 0x59, + CHIP:IN: 0x5b, 0xc3, 0x07, 0x1c, 0x5c, 0xf4, 0x4e, 0x5f, + CHIP:IN: 0x71, 0x06, 0x9a, 0xbb, 0x2f, 0xef, 0x20, 0x0d, + CHIP:IN: 0x0e, 0x9b, 0x26, 0x3e, 0x8d, 0x46, 0x09, 0xd8, + CHIP:IN: 0xfd, 0xa1, 0xc0, 0x10, 0x4f, 0x05, 0x14, 0x99, + CHIP:IN: 0x22, + CHIP:IN: Generated compressed fabric ID + CHIP:IN: 0x4a, 0x53, 0x1e, 0x52, 0x06, 0xed, 0x06, 0xda, + CHIP:DIS: Added new fabric at index: 1, Initialized: 1 + CHIP:DIS: Assigned compressed fabric ID: 0x4A531E5206ED06DA, node ID: 0x000000000001B669 + CHIP:CTL: Joined the fabric at index 1. Compressed fabric ID is: 0x4A531E5206ED06DA + CHIP:DL: CHIP task running + CHIP:DIS: Attempt to mDNS broadcast failed: ../third_party/connectedhomeip/src/inet/UDP + CHIP:DIS: Attempt to mDNS broadcast failed: ../third_party/connectedhomeip/src/inet/UDP + CHIP:DIS: Attempt to mDNS broadcast failed: ../third_party/connectedhomeip/src/inet/UDP + CHIP:DIS: Attempt to mDNS broadcast failed: ../third_party/connectedhomeip/src/inet/UDP + CHIP:DIS: Discovered Node: + CHIP:DIS: Host name: EEAABADABAD0DDCA + CHIP:DIS: Port: 5540 + CHIP:DIS: Long discriminator: 3840 + CHIP:DIS: Vendor ID: 9050 + CHIP:DIS: Product ID: 65279 + CHIP:DIS: Commissioning Mode 1 + CHIP:DIS: Device Type 0 + CHIP:DIS: Device Name + CHIP:DIS: Rotating Id 00007C5F6E176CD40F68685D100A1CF8A98B + CHIP:DIS: Pairing Instruction + CHIP:DIS: Pairing Hint 0x21 + CHIP:DIS: Address 0: 2402:e280:2108:181:dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 1: fe80::dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 2: 192.168.1.12 + CHIP:DIS: Discovered Node: + CHIP:DIS: Host name: EEAABADABAD0DDCA + CHIP:DIS: Port: 5540 + CHIP:DIS: Long discriminator: 3840 + CHIP:DIS: Vendor ID: 9050 + CHIP:DIS: Product ID: 65279 + CHIP:DIS: Commissioning Mode 1 + CHIP:DIS: Device Type 0 + CHIP:DIS: Device Name + CHIP:DIS: Rotating Id 00007C5F6E176CD40F68685D100A1CF8A98B + CHIP:DIS: Pairing Instruction + CHIP:DIS: Pairing Hint 0x21 + CHIP:DIS: Address 0: 2402:e280:2108:181:dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 1: fe80::dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 2: 192.168.1.12 + CHIP:DIS: Discovered Node: + CHIP:DIS: Host name: EEAABADABAD0DDCA + CHIP:DIS: Port: 5540 + CHIP:DIS: Long discriminator: 3840 + CHIP:DIS: Vendor ID: 9050 + CHIP:DIS: Product ID: 65279 + CHIP:DIS: Commissioning Mode 1 + CHIP:DIS: Device Type 0 + CHIP:DIS: Device Name + CHIP:DIS: Rotating Id 00007C5F6E176CD40F68685D100A1CF8A98B + CHIP:DIS: Pairing Instruction + CHIP:DIS: Pairing Hint 0x21 + CHIP:DIS: Address 0: 2402:e280:2108:181:dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 1: fe80::dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 2: 192.168.1.12 + CHIP:DIS: Discovered Node: + CHIP:DIS: Host name: EEAABADABAD0DDCA + CHIP:DIS: Port: 5540 + CHIP:DIS: Long discriminator: 3840 + CHIP:DIS: Vendor ID: 9050 + CHIP:DIS: Product ID: 65279 + CHIP:DIS: Commissioning Mode 1 + CHIP:DIS: Device Type 0 + CHIP:DIS: Device Name + CHIP:DIS: Rotating Id 00007C5F6E176CD40F68685D100A1CF8A98B + CHIP:DIS: Pairing Instruction + CHIP:DIS: Pairing Hint 0x21 + CHIP:DIS: Address 0: 2402:e280:2108:181:dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 1: fe80::dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 2: 192.168.1.12 + CHIP:DIS: Discovered Node: + CHIP:DIS: Host name: EEAABADABAD0DDCA + CHIP:DIS: Port: 5540 + CHIP:DIS: Long discriminator: 3840 + CHIP:DIS: Vendor ID: 9050 + CHIP:DIS: Product ID: 65279 + CHIP:DIS: Commissioning Mode 1 + CHIP:DIS: Device Type 0 + CHIP:DIS: Device Name + CHIP:DIS: Rotating Id 00007C5F6E176CD40F68685D100A1CF8A98B + CHIP:DIS: Pairing Instruction + CHIP:DIS: Pairing Hint 0x21 + CHIP:DIS: Address 0: 2402:e280:2108:181:dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 1: fe80::dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 2: 192.168.1.12 + CHIP:DIS: Discovered Node: + CHIP:DIS: Host name: EEAABADABAD0DDCA + CHIP:DIS: Port: 5540 + CHIP:DIS: Long discriminator: 3840 + CHIP:DIS: Vendor ID: 9050 + CHIP:DIS: Product ID: 65279 + CHIP:DIS: Commissioning Mode 1 + CHIP:DIS: Device Type 0 + CHIP:DIS: Device Name + CHIP:DIS: Rotating Id 00007C5F6E176CD40F68685D100A1CF8A98B + CHIP:DIS: Pairing Instruction + CHIP:DIS: Pairing Hint 0x21 + CHIP:DIS: Address 0: 2402:e280:2108:181:dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 1: fe80::dea6:32ff:fef9:f0a1 + CHIP:DIS: Address 2: 192.168.1.12 + disabled: true + + - label: + "Establish encryption keys with Password Authenticated Session + Establishment on the commissioning channel" + verification: | + Verify on DUT: + + CHIP:SC: Sent PBKDF param request + CHIP:CTL: Setting attestation nonce to random value + CHIP:CTL: Setting CSR nonce to random value + CHIP:CTL: Commission called for node ID 0x000000000001B669 + CHIP:EM: Received message of type 0x21 with protocolId (0, 0) and MessageCounter:1341084110 on exchange 63762i + CHIP:EM: Found matching exchange: 63762i, Delegate: 0xffff8c000bc0 + CHIP:EM: Rxd Ack; Removing MessageCounter:850320430 from Retrans Table on exchange 63762i + CHIP:EM: Removed CHIP MessageCounter:850320430 from RetransTable on exchange 63762i + CHIP:SC: Received PBKDF param response + disabled: true + + - label: + "Commissioner SHALL re-arm Fail-safe timer on Commissionee within 60s + (the autonomously Fail-safe timer length set by Commissionee)" + verification: | + Verify on DUT: + + CHIP:CTL: Commissioning stage next step: 'ReadCommissioningInfo' -> 'ArmFailSafe' + CHIP:CTL: Performing next commissioning step 'ArmFailSafe' + CHIP:CTL: Arming failsafe (60 seconds) + disabled: true + + - label: + "If (PICS_WIFI) or (PICS_THREAD), Commissioner SHALL configure + regulatory information in the Commissionee." + verification: | + Need chip-tool implementation + disabled: true + + - label: + "Commissioner requests operational CSR from Commissionee with + OperationalCSRRequest command" + verification: | + Verify on TH: + + CHIP:ZCL: OpCreds: commissioner has requested a CSR + CHIP:ZCL: OpCreds: NewCertificateSigningRequest returned ../../third_party/connectedhomeip/src/crypto/CHIPCryptoPALOpenSSL.cpp:1114: Success + disabled: true + + - label: + "Commissioner configures operational credentials on DUT if not + previously installed" + verification: | + Verify on DUT: + + CHIP:CTL: Performing next commissioning step 'SendTrustedRootCert' + CHIP:CTL: Sending root certificate to the device + CHIP:DMG: ICR moving to [AddingComm] + CHIP:DMG: ICR moving to [AddedComma] + CHIP:IN: Prepared secure message 0xaaaafc0d5be8 to 0x000000000001B669 (1) of type 0x8 and protocolId (0, 1) on exchange 63770i with MessageCounter:695615. + CHIP:IN: Sending encrypted msg 0xaaaafc0d5be8 with MessageCounter:695615 to 0x000000000001B669 (1) at monotonic time: 0000000000FBA3DE msec + CHIP:DMG: ICR moving to [CommandSen] + CHIP:CTL: Sent root certificate to the device + disabled: true + + - label: + "Commissioner configures itself as administrator in ACL on TH if + needed" + verification: | + Verify the following on DUT after commissioning + [1646909537.115328][3145:3150] CHIP:CTL: Sending CSR request to 0xffffac001730 device + [1646909537.115512][3145:3150] CHIP:DMG: ICR moving to [AddingComm] + [1646909537.115589][3145:3150] CHIP:DMG: ICR moving to [AddedComma] + [1646909537.115861][3145:3150] CHIP:IN: Prepared secure message 0xffffb67cbd98 to 0x0000000000000001 (1) of type 0x8 and protocolId (0, 1) on exchange 7731i with MessageCounter:8191681. + [1646909537.115959][3145:3150] CHIP:IN: Sending encrypted msg 0xffffb67cbd98 with MessageCounter:8191681 to 0x0000000000000001 (1) at monotonic time: 10877964 msec + [1646909537.116173][3145:3150] CHIP:DMG: ICR moving to [CommandSen] + [1646909537.116242][3145:3150] CHIP:CTL: Sent CSR request, waiting for the CSR + [1646909537.116356][3145:3150] CHIP:DMG: ICR moving to [AwaitingDe] + [1646909537.193355][3145:3150] CHIP:DL: HandlePlatformSpecificBLEEvent 16387 + [1646909537.241579][3145:3148] CHIP:DL: Indication received, conn = 0xffffa803b310 + [1646909537.241838][3145:3150] CHIP:DL: HandlePlatformSpecificBLEEvent 16389 + [1646909537.341266][3145:3148] CHIP:DL: Indication received, conn = 0xffffa803b310 + [1646909537.341523][3145:3150] CHIP:DL: HandlePlatformSpecificBLEEvent 16389 + [1646909537.341903][3145:3150] CHIP:EM: Received message of type 0x9 with protocolId (0, 1) and MessageCounter:2304337 on exchange 7731i + [1646909537.341988][3145:3150] CHIP:EM: Found matching exchange: 7731i, Delegate: 0xffffa8026ab0 + [1646909537.342086][3145:3150] CHIP:DMG: ICR moving to [ResponseRe] + [1646909537.342191][3145:3150] CHIP:DMG: InvokeResponseMessage = + [1646909537.342251][3145:3150] CHIP:DMG: { + [1646909537.342310][3145:3150] CHIP:DMG: suppressResponse = false, + [1646909537.342370][3145:3150] CHIP:DMG: InvokeResponseIBs = + [1646909537.342450][3145:3150] CHIP:DMG: [ + [1646909537.342511][3145:3150] CHIP:DMG: InvokeResponseIB = + [1646909537.342598][3145:3150] CHIP:DMG: { + [1646909537.342662][3145:3150] CHIP:DMG: CommandDataIB = + [1646909537.342749][3145:3150] CHIP:DMG: { + [1646909537.342832][3145:3150] CHIP:DMG: CommandPathIB = + [1646909537.342915][3145:3150] CHIP:DMG: { + [1646909537.342998][3145:3150] CHIP:DMG: EndpointId = 0x0, + [1646909537.343091][3145:3150] CHIP:DMG: ClusterId = 0x3e, + [1646909537.343177][3145:3150] CHIP:DMG: CommandId = 0x5, + [1646909537.343262][3145:3150] CHIP:DMG: }, + [1646909537.343346][3145:3150] CHIP:DMG: + [1646909537.343420][3145:3150] CHIP:DMG: CommandData = + [1646909537.343548][3145:3150] CHIP:DMG: { + [1646909537.343632][3145:3150] CHIP:DMG: 0x0 = [ + [1646909537.343772][3145:3150] CHIP:DMG: 0x15, 0x30, 0x1, 0xcb, 0x30, 0x81, 0xc8, 0x30, 0x70, 0x2, 0x1, 0x0, 0x30, 0xe, 0x31, 0xc, 0x30, 0xa, 0x6, 0x3, 0x55, 0x4, 0xa, 0xc, 0x3, 0x43, 0x53, 0x52, 0x30, 0x59, 0x30, 0x13, 0x6, 0x7, 0x2a, 0x86, 0x48, 0xce, 0x3d, 0x2, 0x1, 0x6, 0x8, 0x2a, 0x86 + [1646909537.343880][3145:3150] CHIP:DMG: ] + [1646909537.343968][3145:3150] CHIP:DMG: 0x1 = [ + [1646909537.344094][3145:3150] CHIP:DMG: 0xbd, 0xef, 0xb7, 0x8c, 0x5, 0x95, 0x9b, 0x60, 0xf4, 0xb1, 0xf7, 0x9c, 0x24, 0x50, 0x51, 0x9c, 0x59, 0x46, 0x97, 0x5e, 0x89, 0xe8, 0x7d, 0x29, 0x88, 0xac, 0x45, 0xed, 0xa6, 0xca, 0xac, 0x55, 0x2a, 0x7e, 0x11, 0x71, 0xe9, 0x68, 0x0, 0x91, 0xe, 0x23, + [1646909537.344193][3145:3150] CHIP:DMG: ] + [1646909537.344274][3145:3150] CHIP:DMG: }, + [1646909537.344349][3145:3150] CHIP:DMG: }, + [1646909537.344442][3145:3150] CHIP:DMG: + [1646909537.344508][3145:3150] CHIP:DMG: }, + [1646909537.344588][3145:3150] CHIP:DMG: + [1646909537.344646][3145:3150] CHIP:DMG: ], + [1646909537.344721][3145:3150] CHIP:DMG: + [1646909537.344779][3145:3150] CHIP:DMG: InteractionModelRevision = 1 + [1646909537.344837][3145:3150] CHIP:DMG: }, + [1646909537.344985][3145:3150] CHIP:DMG: Received Command Response Data, Endpoint=0 Cluster=0x0000_003E Command=0x0000_0005 + [1646909537.345068][3145:3150] CHIP:CTL: Received certificate signing request from the device + [1646909537.345139][3145:3150] CHIP:CTL: Getting certificate chain for the device from the issuer + [1646909537.347800][3145:3150] CHIP:CTL: Verifying Certificate Signing Request + [1646909537.349300][3145:3150] CHIP:CTL: Generating NOC + [1646909537.350268][3145:3150] CHIP:CTL: Providing certificate chain to the commissioner + [1646909537.350347][3145:3150] CHIP:CTL: Received callback from the CA for NOC Chain generation. Status ../../third_party/connectedhomeip/src/controller/ExampleOperationalCredentialsIssuer.cpp:225: Success + disabled: true + + - label: + "Commissioner configures operational network on TH if TH both supports + and requires" + verification: | + Verifiy on DUT: + + CHIP:CTL: Operational credentials provisioned on device 0xffff8c000b60 + CHIP:TOO: Secure Pairing Success + disabled: true + + - label: + "Commissioner instructs Commissionee to connect to operational network + if not already connected" + verification: | + Verify on DUT: + + CHIP:CTL: Performing next commissioning step 'FindOperational' + CHIP:CSM: FindOrEstablishSession: PeerId = BFCBED670D527591:000000000001B669 + CHIP:CSM: FindOrEstablishSession: No existing OperationalDeviceProxy instance found + disabled: true + + - label: "Reboot TH" + verification: | + 1. Using TH=all-clusters-app, exit the app, re-launch app + disabled: true + + - label: + "Commissioner should return to the same state as step 13 to continue + commissioning (i.e. Commissioner configure operational network on TH + if TH both supports and requires)" + verification: | + Verifiy on DUT: + + CHIP:CTL: Operational credentials provisioned on device 0xffff8c000b60 + CHIP:TOO: Secure Pairing Success + disabled: true + + - label: + "Commissioner instructs Commissionee to connect to operational network + if not already connected" + verification: | + Verify on DUT: + + CHIP:CTL: Performing next commissioning step 'FindOperational' + CHIP:CSM: FindOrEstablishSession: PeerId = BFCBED670D527591:000000000001B669 + CHIP:CSM: FindOrEstablishSession: No existing OperationalDeviceProxy instance found + disabled: true + + - label: "Commissioner starts discovery of TH using Operational Discovery" + verification: | + Verify on DUT: + + CHIP:DIS: Resolving BFCBED670D527591:000000000001B669 ... + CHIP:DIS: Operational node lookup already in progress. Will NOT start a new one. + CHIP:DMG: ICR moving to [AwaitingDe] + CHIP:EM: Sending Standalone Ack for MessageCounter:9439913 on exchange 63771i + CHIP:IN: Prepared secure message 0xffffa1c07938 to 0x000000000001B669 (1) of type 0x10 and protocolId (0, 0) on exchange 63771i with MessageCounter:695619. + CHIP:IN: Sending encrypted msg 0xffffa1c07938 with MessageCounter:695619 to 0x000000000001B669 (1) at monotonic time: 0000000000FBA446 msec + CHIP:EM: Flushed pending ack for MessageCounter:9439913 on exchange 63771i + CHIP:DL: Avahi resolve found + CHIP:DIS: Node ID resolved for BFCBED670D527591:000000000001B669 + CHIP:DIS: Addr 0: [fe80::dea6:32ff:feba:b3f7]:5540 + disabled: true + + - label: + "Commissioner opens a CASE session with TH over operational network" + verification: | + Verifiy on DUT: + + CHIP:SC: Establishing CASE session + disabled: true + + - label: "Commissioner sends CommissioningComplete command" + verification: | + Verifiy on DUT: + + CHIP:CTL: Received CommissioningComplete response + CHIP:CTL: Successfully finished commissioning step 'SendComplete' disabled: true - label: - "Repeat steps 1.a-1.o from [TC-DD-3.5]. Force Fail any step between - 1.k and 1.o" + "Commissioning channel between the Commissioner and Commissionee is + terminated." verification: | + Verify the following on DUT: + CHIP:CTL: Successfully finished commissioning step 'SendComplete' + CHIP:CTL: Commissioning stage next step: 'SendComplete' -> 'Cleanup' + CHIP:CTL: Performing next commissioning step 'Cleanup' + CHIP:CTL: Successfully finished commissioning step 'Cleanup' + CHIP:TOO: Device commissioning completed with success disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_8.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_8.yaml index 488ca8ad4b460d..563872367b5ba5 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_8.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_8.yaml @@ -14,7 +14,7 @@ # Auto-generated scripts for harness use only, please review before automation. The endpoints and cluster names are currently set to default name: - 3.3.8. [TC-DD-3.8] Commissioning Flow - Non-concurrent - Negative scenario + 3.3.8. [TC-DD-3.8] Commissioning Flow - Non-concurrent - Negative Scenario [DUT - Commissioner] config: @@ -24,8 +24,702 @@ config: tests: - label: - "Repeat steps 1.a-1.o from [TC-DD-3.6]. Force exit any step in 1.a and - 1.o." + "Commissioner has regulatory and fabric information available and has + accurate date, time and timezone" verification: | disabled: true + + - label: + "Commissioner and Commissionee discover each other and connect via the + discovery mode applicable for the DUT." + verification: | + On TH: start BLE Advertising by specific DUT implementation + + On DUT: start commissioning process(need to obtain the Thread dataset first) + + ./chip-tool pairing ble-thread 1 hex:0e080000000000010000000300000f35060004001fffe0020811111111222222220708fd27e57b1b1e22d9051000112233445566778899aabbccddeeff030e4f70656e54687265616444656d6f01021234041061e1206d2c2b46e079eb775f41fc72190c0402a0fff8 20202021 3840 + ,, + disabled: true + + - label: + "Establish encryption keys with Password Authenticated Session + Establishment on the commissioning channel" + verification: | + On DUT: + CHIP:SC: Received PBKDF param response + disabled: true + + - label: + "Commissioner SHALL re-arm Fail-safe timer on Commissionee within 60s + (the autonomously Fail-safe timer length set by Commissionee)" + verification: | + On DUT: + CHIP:CTL: Arming failsafe (60 seconds) + disabled: true + + - label: + "If (PICS_WIFI) or (PICS_THREAD), Commissioner SHALL configure + regulatory information in the Commissionee." + verification: | + On DUT: + CHIP:CTL: Setting Regulatory Config + disabled: true + + - label: + "Commissioner requests operational CSR from Commissionee with + OperationalCSRRequest command" + verification: | + On DUT: + CHIP:CTL: Sending CSR request to 0xffffa4001730 device + CHIP:DMG: ICR moving to [AddingComm] + CHIP:DMG: ICR moving to [AddedComma] + CHIP:IN: Prepared secure message 0xffffb9ba6db8 to 0x0000000000000001 (1) of type 0x8 and protocolId (0, 1) on exchange 45042i with MessageCounter:12011388. + CHIP:IN: Sending encrypted msg 0xffffb9ba6db8 with MessageCounter:12011388 to 0x0000000000000001 (1) at monotonic time: 304120 msec + CHIP:DMG: ICR moving to [CommandSen] + CHIP:CTL: Sent CSR request, waiting for the CSR + CHIP:DMG: ICR moving to [AwaitingDe] + CHIP:DL: HandlePlatformSpecificBLEEvent 16387 + CHIP:DL: Indication received, conn = 0xffffb0044210 + CHIP:DL: HandlePlatformSpecificBLEEvent 16389 + CHIP:DL: Indication received, conn = 0xffffb0044210 + CHIP:DL: HandlePlatformSpecificBLEEvent 16389 + CHIP:EM: Received message of type 0x9 with protocolId (0, 1) and MessageCounter:8508040 on exchange 45042i + CHIP:EM: Found matching exchange: 45042i, Delegate: 0xffffb0040000 + CHIP:DMG: ICR moving to [ResponseRe] + CHIP:DMG: InvokeResponseMessage = + CHIP:DMG: { + CHIP:DMG: suppressResponse = false, + CHIP:DMG: InvokeResponseIBs = + CHIP:DMG: [ + CHIP:DMG: InvokeResponseIB = + CHIP:DMG: { + CHIP:DMG: CommandDataIB = + CHIP:DMG: { + CHIP:DMG: CommandPathIB = + CHIP:DMG: { + CHIP:DMG: EndpointId = 0x0, + CHIP:DMG: ClusterId = 0x3e, + CHIP:DMG: CommandId = 0x5, + CHIP:DMG: }, + CHIP:DMG: + CHIP:DMG: CommandData = + CHIP:DMG: { + CHIP:DMG: 0x0 = [ + CHIP:DMG: 0x15, 0x30, 0x1, 0xcd, 0x30, 0x81, 0xca, 0x30, 0x70, 0x2, 0x1, 0x0, 0x30, 0xe, 0x31, 0xc, 0x30, 0xa, 0x6, 0x3, 0x55, 0x4, 0xa, 0xc, 0x3, 0x43, 0x53, 0x52, 0x30, 0x59, 0x30, 0x13, 0x6, 0x7, 0x2a, 0x86, 0x48, 0xce, 0x3d, 0x2, 0x1, 0x6, 0x8, 0x2a, 0x86 + CHIP:DMG: ] + CHIP:DMG: 0x1 = [ + CHIP:DMG: 0xea, 0xd6, 0x96, 0x53, 0x4d, 0x46, 0x1d, 0xd6, 0xcc, 0x7f, 0x25, 0x50, 0x80, 0x4c, 0x2a, 0xe9, 0xc8, 0xb8, 0x1b, 0x34, 0xca, 0x98, 0x38, 0x42, 0x74, 0xc2, 0x13, 0xf4, 0x10, 0x4d, 0xa2, 0x44, 0x38, 0x98, 0x28, 0xb6, 0xb1, 0x94, 0x6b, 0xd, 0x29, 0x1b + CHIP:DMG: ] + CHIP:DMG: }, + CHIP:DMG: }, + CHIP:DMG: + CHIP:DMG: }, + CHIP:DMG: + CHIP:DMG: ], + CHIP:DMG: + CHIP:DMG: InteractionModelRevision = 1 + CHIP:DMG: }, + CHIP:DMG: Received Command Response Data, Endpoint=0 Cluster=0x0000_003E Command=0x0000_0005 + CHIP:CTL: Received certificate signing request from the device + CHIP:CTL: Getting certificate chain for the device from the issuer + CHIP:CTL: Verifying Certificate Signing Request + CHIP:CTL: Generating NOC + CHIP:CTL: Providing certificate chain to the commissioner + CHIP:CTL: Received callback from the CA for NOC Chain generation. Status ../../src/controller/ExampleOperationalCredentialsIssuer.cpp:225: Success + disabled: true + + - label: + "Commissioner configures operational credentials on DUT if not + previously installed" + verification: | + On DUT: + [1651218829.220063][3273:3278] CHIP:CTL: Sending root certificate to the device + [1651218829.220201][3273:3278] CHIP:DMG: ICR moving to [AddingComm] + [1651218829.222415][3273:3278] CHIP:DMG: ICR moving to [AddedComma] + [1651218829.222549][3273:3278] CHIP:IN: Prepared secure message 0xffffb9ba6b98 to 0x0000000000000001 (1) of type 0x8 and protocolId (0, 1) on exchange 45043i with MessageCounter:12011389. + [1651218829.222616][3273:3278] CHIP:IN: Sending encrypted msg 0xffffb9ba6b98 with MessageCounter:12011389 to 0x0000000000000001 (1) at monotonic time: 305872 msec + [1651218829.222746][3273:3278] CHIP:DMG: ICR moving to [CommandSen] + [1651218829.222789][3273:3278] CHIP:CTL: Sent root certificate to the device + [1651218829.223121][3273:3278] CHIP:DMG: ICR moving to [AwaitingDe] + [1651218829.306861][3273:3278] CHIP:DL: HandlePlatformSpecificBLEEvent 16387 + [1651218829.404144][3273:3278] CHIP:DL: HandlePlatformSpecificBLEEvent 16387 + [1651218829.454121][3273:3276] CHIP:DL: Indication received, conn = 0xffffb0044210 + [1651218829.454352][3273:3278] CHIP:DL: HandlePlatformSpecificBLEEvent 16389 + CHIP:EM: Received message of type 0x9 with protocolId (0, 1) and MessageCounter:8508041 on exchange 45043i + CHIP:EM: Found matching exchange: 45043i, Delegate: 0xffffa400def0 + CHIP:DMG: ICR moving to [ResponseRe] + CHIP:DMG: InvokeResponseMessage = + CHIP:DMG: { + CHIP:DMG: suppressResponse = false, + CHIP:DMG: InvokeResponseIBs = + CHIP:DMG: [ + CHIP:DMG: InvokeResponseIB = + CHIP:DMG: { + CHIP:DMG: CommandStatusIB = + CHIP:DMG: { + CHIP:DMG: CommandPathIB = + CHIP:DMG: { + CHIP:DMG: EndpointId = 0x0, + CHIP:DMG: ClusterId = 0x3e, + CHIP:DMG: CommandId = 0xb, + CHIP:DMG: }, + CHIP:DMG: + CHIP:DMG: StatusIB = + CHIP:DMG: { + CHIP:DMG: status = 0x0, + CHIP:DMG: }, + CHIP:DMG: + CHIP:DMG: }, + CHIP:DMG: + CHIP:DMG: }, + CHIP:DMG: + CHIP:DMG: ], + CHIP:DMG: + CHIP:DMG: InteractionModelRevision = 1 + CHIP:DMG: }, + CHIP:DMG: Received Command Response Status for Endpoint=0 Cluster=0x0000_003E Command=0x0000_000B Status=0x0 + CHIP:CTL: Device confirmed that it has received the root certificate + disabled: true + + - label: + "Commissioner configures itself as administrator in ACL on TH if + needed" + verification: | + On DUT: + [1651218829.457248][3273:3278] CHIP:CTL: Sending operational certificate chain to the device + [1651218829.457372][3273:3278] CHIP:DMG: ICR moving to [AddingComm] + [1651218829.460013][3273:3278] CHIP:DMG: ICR moving to [AddedComma] + [1651218829.460273][3273:3278] CHIP:IN: Prepared secure message 0xffffb9ba7828 to 0x0000000000000001 (1) of type 0x8 and protocolId (0, 1) on exchange 45044i with MessageCounter:12011390. + [1651218829.460374][3273:3278] CHIP:IN: Sending encrypted msg 0xffffb9ba7828 with MessageCounter:12011390 to 0x0000000000000001 (1) at monotonic time: 306110 msec + [1651218829.460602][3273:3278] CHIP:DMG: ICR moving to [CommandSen] + [1651218829.460684][3273:3278] CHIP:CTL: Sent operational certificate to the device + [1651218829.460778][3273:3278] CHIP:DMG: ICR moving to [AwaitingDe] + [1651218829.550574][3273:3278] CHIP:DL: HandlePlatformSpecificBLEEvent 16387 + [1651218829.648065][3273:3278] CHIP:DL: HandlePlatformSpecificBLEEvent 16387 + [1651218829.745594][3273:3278] CHIP:DL: HandlePlatformSpecificBLEEvent 16387 + [1651218833.988087][3273:3276] CHIP:DL: Indication received, conn = 0xffffb0044210 + [1651218833.988336][3273:3278] CHIP:DL: HandlePlatformSpecificBLEEvent 16389 + [1651218833.988598][3273:3278] CHIP:EM: Received message of type 0x9 with protocolId (0, 1) and MessageCounter:8508042 on exchange 45044i + CHIP:EM: Found matching exchange: 45044i, Delegate: 0xffffb0040000 + CHIP:DMG: ICR moving to [ResponseRe] + CHIP:DMG: InvokeResponseMessage = + CHIP:DMG: { + CHIP:DMG: suppressResponse = false, + CHIP:DMG: InvokeResponseIBs = + CHIP:DMG: [ + CHIP:DMG: InvokeResponseIB = + CHIP:DMG: { + CHIP:DMG: CommandDataIB = + CHIP:DMG: { + CHIP:DMG: CommandPathIB = + CHIP:DMG: { + CHIP:DMG: EndpointId = 0x0, + CHIP:DMG: ClusterId = 0x3e, + CHIP:DMG: CommandId = 0x8, + CHIP:DMG: }, + CHIP:DMG: + CHIP:DMG: CommandData = + CHIP:DMG: { + CHIP:DMG: 0x0 = 0, + CHIP:DMG: 0x1 = 1, + CHIP:DMG: }, + CHIP:DMG: }, + CHIP:DMG: + CHIP:DMG: }, + CHIP:DMG: + CHIP:DMG: ], + CHIP:DMG: + CHIP:DMG: InteractionModelRevision = 1 + CHIP:DMG: }, + CHIP:DMG: Received Command Response Data, Endpoint=0 Cluster=0x0000_003E Command=0x0000_0008 + CHIP:CTL: Device returned status 0 on receiving the NOC + CHIP:CTL: Operational credentials provisioned on device 0xffffa4001730 + disabled: true + + - label: + "Commissioner configures operational network on TH if TH both supports + and requires" + verification: | + On DUT: + [1651218833.995054][3273:3278] CHIP:CTL: Adding thread network + [1651218833.995176][3273:3278] CHIP:DMG: ICR moving to [AddingComm] + [1651218833.995253][3273:3278] CHIP:DMG: ICR moving to [AddedComma] + [1651218833.995431][3273:3278] CHIP:IN: Prepared secure message 0xffffb9ba7848 to 0x0000000000000001 (1) of type 0x8 and protocolId (0, 1) on exchange 45045i with MessageCounter:12011391. + [1651218833.995523][3273:3278] CHIP:IN: Sending encrypted msg 0xffffb9ba7848 with MessageCounter:12011391 to 0x0000000000000001 (1) at monotonic time: 310645 msec + [1651218833.995723][3273:3278] CHIP:DMG: ICR moving to [CommandSen] + [1651218833.995823][3273:3278] CHIP:DMG: ICR moving to [AwaitingDe] + [1651218834.084548][3273:3278] CHIP:DL: HandlePlatformSpecificBLEEvent 16387 + [1651218834.134690][3273:3276] CHIP:DL: Indication received, conn = 0xffffb0044210 + [1651218834.134918][3273:3278] CHIP:DL: HandlePlatformSpecificBLEEvent 16389 + CHIP:EM: Received message of type 0x9 with protocolId (0, 1) and MessageCounter:8508043 on exchange 45045i + CHIP:EM: Found matching exchange: 45045i, Delegate: 0xffffa400def0 + CHIP:DMG: ICR moving to [ResponseRe] + CHIP:DMG: InvokeResponseMessage = + CHIP:DMG: { + CHIP:DMG: suppressResponse = false, + CHIP:DMG: InvokeResponseIBs = + CHIP:DMG: [ + CHIP:DMG: InvokeResponseIB = + CHIP:DMG: { + CHIP:DMG: CommandDataIB = + CHIP:DMG: { + CHIP:DMG: CommandPathIB = + CHIP:DMG: { + CHIP:DMG: EndpointId = 0x0, + CHIP:DMG: ClusterId = 0x31, + CHIP:DMG: CommandId = 0x5, + CHIP:DMG: }, + CHIP:DMG: + CHIP:DMG: CommandData = + CHIP:DMG: { + CHIP:DMG: 0x0 = 0, + CHIP:DMG: 0x1 = "", + CHIP:DMG: }, + CHIP:DMG: }, + CHIP:DMG: + CHIP:DMG: }, + CHIP:DMG: + CHIP:DMG: ], + CHIP:DMG: + CHIP:DMG: InteractionModelRevision = 1 + CHIP:DMG: }, + CHIP:DMG: Received Command Response Data, Endpoint=0 Cluster=0x0000_0031 Command=0x0000_0005 + CHIP:CTL: Received NetworkConfig response + disabled: true + + - label: + "Commissioner instructs Commissionee to connect to operational network + if not already connected" + verification: | + On DUT: + [1651218834.137891][3273:3278] CHIP:CTL: Enabling thread network + [1651218834.138014][3273:3278] CHIP:DMG: ICR moving to [AddingComm] + [1651218834.138086][3273:3278] CHIP:DMG: ICR moving to [AddedComma] + [1651218834.138236][3273:3278] CHIP:IN: Prepared secure message 0xffffb9ba7938 to 0x0000000000000001 (1) of type 0x8 and protocolId (0, 1) on exchange 45046i with MessageCounter:12011392. + [1651218834.138325][3273:3278] CHIP:IN: Sending encrypted msg 0xffffb9ba7938 with MessageCounter:12011392 to 0x0000000000000001 (1) at monotonic time: 310788 msec + [1651218834.138522][3273:3278] CHIP:DMG: ICR moving to [CommandSen] + [1651218834.138628][3273:3278] CHIP:DMG: ICR moving to [AwaitingDe] + [1651218834.231701][3273:3278] CHIP:DL: HandlePlatformSpecificBLEEvent 16387 + [1651218834.426948][3273:3276] CHIP:DL: Indication received, conn = 0xffffb0044210 + [1651218834.427186][3273:3278] CHIP:DL: HandlePlatformSpecificBLEEvent 16389 + [1651218834.427443][3273:3278] CHIP:EM: Received message of type 0x9 with protocolId (0, 1) and MessageCounter:8508044 on exchange 45046i + CHIP:EM: Found matching exchange: 45046i, Delegate: 0xffffb0040000 + CHIP:DMG: ICR moving to [ResponseRe] + CHIP:DMG: InvokeResponseMessage = + CHIP:DMG: { + CHIP:DMG: suppressResponse = false, + CHIP:DMG: InvokeResponseIBs = + CHIP:DMG: [ + CHIP:DMG: InvokeResponseIB = + CHIP:DMG: { + CHIP:DMG: CommandDataIB = + CHIP:DMG: { + CHIP:DMG: CommandPathIB = + CHIP:DMG: { + CHIP:DMG: EndpointId = 0x0, + CHIP:DMG: ClusterId = 0x31, + CHIP:DMG: CommandId = 0x7, + CHIP:DMG: }, + CHIP:DMG: + CHIP:DMG: CommandData = + CHIP:DMG: { + CHIP:DMG: 0x0 = 0, + CHIP:DMG: 0x1 = "", + CHIP:DMG: 0x2 = 0, + CHIP:DMG: }, + CHIP:DMG: }, + CHIP:DMG: + CHIP:DMG: }, + CHIP:DMG: + CHIP:DMG: ], + CHIP:DMG: + CHIP:DMG: InteractionModelRevision = 1 + CHIP:DMG: }, + CHIP:DMG: Received Command Response Data, Endpoint=0 Cluster=0x0000_0031 Command=0x0000_0007 + CHIP:CTL: Received ConnectNetwork response + disabled: true + + - label: + "Commissioning channel between the Commissioner and Commissionee is + terminated." + verification: | + 1. Verify the channel was terminated on DUT=chip-tool + [1651271753284] [23287:743790] CHIP: [CTL] Received CommissioningComplete response + [1651271753284] [23287:743790] CHIP: [CTL] Successfully finished commissioning step 'SendComplete' + [1651271753284] [23287:743790] CHIP: [CTL] Commissioning stage next step: 'SendComplete' -> 'Cleanup' + [1651271753284] [23287:743790] CHIP: [CTL] Performing next commissioning step 'Cleanup' + [1651271753284] [23287:743790] CHIP: [CTL] Successfully finished commissioning step 'Cleanup' + [1651271753284] [23287:743790] CHIP: [TOO] Device commissioning completed with success + disabled: true + + - label: "Reboot TH and prepare for commissioning" + verification: | + 1. Using TH=all-clusters-app, exit the app, re-launch app + disabled: true + + - label: + "Establish encryption keys with Password Authenticated Session + Establishment on the commissioning channel" + verification: | + On DUT: + CHIP:SC: Received PBKDF param response + disabled: true + + - label: + "Commissioner re-arms Fail-safe timer on Commissionee within 60s (the + autonomously Fail-safe timer length set by Commissionee)" + verification: | + On DUT: + CHIP:CTL: Arming failsafe (60 seconds) + disabled: true + + - label: + "If (PICS_WIFI) or (PICS_THREAD), Commissioner SHALL configure + regulatory information in the Commissionee." + verification: | + Need chip-tool implementation + disabled: true + + - label: + "Commissioner requests operational CSR from Commissionee with + OperationalCSRRequest command" + verification: | + On DUT: + CHIP:CTL: Sending CSR request to 0xffffa4001730 device + CHIP:DMG: ICR moving to [AddingComm] + CHIP:DMG: ICR moving to [AddedComma] + CHIP:IN: Prepared secure message 0xffffb9ba6db8 to 0x0000000000000001 (1) of type 0x8 and protocolId (0, 1) on exchange 45042i with MessageCounter:12011388. + CHIP:IN: Sending encrypted msg 0xffffb9ba6db8 with MessageCounter:12011388 to 0x0000000000000001 (1) at monotonic time: 304120 msec + CHIP:DMG: ICR moving to [CommandSen] + CHIP:CTL: Sent CSR request, waiting for the CSR + CHIP:DMG: ICR moving to [AwaitingDe] + CHIP:DL: HandlePlatformSpecificBLEEvent 16387 + CHIP:DL: Indication received, conn = 0xffffb0044210 + CHIP:DL: HandlePlatformSpecificBLEEvent 16389 + CHIP:DL: Indication received, conn = 0xffffb0044210 + CHIP:DL: HandlePlatformSpecificBLEEvent 16389 + CHIP:EM: Received message of type 0x9 with protocolId (0, 1) and MessageCounter:8508040 on exchange 45042i + CHIP:EM: Found matching exchange: 45042i, Delegate: 0xffffb0040000 + CHIP:DMG: ICR moving to [ResponseRe] + CHIP:DMG: InvokeResponseMessage = + CHIP:DMG: { + CHIP:DMG: suppressResponse = false, + CHIP:DMG: InvokeResponseIBs = + CHIP:DMG: [ + CHIP:DMG: InvokeResponseIB = + CHIP:DMG: { + CHIP:DMG: CommandDataIB = + CHIP:DMG: { + CHIP:DMG: CommandPathIB = + CHIP:DMG: { + CHIP:DMG: EndpointId = 0x0, + CHIP:DMG: ClusterId = 0x3e, + CHIP:DMG: CommandId = 0x5, + CHIP:DMG: }, + CHIP:DMG: + CHIP:DMG: CommandData = + CHIP:DMG: { + CHIP:DMG: 0x0 = [ + CHIP:DMG: 0x15, 0x30, 0x1, 0xcd, 0x30, 0x81, 0xca, 0x30, 0x70, 0x2, 0x1, 0x0, 0x30, 0xe, 0x31, 0xc, 0x30, 0xa, 0x6, 0x3, 0x55, 0x4, 0xa, 0xc, 0x3, 0x43, 0x53, 0x52, 0x30, 0x59, 0x30, 0x13, 0x6, 0x7, 0x2a, 0x86, 0x48, 0xce, 0x3d, 0x2, 0x1, 0x6, 0x8, 0x2a, 0x86 + CHIP:DMG: ] + CHIP:DMG: 0x1 = [ + CHIP:DMG: 0xea, 0xd6, 0x96, 0x53, 0x4d, 0x46, 0x1d, 0xd6, 0xcc, 0x7f, 0x25, 0x50, 0x80, 0x4c, 0x2a, 0xe9, 0xc8, 0xb8, 0x1b, 0x34, 0xca, 0x98, 0x38, 0x42, 0x74, 0xc2, 0x13, 0xf4, 0x10, 0x4d, 0xa2, 0x44, 0x38, 0x98, 0x28, 0xb6, 0xb1, 0x94, 0x6b, 0xd, 0x29, 0x1b + CHIP:DMG: ] + CHIP:DMG: }, + CHIP:DMG: }, + CHIP:DMG: + CHIP:DMG: }, + CHIP:DMG: + CHIP:DMG: ], + CHIP:DMG: + CHIP:DMG: InteractionModelRevision = 1 + CHIP:DMG: }, + CHIP:DMG: Received Command Response Data, Endpoint=0 Cluster=0x0000_003E Command=0x0000_0005 + CHIP:CTL: Received certificate signing request from the device + CHIP:CTL: Getting certificate chain for the device from the issuer + CHIP:CTL: Verifying Certificate Signing Request + CHIP:CTL: Generating NOC + CHIP:CTL: Providing certificate chain to the commissioner + CHIP:CTL: Received callback from the CA for NOC Chain generation. Status ../../src/controller/ExampleOperationalCredentialsIssuer.cpp:225: Success + disabled: true + + - label: + "Commissioner configures operational credentials on DUT if not + previously installed" + verification: | + On DUT: + [1651218829.220063][3273:3278] CHIP:CTL: Sending root certificate to the device + [1651218829.220201][3273:3278] CHIP:DMG: ICR moving to [AddingComm] + [1651218829.222415][3273:3278] CHIP:DMG: ICR moving to [AddedComma] + [1651218829.222549][3273:3278] CHIP:IN: Prepared secure message 0xffffb9ba6b98 to 0x0000000000000001 (1) of type 0x8 and protocolId (0, 1) on exchange 45043i with MessageCounter:12011389. + [1651218829.222616][3273:3278] CHIP:IN: Sending encrypted msg 0xffffb9ba6b98 with MessageCounter:12011389 to 0x0000000000000001 (1) at monotonic time: 305872 msec + [1651218829.222746][3273:3278] CHIP:DMG: ICR moving to [CommandSen] + [1651218829.222789][3273:3278] CHIP:CTL: Sent root certificate to the device + [1651218829.223121][3273:3278] CHIP:DMG: ICR moving to [AwaitingDe] + [1651218829.306861][3273:3278] CHIP:DL: HandlePlatformSpecificBLEEvent 16387 + [1651218829.404144][3273:3278] CHIP:DL: HandlePlatformSpecificBLEEvent 16387 + [1651218829.454121][3273:3276] CHIP:DL: Indication received, conn = 0xffffb0044210 + [1651218829.454352][3273:3278] CHIP:DL: HandlePlatformSpecificBLEEvent 16389 + CHIP:EM: Received message of type 0x9 with protocolId (0, 1) and MessageCounter:8508041 on exchange 45043i + CHIP:EM: Found matching exchange: 45043i, Delegate: 0xffffa400def0 + CHIP:DMG: ICR moving to [ResponseRe] + CHIP:DMG: InvokeResponseMessage = + CHIP:DMG: { + CHIP:DMG: suppressResponse = false, + CHIP:DMG: InvokeResponseIBs = + CHIP:DMG: [ + CHIP:DMG: InvokeResponseIB = + CHIP:DMG: { + CHIP:DMG: CommandStatusIB = + CHIP:DMG: { + CHIP:DMG: CommandPathIB = + CHIP:DMG: { + CHIP:DMG: EndpointId = 0x0, + CHIP:DMG: ClusterId = 0x3e, + CHIP:DMG: CommandId = 0xb, + CHIP:DMG: }, + CHIP:DMG: + CHIP:DMG: StatusIB = + CHIP:DMG: { + CHIP:DMG: status = 0x0, + CHIP:DMG: }, + CHIP:DMG: + CHIP:DMG: }, + CHIP:DMG: + CHIP:DMG: }, + CHIP:DMG: + CHIP:DMG: ], + CHIP:DMG: + CHIP:DMG: InteractionModelRevision = 1 + CHIP:DMG: }, + CHIP:DMG: Received Command Response Status for Endpoint=0 Cluster=0x0000_003E Command=0x0000_000B Status=0x0 + CHIP:CTL: Device confirmed that it has received the root certificate + disabled: true + + - label: + "Commissioner configures itself as administrator in ACL on TH if + needed" + verification: | + On DUT: + [1651218829.457248][3273:3278] CHIP:CTL: Sending operational certificate chain to the device + [1651218829.457372][3273:3278] CHIP:DMG: ICR moving to [AddingComm] + [1651218829.460013][3273:3278] CHIP:DMG: ICR moving to [AddedComma] + [1651218829.460273][3273:3278] CHIP:IN: Prepared secure message 0xffffb9ba7828 to 0x0000000000000001 (1) of type 0x8 and protocolId (0, 1) on exchange 45044i with MessageCounter:12011390. + [1651218829.460374][3273:3278] CHIP:IN: Sending encrypted msg 0xffffb9ba7828 with MessageCounter:12011390 to 0x0000000000000001 (1) at monotonic time: 306110 msec + [1651218829.460602][3273:3278] CHIP:DMG: ICR moving to [CommandSen] + [1651218829.460684][3273:3278] CHIP:CTL: Sent operational certificate to the device + [1651218829.460778][3273:3278] CHIP:DMG: ICR moving to [AwaitingDe] + [1651218829.550574][3273:3278] CHIP:DL: HandlePlatformSpecificBLEEvent 16387 + [1651218829.648065][3273:3278] CHIP:DL: HandlePlatformSpecificBLEEvent 16387 + [1651218829.745594][3273:3278] CHIP:DL: HandlePlatformSpecificBLEEvent 16387 + [1651218833.988087][3273:3276] CHIP:DL: Indication received, conn = 0xffffb0044210 + [1651218833.988336][3273:3278] CHIP:DL: HandlePlatformSpecificBLEEvent 16389 + [1651218833.988598][3273:3278] CHIP:EM: Received message of type 0x9 with protocolId (0, 1) and MessageCounter:8508042 on exchange 45044i + CHIP:EM: Found matching exchange: 45044i, Delegate: 0xffffb0040000 + CHIP:DMG: ICR moving to [ResponseRe] + CHIP:DMG: InvokeResponseMessage = + CHIP:DMG: { + CHIP:DMG: suppressResponse = false, + CHIP:DMG: InvokeResponseIBs = + CHIP:DMG: [ + CHIP:DMG: InvokeResponseIB = + CHIP:DMG: { + CHIP:DMG: CommandDataIB = + CHIP:DMG: { + CHIP:DMG: CommandPathIB = + CHIP:DMG: { + CHIP:DMG: EndpointId = 0x0, + CHIP:DMG: ClusterId = 0x3e, + CHIP:DMG: CommandId = 0x8, + CHIP:DMG: }, + CHIP:DMG: + CHIP:DMG: CommandData = + CHIP:DMG: { + CHIP:DMG: 0x0 = 0, + CHIP:DMG: 0x1 = 1, + CHIP:DMG: }, + CHIP:DMG: }, + CHIP:DMG: + CHIP:DMG: }, + CHIP:DMG: + CHIP:DMG: ], + CHIP:DMG: + CHIP:DMG: InteractionModelRevision = 1 + CHIP:DMG: }, + CHIP:DMG: Received Command Response Data, Endpoint=0 Cluster=0x0000_003E Command=0x0000_0008 + CHIP:CTL: Device returned status 0 on receiving the NOC + CHIP:CTL: Operational credentials provisioned on device 0xffffa4001730 + disabled: true + + - label: + "Commissioner configures operational network on TH if TH both supports + and requires" + verification: | + On DUT: + [1651218833.995054][3273:3278] CHIP:CTL: Adding thread network + [1651218833.995176][3273:3278] CHIP:DMG: ICR moving to [AddingComm] + [1651218833.995253][3273:3278] CHIP:DMG: ICR moving to [AddedComma] + [1651218833.995431][3273:3278] CHIP:IN: Prepared secure message 0xffffb9ba7848 to 0x0000000000000001 (1) of type 0x8 and protocolId (0, 1) on exchange 45045i with MessageCounter:12011391. + [1651218833.995523][3273:3278] CHIP:IN: Sending encrypted msg 0xffffb9ba7848 with MessageCounter:12011391 to 0x0000000000000001 (1) at monotonic time: 310645 msec + [1651218833.995723][3273:3278] CHIP:DMG: ICR moving to [CommandSen] + [1651218833.995823][3273:3278] CHIP:DMG: ICR moving to [AwaitingDe] + [1651218834.084548][3273:3278] CHIP:DL: HandlePlatformSpecificBLEEvent 16387 + [1651218834.134690][3273:3276] CHIP:DL: Indication received, conn = 0xffffb0044210 + [1651218834.134918][3273:3278] CHIP:DL: HandlePlatformSpecificBLEEvent 16389 + CHIP:EM: Received message of type 0x9 with protocolId (0, 1) and MessageCounter:8508043 on exchange 45045i + CHIP:EM: Found matching exchange: 45045i, Delegate: 0xffffa400def0 + CHIP:DMG: ICR moving to [ResponseRe] + CHIP:DMG: InvokeResponseMessage = + CHIP:DMG: { + CHIP:DMG: suppressResponse = false, + CHIP:DMG: InvokeResponseIBs = + CHIP:DMG: [ + CHIP:DMG: InvokeResponseIB = + CHIP:DMG: { + CHIP:DMG: CommandDataIB = + CHIP:DMG: { + CHIP:DMG: CommandPathIB = + CHIP:DMG: { + CHIP:DMG: EndpointId = 0x0, + CHIP:DMG: ClusterId = 0x31, + CHIP:DMG: CommandId = 0x5, + CHIP:DMG: }, + CHIP:DMG: + CHIP:DMG: CommandData = + CHIP:DMG: { + CHIP:DMG: 0x0 = 0, + CHIP:DMG: 0x1 = "", + CHIP:DMG: }, + CHIP:DMG: }, + CHIP:DMG: + CHIP:DMG: }, + CHIP:DMG: + CHIP:DMG: ], + CHIP:DMG: + CHIP:DMG: InteractionModelRevision = 1 + CHIP:DMG: }, + CHIP:DMG: Received Command Response Data, Endpoint=0 Cluster=0x0000_0031 Command=0x0000_0005 + CHIP:CTL: Received NetworkConfig response + disabled: true + + - label: + "Commissioner instructs Commissionee to connect to operational network + if not already connected" + verification: | + On DUT: + [1651218834.137891][3273:3278] CHIP:CTL: Enabling thread network + [1651218834.138014][3273:3278] CHIP:DMG: ICR moving to [AddingComm] + [1651218834.138086][3273:3278] CHIP:DMG: ICR moving to [AddedComma] + [1651218834.138236][3273:3278] CHIP:IN: Prepared secure message 0xffffb9ba7938 to 0x0000000000000001 (1) of type 0x8 and protocolId (0, 1) on exchange 45046i with MessageCounter:12011392. + [1651218834.138325][3273:3278] CHIP:IN: Sending encrypted msg 0xffffb9ba7938 with MessageCounter:12011392 to 0x0000000000000001 (1) at monotonic time: 310788 msec + [1651218834.138522][3273:3278] CHIP:DMG: ICR moving to [CommandSen] + [1651218834.138628][3273:3278] CHIP:DMG: ICR moving to [AwaitingDe] + [1651218834.231701][3273:3278] CHIP:DL: HandlePlatformSpecificBLEEvent 16387 + [1651218834.426948][3273:3276] CHIP:DL: Indication received, conn = 0xffffb0044210 + [1651218834.427186][3273:3278] CHIP:DL: HandlePlatformSpecificBLEEvent 16389 + [1651218834.427443][3273:3278] CHIP:EM: Received message of type 0x9 with protocolId (0, 1) and MessageCounter:8508044 on exchange 45046i + CHIP:EM: Found matching exchange: 45046i, Delegate: 0xffffb0040000 + CHIP:DMG: ICR moving to [ResponseRe] + CHIP:DMG: InvokeResponseMessage = + CHIP:DMG: { + CHIP:DMG: suppressResponse = false, + CHIP:DMG: InvokeResponseIBs = + CHIP:DMG: [ + CHIP:DMG: InvokeResponseIB = + CHIP:DMG: { + CHIP:DMG: CommandDataIB = + CHIP:DMG: { + CHIP:DMG: CommandPathIB = + CHIP:DMG: { + CHIP:DMG: EndpointId = 0x0, + CHIP:DMG: ClusterId = 0x31, + CHIP:DMG: CommandId = 0x7, + CHIP:DMG: }, + CHIP:DMG: + CHIP:DMG: CommandData = + CHIP:DMG: { + CHIP:DMG: 0x0 = 0, + CHIP:DMG: 0x1 = "", + CHIP:DMG: 0x2 = 0, + CHIP:DMG: }, + CHIP:DMG: }, + CHIP:DMG: + CHIP:DMG: }, + CHIP:DMG: + CHIP:DMG: ], + CHIP:DMG: + CHIP:DMG: InteractionModelRevision = 1 + CHIP:DMG: }, + CHIP:DMG: Received Command Response Data, Endpoint=0 Cluster=0x0000_0031 Command=0x0000_0007 + CHIP:CTL: Received ConnectNetwork response + disabled: true + + - label: + "Commissioning channel between the Commissioner and Commissionee is + terminated." + verification: | + 1. Verify the channel was terminated on DUT=chip-tool + [1651271753284] [23287:743790] CHIP: [CTL] Received CommissioningComplete response + [1651271753284] [23287:743790] CHIP: [CTL] Successfully finished commissioning step 'SendComplete' + [1651271753284] [23287:743790] CHIP: [CTL] Commissioning stage next step: 'SendComplete' -> 'Cleanup' + [1651271753284] [23287:743790] CHIP: [CTL] Performing next commissioning step 'Cleanup' + [1651271753284] [23287:743790] CHIP: [CTL] Successfully finished commissioning step 'Cleanup' + [1651271753284] [23287:743790] CHIP: [TOO] Device commissioning completed with success + disabled: true + + - label: "Commissioner starts discovery of TH using Operational Discovery" + verification: | + On DUT: + CHIP:DL: Avahi resolve found + CHIP:DIS: Node ID resolved for 0x0000000000000001 + CHIP:DIS: Addr 0: [fd11:22::9d96:8fcf:10cf:799e]:5540 + CHIP:CTL: OperationalDiscoveryComplete for device ID 0x0000000000000001 + disabled: true + + - label: + "Commissioner opens a CASE session with TH over operational network" + verification: | + On DUT: + CHIP:SC: Sent Sigma1 msg + CHIP:CTL: Address resolved for node: 0x0000000000000001 + CHIP:EM: Received message of type 0x31 with protocolId (0, 0) and MessageCounter:1066460336 on exchange 45047i + CHIP:EM: Found matching exchange: 45047i, Delegate: 0xffffa400f7f8 + CHIP:EM: Rxd Ack; Removing MessageCounter:2352378411 from Retrans Table on exchange 45047i + CHIP:EM: Removed CHIP MessageCounter:2352378411 from RetransTable on exchange 45047i + CHIP:SC: Received Sigma2 msg + CHIP:SC: Peer assigned session session ID 2 + CHIP:SC: The device does not support GetClock_RealTimeMS() API. This will eventually result in CASE session setup failures. + CHIP:IN: Generating compressed fabric ID using uncompressed fabric ID 0x0000000000000001 and root pubkey + CHIP:IN: 0x04, 0x6e, 0x3e, 0x58, 0x9d, 0x08, 0xd6, 0xae, + CHIP:IN: 0xe9, 0xff, 0x9b, 0x8f, 0xba, 0x6f, 0x57, 0x73, + CHIP:IN: 0x21, 0xc4, 0xe2, 0x7b, 0x09, 0xe4, 0x24, 0x7f, + CHIP:IN: 0x55, 0x44, 0x3b, 0xf2, 0x7c, 0x13, 0x45, 0x3b, + CHIP:IN: 0x82, 0xa8, 0x42, 0x96, 0xb4, 0x36, 0x78, 0x20, + CHIP:IN: 0xa1, 0x37, 0x69, 0xf0, 0x20, 0xc9, 0x20, 0x7e, + CHIP:IN: 0x66, 0x45, 0x84, 0x53, 0x1b, 0x3e, 0xd2, 0x61, + CHIP:IN: 0xb6, 0x89, 0x27, 0xfd, 0xe8, 0x23, 0x69, 0x6d, + CHIP:IN: 0x93, + CHIP:IN: Generated compressed fabric ID + CHIP:IN: 0xa3, 0x54, 0xab, 0x2a, 0xa2, 0x1f, 0x8e, 0x48, + CHIP:SC: Found MRP parameters in the message + CHIP:SC: Sending Sigma3 + CHIP:EM: Piggybacking Ack for MessageCounter:1066460336 on exchange: 45047i + CHIP:IN: Prepared unauthenticated message 0xaaaad7ce1bf8 to 0x0000000000000000 (0) of type 0x32 and protocolId (0, 0) on exchange 45047i with MessageCounter:2352378412. + CHIP:IN: Sending unauthenticated msg 0xaaaad7ce1bf8 with MessageCounter:2352378412 to 0x0000000000000000 at monotonic time: 315803 msec + CHIP:SC: Sent Sigma3 msg + CHIP:EM: Received message of type 0x40 with protocolId (0, 0) and MessageCounter:1066460337 on exchange 45047i + CHIP:EM: Found matching exchange: 45047i, Delegate: 0xffffa400f7f8 + CHIP:EM: Rxd Ack; Removing MessageCounter:2352378412 from Retrans Table on exchange 45047i + CHIP:EM: Removed CHIP MessageCounter:2352378412 from RetransTable on exchange 45047i + CHIP:SC: Success status report received. Session was established + CHIP:IN: New secure session created for device 0x0000000000000001, LSID:2 PSID:2! + disabled: true + + - label: "Commissioner sends CommissioningComplete command" + verification: | + On DUT: + CHIP:CTL: Received CommissioningComplete response + CHIP:CTL: Rendezvous cleanup + CHIP:TOO: Device commissioning completed with success + disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_DM_1_2.yaml b/src/app/tests/suites/certification/Test_TC_DM_1_2.yaml index fa8b9a14fdb3a8..e4f4c86f822396 100644 --- a/src/app/tests/suites/certification/Test_TC_DM_1_2.yaml +++ b/src/app/tests/suites/certification/Test_TC_DM_1_2.yaml @@ -13,25 +13,86 @@ # 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: 10.1.2. [TC-DM-1.2] Basic Information Cluster Events +name: + 10.1.2. [TC-DM-1.2] Global Attributes for Node Operational Credentials + Cluster [DUT-Server] config: nodeId: 0x12344321 cluster: "Basic" endpoint: 0 - tests: - - label: "Reboot the DUT" + - label: "Test Step" + verification: | + chip-tool verification steps + disabled: true + - label: "Commission DUT to TH" + verification: |4+ + disabled: true + - label: "TH reads the ClusterRevision from DUT" + verification: | + ubuntu@ubuntu:~/sethu-apr1/connectedhomeip/examples/chip-tool/out/debug$ ./chip-tool operationalcredentials read cluster-revision 1 0 - - label: "Shut down the DUT" + [1649422711.953376][3312:3317] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_003E Attribute 0x0000_FFFD DataVersion: 698307857 + [1649422711.953487][3312:3317] CHIP:TOO: ClusterRevision: 1 + [1649422711.953574][3312:3317] CHIP:EM: Sending Standalone Ack for MessageCounter:9018855 on exchange 29017i disabled: true + - label: "TH reads the FeatureMap from DUT" + verification: | + ubuntu@ubuntu:~/sethu-apr1/connectedhomeip/examples/chip-tool/out/debug$ ./chip-tool operationalcredentials read feature-map 1 0 - - label: "Send events/messages to DUT from TH" + [1649423105.884270][3334:3339] CHIP:TOO: Response Failure: IM Error 0x00000586: General error: 0x86 (UNSUPPORTED_ATTRIBUTE) + [1649423105.884373][3334:3339] CHIP:EM: Sending Standalone Ack for MessageCounter:5943193 on exchange 30408i + disabled: true + - label: "TH reads AttributeList from DUT" + verification: | + ubuntu@ubuntu:~/sethu-apr1/connectedhomeip/examples/chip-tool/out/debug$ ./chip-tool operationalcredentials read attribute-list 1 0 + + [1649423226.138143][3345:3350] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_003E Attribute 0x0000_FFFB DataVersion: 698307857 + [1649423226.138237][3345:3350] CHIP:TOO: AttributeList: 10 entries + [1649423226.138287][3345:3350] CHIP:TOO: [1]: 0 + [1649423226.138317][3345:3350] CHIP:TOO: [2]: 1 + [1649423226.138345][3345:3350] CHIP:TOO: [3]: 2 + [1649423226.138373][3345:3350] CHIP:TOO: [4]: 3 + [1649423226.138401][3345:3350] CHIP:TOO: [5]: 4 + [1649423226.138429][3345:3350] CHIP:TOO: [6]: 5 + [1649423226.138457][3345:3350] CHIP:TOO: [7]: 65528 + [1649423226.138485][3345:3350] CHIP:TOO: [8]: 65529 + [1649423226.138513][3345:3350] CHIP:TOO: [9]: 65531 + [1649423226.138541][3345:3350] CHIP:TOO: [10]: 65533 + [1649423226.138683][3345:3350] CHIP:EM: Sending Standalone Ack for MessageCounter:185027 on exchange 31246i + disabled: true + - label: "TH reads EventList from DUT" + verification: | + No Event-list is on attributes list disabled: true + - label: "TH reads AcceptedCommandList from DUT" + verification: | + ubuntu@ubuntu:~/sethu-apr1/connectedhomeip/examples/chip-tool/out/debug$ ./chip-tool operationalcredentials read accepted-command-list 1 0 - - label: "Reboot the DUT" + [1649423499.262187][3365:3370] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_003E Attribute 0x0000_FFF9 DataVersion: 698307857 + [1649423499.262316][3365:3370] CHIP:TOO: AcceptedCommandList: 9 entries + [1649423499.262386][3365:3370] CHIP:TOO: [1]: 0 + [1649423499.262430][3365:3370] CHIP:TOO: [2]: 2 + [1649423499.262472][3365:3370] CHIP:TOO: [3]: 4 + [1649423499.262513][3365:3370] CHIP:TOO: [4]: 6 + [1649423499.262553][3365:3370] CHIP:TOO: [5]: 7 + [1649423499.262593][3365:3370] CHIP:TOO: [6]: 9 + [1649423499.262635][3365:3370] CHIP:TOO: [7]: 10 + [1649423499.262676][3365:3370] CHIP:TOO: [8]: 11 + [1649423499.262717][3365:3370] CHIP:TOO: [9]: 12 + [1649423499.262866][3365:3370] CHIP:EM: Sending Standalone Ack for MessageCounter:8288254 on exchange 44255i disabled: true + - label: "TH reads GeneratedCommandList from DUT" + verification: | + ubuntu@ubuntu:~/sethu-apr1/connectedhomeip/examples/chip-tool/out/debug$ ./chip-tool operationalcredentials read generated-command-list 1 0 - - label: "Factory Reset the DUT" + [1649423586.012638][3376:3381] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_003E Attribute 0x0000_FFF8 DataVersion: 698307857 + [1649423586.012746][3376:3381] CHIP:TOO: GeneratedCommandList: 4 entries + [1649423586.012809][3376:3381] CHIP:TOO: [1]: 1 + [1649423586.012848][3376:3381] CHIP:TOO: [2]: 3 + [1649423586.012884][3376:3381] CHIP:TOO: [3]: 5 + [1649423586.012919][3376:3381] CHIP:TOO: [4]: 8 + [1649423586.013057][3376:3381] CHIP:EM: Sending Standalone Ack for MessageCounter:4917669 on exchange 24524i disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_DM_2_3.yaml b/src/app/tests/suites/certification/Test_TC_DM_2_3.yaml deleted file mode 100644 index b88de7f9b24f37..00000000000000 --- a/src/app/tests/suites/certification/Test_TC_DM_2_3.yaml +++ /dev/null @@ -1,57 +0,0 @@ -# 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: 10.2.3. [TC-DM-2.3] Operational Credential Commands [DUT - Commissioner] - -config: - nodeId: 0x12344321 - cluster: "Basic" - endpoint: 0 - -tests: - - label: "Commission TH to DUT" - verification: | - - disabled: true - - - label: "DUT Sends Attestation Request to TH" - verification: | - - disabled: true - - - label: "DUT Sends Attestation Certificate Chain Request to TH" - verification: | - - disabled: true - - - label: "DUT Sends CSR Request to TH" - verification: | - - disabled: true - - - label: "DUT Sends Add Trusted Root Certificate Request to TH" - verification: | - - disabled: true - - - label: "DUT Sends Add Op Cert Request to TH" - verification: | - - disabled: true - - - label: "Verify DUT and TH are on the same Fabric" - verification: | - - disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_IDM_2_2.yaml b/src/app/tests/suites/certification/Test_TC_IDM_2_2.yaml index 1ae5aaa1782ac1..a8dd1f7d82f0eb 100644 --- a/src/app/tests/suites/certification/Test_TC_IDM_2_2.yaml +++ b/src/app/tests/suites/certification/Test_TC_IDM_2_2.yaml @@ -13,7 +13,7 @@ # 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: 19.2.2. [TC-IDM-2.2] Report Data Action from DUT to TH [DUT - Controller] +name: 19.2.2. [TC-IDM-2.2] Report Data Action from DUT to TH config: nodeId: 0x12344321 @@ -27,9 +27,42 @@ tests: CommandDataIB, which has the specific Endpoint, Specific Cluster and Specific Attribute. On receipt of this message, DUT should send a report data action with the attribute value to the DUT." - verification: - "In case of chip tool, here is an example command to use sudo - ./chip-tool identify read identify-time 1 1" + verification: | + In case of chip tool, here is an example command to use + '' ./chip-tool identify read identify-time 1 1 + + + + TH side---Verify we are getting right attribute value on TH when we sent above command + + [1650358005665] [85455:1222335] CHIP: [DMG] ReportDataMessage = + [1650358005665] [85455:1222335] CHIP: [DMG] { + [1650358005665] [85455:1222335] CHIP: [DMG] AttributeReportIBs = + [1650358005665] [85455:1222335] CHIP: [DMG] [ + [1650358005665] [85455:1222335] CHIP: [DMG] AttributeReportIB = + [1650358005665] [85455:1222335] CHIP: [DMG] { + [1650358005665] [85455:1222335] CHIP: [DMG] AttributeDataIB = + [1650358005665] [85455:1222335] CHIP: [DMG] { + [1650358005665] [85455:1222335] CHIP: [DMG] DataVersion = 0x1f79ca06, + [1650358005665] [85455:1222335] CHIP: [DMG] AttributePathIB = + [1650358005665] [85455:1222335] CHIP: [DMG] { + [1650358005665] [85455:1222335] CHIP: [DMG] Endpoint = 0x1, + [1650358005665] [85455:1222335] CHIP: [DMG] Cluster = 0x3, + [1650358005665] [85455:1222335] CHIP: [DMG] Attribute = 0x0000_0000, + [1650358005665] [85455:1222335] CHIP: [DMG] } + [1650358005665] [85455:1222335] CHIP: [DMG] + [1650358005665] [85455:1222335] CHIP: [DMG] Data = 0, + [1650358005665] [85455:1222335] CHIP: [DMG] }, + [1650358005665] [85455:1222335] CHIP: [DMG] + [1650358005665] [85455:1222335] CHIP: [DMG] }, + [1650358005665] [85455:1222335] CHIP: [DMG] + [1650358005665] [85455:1222335] CHIP: [DMG] ], + [1650358005665] [85455:1222335] CHIP: [DMG] + [1650358005665] [85455:1222335] CHIP: [DMG] SuppressResponse = true, + [1650358005665] [85455:1222335] CHIP: [DMG] InteractionModelRevision = 1 + [1650358005665] [85455:1222335] CHIP: [DMG] } + [1650358005665] [85455:1222335] CHIP: [TOO] Endpoint: 1 Cluster: 0x0000_0003 Attribute 0x0000_0000 DataVersion: 528075270 + [1650358005665] [85455:1222335] CHIP: [TOO] identify time: 0 disabled: true - label: @@ -38,9 +71,35 @@ tests: [[Endpoint = Endpoint1, Cluster = ClusterID]] On receipt of this message, DUT should send a report data action with the attribute value to the DUT." - verification: - "In case of chip tool, here is an example command to use sudo - ./chip-tool any read-by-id 0x3 0xFFFFFFFF 1 0" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool any read-by-id 0x3 0xFFFFFFFF 1 0 + + TH side---Verify we are getting right attribute value on TH when we sent above command + + [1650358167494] [85475:1223021] CHIP: [TOO] Endpoint: 0 Cluster: 0x0000_0003 Attribute 0x0000_0000 DataVersion: 3061827023 + [1650358167494] [85475:1223021] CHIP: [TOO] identify time: 0 + [1650358167494] [85475:1223021] CHIP: [TOO] Endpoint: 0 Cluster: 0x0000_0003 Attribute 0x0000_0001 DataVersion: 3061827023 + [1650358167494] [85475:1223021] CHIP: [TOO] identify type: 2 + [1650358167494] [85475:1223021] CHIP: [TOO] Endpoint: 0 Cluster: 0x0000_0003 Attribute 0x0000_FFFD DataVersion: 3061827023 + [1650358167494] [85475:1223021] CHIP: [TOO] ClusterRevision: 4 + [1650358167494] [85475:1223021] CHIP: [TOO] Endpoint: 0 Cluster: 0x0000_0003 Attribute 0x0000_FFF8 DataVersion: 3061827023 + [1650358167494] [85475:1223021] CHIP: [TOO] GeneratedCommandList: 1 entries + [1650358167494] [85475:1223021] CHIP: [TOO] [1]: 0 + [1650358167494] [85475:1223021] CHIP: [TOO] Endpoint: 0 Cluster: 0x0000_0003 Attribute 0x0000_FFF9 DataVersion: 3061827023 + [1650358167494] [85475:1223021] CHIP: [TOO] AcceptedCommandList: 3 entries + [1650358167494] [85475:1223021] CHIP: [TOO] [1]: 0 + [1650358167494] [85475:1223021] CHIP: [TOO] [2]: 1 + [1650358167494] [85475:1223021] CHIP: [TOO] [3]: 64 + [1650358167494] [85475:1223021] CHIP: [TOO] Endpoint: 0 Cluster: 0x0000_0003 Attribute 0x0000_FFFB DataVersion: 3061827023 + [1650358167494] [85475:1223021] CHIP: [TOO] AttributeList: 6 entries + [1650358167494] [85475:1223021] CHIP: [TOO] [1]: 0 + [1650358167494] [85475:1223021] CHIP: [TOO] [2]: 1 + [1650358167494] [85475:1223021] CHIP: [TOO] [3]: 65528 + [1650358167494] [85475:1223021] CHIP: [TOO] [4]: 65529 + [1650358167494] [85475:1223021] CHIP: [TOO] [5]: 65531 + [1650358167494] [85475:1223021] CHIP: [TOO] [6]: 65533 disabled: true - label: @@ -49,9 +108,12 @@ tests: = ClusterID, Attribute = AttributeID]] On receipt of this message, DUT should send a report data action with the attribute value from all the Endpoints to the DUT." - verification: - "In case of chip tool, here is an example command to use ./chip-tool - any read-by-id 0x03 1 1 0xffff" + verification: | + In case of chip tool, here is an example command to use + + ./chip-tool any read-by-id 0x03 1 1 0xffff + + TH side---Verify we are getting all supported right attribute value on TH when we sent above command disabled: true - label: @@ -60,9 +122,12 @@ tests: [[Endpoint = Endpoint1, Attribute = AttributeID]] On receipt of this message, DUT should send a report data action with the attribute value from all the clusters to the DUT." - verification: - "In case of chip tool, here is an example command to use sudo - ./chip-tool any read-by-id 0xFFFFFFFF 0 1 1" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool any read-by-id 0xFFFFFFFF 0 1 1 + + TH side---Verify we are getting all supported right attribute value on TH when we sent above command disabled: true - label: @@ -70,155 +135,602 @@ tests: all attributes from all clusters AttributePath = [[]] On receipt of this message, DUT should send a report data action with the attribute value from all the clusters to the DUT." - verification: - "In case of chip tool, here is an example command to use sudo - ./chip-tool any read-by-id 0xFFFFFFFF 0xFFFFFFFF 1 1" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool any read-by-id 0xFFFFFFFF 0xFFFFFFFF 1 0xFFFF + + TH side---Verify we are getting all supported right attribute value on TH when we sent above command disabled: true - label: "[Optional] TH sends the Read Request Message to the DUT to read an attribute of data type bool. DUT responds with the report data action with the right attribute value." - verification: - "In case of chip tool, here is an example command to use sudo - ./chip-tool onoff read on-off 1 1" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool onoff read on-off 1 1 + + TH side---Verify we are getting ReportData message path(EndpointID, AttributeID, ClusterID ) same as provided data sent in the above command. + + [1650360287270] [85704:1230840] CHIP: [DMG] ReportDataMessage = + [1650360287270] [85704:1230840] CHIP: [DMG] { + [1650360287270] [85704:1230840] CHIP: [DMG] AttributeReportIBs = + [1650360287270] [85704:1230840] CHIP: [DMG] [ + [1650360287270] [85704:1230840] CHIP: [DMG] AttributeReportIB = + [1650360287270] [85704:1230840] CHIP: [DMG] { + [1650360287270] [85704:1230840] CHIP: [DMG] AttributeDataIB = + [1650360287270] [85704:1230840] CHIP: [DMG] { + [1650360287270] [85704:1230840] CHIP: [DMG] DataVersion = 0xdc20dc44, + [1650360287270] [85704:1230840] CHIP: [DMG] AttributePathIB = + [1650360287270] [85704:1230840] CHIP: [DMG] { + [1650360287270] [85704:1230840] CHIP: [DMG] Endpoint = 0x1, + [1650360287270] [85704:1230840] CHIP: [DMG] Cluster = 0x6, + [1650360287270] [85704:1230840] CHIP: [DMG] Attribute = 0x0000_0000, + [1650360287270] [85704:1230840] CHIP: [DMG] } + [1650360287270] [85704:1230840] CHIP: [DMG] + [1650360287270] [85704:1230840] CHIP: [DMG] Data = false, + [1650360287270] [85704:1230840] CHIP: [DMG] }, + [1650360287270] [85704:1230840] CHIP: [DMG] + [1650360287270] [85704:1230840] CHIP: [DMG] }, + [1650360287270] [85704:1230840] CHIP: [DMG] + [1650360287270] [85704:1230840] CHIP: [DMG] ], + [1650360287270] [85704:1230840] CHIP: [DMG] + [1650360287270] [85704:1230840] CHIP: [DMG] SuppressResponse = true, + [1650360287270] [85704:1230840] CHIP: [DMG] InteractionModelRevision = 1 + [1650360287270] [85704:1230840] CHIP: [DMG] } + [1650360287270] [85704:1230840] CHIP: [TOO] Endpoint: 1 Cluster: 0x0000_0006 Attribute 0x0000_0000 DataVersion: 3693141060 + [1650360287270] [85704:1230840] CHIP: [TOO] OnOff: FALSE disabled: true - label: "[Optional] TH sends the Read Request Message to the DUT to read an attribute of data type string. DUT responds with the report data action with the right attribute value." - verification: - "In case of chip tool, here is an example command to use sudo - ./chip-tool modeselect read description 1 1" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool modeselect read description 1 1 + + TH side---Verify we are getting ReportData message path(EndpointID, AttributeID, ClusterID ) same as provided data sent in the above command. + + [1650360466457] [85724:1231451] CHIP: [DMG] ReportDataMessage = + [1650360466457] [85724:1231451] CHIP: [DMG] { + [1650360466457] [85724:1231451] CHIP: [DMG] AttributeReportIBs = + [1650360466457] [85724:1231451] CHIP: [DMG] [ + [1650360466457] [85724:1231451] CHIP: [DMG] AttributeReportIB = + [1650360466457] [85724:1231451] CHIP: [DMG] { + [1650360466457] [85724:1231451] CHIP: [DMG] AttributeDataIB = + [1650360466457] [85724:1231451] CHIP: [DMG] { + [1650360466457] [85724:1231451] CHIP: [DMG] DataVersion = 0xfc73c079, + [1650360466457] [85724:1231451] CHIP: [DMG] AttributePathIB = + [1650360466457] [85724:1231451] CHIP: [DMG] { + [1650360466457] [85724:1231451] CHIP: [DMG] Endpoint = 0x1, + [1650360466457] [85724:1231451] CHIP: [DMG] Cluster = 0x50, + [1650360466457] [85724:1231451] CHIP: [DMG] Attribute = 0x0000_0000, + [1650360466457] [85724:1231451] CHIP: [DMG] } + [1650360466457] [85724:1231451] CHIP: [DMG] + [1650360466457] [85724:1231451] CHIP: [DMG] Data = "Coffee", + [1650360466457] [85724:1231451] CHIP: [DMG] }, + [1650360466457] [85724:1231451] CHIP: [DMG] + [1650360466457] [85724:1231451] CHIP: [DMG] }, + [1650360466457] [85724:1231451] CHIP: [DMG] + [1650360466457] [85724:1231451] CHIP: [DMG] ], + [1650360466457] [85724:1231451] CHIP: [DMG] + [1650360466457] [85724:1231451] CHIP: [DMG] SuppressResponse = true, + [1650360466457] [85724:1231451] CHIP: [DMG] InteractionModelRevision = 1 + [1650360466457] [85724:1231451] CHIP: [DMG] } + [1650360466457] [85724:1231451] CHIP: [TOO] Endpoint: 1 Cluster: 0x0000_0050 Attribute 0x0000_0000 DataVersion: 4235444345 + [1650360466457] [85724:1231451] CHIP: [TOO] Description: Coffee disabled: true - label: "[Optional] TH sends the Read Request Message to the DUT to read an attribute of data type unsigned integer. DUT responds with the report data action with the right attribute value." - verification: - "In case of chip tool, here is an example command to use sudo - ./chip-tool any read-by-id 0x3 0x1 1 0" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool any read-by-id 0x3 0x1 1 0 + + TH side---Verify we are getting ReportData message path(EndpointID, AttributeID, ClusterID ) same as provided data sent in the above command. + + [1650360573160] [85736:1231972] CHIP: [DMG] ReportDataMessage = + [1650360573160] [85736:1231972] CHIP: [DMG] { + [1650360573160] [85736:1231972] CHIP: [DMG] AttributeReportIBs = + [1650360573160] [85736:1231972] CHIP: [DMG] [ + [1650360573160] [85736:1231972] CHIP: [DMG] AttributeReportIB = + [1650360573160] [85736:1231972] CHIP: [DMG] { + [1650360573160] [85736:1231972] CHIP: [DMG] AttributeDataIB = + [1650360573160] [85736:1231972] CHIP: [DMG] { + [1650360573160] [85736:1231972] CHIP: [DMG] DataVersion = 0xb67fc5cf, + [1650360573160] [85736:1231972] CHIP: [DMG] AttributePathIB = + [1650360573160] [85736:1231972] CHIP: [DMG] { + [1650360573160] [85736:1231972] CHIP: [DMG] Endpoint = 0x0, + [1650360573160] [85736:1231972] CHIP: [DMG] Cluster = 0x3, + [1650360573160] [85736:1231972] CHIP: [DMG] Attribute = 0x0000_0001, + [1650360573160] [85736:1231972] CHIP: [DMG] } + [1650360573160] [85736:1231972] CHIP: [DMG] + [1650360573160] [85736:1231972] CHIP: [DMG] Data = 2, + [1650360573160] [85736:1231972] CHIP: [DMG] }, + [1650360573160] [85736:1231972] CHIP: [DMG] + [1650360573160] [85736:1231972] CHIP: [DMG] }, + [1650360573160] [85736:1231972] CHIP: [DMG] + [1650360573160] [85736:1231972] CHIP: [DMG] ], + [1650360573160] [85736:1231972] CHIP: [DMG] + [1650360573160] [85736:1231972] CHIP: [DMG] SuppressResponse = true, + [1650360573160] [85736:1231972] CHIP: [DMG] InteractionModelRevision = 1 + [1650360573160] [85736:1231972] CHIP: [DMG] } + [1650360573160] [85736:1231972] CHIP: [TOO] Endpoint: 0 Cluster: 0x0000_0003 Attribute 0x0000_0001 DataVersion: 3061827023 + [1650360573160] [85736:1231972] CHIP: [TOO] identify type: 2 disabled: true - label: "[Optional] TH sends the Read Request Message to the DUT to read an attribute of data type signed integer. DUT responds with the report data action with the right attribute value." - verification: - "In case of chip tool, here is an example command to use sudo - ./chip-tool pressuremeasurement read measured-value 1 1" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool pressuremeasurement read measured-value 1 1 + + Verify we are getting right attribute value on TH when we sent above command + + [1650360637967] [85753:1232470] CHIP: [DMG] ReportDataMessage = + [1650360637967] [85753:1232470] CHIP: [DMG] { + [1650360637967] [85753:1232470] CHIP: [DMG] AttributeReportIBs = + [1650360637967] [85753:1232470] CHIP: [DMG] [ + [1650360637967] [85753:1232470] CHIP: [DMG] AttributeReportIB = + [1650360637967] [85753:1232470] CHIP: [DMG] { + [1650360637967] [85753:1232470] CHIP: [DMG] AttributeDataIB = + [1650360637967] [85753:1232470] CHIP: [DMG] { + [1650360637967] [85753:1232470] CHIP: [DMG] DataVersion = 0x560e9d91, + [1650360637967] [85753:1232470] CHIP: [DMG] AttributePathIB = + [1650360637967] [85753:1232470] CHIP: [DMG] { + [1650360637967] [85753:1232470] CHIP: [DMG] Endpoint = 0x1, + [1650360637967] [85753:1232470] CHIP: [DMG] Cluster = 0x403, + [1650360637967] [85753:1232470] CHIP: [DMG] Attribute = 0x0000_0000, + [1650360637967] [85753:1232470] CHIP: [DMG] } + [1650360637967] [85753:1232470] CHIP: [DMG] + [1650360637967] [85753:1232470] CHIP: [DMG] Data = 0, + [1650360637967] [85753:1232470] CHIP: [DMG] }, + [1650360637967] [85753:1232470] CHIP: [DMG] + [1650360637967] [85753:1232470] CHIP: [DMG] }, + [1650360637967] [85753:1232470] CHIP: [DMG] + [1650360637967] [85753:1232470] CHIP: [DMG] ], + [1650360637967] [85753:1232470] CHIP: [DMG] + [1650360637967] [85753:1232470] CHIP: [DMG] SuppressResponse = true, + [1650360637967] [85753:1232470] CHIP: [DMG] InteractionModelRevision = 1 + [1650360637967] [85753:1232470] CHIP: [DMG] } + [1650360637967] [85753:1232470] CHIP: [TOO] Endpoint: 1 Cluster: 0x0000_0403 Attribute 0x0000_0000 DataVersion: 1443798417 + [1650360637967] [85753:1232470] CHIP: [TOO] MeasuredValue: 0 disabled: true - label: "[Optional] TH sends the Read Request Message to the DUT to read an attribute of data type floating point. DUT responds with the report data action with the right attribute value." - verification: "Currently the Spec is not supporting for this data type." + verification: | + DUT implementation required to verify read an attribute of data type floating point disabled: true - label: "[Optional] TH sends the Read Request Message to the DUT to read an attribute of data type Octet String. DUT responds with the report data action with the right attribute value." - verification: - "In case of chip tool, here is an example command to use sudo - ./chip-tool operationalcredentials read trusted-root-certificates 1 0" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool operationalcredentials read trusted-root-certificates 1 0 + + TH side--Verify we are getting right attribute value on TH when we sent above command + + [1650360694433] [85761:1232769] CHIP: [DMG] ReportDataMessage = + [1650360694433] [85761:1232769] CHIP: [DMG] { + [1650360694433] [85761:1232769] CHIP: [DMG] AttributeReportIBs = + [1650360694433] [85761:1232769] CHIP: [DMG] [ + [1650360694433] [85761:1232769] CHIP: [DMG] AttributeReportIB = + [1650360694433] [85761:1232769] CHIP: [DMG] { + [1650360694433] [85761:1232769] CHIP: [DMG] AttributeDataIB = + [1650360694433] [85761:1232769] CHIP: [DMG] { + [1650360694433] [85761:1232769] CHIP: [DMG] DataVersion = 0xb318d380, + [1650360694433] [85761:1232769] CHIP: [DMG] AttributePathIB = + [1650360694433] [85761:1232769] CHIP: [DMG] { + [1650360694433] [85761:1232769] CHIP: [DMG] Endpoint = 0x0, + [1650360694433] [85761:1232769] CHIP: [DMG] Cluster = 0x3e, + [1650360694433] [85761:1232769] CHIP: [DMG] Attribute = 0x0000_0004, + [1650360694433] [85761:1232769] CHIP: [DMG] } + [1650360694433] [85761:1232769] CHIP: [DMG] + [1650360694433] [85761:1232769] CHIP: [DMG] Data = [ + [1650360694433] [85761:1232769] CHIP: [DMG] + [1650360694433] [85761:1232769] CHIP: [DMG] ], + [1650360694433] [85761:1232769] CHIP: [DMG] }, + [1650360694434] [85761:1232769] CHIP: [DMG] + [1650360694434] [85761:1232769] CHIP: [DMG] }, + [1650360694434] [85761:1232769] CHIP: [DMG] + [1650360694434] [85761:1232769] CHIP: [DMG] AttributeReportIB = + [1650360694434] [85761:1232769] CHIP: [DMG] { + [1650360694434] [85761:1232769] CHIP: [DMG] AttributeDataIB = + [1650360694434] [85761:1232769] CHIP: [DMG] { + [1650360694434] [85761:1232769] CHIP: [DMG] DataVersion = 0xb318d380, + [1650360694434] [85761:1232769] CHIP: [DMG] AttributePathIB = + [1650360694434] [85761:1232769] CHIP: [DMG] { + [1650360694434] [85761:1232769] CHIP: [DMG] Endpoint = 0x0, + [1650360694434] [85761:1232769] CHIP: [DMG] Cluster = 0x3e, + [1650360694434] [85761:1232769] CHIP: [DMG] Attribute = 0x0000_0004, + [1650360694434] [85761:1232769] CHIP: [DMG] ListIndex = Null, + [1650360694434] [85761:1232769] CHIP: [DMG] } + [1650360694434] [85761:1232769] CHIP: [DMG] + [1650360694434] [85761:1232769] CHIP: [DMG] Data = [ + [1650360694434] [85761:1232769] CHIP: [DMG] 0x15, 0x30, 0x1, 0x1, 0x0, 0x24, 0x2, 0x1, 0x37, 0x3, 0x24, 0x14, 0x0, 0x18, 0x26, 0x4, 0x80, 0x22, 0x81, 0x27, 0x26, 0x5, 0x80, 0x25, 0x4d, 0x3a, 0x37, 0x6, 0x24, 0x14, 0x0, 0x18, 0x24, 0x7, 0x1, 0x24, 0x + [1650360694434] [85761:1232769] CHIP: [DMG] ] + [1650360694434] [85761:1232769] CHIP: [DMG] }, + [1650360694434] [85761:1232769] CHIP: [DMG] + [1650360694434] [85761:1232769] CHIP: [DMG] }, + [1650360694434] [85761:1232769] CHIP: [DMG] + [1650360694434] [85761:1232769] CHIP: [DMG] ], + [1650360694434] [85761:1232769] CHIP: [DMG] + [1650360694434] [85761:1232769] CHIP: [DMG] SuppressResponse = true, + [1650360694434] [85761:1232769] CHIP: [DMG] InteractionModelRevision = 1 + [1650360694434] [85761:1232769] CHIP: [DMG] } + [1650360694435] [85761:1232769] CHIP: [TOO] Endpoint: 0 Cluster: 0x0000_003E Attribute 0x0000_0004 DataVersion: 3004748672 + [1650360694435] [85761:1232769] CHIP: [TOO] TrustedRootCertificates: 1 entries disabled: true - label: "[Optional] TH sends the Read Request Message to the DUT to read an attribute of data type Struct. DUT responds with the report data action with the right attribute value." - verification: "Currently the Spec is not supporting for this data type." + verification: | + DUT implementation required to verify read an attribute of data type struct. disabled: true - label: "[Optional] TH sends the Read Request Message to the DUT to read an attribute of data type List. DUT responds with the report data action with the right attribute value." - verification: - "In case of chip tool, here is an example command to use sudo - ./chip-tool modeselect read supported-modes 1 1" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool modeselect read supported-modes 1 1 + + TH side---Verify we are getting right attribute value on TH when we sent above command + + [1650362184885] [85960:1238675] CHIP: [TOO] Endpoint: 1 Cluster: 0x0000_0050 Attribute 0x0000_0002 DataVersion: 4235444345 + [1650362184885] [85960:1238675] CHIP: [TOO] SupportedModes: 3 entries + [1650362184885] [85960:1238675] CHIP: [TOO] [1]: { + [1650362184885] [85960:1238675] CHIP: [TOO] Label: Black + [1650362184885] [85960:1238675] CHIP: [TOO] Mode: 0 + [1650362184885] [85960:1238675] CHIP: [TOO] SemanticTag: 0 + [1650362184885] [85960:1238675] CHIP: [TOO] } + [1650362184885] [85960:1238675] CHIP: [TOO] [2]: { + [1650362184885] [85960:1238675] CHIP: [TOO] Label: Cappuccino + [1650362184885] [85960:1238675] CHIP: [TOO] Mode: 4 + [1650362184885] [85960:1238675] CHIP: [TOO] SemanticTag: 0 + [1650362184885] [85960:1238675] CHIP: [TOO] } + [1650362184885] [85960:1238675] CHIP: [TOO] [3]: { + [1650362184885] [85960:1238675] CHIP: [TOO] Label: Espresso + [1650362184885] [85960:1238675] CHIP: [TOO] Mode: 7 + [1650362184885] [85960:1238675] CHIP: [TOO] SemanticTag: 0 + [1650362184885] [85960:1238675] CHIP: [TOO] } disabled: true - label: "[Optional] TH sends the Read Request Message to the DUT to read an attribute of data type enum. DUT responds with the report data action with the right attribute value." - verification: - "In case of chip tool, here is an example command to use sudo - ./chip-tool occupancysensing read occupancy-sensor-type 1 1" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool occupancysensing read occupancy-sensor-type 1 1 + + TH side---Verify we are getting right attribute value on TH when we sent above command + + + [1650362650962] [86020:1240713] CHIP: [DMG] ReportDataMessage = + [1650362650963] [86020:1240713] CHIP: [DMG] { + [1650362650963] [86020:1240713] CHIP: [DMG] AttributeReportIBs = + [1650362650963] [86020:1240713] CHIP: [DMG] [ + [1650362650963] [86020:1240713] CHIP: [DMG] AttributeReportIB = + [1650362650963] [86020:1240713] CHIP: [DMG] { + [1650362650963] [86020:1240713] CHIP: [DMG] AttributeDataIB = + [1650362650963] [86020:1240713] CHIP: [DMG] { + [1650362650963] [86020:1240713] CHIP: [DMG] DataVersion = 0xa301ff86, + [1650362650963] [86020:1240713] CHIP: [DMG] AttributePathIB = + [1650362650963] [86020:1240713] CHIP: [DMG] { + [1650362650963] [86020:1240713] CHIP: [DMG] Endpoint = 0x1, + [1650362650963] [86020:1240713] CHIP: [DMG] Cluster = 0x406, + [1650362650963] [86020:1240713] CHIP: [DMG] Attribute = 0x0000_0001, + [1650362650963] [86020:1240713] CHIP: [DMG] } + [1650362650963] [86020:1240713] CHIP: [DMG] + [1650362650963] [86020:1240713] CHIP: [DMG] Data = 0, + [1650362650963] [86020:1240713] CHIP: [DMG] }, + [1650362650963] [86020:1240713] CHIP: [DMG] + [1650362650963] [86020:1240713] CHIP: [DMG] }, + [1650362650963] [86020:1240713] CHIP: [DMG] + [1650362650963] [86020:1240713] CHIP: [DMG] ], + [1650362650963] [86020:1240713] CHIP: [DMG] + [1650362650963] [86020:1240713] CHIP: [DMG] SuppressResponse = true, + [1650362650963] [86020:1240713] CHIP: [DMG] InteractionModelRevision = 1 + [1650362650963] [86020:1240713] CHIP: [DMG] } + [1650362650963] [86020:1240713] CHIP: [TOO] Endpoint: 1 Cluster: 0x0000_0406 Attribute 0x0000_0001 DataVersion: 2734817158 + [1650362650963] [86020:1240713] CHIP: [TOO] occupancy sensor type: 0 disabled: true - label: "[Optional] TH sends the Read Request Message to the DUT to read an attribute of data type bitmap. DUT responds with the report data action with the right attribute value." - verification: - "In case of chip tool, here is an example command to use sudo - ./chip-tool levelcontrol read options 1 1" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool levelcontrol read options 1 1 + + TH side---Verify we are getting right attribute value on TH when we sent above command + + [1650362616022] [86014:1240558] CHIP: [DMG] ReportDataMessage = + [1650362616022] [86014:1240558] CHIP: [DMG] { + [1650362616022] [86014:1240558] CHIP: [DMG] AttributeReportIBs = + [1650362616022] [86014:1240558] CHIP: [DMG] [ + [1650362616022] [86014:1240558] CHIP: [DMG] AttributeReportIB = + [1650362616022] [86014:1240558] CHIP: [DMG] { + [1650362616022] [86014:1240558] CHIP: [DMG] AttributeDataIB = + [1650362616022] [86014:1240558] CHIP: [DMG] { + [1650362616022] [86014:1240558] CHIP: [DMG] DataVersion = 0x3355c36c, + [1650362616022] [86014:1240558] CHIP: [DMG] AttributePathIB = + [1650362616022] [86014:1240558] CHIP: [DMG] { + [1650362616022] [86014:1240558] CHIP: [DMG] Endpoint = 0x1, + [1650362616022] [86014:1240558] CHIP: [DMG] Cluster = 0x8, + [1650362616022] [86014:1240558] CHIP: [DMG] Attribute = 0x0000_000F, + [1650362616022] [86014:1240558] CHIP: [DMG] } + [1650362616022] [86014:1240558] CHIP: [DMG] + [1650362616022] [86014:1240558] CHIP: [DMG] Data = 0, + [1650362616022] [86014:1240558] CHIP: [DMG] }, + [1650362616022] [86014:1240558] CHIP: [DMG] + [1650362616022] [86014:1240558] CHIP: [DMG] }, + [1650362616022] [86014:1240558] CHIP: [DMG] + [1650362616022] [86014:1240558] CHIP: [DMG] ], + [1650362616022] [86014:1240558] CHIP: [DMG] + [1650362616022] [86014:1240558] CHIP: [DMG] SuppressResponse = true, + [1650362616022] [86014:1240558] CHIP: [DMG] InteractionModelRevision = 1 + [1650362616022] [86014:1240558] CHIP: [DMG] } + [1650362616022] [86014:1240558] CHIP: [TOO] Endpoint: 1 Cluster: 0x0000_0008 Attribute 0x0000_000F DataVersion: 861258604 + [1650362616022] [86014:1240558] CHIP: [TOO] options: 0 disabled: true - label: "TH sends the Read Request Message to the DUT to read any attribute to an unsupported node. DUT responds with the report data action." - verification: - "Unsupported for TE8 - - https://github.com/CHIP-Specifications/connectedhomeip-spec/pull/4999" + verification: | + https://github.com/project-chip/connectedhomeip/issues/17500 disabled: true - label: "TH sends the Read Request Message to the DUT to read any attribute to an unsupported Endpoint. DUT responds with the report data action." - verification: - "In case of chip tool, here is an example command to use sudo - ./chip-tool levelcontrol read-by-id 0 1 4" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool levelcontrol read-by-id 0 1 4 + + TH side---Verify we are getting "status = 0x7f (UNSUPPORTED_ENDPOINT)" for above command. + + + [1650361252618] [85838:1235112] CHIP: [DMG] ReportDataMessage = + [1650361252618] [85838:1235112] CHIP: [DMG] { + [1650361252618] [85838:1235112] CHIP: [DMG] AttributeReportIBs = + [1650361252618] [85838:1235112] CHIP: [DMG] [ + [1650361252618] [85838:1235112] CHIP: [DMG] AttributeReportIB = + [1650361252618] [85838:1235112] CHIP: [DMG] { + [1650361252618] [85838:1235112] CHIP: [DMG] AttributeStatusIB = + [1650361252618] [85838:1235112] CHIP: [DMG] { + [1650361252618] [85838:1235112] CHIP: [DMG] AttributePathIB = + [1650361252618] [85838:1235112] CHIP: [DMG] { + [1650361252618] [85838:1235112] CHIP: [DMG] Endpoint = 0x4, + [1650361252618] [85838:1235112] CHIP: [DMG] Cluster = 0x8, + [1650361252618] [85838:1235112] CHIP: [DMG] Attribute = 0x0000_0000, + [1650361252618] [85838:1235112] CHIP: [DMG] } + [1650361252618] [85838:1235112] CHIP: [DMG] + [1650361252618] [85838:1235112] CHIP: [DMG] StatusIB = + [1650361252618] [85838:1235112] CHIP: [DMG] { + [1650361252618] [85838:1235112] CHIP: [DMG] status = 0x7f (UNSUPPORTED_ENDPOINT), + [1650361252618] [85838:1235112] CHIP: [DMG] }, + [1650361252618] [85838:1235112] CHIP: [DMG] + [1650361252618] [85838:1235112] CHIP: [DMG] }, + [1650361252618] [85838:1235112] CHIP: [DMG] + [1650361252618] [85838:1235112] CHIP: [DMG] }, + [1650361252618] [85838:1235112] CHIP: [DMG] + [1650361252618] [85838:1235112] CHIP: [DMG] ], + [1650361252618] [85838:1235112] CHIP: [DMG] + [1650361252618] [85838:1235112] CHIP: [DMG] SuppressResponse = true, + [1650361252618] [85838:1235112] CHIP: [DMG] InteractionModelRevision = 1 + [1650361252618] [85838:1235112] CHIP: [DMG] } + [1650361252618] [85838:1235112] CHIP: [TOO] Response Failure: IM Error 0x0000057F: General error: 0x7f (UNSUPPORTED_ENDPOINT) disabled: true - label: "TH sends the Read Request Message to the DUT to read any attribute to an unsupported cluster. DUT responds with the report data action." - verification: - "In case of chip tool, here is an example command to use ./chip-tool - any command-by-id 0x0003 0 1 1 2" + verification: | + In case of chip tool, here is an example command to use + + ./chip-tool any command-by-id 0x0003 0 1 1 2 + + TH side---Verify we are getting " status = 0xc3 (UNSUPPORTED_CLUSTER)" for above command. + + [1650361310127] [85846:1235360] CHIP: [DMG] InvokeResponseMessage = + [1650361310127] [85846:1235360] CHIP: [DMG] { + [1650361310127] [85846:1235360] CHIP: [DMG] suppressResponse = false, + [1650361310127] [85846:1235360] CHIP: [DMG] InvokeResponseIBs = + [1650361310127] [85846:1235360] CHIP: [DMG] [ + [1650361310127] [85846:1235360] CHIP: [DMG] InvokeResponseIB = + [1650361310127] [85846:1235360] CHIP: [DMG] { + [1650361310127] [85846:1235360] CHIP: [DMG] CommandStatusIB = + [1650361310127] [85846:1235360] CHIP: [DMG] { + [1650361310127] [85846:1235360] CHIP: [DMG] CommandPathIB = + [1650361310127] [85846:1235360] CHIP: [DMG] { + [1650361310127] [85846:1235360] CHIP: [DMG] EndpointId = 0x2, + [1650361310127] [85846:1235360] CHIP: [DMG] ClusterId = 0x3, + [1650361310128] [85846:1235360] CHIP: [DMG] CommandId = 0x0, + [1650361310128] [85846:1235360] CHIP: [DMG] }, + [1650361310128] [85846:1235360] CHIP: [DMG] + [1650361310128] [85846:1235360] CHIP: [DMG] StatusIB = + [1650361310128] [85846:1235360] CHIP: [DMG] { + [1650361310128] [85846:1235360] CHIP: [DMG] status = 0xc3 (UNSUPPORTED_CLUSTER), + [1650361310128] [85846:1235360] CHIP: [DMG] }, + [1650361310128] [85846:1235360] CHIP: [DMG] + [1650361310128] [85846:1235360] CHIP: [DMG] }, + [1650361310128] [85846:1235360] CHIP: [DMG] + [1650361310128] [85846:1235360] CHIP: [DMG] }, + [1650361310128] [85846:1235360] CHIP: [DMG] + [1650361310128] [85846:1235360] CHIP: [DMG] ], + [1650361310128] [85846:1235360] CHIP: [DMG] + [1650361310128] [85846:1235360] CHIP: [DMG] InteractionModelRevision = 1 + [1650361310128] [85846:1235360] CHIP: [DMG] }, + [1650361310128] [85846:1235360] CHIP: [DMG] Received Command Response Status for Endpoint=2 Cluster=0x0000_0003 Command=0x0000_0000 Status=0xc3 + [1650361310128] [85846:1235360] CHIP: [TOO] Error: IM Error 0x000005C3: General error: 0xc3 (UNSUPPORTED_CLUSTER) disabled: true - label: "TH sends the Read Request Message to the DUT to read an unsupported attribute DUT responds with the report data action." - verification: "Check for optional one that is not implemented" + verification: | + '' ./chip-tool thermostat read outdoor-temperature 1 1 + + TH side---Verify we are getting "status = 0x86 (UNSUPPORTED_ATTRIBUTE)" for above command. + + [1650361351617] [85853:1235541] CHIP: [DMG] ReportDataMessage = + [1650361351617] [85853:1235541] CHIP: [DMG] { + [1650361351617] [85853:1235541] CHIP: [DMG] AttributeReportIBs = + [1650361351617] [85853:1235541] CHIP: [DMG] [ + [1650361351617] [85853:1235541] CHIP: [DMG] AttributeReportIB = + [1650361351617] [85853:1235541] CHIP: [DMG] { + [1650361351617] [85853:1235541] CHIP: [DMG] AttributeStatusIB = + [1650361351617] [85853:1235541] CHIP: [DMG] { + [1650361351617] [85853:1235541] CHIP: [DMG] AttributePathIB = + [1650361351617] [85853:1235541] CHIP: [DMG] { + [1650361351617] [85853:1235541] CHIP: [DMG] Endpoint = 0x1, + [1650361351617] [85853:1235541] CHIP: [DMG] Cluster = 0x201, + [1650361351617] [85853:1235541] CHIP: [DMG] Attribute = 0x0000_0001, + [1650361351617] [85853:1235541] CHIP: [DMG] } + [1650361351617] [85853:1235541] CHIP: [DMG] + [1650361351617] [85853:1235541] CHIP: [DMG] StatusIB = + [1650361351617] [85853:1235541] CHIP: [DMG] { + [1650361351617] [85853:1235541] CHIP: [DMG] status = 0x86 (UNSUPPORTED_ATTRIBUTE), + [1650361351617] [85853:1235541] CHIP: [DMG] }, + [1650361351617] [85853:1235541] CHIP: [DMG] + [1650361351617] [85853:1235541] CHIP: [DMG] }, + [1650361351617] [85853:1235541] CHIP: [DMG] + [1650361351617] [85853:1235541] CHIP: [DMG] }, + [1650361351617] [85853:1235541] CHIP: [DMG] + [1650361351617] [85853:1235541] CHIP: [DMG] ], + [1650361351617] [85853:1235541] CHIP: [DMG] + [1650361351617] [85853:1235541] CHIP: [DMG] SuppressResponse = true, + [1650361351617] [85853:1235541] CHIP: [DMG] InteractionModelRevision = 1 + [1650361351617] [85853:1235541] CHIP: [DMG] } + [1650361351617] [85853:1235541] CHIP: [TOO] Response Failure: IM Error 0x00000586: General error: 0x86 (UNSUPPORTED_ATTRIBUTE) + + or + + '' ./chip-tool applicationlauncher read feature-map 1 1 disabled: true - label: "TH sends the Read Request Message to the DUT to read an attribute which is not readable. DUT responds with the report data action." - verification: "Need to find more info" + verification: | + DUT implementation required to verify read an attribute which is nor readable disabled: true - label: "TH sends the Read Request Message to the DUT to read an attribute in the path that requires a privilege that is not granted for the cluster in the path. DUT responds with the report data action." - verification: "Unsupported in TE8 - Out of scope" + verification: | + '' ./chip-tool basic read vendor-name 2 0 --commissioner-nodeid 332211 + + TH side---Verify we are getting "status = 0x7e (UNSUPPORTED_ACCESS)" for above command. + + [1650361510244] [85874:1236133] CHIP: [DMG] ReportDataMessage = + [1650361510244] [85874:1236133] CHIP: [DMG] { + [1650361510244] [85874:1236133] CHIP: [DMG] AttributeReportIBs = + [1650361510244] [85874:1236133] CHIP: [DMG] [ + [1650361510244] [85874:1236133] CHIP: [DMG] AttributeReportIB = + [1650361510244] [85874:1236133] CHIP: [DMG] { + [1650361510244] [85874:1236133] CHIP: [DMG] AttributeStatusIB = + [1650361510244] [85874:1236133] CHIP: [DMG] { + [1650361510244] [85874:1236133] CHIP: [DMG] AttributePathIB = + [1650361510244] [85874:1236133] CHIP: [DMG] { + [1650361510244] [85874:1236133] CHIP: [DMG] Endpoint = 0x0, + [1650361510244] [85874:1236133] CHIP: [DMG] Cluster = 0x28, + [1650361510244] [85874:1236133] CHIP: [DMG] Attribute = 0x0000_0001, + [1650361510244] [85874:1236133] CHIP: [DMG] } + [1650361510244] [85874:1236133] CHIP: [DMG] + [1650361510244] [85874:1236133] CHIP: [DMG] StatusIB = + [1650361510244] [85874:1236133] CHIP: [DMG] { + [1650361510244] [85874:1236133] CHIP: [DMG] status = 0x7e (UNSUPPORTED_ACCESS), + [1650361510244] [85874:1236133] CHIP: [DMG] }, + [1650361510244] [85874:1236133] CHIP: [DMG] + [1650361510244] [85874:1236133] CHIP: [DMG] }, + [1650361510244] [85874:1236133] CHIP: [DMG] + [1650361510244] [85874:1236133] CHIP: [DMG] }, + [1650361510244] [85874:1236133] CHIP: [DMG] + [1650361510244] [85874:1236133] CHIP: [DMG] ], + [1650361510244] [85874:1236133] CHIP: [DMG] + [1650361510244] [85874:1236133] CHIP: [DMG] SuppressResponse = true, + [1650361510244] [85874:1236133] CHIP: [DMG] InteractionModelRevision = 1 + [1650361510244] [85874:1236133] CHIP: [DMG] } + [1650361510244] [85874:1236133] CHIP: [TOO] Response Failure: IM Error 0x0000057E: General error: 0x7e (UNSUPPORTED_ACCESS) disabled: true - label: "TH sends the Read Request Message to the DUT to read an attribute in the path that is fabric scoped, and the associated fabric does not match the accessing fabric. DUT responds with the Report Data action" - verification: "Unsupported in TE8 - Out of scope" + verification: | + https://github.com/project-chip/connectedhomeip/issues/16569 disabled: true - label: "TH sends the Read Request Message to the DUT to read an attribute Repeat the above steps 3 times." - verification: - "In case of chip tool, here is an example command to use sudo - ./chip-tool occupancysensing read occupancy 1 1 sudo ./chip-tool - occupancysensing read occupancy 1 1 sudo ./chip-tool occupancysensing - read occupancy 1 1" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool occupancysensing read occupancy 1 1 (send same command 3 times) + + TH side---Verify we are getting ReportData message path and value (EndpointID, AttributeID, ClusterID ) same as provided data sent in the above command + (verify the values we are getting same when we send same command 3 times) + + [1650362704154] [86027:1240909] CHIP: [DMG] ReportDataMessage = + [1650362704154] [86027:1240909] CHIP: [DMG] { + [1650362704154] [86027:1240909] CHIP: [DMG] AttributeReportIBs = + [1650362704154] [86027:1240909] CHIP: [DMG] [ + [1650362704154] [86027:1240909] CHIP: [DMG] AttributeReportIB = + [1650362704154] [86027:1240909] CHIP: [DMG] { + [1650362704154] [86027:1240909] CHIP: [DMG] AttributeDataIB = + [1650362704154] [86027:1240909] CHIP: [DMG] { + [1650362704154] [86027:1240909] CHIP: [DMG] DataVersion = 0xa301ff86, + [1650362704154] [86027:1240909] CHIP: [DMG] AttributePathIB = + [1650362704154] [86027:1240909] CHIP: [DMG] { + [1650362704154] [86027:1240909] CHIP: [DMG] Endpoint = 0x1, + [1650362704154] [86027:1240909] CHIP: [DMG] Cluster = 0x406, + [1650362704154] [86027:1240909] CHIP: [DMG] Attribute = 0x0000_0000, + [1650362704154] [86027:1240909] CHIP: [DMG] } + [1650362704154] [86027:1240909] CHIP: [DMG] + [1650362704154] [86027:1240909] CHIP: [DMG] Data = 0, + [1650362704154] [86027:1240909] CHIP: [DMG] }, + [1650362704154] [86027:1240909] CHIP: [DMG] + [1650362704154] [86027:1240909] CHIP: [DMG] }, + [1650362704154] [86027:1240909] CHIP: [DMG] + [1650362704154] [86027:1240909] CHIP: [DMG] ], + [1650362704154] [86027:1240909] CHIP: [DMG] + [1650362704154] [86027:1240909] CHIP: [DMG] SuppressResponse = true, + [1650362704154] [86027:1240909] CHIP: [DMG] InteractionModelRevision = 1 + [1650362704154] [86027:1240909] CHIP: [DMG] } + [1650362704154] [86027:1240909] CHIP: [TOO] Endpoint: 1 Cluster: 0x0000_0406 Attribute 0x0000_0000 DataVersion: 2734817158 + [1650362704154] [86027:1240909] CHIP: [TOO] occupancy: 0 disabled: true - label: @@ -227,9 +739,12 @@ tests: attribute AttributePath = [[ Attribute = AttributeID]] On receipt of this message, DUT should send a report data action with the attribute value from all the clusters and endpoints to the DUT." - verification: - "In case of chip tool, here is an example command to use sudo - ./chip-tool any read-by-id 0xFFFFFFFF 0 1 0xFFFF" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool any read-by-id 0xFFFFFFFF 0 1 0xFFFF + + TH side---Verify we are getting all supported right attribute value on TH when we sent above command disabled: true - label: @@ -238,9 +753,12 @@ tests: AttributePath = [[ Endpoint = EndpointID]] On receipt of this message, DUT should send a report data action with all the attribute values from all the clusters from that particular endpointID to the DUT." - verification: - "In case of chip tool, here is an example command to use sudo - ./chip-tool any read-by-id 0xFFFFFFFF 0xFFFFFFFF 1 1" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool any read-by-id 0xFFFFFFFF 0xFFFFFFFF 1 1 + + TH side---Verify we are getting all supported right attribute value on TH when we sent above command disabled: true - label: @@ -249,9 +767,12 @@ tests: AttributePath = [[ Cluster = ClusterID]] On receipt of this message, DUT should send a report data action with all the attribute values from all the endpoints from that particular ClusterID to the DUT." - verification: - "In case of chip tool, here is an example command to use sudo - ./chip-tool any read-by-id 0x3 0xFFFFFFFF 1 0xFFFF" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool any read-by-id 0x3 0xFFFFFFFF 1 0xFFFF + + TH side---Verify we are getting all supported right attribute value on TH when we sent above command disabled: true - label: @@ -260,9 +781,45 @@ tests: attribute value with the DataVersion of the cluster. TH sends a second read request to the same cluster with the DataVersionFilter Field set with the dataversion value received before." - verification: - "Unsupported in TE8 - Out of scope - Need to file ticket (No - DataVersionFilter available)" + verification: | + ./chip-tool identify read identify-time 1 1 + + [1650615356.464413][2439:2444] CHIP:DMG: ReportDataMessage = + [1650615356.464525][2439:2444] CHIP:DMG: { + [1650615356.464597][2439:2444] CHIP:DMG: AttributeReportIBs = + [1650615356.464651][2439:2444] CHIP:DMG: [ + [1650615356.464690][2439:2444] CHIP:DMG: AttributeReportIB = + [1650615356.464743][2439:2444] CHIP:DMG: { + [1650615356.464785][2439:2444] CHIP:DMG: AttributeDataIB = + [1650615356.464926][2439:2444] CHIP:DMG: { + [1650615356.464975][2439:2444] CHIP:DMG: DataVersion = 0x9125b20e, + [1650615356.465027][2439:2444] CHIP:DMG: AttributePathIB = + [1650615356.465076][2439:2444] CHIP:DMG: { + [1650615356.465129][2439:2444] CHIP:DMG: Endpoint = 0x1, + [1650615356.465308][2439:2444] CHIP:DMG: Cluster = 0x3, + [1650615356.465364][2439:2444] CHIP:DMG: Attribute = 0x0000_0000, + [1650615356.465415][2439:2444] CHIP:DMG: } + [1650615356.465471][2439:2444] CHIP:DMG: + [1650615356.465523][2439:2444] CHIP:DMG: Data = 0, + [1650615356.465576][2439:2444] CHIP:DMG: }, + [1650615356.465661][2439:2444] CHIP:DMG: + [1650615356.465703][2439:2444] CHIP:DMG: }, + [1650615356.465750][2439:2444] CHIP:DMG: + [1650615356.465787][2439:2444] CHIP:DMG: ], + [1650615356.465887][2439:2444] CHIP:DMG: + [1650615356.465928][2439:2444] CHIP:DMG: SuppressResponse = true, + [1650615356.465968][2439:2444] CHIP:DMG: InteractionModelRevision = 1 + [1650615356.466007][2439:2444] CHIP:DMG: } + [1650615356.470192][2439:2444] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0003 Attribute 0x0000_0000 DataVersion: 2435166734 + [1650615356.472574][2439:2444] CHIP:TOO: identify time: 0 + + + '' ./chip-tool identify read identify-time 1 1 --data-version 0x9125b20e + [1650615415.501037][2459:2464] CHIP:DMG: ReportDataMessage = + [1650615415.501075][2459:2464] CHIP:DMG: { + [1650615415.501109][2459:2464] CHIP:DMG: SuppressResponse = true, + [1650615415.501172][2459:2464] CHIP:DMG: InteractionModelRevision = 1 + [1650615415.501208][2459:2464] CHIP:DMG: } disabled: true - label: @@ -273,7 +830,94 @@ tests: second read request to read an attribute from the same cluster with the DataVersionFilter Field set with the dataversion value received before." - verification: "Unsupported in TE8 - Out of scope" + verification: | + ./chip-tool levelcontrol read on-level 1 1 + [1650615572.769784][2475:2480] CHIP:DMG: ReportDataMessage = + [1650615572.769821][2475:2480] CHIP:DMG: { + [1650615572.769849][2475:2480] CHIP:DMG: AttributeReportIBs = + [1650615572.769887][2475:2480] CHIP:DMG: [ + [1650615572.769918][2475:2480] CHIP:DMG: AttributeReportIB = + [1650615572.769959][2475:2480] CHIP:DMG: { + [1650615572.769991][2475:2480] CHIP:DMG: AttributeDataIB = + [1650615572.770031][2475:2480] CHIP:DMG: { + [1650615572.770069][2475:2480] CHIP:DMG: DataVersion = 0x5709863, + [1650615572.770113][2475:2480] CHIP:DMG: AttributePathIB = + [1650615572.770163][2475:2480] CHIP:DMG: { + [1650615572.770210][2475:2480] CHIP:DMG: Endpoint = 0x1, + [1650615572.770247][2475:2480] CHIP:DMG: Cluster = 0x8, + [1650615572.770296][2475:2480] CHIP:DMG: Attribute = 0x0000_0011, + [1650615572.770337][2475:2480] CHIP:DMG: } + [1650615572.770376][2475:2480] CHIP:DMG: + [1650615572.770417][2475:2480] CHIP:DMG: Data = NULL + [1650615572.770458][2475:2480] CHIP:DMG: }, + [1650615572.770496][2475:2480] CHIP:DMG: + [1650615572.770528][2475:2480] CHIP:DMG: }, + [1650615572.770566][2475:2480] CHIP:DMG: + [1650615572.770595][2475:2480] CHIP:DMG: ], + [1650615572.770633][2475:2480] CHIP:DMG: + [1650615572.770664][2475:2480] CHIP:DMG: SuppressResponse = true, + [1650615572.770695][2475:2480] CHIP:DMG: InteractionModelRevision = 1 + [1650615572.770724][2475:2480] CHIP:DMG: } + [1650615572.770895][2475:2480] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0008 Attribute 0x0000_0011 DataVersion: 91265123 + [1650615572.770989][2475:2480] CHIP:TOO: on level: null + + ./chip-tool levelcontrol write on-level 1 1 1 + [1650615622.935047][2483:2488] CHIP:DMG: WriteResponseMessage = + [1650615622.935078][2483:2488] CHIP:DMG: { + [1650615622.935119][2483:2488] CHIP:DMG: AttributeStatusIBs = + [1650615622.935160][2483:2488] CHIP:DMG: [ + [1650615622.935212][2483:2488] CHIP:DMG: AttributeStatusIB = + [1650615622.935252][2483:2488] CHIP:DMG: { + [1650615622.935298][2483:2488] CHIP:DMG: AttributePathIB = + [1650615622.935367][2483:2488] CHIP:DMG: { + [1650615622.935410][2483:2488] CHIP:DMG: Endpoint = 0x1, + [1650615622.935469][2483:2488] CHIP:DMG: Cluster = 0x8, + [1650615622.935516][2483:2488] CHIP:DMG: Attribute = 0x0000_0011, + [1650615622.935562][2483:2488] CHIP:DMG: } + [1650615622.935616][2483:2488] CHIP:DMG: + [1650615622.935674][2483:2488] CHIP:DMG: StatusIB = + [1650615622.935728][2483:2488] CHIP:DMG: { + [1650615622.935804][2483:2488] CHIP:DMG: status = 0x00 (SUCCESS), + [1650615622.935853][2483:2488] CHIP:DMG: }, + [1650615622.935915][2483:2488] CHIP:DMG: + [1650615622.935973][2483:2488] CHIP:DMG: }, + [1650615622.936028][2483:2488] CHIP:DMG: + [1650615622.936081][2483:2488] CHIP:DMG: ], + [1650615622.936132][2483:2488] CHIP:DMG: + [1650615622.936185][2483:2488] CHIP:DMG: InteractionModelRevision = 1 + [1650615622.936224][2483:2488] CHIP:DMG: } + + + ./chip-tool levelcontrol read on-level 1 1 --data-version 0xa8215230 + + [1650615673.320008][2497:2502] CHIP:DMG: ReportDataMessage = + [1650615673.320039][2497:2502] CHIP:DMG: { + [1650615673.320098][2497:2502] CHIP:DMG: AttributeReportIBs = + [1650615673.320140][2497:2502] CHIP:DMG: [ + [1650615673.320168][2497:2502] CHIP:DMG: AttributeReportIB = + [1650615673.320205][2497:2502] CHIP:DMG: { + [1650615673.320238][2497:2502] CHIP:DMG: AttributeDataIB = + [1650615673.320280][2497:2502] CHIP:DMG: { + [1650615673.320522][2497:2502] CHIP:DMG: DataVersion = 0x5709864, + [1650615673.320625][2497:2502] CHIP:DMG: AttributePathIB = + [1650615673.320674][2497:2502] CHIP:DMG: { + [1650615673.320807][2497:2502] CHIP:DMG: Endpoint = 0x1, + [1650615673.320877][2497:2502] CHIP:DMG: Cluster = 0x8, + [1650615673.320946][2497:2502] CHIP:DMG: Attribute = 0x0000_0011, + [1650615673.321005][2497:2502] CHIP:DMG: } + [1650615673.321062][2497:2502] CHIP:DMG: + [1650615673.321187][2497:2502] CHIP:DMG: Data = 1, + [1650615673.321249][2497:2502] CHIP:DMG: }, + [1650615673.321306][2497:2502] CHIP:DMG: + [1650615673.321351][2497:2502] CHIP:DMG: }, + [1650615673.321405][2497:2502] CHIP:DMG: + [1650615673.321444][2497:2502] CHIP:DMG: ], + [1650615673.321559][2497:2502] CHIP:DMG: + [1650615673.321605][2497:2502] CHIP:DMG: SuppressResponse = true, + [1650615673.321647][2497:2502] CHIP:DMG: InteractionModelRevision = 1 + [1650615673.321685][2497:2502] CHIP:DMG: } + [1650615673.321895][2497:2502] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0008 Attribute 0x0000_0011 DataVersion: 91265124 + [1650615673.322012][2497:2502] CHIP:TOO: on level: 1 disabled: true - label: @@ -284,7 +928,36 @@ tests: sends a second read request to read all the attributes from the same cluster with the DataVersionFilter Field set with the dataversion value received before." - verification: - "Unsupported in TE8 - https://github.com/project-chip/connectedhomeip/issues/15812" + verification: | + /chip-tool levelcontrol read-by-id 0xFFFFFFFF 1 1 + + + ./chip-tool levelcontrol write on-level 2 1 1 + [1650615802.966713][2527:2532] CHIP:DMG: WriteResponseMessage = + [1650615802.966754][2527:2532] CHIP:DMG: { + [1650615802.966791][2527:2532] CHIP:DMG: AttributeStatusIBs = + [1650615802.966828][2527:2532] CHIP:DMG: [ + [1650615802.966863][2527:2532] CHIP:DMG: AttributeStatusIB = + [1650615802.966909][2527:2532] CHIP:DMG: { + [1650615802.966936][2527:2532] CHIP:DMG: AttributePathIB = + [1650615802.966995][2527:2532] CHIP:DMG: { + [1650615802.967038][2527:2532] CHIP:DMG: Endpoint = 0x1, + [1650615802.967081][2527:2532] CHIP:DMG: Cluster = 0x8, + [1650615802.967133][2527:2532] CHIP:DMG: Attribute = 0x0000_0011, + [1650615802.967169][2527:2532] CHIP:DMG: } + [1650615802.967221][2527:2532] CHIP:DMG: + [1650615802.967259][2527:2532] CHIP:DMG: StatusIB = + [1650615802.967304][2527:2532] CHIP:DMG: { + [1650615802.967340][2527:2532] CHIP:DMG: status = 0x00 (SUCCESS), + [1650615802.967378][2527:2532] CHIP:DMG: }, + [1650615802.967424][2527:2532] CHIP:DMG: + [1650615802.967456][2527:2532] CHIP:DMG: }, + [1650615802.967502][2527:2532] CHIP:DMG: + [1650615802.967530][2527:2532] CHIP:DMG: ], + [1650615802.967576][2527:2532] CHIP:DMG: + [1650615802.967613][2527:2532] CHIP:DMG: InteractionModelRevision = 1 + [1650615802.967640][2527:2532] CHIP:DMG: } + + + ./chip-tool levelcontrol read-by-id 0xFFFFFFFF 1 1 --data-version 0xa8215232 disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_IDM_3_1.yaml b/src/app/tests/suites/certification/Test_TC_IDM_3_1.yaml index f88239a6476aac..9392dbe938e48c 100644 --- a/src/app/tests/suites/certification/Test_TC_IDM_3_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_IDM_3_1.yaml @@ -27,110 +27,324 @@ tests: data as indicated by the path. The Message should contain one valid CommandDataIB, which has the specific Endpoint, Specific Cluster and Specific Attribute." - verification: - "In case of chip tool, here is an example command to use sudo - ./chip-tool levelcontrol write on-level 2 1 1 sudo ./chip-tool - levelcontrol read on-level 1 1" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool levelcontrol write on-level 2 1 1 + 1648722241.711212][2528:2528] CHIP:DMG: WriteRequestMessage = + [1648722241.711258][2528:2528] CHIP:DMG: { + [1648722241.711300][2528:2528] CHIP:DMG: suppressResponse = false, + [1648722241.711348][2528:2528] CHIP:DMG: timedRequest = false, + [1648722241.711393][2528:2528] CHIP:DMG: AttributeDataIBs = + [1648722241.711446][2528:2528] CHIP:DMG: [ + [1648722241.711490][2528:2528] CHIP:DMG: AttributeDataIB = + [1648722241.711540][2528:2528] CHIP:DMG: { + [1648722241.711587][2528:2528] CHIP:DMG: AttributePathIB = + [1648722241.711644][2528:2528] CHIP:DMG: { + [1648722241.711703][2528:2528] CHIP:DMG: Endpoint = 0x1, + [1648722241.711763][2528:2528] CHIP:DMG: Cluster = 0x8, + [1648722241.711824][2528:2528] CHIP:DMG: Attribute = 0x0000_0011, + [1648722241.711884][2528:2528] CHIP:DMG: } + [1648722241.711945][2528:2528] CHIP:DMG: + [1648722241.712009][2528:2528] CHIP:DMG: Data = 2, + [1648722241.712071][2528:2528] CHIP:DMG: }, + [1648722241.712124][2528:2528] CHIP:DMG: + [1648722241.712166][2528:2528] CHIP:DMG: ], + [1648722241.712218][2528:2528] CHIP:DMG: + [1648722241.712263][2528:2528] CHIP:DMG: moreChunkedMessages = false, + [1648722241.712308][2528:2528] CHIP:DMG: InteractionModelRevision = 1 + [1648722241.712350][2528:2528] CHIP:DMG: }, + [1648722241.712484][2528:2528] CHIP:DMG: AccessControl: checking f=1 a=c s=0x000000000001B669 t= c=0x0000_0008 e=1 p=o + [1648722241.712545][2528:2528] CHIP:DMG: AccessControl: allowed + + '' ./chip-tool levelcontrol read on-level 1 1 disabled: true - label: "DUT sends the Write Request Message to the TH. The Message should read one attribute on all Endpoints On receipt of this message, TH should send a report data action with the attribute value to the DUT." - verification: - "In case of chip tool, here is an example command to use sudo - ./chip-tool any write-by-id 0x0008 0x0010 1 1 0xffff" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool any write-by-id 0x0008 0x0010 1 1 0xffff + (V1 out of scope) disabled: true - label: "[Optional] DUT sends the Write Request Message to the TH to write an attribute of data type bool." - verification: - "In case of chip tool, here is an example command to use sudo - ./chip-tool basic write local-config-disabled 1 1 0" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool basic write local-config-disabled 1 1 0 + [1649151041.770412][3376:3376] CHIP:DMG: WriteRequestMessage = + [1649151041.770459][3376:3376] CHIP:DMG: { + [1649151041.770502][3376:3376] CHIP:DMG: suppressResponse = false, + [1649151041.770550][3376:3376] CHIP:DMG: timedRequest = false, + [1649151041.770594][3376:3376] CHIP:DMG: AttributeDataIBs = + [1649151041.770647][3376:3376] CHIP:DMG: [ + [1649151041.770692][3376:3376] CHIP:DMG: AttributeDataIB = + [1649151041.770745][3376:3376] CHIP:DMG: { + [1649151041.770793][3376:3376] CHIP:DMG: AttributePathIB = + [1649151041.770857][3376:3376] CHIP:DMG: { + [1649151041.770917][3376:3376] CHIP:DMG: Endpoint = 0x0, + [1649151041.770984][3376:3376] CHIP:DMG: Cluster = 0x28, + [1649151041.771040][3376:3376] CHIP:DMG: Attribute = 0x0000_0010, + [1649151041.771095][3376:3376] CHIP:DMG: } + [1649151041.771146][3376:3376] CHIP:DMG: + [1649151041.771203][3376:3376] CHIP:DMG: Data = true, + [1649151041.771261][3376:3376] CHIP:DMG: }, + [1649151041.771316][3376:3376] CHIP:DMG: + [1649151041.771359][3376:3376] CHIP:DMG: ], + [1649151041.771412][3376:3376] CHIP:DMG: + [1649151041.771457][3376:3376] CHIP:DMG: moreChunkedMessages = false, + [1649151041.771503][3376:3376] CHIP:DMG: InteractionModelRevision = 1 + [1649151041.771546][3376:3376] CHIP:DMG: }, + [1649151041.771675][3376:3376] CHIP:DMG: AccessControl: checking f=1 a=c s=0x000000000001B669 t= c=0x0000_0028 e=0 p=m + + + '' ./chip-tool basic read local-config-disabled 1 0 + 1649151101.825618][3376:3376] CHIP:DMG: ReadRequestMessage = + [1649151101.825662][3376:3376] CHIP:DMG: { + [1649151101.825698][3376:3376] CHIP:DMG: AttributePathIBs = + [1649151101.825758][3376:3376] CHIP:DMG: [ + [1649151101.825798][3376:3376] CHIP:DMG: AttributePathIB = + [1649151101.825860][3376:3376] CHIP:DMG: { + [1649151101.825917][3376:3376] CHIP:DMG: Endpoint = 0x0, + [1649151101.825991][3376:3376] CHIP:DMG: Cluster = 0x28, + [1649151101.826059][3376:3376] CHIP:DMG: Attribute = 0x0000_0010, + [1649151101.826113][3376:3376] CHIP:DMG: } + [1649151101.826176][3376:3376] CHIP:DMG: + [1649151101.826222][3376:3376] CHIP:DMG: ], + [1649151101.826334][3376:3376] CHIP:DMG: + [1649151101.826393][3376:3376] CHIP:DMG: isFabricFiltered = true, + [1649151101.826474][3376:3376] CHIP:DMG: InteractionModelRevision = 1 + [1649151101.826527][3376:3376] CHIP:DMG: }, disabled: true - label: "[Optional] DUT sends the Write Request Message to the TH to write an attribute of data type string." - verification: - "In case of chip tool, here is an example command to use sudo - ./chip-tool basic write node-label 1 1 0" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool basic write node-label node 1 0 + 1649151261.296520][3376:3376] CHIP:DMG: WriteRequestMessage = + [1649151261.296554][3376:3376] CHIP:DMG: { + [1649151261.296613][3376:3376] CHIP:DMG: suppressResponse = false, + [1649151261.296649][3376:3376] CHIP:DMG: timedRequest = false, + [1649151261.296682][3376:3376] CHIP:DMG: AttributeDataIBs = + [1649151261.296723][3376:3376] CHIP:DMG: [ + [1649151261.296756][3376:3376] CHIP:DMG: AttributeDataIB = + [1649151261.296801][3376:3376] CHIP:DMG: { + [1649151261.296836][3376:3376] CHIP:DMG: AttributePathIB = + [1649151261.296881][3376:3376] CHIP:DMG: { + [1649151261.296923][3376:3376] CHIP:DMG: Endpoint = 0x0, + [1649151261.296960][3376:3376] CHIP:DMG: Cluster = 0x28, + [1649151261.297005][3376:3376] CHIP:DMG: Attribute = 0x0000_0005, + [1649151261.297051][3376:3376] CHIP:DMG: } + [1649151261.297094][3376:3376] CHIP:DMG: + [1649151261.297138][3376:3376] CHIP:DMG: Data = "node", + [1649151261.297184][3376:3376] CHIP:DMG: }, + [1649151261.297226][3376:3376] CHIP:DMG: + [1649151261.297257][3376:3376] CHIP:DMG: ], + [1649151261.297296][3376:3376] CHIP:DMG: + [1649151261.297329][3376:3376] CHIP:DMG: moreChunkedMessages = false, + [1649151261.297362][3376:3376] CHIP:DMG: InteractionModelRevision = 1 + [1649151261.297393][3376:3376] CHIP:DMG: }, + [1649151261.297498][3376:3376] CHIP:DMG: AccessControl: checking f=1 a=c s=0x000000000001B669 t= c=0x0000_0028 e=0 p=m + + '' ./chip-tool basic read node-label 1 -0 disabled: true - label: "[Optional] DUT sends the Write Request Message to the TH to write an attribute of data type unsigned integer." - verification: - "In case of chip tool, here is an example command to use sudo - ./chip-tool any write-by-id 0x0008 0x0010 1 1 1" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool any write-by-id 0x0008 0x0010 1 1 1 + [1649151355.273946][3376:3376] CHIP:DMG: WriteRequestMessage = + [1649151355.273980][3376:3376] CHIP:DMG: { + [1649151355.274011][3376:3376] CHIP:DMG: suppressResponse = false, + [1649151355.274046][3376:3376] CHIP:DMG: timedRequest = false, + [1649151355.274079][3376:3376] CHIP:DMG: AttributeDataIBs = + [1649151355.274119][3376:3376] CHIP:DMG: [ + [1649151355.274151][3376:3376] CHIP:DMG: AttributeDataIB = + [1649151355.274190][3376:3376] CHIP:DMG: { + [1649151355.274225][3376:3376] CHIP:DMG: AttributePathIB = + [1649151355.274267][3376:3376] CHIP:DMG: { + [1649151355.274313][3376:3376] CHIP:DMG: Endpoint = 0x1, + [1649151355.274359][3376:3376] CHIP:DMG: Cluster = 0x8, + [1649151355.274403][3376:3376] CHIP:DMG: Attribute = 0x0000_0010, + [1649151355.274445][3376:3376] CHIP:DMG: } + [1649151355.274489][3376:3376] CHIP:DMG: + [1649151355.274537][3376:3376] CHIP:DMG: Data = 1, + [1649151355.274577][3376:3376] CHIP:DMG: }, + [1649151355.274616][3376:3376] CHIP:DMG: + [1649151355.274647][3376:3376] CHIP:DMG: ], + [1649151355.274686][3376:3376] CHIP:DMG: + [1649151355.274718][3376:3376] CHIP:DMG: moreChunkedMessages = false, + [1649151355.274752][3376:3376] CHIP:DMG: InteractionModelRevision = 1 + [1649151355.274785][3376:3376] CHIP:DMG: }, + [1649151355.274885][3376:3376] CHIP:DMG: AccessControl: checking f=1 a=c s=0x000000000001B669 t= c=0x0000_0008 e=1 p=o + + + + '' ./chip-tool any read-by-id 0x0008 0x0010 1 1 disabled: true - label: "[Optional] DUT sends the Write Request Message to the TH to write an attribute of data type signed integer." - verification: - "wirte to an attribute of type signed integer to the Harness" + verification: | + DUT implementation required to verify read an attribute of data type signed integer. disabled: true - label: "[Optional] DUT sends the Write Request Message to the TH to write an attribute of data type floating point." - verification: - "wirte to an attribute of type floating integer to the Harness" + verification: | + DUT implementation required to verify read an attribute of data type floating point disabled: true - label: "[Optional] DUT sends the Write Request Message to the TH to write an attribute of data type Octet String." - verification: "wirte to an attribute of type oct string to the Harness" + verification: | + DUT implementation required to verify read an attribute of data type Octet String disabled: true - label: "[Optional] DUT sends the Write Request Message to the TH to write an attribute of data type Struct." - verification: "wirte to an attribute of type Struct to the Harness" + verification: | + DUT implementation required to verify read an attribute ofdata type Struct disabled: true - label: "[Optional] DUT sends the Write Request Message to the TH to write an attribute of data type List." - verification: "wirte to an attribute of type list integer to the Harness" + verification: | + DUT implementation required to verify read an attribute of data type List disabled: true - label: "[Optional] DUT sends the Write Request Message to the TH to write an attribute of data type enum." - verification: - "In case of chip tool, here is an example command to use sudo - ./chip-tool any write-by-id 0x0204 0 1 1 1" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool any write-by-id 0x0204 0 1 1 1 + '' ./chip-tool any read-by-id 0x0204 0 1 1 disabled: true - label: "[Optional] DUT sends the Write Request Message to the TH to write an attribute of data type bitmap." - verification: - "In case of chip tool, here is an example command to use sudo - ./chip-tool colorcontrol write-by-id 0x000f 1 1 1" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool colorcontrol write-by-id 0x000f 1 1 1 + '' ./chip-tool colorcontrol read-by-id 0x000f 1 1 disabled: true - label: "DUT sends a group cast Write Request Message to the TH to modify any attribute SuppressResponse field is set to True" - verification: - "Suppress Response field can't be done is chip tool - file ticket" + verification: | + ./chip-tool colorcontrol write-by-id 0x000f 1 1 1 --suppressResponse 1 + [1649151441.506191][3376:3376] CHIP:DMG: WriteRequestMessage = + [1649151441.506218][3376:3376] CHIP:DMG: { + [1649151441.506241][3376:3376] CHIP:DMG: suppressResponse = true, + [1649151441.506268][3376:3376] CHIP:DMG: timedRequest = false, + [1649151441.506293][3376:3376] CHIP:DMG: AttributeDataIBs = + [1649151441.506323][3376:3376] CHIP:DMG: [ + [1649151441.506348][3376:3376] CHIP:DMG: AttributeDataIB = + [1649151441.506382][3376:3376] CHIP:DMG: { + [1649151441.506408][3376:3376] CHIP:DMG: AttributePathIB = + [1649151441.506438][3376:3376] CHIP:DMG: { + [1649151441.506468][3376:3376] CHIP:DMG: Endpoint = 0x1, + [1649151441.506501][3376:3376] CHIP:DMG: Cluster = 0x300, + [1649151441.506531][3376:3376] CHIP:DMG: Attribute = 0x0000_000F, + [1649151441.506560][3376:3376] CHIP:DMG: } + [1649151441.506591][3376:3376] CHIP:DMG: + [1649151441.506621][3376:3376] CHIP:DMG: Data = 1, + [1649151441.506650][3376:3376] CHIP:DMG: }, + [1649151441.506678][3376:3376] CHIP:DMG: + [1649151441.506702][3376:3376] CHIP:DMG: ], + [1649151441.506730][3376:3376] CHIP:DMG: + [1649151441.506755][3376:3376] CHIP:DMG: moreChunkedMessages = false, + [1649151441.506780][3376:3376] CHIP:DMG: InteractionModelRevision = 1 + [1649151441.506803][3376:3376] CHIP:DMG: }, + + TH side log + + [1649151441.502228][16050:16055] CHIP:DMG: WriteResponseMessage = + [1649151441.502257][16050:16055] CHIP:DMG: { + [1649151441.502282][16050:16055] CHIP:DMG: AttributeStatusIBs = + [1649151441.502321][16050:16055] CHIP:DMG: [ + [1649151441.502349][16050:16055] CHIP:DMG: AttributeStatusIB = + [1649151441.502382][16050:16055] CHIP:DMG: { + [1649151441.502411][16050:16055] CHIP:DMG: AttributePathIB = + [1649151441.502444][16050:16055] CHIP:DMG: { + [1649151441.502476][16050:16055] CHIP:DMG: Endpoint = 0x1, + [1649151441.502512][16050:16055] CHIP:DMG: Cluster = 0x300, + [1649151441.502553][16050:16055] CHIP:DMG: Attribute = 0x0000_000F, + [1649151441.502585][16050:16055] CHIP:DMG: } + [1649151441.502625][16050:16055] CHIP:DMG: + [1649151441.502664][16050:16055] CHIP:DMG: StatusIB = + [1649151441.502703][16050:16055] CHIP:DMG: { + [1649151441.502739][16050:16055] CHIP:DMG: status = 0x00 (SUCCESS), + [1649151441.502778][16050:16055] CHIP:DMG: }, + [1649151441.502819][16050:16055] CHIP:DMG: + [1649151441.502861][16050:16055] CHIP:DMG: }, + [1649151441.502916][16050:16055] CHIP:DMG: + [1649151441.502953][16050:16055] CHIP:DMG: ], + [1649151441.502993][16050:16055] CHIP:DMG: + [1649151441.503026][16050:16055] CHIP:DMG: InteractionModelRevision = 1 + [1649151441.503058][16050:16055] CHIP:DMG: } disabled: true - label: "DUT sends a Write Request Message to the TH with a large list of attribute data which has to be sent in multiple messages." - verification: "Need to find more info" + verification: | + '' ./chip-tool levelcontrol write on-off-transition-time 5 1 1 + '' ./chip-tool levelcontrol write on-level 5 1 1 + '' ./chip-tool levelcontrol write default-move-rate 5 1 1 + '' ./chip-tool levelcontrol write off-transition-time 5 1 1 disabled: true - label: "DUT sends the Write Request Message to the TH to write one attribute on a given cluster and endpoint. Repeat the above steps 3 times." - verification: - "In case of chip tool, here is an example command to use sudo - ./chip-tool basic write node-label 1 1 0" + verification: | + '' ./chip-tool basic write node-label 1 1 0 + [1649152106.541047][3376:3376] CHIP:DMG: WriteRequestMessage = + [1649152106.541088][3376:3376] CHIP:DMG: { + [1649152106.541125][3376:3376] CHIP:DMG: suppressResponse = false, + [1649152106.541168][3376:3376] CHIP:DMG: timedRequest = false, + [1649152106.541208][3376:3376] CHIP:DMG: AttributeDataIBs = + [1649152106.541258][3376:3376] CHIP:DMG: [ + [1649152106.541298][3376:3376] CHIP:DMG: AttributeDataIB = + [1649152106.541354][3376:3376] CHIP:DMG: { + [1649152106.541397][3376:3376] CHIP:DMG: AttributePathIB = + [1649152106.541448][3376:3376] CHIP:DMG: { + [1649152106.541506][3376:3376] CHIP:DMG: Endpoint = 0x0, + [1649152106.541563][3376:3376] CHIP:DMG: Cluster = 0x28, + [1649152106.541622][3376:3376] CHIP:DMG: Attribute = 0x0000_0005, + [1649152106.541678][3376:3376] CHIP:DMG: } + [1649152106.541733][3376:3376] CHIP:DMG: + [1649152106.541789][3376:3376] CHIP:DMG: Data = "1", + [1649152106.541840][3376:3376] CHIP:DMG: }, + [1649152106.541890][3376:3376] CHIP:DMG: + [1649152106.541929][3376:3376] CHIP:DMG: ], + [1649152106.541976][3376:3376] CHIP:DMG: + [1649152106.542016][3376:3376] CHIP:DMG: moreChunkedMessages = false, + [1649152106.542058][3376:3376] CHIP:DMG: InteractionModelRevision = 1 + [1649152106.542095][3376:3376] CHIP:DMG: }, + + Repeat the above steps 3 times. disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_IDM_3_2.yaml b/src/app/tests/suites/certification/Test_TC_IDM_3_2.yaml index 438d9e7582c167..45a5d5792621ae 100644 --- a/src/app/tests/suites/certification/Test_TC_IDM_3_2.yaml +++ b/src/app/tests/suites/certification/Test_TC_IDM_3_2.yaml @@ -27,140 +27,411 @@ tests: CommandDataIB, which has the specific Endpoint, Specific Cluster and Specific Attribute. On receipt of this message, DUT should send a write response action with the modified attribute value to the TH." - verification: - "In case of chip tool, here is an example command to use ./chip-tool - levelcontrol write on-level 2 1 1" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool levelcontrol write on-level 2 1 1 + [1649152253.662672][16169:16174] CHIP:DMG: WriteResponseMessage = + [1649152253.662703][16169:16174] CHIP:DMG: { + [1649152253.662730][16169:16174] CHIP:DMG: AttributeStatusIBs = + [1649152253.662769][16169:16174] CHIP:DMG: [ + [1649152253.662800][16169:16174] CHIP:DMG: AttributeStatusIB = + [1649152253.662844][16169:16174] CHIP:DMG: { + [1649152253.662877][16169:16174] CHIP:DMG: AttributePathIB = + [1649152253.662915][16169:16174] CHIP:DMG: { + [1649152253.662956][16169:16174] CHIP:DMG: Endpoint = 0x1, + [1649152253.662998][16169:16174] CHIP:DMG: Cluster = 0x8, + [1649152253.663040][16169:16174] CHIP:DMG: Attribute = 0x0000_0011, + [1649152253.663079][16169:16174] CHIP:DMG: } + [1649152253.663123][16169:16174] CHIP:DMG: + [1649152253.663160][16169:16174] CHIP:DMG: StatusIB = + [1649152253.663202][16169:16174] CHIP:DMG: { + [1649152253.663240][16169:16174] CHIP:DMG: status = 0x00 (SUCCESS), + [1649152253.663279][16169:16174] CHIP:DMG: }, + [1649152253.663319][16169:16174] CHIP:DMG: + [1649152253.663354][16169:16174] CHIP:DMG: }, + [1649152253.663393][16169:16174] CHIP:DMG: + [1649152253.663423][16169:16174] CHIP:DMG: ], + [1649152253.663461][16169:16174] CHIP:DMG: + [1649152253.663491][16169:16174] CHIP:DMG: InteractionModelRevision = 1 + [1649152253.663520][16169:16174] CHIP:DMG: } disabled: true - label: "TH sends a Write Request Message to the DUT to all endpoints. On receipt of this message, DUT should send a Write Response action with the attribute value to the DUT." - verification: - "In case of chip tool, here is an example command to use ./chip-tool - any write-by-id 0x0008 0x0010 1 1 0xffff" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool any write-by-id 0x0008 0x0010 1 1 0xffff + (V1 out of scope) disabled: true - label: "[Optional] TH sends the Write Request Message to the DUT to write an attribute of data type bool. DUT responds with the Write Response action with the right attribute value." - verification: - "In case of chip tool, here is an example command to use ./chip-tool - basic write local-config-disabled 1 1 0" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool basic write local-config-disabled 1 1 0 + + 1649152398.774420][16190:16195] CHIP:DMG: WriteResponseMessage = + [1649152398.774454][16190:16195] CHIP:DMG: { + [1649152398.774483][16190:16195] CHIP:DMG: AttributeStatusIBs = + [1649152398.774524][16190:16195] CHIP:DMG: [ + [1649152398.774556][16190:16195] CHIP:DMG: AttributeStatusIB = + [1649152398.774597][16190:16195] CHIP:DMG: { + [1649152398.774631][16190:16195] CHIP:DMG: AttributePathIB = + [1649152398.774677][16190:16195] CHIP:DMG: { + [1649152398.774723][16190:16195] CHIP:DMG: Endpoint = 0x0, + [1649152398.774768][16190:16195] CHIP:DMG: Cluster = 0x28, + [1649152398.774813][16190:16195] CHIP:DMG: Attribute = 0x0000_0010, + [1649152398.774854][16190:16195] CHIP:DMG: } + [1649152398.774901][16190:16195] CHIP:DMG: + [1649152398.774942][16190:16195] CHIP:DMG: StatusIB = + [1649152398.775028][16190:16195] CHIP:DMG: { + [1649152398.775135][16190:16195] CHIP:DMG: status = 0x00 (SUCCESS), + [1649152398.775181][16190:16195] CHIP:DMG: }, + [1649152398.775225][16190:16195] CHIP:DMG: + [1649152398.775261][16190:16195] CHIP:DMG: }, + [1649152398.775303][16190:16195] CHIP:DMG: + [1649152398.775335][16190:16195] CHIP:DMG: ], + [1649152398.775375][16190:16195] CHIP:DMG: + [1649152398.775407][16190:16195] CHIP:DMG: InteractionModelRevision = 1 + [1649152398.775438][16190:16195] CHIP:DMG: } disabled: true - label: "[Optional] TH sends the Write Request Message to the DUT to write an attribute of data type string. DUT responds with the Write Response action with the right attribute value." - verification: - "In case of chip tool, here is an example command to use ./chip-tool - basic write node-label 1 1 0" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool basic write node-label 1 1 0 + [1649152505.885287][16202:16208] CHIP:DMG: WriteResponseMessage = + [1649152505.885339][16202:16208] CHIP:DMG: { + [1649152505.885378][16202:16208] CHIP:DMG: AttributeStatusIBs = + [1649152505.885415][16202:16208] CHIP:DMG: [ + [1649152505.885454][16202:16208] CHIP:DMG: AttributeStatusIB = + [1649152505.885499][16202:16208] CHIP:DMG: { + [1649152505.885530][16202:16208] CHIP:DMG: AttributePathIB = + [1649152505.885575][16202:16208] CHIP:DMG: { + [1649152505.885616][16202:16208] CHIP:DMG: Endpoint = 0x0, + [1649152505.885668][16202:16208] CHIP:DMG: Cluster = 0x28, + [1649152505.885720][16202:16208] CHIP:DMG: Attribute = 0x0000_0005, + [1649152505.885759][16202:16208] CHIP:DMG: } + [1649152505.885810][16202:16208] CHIP:DMG: + [1649152505.885855][16202:16208] CHIP:DMG: StatusIB = + [1649152505.885892][16202:16208] CHIP:DMG: { + [1649152505.885942][16202:16208] CHIP:DMG: status = 0x00 (SUCCESS), + [1649152505.885988][16202:16208] CHIP:DMG: }, + [1649152505.886024][16202:16208] CHIP:DMG: + [1649152505.886065][16202:16208] CHIP:DMG: }, + [1649152505.886102][16202:16208] CHIP:DMG: + [1649152505.886139][16202:16208] CHIP:DMG: ], + [1649152505.886174][16202:16208] CHIP:DMG: + [1649152505.886213][16202:16208] CHIP:DMG: InteractionModelRevision = 1 + [1649152505.886240][16202:16208] CHIP:DMG: } disabled: true - label: "[Optional] TH sends the Write Request Message to the DUT to write an attribute of data type unsigned integer. DUT responds with the Write Response action with the right attribute value." - verification: - "In case of chip tool, here is an example command to use ./chip-tool - any write-by-id 0x0008 0x0010 1 1 1" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool any write-by-id 0x0008 0x0010 1 1 1 + [1649152567.635323][16212:16217] CHIP:DMG: WriteResponseMessage = + [1649152567.635361][16212:16217] CHIP:DMG: { + [1649152567.635394][16212:16217] CHIP:DMG: AttributeStatusIBs = + [1649152567.635441][16212:16217] CHIP:DMG: [ + [1649152567.635479][16212:16217] CHIP:DMG: AttributeStatusIB = + [1649152567.635524][16212:16217] CHIP:DMG: { + [1649152567.635565][16212:16217] CHIP:DMG: AttributePathIB = + [1649152567.635612][16212:16217] CHIP:DMG: { + [1649152567.635659][16212:16217] CHIP:DMG: Endpoint = 0x1, + [1649152567.635710][16212:16217] CHIP:DMG: Cluster = 0x8, + [1649152567.635761][16212:16217] CHIP:DMG: Attribute = 0x0000_0010, + [1649152567.635812][16212:16217] CHIP:DMG: } + [1649152567.635868][16212:16217] CHIP:DMG: + [1649152567.635911][16212:16217] CHIP:DMG: StatusIB = + [1649152567.635963][16212:16217] CHIP:DMG: { + [1649152567.636009][16212:16217] CHIP:DMG: status = 0x00 (SUCCESS), + [1649152567.636056][16212:16217] CHIP:DMG: }, + [1649152567.636103][16212:16217] CHIP:DMG: + [1649152567.636145][16212:16217] CHIP:DMG: }, + [1649152567.636193][16212:16217] CHIP:DMG: + [1649152567.636229][16212:16217] CHIP:DMG: ], + [1649152567.636274][16212:16217] CHIP:DMG: + [1649152567.636309][16212:16217] CHIP:DMG: InteractionModelRevision = 1 + [1649152567.636344][16212:16217] CHIP:DMG: } disabled: true - label: "[Optional] TH sends the Write Request Message to the DUT to write an attribute of data type signed integer. DUT responds with the Write Response action with the right attribute value." - verification: - "write to an attribute of type signed integer to the Harness" + verification: | + DUT implementation required to verify read an attribute of data type signed integer. disabled: true - label: "[Optional] TH sends the Write Request Message to the DUT to write an attribute of data type floating point. DUT responds with the Write Response action with the right attribute value." - verification: "write to an attribute of type floating to the Harness" + verification: | + DUT implementation required to verify read an attribute of data type signed integer. disabled: true - label: "[Optional] TH sends the Write Request Message to the DUT to write an attribute of data type Octet String. DUT responds with the Write Response action with the right attribute value." - verification: "write to an attribute of type oct string to the Harness" + verification: | + DUT implementation required to verify read an attribute of data type string disabled: true - label: "[Optional] TH sends the Write Request Message to the DUT to write an attribute of data type Struct. DUT responds with the Write Response action with the right attribute value." - verification: "write to an attribute of type Struct to the Harness" + verification: | + DUT implementation required to verify read an attribute of data type struct. disabled: true - label: "[Optional] TH sends the Write Request Message to the DUT to write an attribute of data type List. DUT responds with the Write Response action with the right attribute value." - verification: "write to an attribute of type list to the Harness" + verification: | + DUT implementation required to verify read an attribute of data type list. disabled: true - label: "[Optional] TH sends the Write Request Message to the DUT to write an attribute of data type enum. DUT responds with the Write Response action with the right attribute value." - verification: - "In case of chip tool, here is an example command to use ./chip-tool - any write-by-id 0x0204 0 1 1 1" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool any write-by-id 0x0204 0 1 1 1 + [1649152707.514290][16226:16231] CHIP:DMG: WriteResponseMessage = + [1649152707.514324][16226:16231] CHIP:DMG: { + [1649152707.514354][16226:16231] CHIP:DMG: AttributeStatusIBs = + [1649152707.514396][16226:16231] CHIP:DMG: [ + [1649152707.514429][16226:16231] CHIP:DMG: AttributeStatusIB = + [1649152707.514476][16226:16231] CHIP:DMG: { + [1649152707.514511][16226:16231] CHIP:DMG: AttributePathIB = + [1649152707.514553][16226:16231] CHIP:DMG: { + [1649152707.514600][16226:16231] CHIP:DMG: Endpoint = 0x1, + [1649152707.514646][16226:16231] CHIP:DMG: Cluster = 0x204, + [1649152707.514691][16226:16231] CHIP:DMG: Attribute = 0x0000_0000, + [1649152707.514734][16226:16231] CHIP:DMG: } + [1649152707.514781][16226:16231] CHIP:DMG: + [1649152707.514820][16226:16231] CHIP:DMG: StatusIB = + [1649152707.514867][16226:16231] CHIP:DMG: { + [1649152707.514908][16226:16231] CHIP:DMG: status = 0x00 (SUCCESS), + [1649152707.514995][16226:16231] CHIP:DMG: }, + [1649152707.515038][16226:16231] CHIP:DMG: + [1649152707.515072][16226:16231] CHIP:DMG: }, + [1649152707.515113][16226:16231] CHIP:DMG: + [1649152707.515145][16226:16231] CHIP:DMG: ], + [1649152707.515186][16226:16231] CHIP:DMG: + [1649152707.515218][16226:16231] CHIP:DMG: InteractionModelRevision = 1 + [1649152707.515250][16226:16231] CHIP:DMG: } + [1649152707.515374][16226:16231] CHIP:DMG: WriteClient moving to [AwaitingDe] disabled: true - label: "[Optional] TH sends the Write Request Message to the DUT to write an attribute of data type bitmap. DUT responds with the Write Response action with the right attribute value." - verification: - "In case of chip tool, here is an example command to use ./chip-tool - colorcontrol write-by-id 0x000f 1 1 1" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool colorcontrol write-by-id 0x000f 1 1 1 + + [1649152768.817940][16237:16242] CHIP:DMG: WriteResponseMessage = + [1649152768.817971][16237:16242] CHIP:DMG: { + [1649152768.817999][16237:16242] CHIP:DMG: AttributeStatusIBs = + [1649152768.818038][16237:16242] CHIP:DMG: [ + [1649152768.818068][16237:16242] CHIP:DMG: AttributeStatusIB = + [1649152768.818111][16237:16242] CHIP:DMG: { + [1649152768.818146][16237:16242] CHIP:DMG: AttributePathIB = + [1649152768.818188][16237:16242] CHIP:DMG: { + [1649152768.818230][16237:16242] CHIP:DMG: Endpoint = 0x1, + [1649152768.818275][16237:16242] CHIP:DMG: Cluster = 0x300, + [1649152768.818317][16237:16242] CHIP:DMG: Attribute = 0x0000_000F, + [1649152768.818358][16237:16242] CHIP:DMG: } + [1649152768.818405][16237:16242] CHIP:DMG: + [1649152768.818443][16237:16242] CHIP:DMG: StatusIB = + [1649152768.818485][16237:16242] CHIP:DMG: { + [1649152768.818521][16237:16242] CHIP:DMG: status = 0x00 (SUCCESS), + [1649152768.818559][16237:16242] CHIP:DMG: }, + [1649152768.818602][16237:16242] CHIP:DMG: + [1649152768.818640][16237:16242] CHIP:DMG: }, + [1649152768.818681][16237:16242] CHIP:DMG: + [1649152768.818710][16237:16242] CHIP:DMG: ], + [1649152768.818747][16237:16242] CHIP:DMG: + [1649152768.818777][16237:16242] CHIP:DMG: InteractionModelRevision = 1 + [1649152768.818806][16237:16242] CHIP:DMG: } + [1649152768.818890][16237:16242] CHIP:DMG: WriteClient moving to [AwaitingDe] disabled: true - label: "TH sends the Write Request Message to the DUT to read any attribute to an unsupported node. DUT responds with the Write Response action" - verification: - "Unsupported for TE8 - - https://github.com/CHIP-Specifications/connectedhomeip-spec/pull/4999" + verification: | + Out of Scope for V1.0 disabled: true - label: "TH sends the Write Request Message to the DUT to read any attribute to an unsupported Endpoint. DUT responds with the Write Response action" - verification: - "In case of chip tool, here is an example command to use ./chip-tool - onoff on 1 20" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool levelcontrol write on-level 2 1 20 + + + 1649153009.582466][16268:16273] CHIP:DMG: WriteResponseMessage = + [1649153009.582507][16268:16273] CHIP:DMG: { + [1649153009.582557][16268:16273] CHIP:DMG: AttributeStatusIBs = + [1649153009.582610][16268:16273] CHIP:DMG: [ + [1649153009.582667][16268:16273] CHIP:DMG: AttributeStatusIB = + [1649153009.582723][16268:16273] CHIP:DMG: { + [1649153009.582779][16268:16273] CHIP:DMG: AttributePathIB = + [1649153009.582831][16268:16273] CHIP:DMG: { + [1649153009.582899][16268:16273] CHIP:DMG: Endpoint = 0x14, + [1649153009.582970][16268:16273] CHIP:DMG: Cluster = 0x8, + [1649153009.583031][16268:16273] CHIP:DMG: Attribute = 0x0000_0011, + [1649153009.583087][16268:16273] CHIP:DMG: } + [1649153009.583166][16268:16273] CHIP:DMG: + [1649153009.583221][16268:16273] CHIP:DMG: StatusIB = + [1649153009.583291][16268:16273] CHIP:DMG: { + [1649153009.583362][16268:16273] CHIP:DMG: status = 0x7f (UNSUPPORTED_ENDPOINT), + [1649153009.583415][16268:16273] CHIP:DMG: }, + [1649153009.583481][16268:16273] CHIP:DMG: + [1649153009.583527][16268:16273] CHIP:DMG: }, + [1649153009.583594][16268:16273] CHIP:DMG: + [1649153009.583634][16268:16273] CHIP:DMG: ], + [1649153009.583697][16268:16273] CHIP:DMG: + [1649153009.583751][16268:16273] CHIP:DMG: InteractionModelRevision = 1 + [1649153009.583790][16268:16273] CHIP:DMG: } + [1649153009.583903][16268:16273] CHIP:TOO: Response Failure: IM Error 0x0000057F: General error: 0x7f (UNSUPPORTED_ENDPOINT) + + [1649152811.554055][16246:16251] CHIP:DMG: }, disabled: true - label: "TH sends the Write Request Message to the DUT to read any attribute to an unsupported cluster. DUT responds with the Write Response action" - verification: - "In case of chip tool, here is an example command to use ./chip-tool - any command-by-id 0x0003 0 1 1 2" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool thermostat write unoccupied-heating-setpoint 1200 1 0 + + [1650618880.286103][2741:2746] CHIP:DMG: WriteResponseMessage = + [1650618880.286161][2741:2746] CHIP:DMG: { + [1650618880.286210][2741:2746] CHIP:DMG: AttributeStatusIBs = + [1650618880.286280][2741:2746] CHIP:DMG: [ + [1650618880.286334][2741:2746] CHIP:DMG: AttributeStatusIB = + [1650618880.286399][2741:2746] CHIP:DMG: { + [1650618880.286456][2741:2746] CHIP:DMG: AttributePathIB = + [1650618880.286540][2741:2746] CHIP:DMG: { + [1650618880.286598][2741:2746] CHIP:DMG: Endpoint = 0x0, + [1650618880.286670][2741:2746] CHIP:DMG: Cluster = 0x201, + [1650618880.286736][2741:2746] CHIP:DMG: Attribute = 0x0000_0014, + [1650618880.286809][2741:2746] CHIP:DMG: } + [1650618880.286892][2741:2746] CHIP:DMG: + [1650618880.286955][2741:2746] CHIP:DMG: StatusIB = + [1650618880.287015][2741:2746] CHIP:DMG: { + [1650618880.287080][2741:2746] CHIP:DMG: status = 0xc3 (UNSUPPORTED_CLUSTER), + [1650618880.287144][2741:2746] CHIP:DMG: }, + [1650618880.287208][2741:2746] CHIP:DMG: + [1650618880.287267][2741:2746] CHIP:DMG: }, + [1650618880.287328][2741:2746] CHIP:DMG: + [1650618880.287377][2741:2746] CHIP:DMG: ], + [1650618880.287440][2741:2746] CHIP:DMG: + [1650618880.287489][2741:2746] CHIP:DMG: InteractionModelRevision = 1 + [1650618880.287538][2741:2746] CHIP:DMG: } + [1650618880.287657][2741:2746] CHIP:TOO: Response Failure: IM Error 0x000005C3: General error: 0xc3 (UNSUPPORTED_CLUSTER) + [1650618880.287735][2741:2746] CHIP:DMG: WriteClient moving to [AwaitingDe] disabled: true - label: "TH sends the Write Request Message to the DUT to read an unsupported attribute DUT responds with the Write Response action" - verification: - "In case of chip tool, here is an example command to use ./chip-tool - any read-by-id 0x03 -900 1 1" + verification: | + '' ./chip-tool thermostat write unoccupied-heating-setpoint 1200 1 1 + + + [1650618819.921180][2730:2735] CHIP:DMG: WriteResponseMessage = + [1650618819.921212][2730:2735] CHIP:DMG: { + [1650618819.921237][2730:2735] CHIP:DMG: AttributeStatusIBs = + [1650618819.921273][2730:2735] CHIP:DMG: [ + [1650618819.921303][2730:2735] CHIP:DMG: AttributeStatusIB = + [1650618819.921334][2730:2735] CHIP:DMG: { + [1650618819.921364][2730:2735] CHIP:DMG: AttributePathIB = + [1650618819.921400][2730:2735] CHIP:DMG: { + [1650618819.921436][2730:2735] CHIP:DMG: Endpoint = 0x1, + [1650618819.921473][2730:2735] CHIP:DMG: Cluster = 0x201, + [1650618819.921508][2730:2735] CHIP:DMG: Attribute = 0x0000_0014, + [1650618819.921543][2730:2735] CHIP:DMG: } + [1650618819.921586][2730:2735] CHIP:DMG: + [1650618819.921619][2730:2735] CHIP:DMG: StatusIB = + [1650618819.921654][2730:2735] CHIP:DMG: { + [1650618819.921692][2730:2735] CHIP:DMG: status = 0x86 (UNSUPPORTED_ATTRIBUTE), + [1650618819.921733][2730:2735] CHIP:DMG: }, + [1650618819.921773][2730:2735] CHIP:DMG: + [1650618819.921806][2730:2735] CHIP:DMG: }, + [1650618819.921843][2730:2735] CHIP:DMG: + [1650618819.921870][2730:2735] CHIP:DMG: ], + [1650618819.921905][2730:2735] CHIP:DMG: + [1650618819.921932][2730:2735] CHIP:DMG: InteractionModelRevision = 1 + [1650618819.921961][2730:2735] CHIP:DMG: } + [1650618819.922034][2730:2735] CHIP:TOO: Response Failure: IM Error 0x00000586: General error: 0x86 (UNSUPPORTED_ATTRIBUTE) + [1650618819.922076][2730:2735] CHIP:DMG: WriteClient moving to [AwaitingDe] disabled: true - label: "TH sends the Write Request Message to the DUT to read an attribute which is not writable. DUT responds with the Write Response action" - verification: - "In case of chip tool, here is an example command to use - ./out/debug/chip-tool any write-by-id 0x0028 1 test 5 0" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool any write-by-id 0x0028 1 test 1 0 + + [1650618963.559922][2767:2772] CHIP:DMG: WriteResponseMessage = + [1650618963.559950][2767:2772] CHIP:DMG: { + [1650618963.559971][2767:2772] CHIP:DMG: AttributeStatusIBs = + [1650618963.560001][2767:2772] CHIP:DMG: [ + [1650618963.560022][2767:2772] CHIP:DMG: AttributeStatusIB = + [1650618963.560046][2767:2772] CHIP:DMG: { + [1650618963.560067][2767:2772] CHIP:DMG: AttributePathIB = + [1650618963.560092][2767:2772] CHIP:DMG: { + [1650618963.560122][2767:2772] CHIP:DMG: Endpoint = 0x0, + [1650618963.560160][2767:2772] CHIP:DMG: Cluster = 0x28, + [1650618963.560237][2767:2772] CHIP:DMG: Attribute = 0x0000_0001, + [1650618963.560305][2767:2772] CHIP:DMG: } + [1650618963.560350][2767:2772] CHIP:DMG: + [1650618963.560389][2767:2772] CHIP:DMG: StatusIB = + [1650618963.560423][2767:2772] CHIP:DMG: { + [1650618963.560454][2767:2772] CHIP:DMG: status = 0x88 (UNSUPPORTED_WRITE), + [1650618963.560487][2767:2772] CHIP:DMG: }, + [1650618963.560519][2767:2772] CHIP:DMG: + [1650618963.560570][2767:2772] CHIP:DMG: }, + [1650618963.560604][2767:2772] CHIP:DMG: + [1650618963.560627][2767:2772] CHIP:DMG: ], + [1650618963.560658][2767:2772] CHIP:DMG: + [1650618963.560682][2767:2772] CHIP:DMG: InteractionModelRevision = 1 + [1650618963.560706][2767:2772] CHIP:DMG: } + [1650618963.560773][2767:2772] CHIP:TOO: Response Failure: IM Error 0x00000588: General error: 0x88 (UNSUPPORTED_WRITE) disabled: true - label: @@ -168,7 +439,35 @@ tests: attribute in the path that requires a privilege that is not granted for the cluster in the path. DUT responds with the Write Response action" - verification: "Unsupported in TE8 - Out of scope" + verification: | + '' ./chip-tool thermostatuserinterfaceconfiguration write temperature-display-mode 2 1 1 --commissioner-nodeid 1234 + + [1650552778.852950][17227:17232] CHIP:DMG: WriteResponseMessage = + [1650552778.852981][17227:17232] CHIP:DMG: { + [1650552778.853009][17227:17232] CHIP:DMG: AttributeStatusIBs = + [1650552778.853058][17227:17232] CHIP:DMG: [ + [1650552778.853089][17227:17232] CHIP:DMG: AttributeStatusIB = + [1650552778.853127][17227:17232] CHIP:DMG: { + [1650552778.853162][17227:17232] CHIP:DMG: AttributePathIB = + [1650552778.853203][17227:17232] CHIP:DMG: { + [1650552778.853241][17227:17232] CHIP:DMG: Endpoint = 0x1, + [1650552778.853282][17227:17232] CHIP:DMG: Cluster = 0x204, + [1650552778.853324][17227:17232] CHIP:DMG: Attribute = 0x0000_0000, + [1650552778.853366][17227:17232] CHIP:DMG: } + [1650552778.853413][17227:17232] CHIP:DMG: + [1650552778.853454][17227:17232] CHIP:DMG: StatusIB = + [1650552778.853490][17227:17232] CHIP:DMG: { + [1650552778.853531][17227:17232] CHIP:DMG: status = 0x7e (UNSUPPORTED_ACCESS), + [1650552778.853566][17227:17232] CHIP:DMG: }, + [1650552778.853608][17227:17232] CHIP:DMG: + [1650552778.853642][17227:17232] CHIP:DMG: }, + [1650552778.853680][17227:17232] CHIP:DMG: + [1650552778.853712][17227:17232] CHIP:DMG: ], + [1650552778.853751][17227:17232] CHIP:DMG: + [1650552778.853780][17227:17232] CHIP:DMG: InteractionModelRevision = 1 + [1650552778.853813][17227:17232] CHIP:DMG: } + [1650552778.853890][17227:17232] CHIP:TOO: Response Failure: IM Error 0x0000057E: General error: 0x7e (UNSUPPORTED_ACCESS) + [1650552778.853935][17227:17232] CHIP:DMG: WriteClient moving to [AwaitingDe] disabled: true - label: @@ -176,7 +475,8 @@ tests: attribute in the path that is fabric scoped, and the associated fabric does not match the accessing fabric DUT responds with the Write Response action" - verification: "Unsupported in TE8 - Out of scope" + verification: | + '' ./chip-tool thermostatuserinterfaceconfiguration write temperature-display-mode 2 1 1 --commissioner-fabricid 2341 disabled: true - label: @@ -186,10 +486,39 @@ tests: Specific Attribute. On receipt of this message, DUT should send a write response action with the modified attribute value to the TH. Repeat the above steps 3 times." - verification: - "In case of chip tool, here is an example command to use ./chip-tool - basic write node-label TE8 1 1 ./chip-tool basic write node-label TE7 - 1 1 ./chip-tool basic write node-label TE6 1 1" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool basic write node-label TE8 1 0 + [1650619886.253187][2837:2842] CHIP:DMG: WriteResponseMessage = + [1650619886.253239][2837:2842] CHIP:DMG: { + [1650619886.253270][2837:2842] CHIP:DMG: AttributeStatusIBs = + [1650619886.253330][2837:2842] CHIP:DMG: [ + [1650619886.253382][2837:2842] CHIP:DMG: AttributeStatusIB = + [1650619886.253435][2837:2842] CHIP:DMG: { + [1650619886.253479][2837:2842] CHIP:DMG: AttributePathIB = + [1650619886.253558][2837:2842] CHIP:DMG: { + [1650619886.253600][2837:2842] CHIP:DMG: Endpoint = 0x0, + [1650619886.253655][2837:2842] CHIP:DMG: Cluster = 0x28, + [1650619886.253715][2837:2842] CHIP:DMG: Attribute = 0x0000_0005, + [1650619886.253762][2837:2842] CHIP:DMG: } + [1650619886.253829][2837:2842] CHIP:DMG: + [1650619886.253887][2837:2842] CHIP:DMG: StatusIB = + [1650619886.253940][2837:2842] CHIP:DMG: { + [1650619886.254001][2837:2842] CHIP:DMG: status = 0x00 (SUCCESS), + [1650619886.254062][2837:2842] CHIP:DMG: }, + [1650619886.254108][2837:2842] CHIP:DMG: + [1650619886.254158][2837:2842] CHIP:DMG: }, + [1650619886.254207][2837:2842] CHIP:DMG: + [1650619886.254255][2837:2842] CHIP:DMG: ], + [1650619886.254301][2837:2842] CHIP:DMG: + [1650619886.254349][2837:2842] CHIP:DMG: InteractionModelRevision = 1 + [1650619886.254383][2837:2842] CHIP:DMG: } + + + + '' ./chip-tool basic write node-label TE7 1 0 + '' ./chip-tool basic write node-label TE6 1 0 disabled: true - label: @@ -199,21 +528,24 @@ tests: Endpoint, Specific Cluster and Specific Attribute. On receipt of this message, DUT should send a write response action with the modified attribute value to the TH." - verification: "Need to get more info" + verification: | + '' ./chip-tool onoff read start-up-on-off 1 0xFFFF disabled: true - label: "TH sends the Write Request Message to the DUT to append an attribute value On receipt of this message, DUT should send a write response action with the modified attribute value to the TH." - verification: "Need to get more info" + verification: | + Out of Scope for V1.0 disabled: true - label: "TH sends the Write Request Message to the DUT to delete an attribute value On receipt of this message, DUT should send a write response action with the modified attribute value to the TH." - verification: "Need to get more info" + verification: | + Out of Scope for V1.0 disabled: true - label: @@ -222,7 +554,63 @@ tests: should contain one valid CommandDataIB, which has the specific Endpoint, Specific Cluster and Specific Attribute. Set SuppressResponse to True." - verification: "Need to get more info" + verification: | + '' ./chip-tool onoff write start-up-on-off null 1 1 --suppressResponse 1 + + [1650619929.786037][2847:2852] CHIP:DMG: WriteResponseMessage = + [1650619929.786074][2847:2852] CHIP:DMG: { + [1650619929.786105][2847:2852] CHIP:DMG: AttributeStatusIBs = + [1650619929.786148][2847:2852] CHIP:DMG: [ + [1650619929.786243][2847:2852] CHIP:DMG: AttributeStatusIB = + [1650619929.786308][2847:2852] CHIP:DMG: { + [1650619929.786346][2847:2852] CHIP:DMG: AttributePathIB = + [1650619929.786391][2847:2852] CHIP:DMG: { + [1650619929.786433][2847:2852] CHIP:DMG: Endpoint = 0x1, + [1650619929.786546][2847:2852] CHIP:DMG: Cluster = 0x6, + [1650619929.786598][2847:2852] CHIP:DMG: Attribute = 0x0000_4003, + [1650619929.786649][2847:2852] CHIP:DMG: } + [1650619929.786703][2847:2852] CHIP:DMG: + [1650619929.786747][2847:2852] CHIP:DMG: StatusIB = + [1650619929.786816][2847:2852] CHIP:DMG: { + [1650619929.786862][2847:2852] CHIP:DMG: status = 0x00 (SUCCESS), + [1650619929.786902][2847:2852] CHIP:DMG: }, + [1650619929.786944][2847:2852] CHIP:DMG: + [1650619929.786980][2847:2852] CHIP:DMG: }, + [1650619929.787080][2847:2852] CHIP:DMG: + [1650619929.787112][2847:2852] CHIP:DMG: ], + [1650619929.787153][2847:2852] CHIP:DMG: + [1650619929.787219][2847:2852] CHIP:DMG: InteractionModelRevision = 1 + [1650619929.787252][2847:2852] CHIP:DMG: } + + '' ./chip-tool onoff read start-up-on-off 1 1 + [1650619951.210265][2854:2859] CHIP:DMG: ReportDataMessage = + [1650619951.210320][2854:2859] CHIP:DMG: { + [1650619951.210362][2854:2859] CHIP:DMG: AttributeReportIBs = + [1650619951.210428][2854:2859] CHIP:DMG: [ + [1650619951.210476][2854:2859] CHIP:DMG: AttributeReportIB = + [1650619951.210541][2854:2859] CHIP:DMG: { + [1650619951.210701][2854:2859] CHIP:DMG: AttributeDataIB = + [1650619951.210763][2854:2859] CHIP:DMG: { + [1650619951.210823][2854:2859] CHIP:DMG: DataVersion = 0x3f15b287, + [1650619951.210923][2854:2859] CHIP:DMG: AttributePathIB = + [1650619951.210986][2854:2859] CHIP:DMG: { + [1650619951.211043][2854:2859] CHIP:DMG: Endpoint = 0x1, + [1650619951.211107][2854:2859] CHIP:DMG: Cluster = 0x6, + [1650619951.211165][2854:2859] CHIP:DMG: Attribute = 0x0000_4003, + [1650619951.211226][2854:2859] CHIP:DMG: } + [1650619951.211284][2854:2859] CHIP:DMG: + [1650619951.211344][2854:2859] CHIP:DMG: Data = NULL + [1650619951.211404][2854:2859] CHIP:DMG: }, + [1650619951.211528][2854:2859] CHIP:DMG: + [1650619951.211580][2854:2859] CHIP:DMG: }, + [1650619951.211636][2854:2859] CHIP:DMG: + [1650619951.211680][2854:2859] CHIP:DMG: ], + [1650619951.211735][2854:2859] CHIP:DMG: + [1650619951.211780][2854:2859] CHIP:DMG: SuppressResponse = true, + [1650619951.211873][2854:2859] CHIP:DMG: InteractionModelRevision = 1 + [1650619951.211916][2854:2859] CHIP:DMG: } + [1650619951.212190][2854:2859] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0006 Attribute 0x0000_4003 DataVersion: 1058386567 + [1650619951.212306][2854:2859] CHIP:TOO: StartUpOnOff: null disabled: true - label: @@ -233,7 +621,10 @@ tests: indicated. TH sends a second Write Request Message to the DUT to modify the value of an attribute with the dataversion field set to the value received earlier." - verification: - "Unsupported in TE8 - https://github.com/project-chip/connectedhomeip/issues/15812" + verification: | + ''./chip-tool onoff read start-up-on-off 1 1 + + '' ./chip-tool onoff write start-up-on-off 1 1 1 + + '' ./chip-tool onoff write start-up-on-off 2 1 1 --data-version 0x365b6fd5 disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_IDM_4_1.yaml b/src/app/tests/suites/certification/Test_TC_IDM_4_1.yaml index dfb842fb087cf5..64d2284430fbab 100644 --- a/src/app/tests/suites/certification/Test_TC_IDM_4_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_IDM_4_1.yaml @@ -23,149 +23,30 @@ config: tests: - label: "DUT sends a subscription request message to the target node/reference - device for a single attribute of data type bool." - verification: - "1. The subscripbe tests sudo ./chip-tool tests TestSubscribe_OnOff 1 - , can be a good example how controller subscribes and DUT responds to. - TH here is all-cluster/lighting app that the the DUT can subscribe to. - 1. Verify the on refernce application receives Subscription request - Msg [1635857801.163357][2764:2764] CHIP:DMG: IM RH moving to - [Initialized] [1635857801.163395][2764:2764] CHIP:DMG: - SubscribeRequest = [1635857801.163428][2764:2764] CHIP:DMG: { - [1635857801.163456][2764:2764] CHIP:DMG: AttributePathList = - [1635857801.163490][2764:2764] CHIP:DMG: [ - [1635857801.163522][2764:2764] CHIP:DMG: AttributePath = - [1635857801.163561][2764:2764] CHIP:DMG: { - [1635857801.163597][2764:2764] CHIP:DMG: NodeId = 0x1, - [1635857801.163636][2764:2764] CHIP:DMG: EndpointId = 0x0, - [1635857801.163682][2764:2764] CHIP:DMG: ClusterId = 0x6, - [1635857801.163724][2764:2764] CHIP:DMG: FieldTag = 0x0000_000 0, - [1635857801.163760][2764:2764] CHIP:DMG: } - [1635857801.163799][2764:2764] CHIP:DMG: - [1635857801.163833][2764:2764] CHIP:DMG: ], - [1635857801.163875][2764:2764] CHIP:DMG: - [1635857801.163918][2764:2764] CHIP:DMG: MinIntervalSeconds = 0xa, - [1635857801.163953][2764:2764] CHIP:DMG: kMaxInterval = 0x12c, - [1635857801.163986][2764:2764] CHIP:DMG: KeepSubscriptions = false, - [1635857801.164017][2764:2764] CHIP:DMG: }shed pending ack for - MessageCounter:1608870265 on exchange 54981i - [1635857801.183800][3508:3513] CHIP:EM: Received message of type 0x5 - with protocolId (0, 1) and MessageCounter:1 on exchange 54982i - [1635857801.183869][3508:3513] CHIP:EM: Rxd Ack; Removing - MessageCounter:0 from Retrans Table on exchange 54982i - [1635857801.183905][3508:3513] CHIP:EM: Removed CHIP MessageCounter:0 - from RetransTable on exchange 54982i [1635857801.183960][3508:3513] - CHIP:DMG: ReportData = [1635857801.183997][3508:3513] CHIP:DMG: { - [1635857801.184032][3508:3513] CHIP:DMG: SubscriptionId = - 0xf94fde1c9a9a2d6f, [1635857801.184069][3508:3513] CHIP:DMG: - AttributeDataList = [1635857801.184106][3508:3513] CHIP:DMG: [ - [1635857801.184142][3508:3513] CHIP:DMG: AttributeDataElement = - [1635857801.184193][3508:3513] CHIP:DMG: { - [1635857801.184231][3508:3513] CHIP:DMG: AttributePath = - [1635857801.184271][3508:3513] CHIP:DMG: { - [1635857801.184321][3508:3513] CHIP:DMG: NodeId = 0x1, - [1635857801.184376][3508:3513] CHIP:DMG: EndpointId = 0x0, - [1635857801.184425][3508:3513] CHIP:DMG: ClusterId = 0x6, - [1635857801.184478][3508:3513] CHIP:DMG: FieldTag = 0x0000_0000, - [1635857801.184523][3508:3513] CHIP:DMG: } - [1635857801.184578][3508:3513] CHIP:DMG: - [1635857801.184624][3508:3513] CHIP:DMG: Status = 0x86, - [1635857801.184666][3508:3513] CHIP:DMG: }, - [1635857801.184710][3508:3513] CHIP:DMG: - [1635857801.184744][3508:3513] CHIP:DMG: ], - [1635857801.184785][3508:3513] CHIP:DMG: - [1635857801.184817][3508:3513] CHIP:DMG: } - [1635857801.184920][3508:3513] CHIP:ZCL: ReadAttributesResponse: - [1635857801.184951][3508:3513] CHIP:ZCL: ClusterId: 0x0000_0006 - [1635857801.184984][3508:3513] CHIP:ZCL: attributeId: 0x0000_0000 - [1635857801.185015][3508:3513] CHIP:ZCL: status: UnsupportedAttribute - (0x0086) [1635857801.185066][3508:3513] CHIP:DMG: Client[0] moving to - [AwaitingSubscribeResponse] [1635857801.185114][3508:3513] CHIP:EM: - Piggybacking Ack for MessageCounter:1 on exchange: 54982i - [1635857801.185187][3508:3513] CHIP:IN: Prepared encrypted message - 0xaaaaf2abf810 to 0x0000000000000001 of type 0x1 and protocolId (0, 1) - on exchange 54982i with MessageCounter:1. - [1635857801.185243][3508:3513] CHIP:IN: Sending encrypted msg - 0xaaaaf2abf810 with MessageCounter:1 to 0x0000000000000001 at - monotonic time: 2817379 msec [1635857801.186590][3508:3513] CHIP:EM: - Received message of type 0x4 with protocolId (0, 1) and - MessageCounter:2 on exchange 54982i [1635857801.186661][3508:3513] - CHIP:EM: Rxd Ack; Removing MessageCounter:1 from Retrans Table on - exchange 54982i [1635857801.186702][3508:3513] CHIP:EM: Removed CHIP - MessageCounter:1 from RetransTable on exchange 54982i - [1635857801.186760][3508:3513] CHIP:DMG: SubscribeResponse = - [1635857801.186801][3508:3513] CHIP:DMG: { - [1635857801.186839][3508:3513] CHIP:DMG: SubscriptionId = - 0xf94fde1c9a9a2d6f, [1635857801.186882][3508:3513] CHIP:DMG: - MinIntervalFloorSeconds = 0xa, [1635857801.186922][3508:3513] - CHIP:DMG: MaxIntervalCeilingSeconds = 0x12c, - [1635857801.186960][3508:3513] CHIP:DMG: } - [1635857801.187006][3508:3513] CHIP:ZCL: SubscribeResponse: - [1635857801.187040][3508:3513] CHIP:ZCL: SubscriptionId: - 0xf94fde1c9a9a2d6f [1635857801.187073][3508:3513] CHIP:ZCL: - ApplicationIdentifier: 0 [1635857801.187106][3508:3513] CHIP:ZCL: - status: EMBER_ZCL_STATUS_SUCCESS (0x00) [1635857801.187144][3508:3513] - CHIP:TOO: Default Success Response [1635857801.187207][3508:3513] - CHIP:DMG: Client[0] moving to [SubscriptionActive] - [1635857801.187251][3508:3513] CHIP:EM: Sending Standalone Ack for - MessageCounter:2 on exchange 54982i [1635857801.187320][3508:3513] - CHIP:IN: Prepared encrypted message 0xffff737ed930 to - 0x0000000000000001 of type 0x10 and protocolId (0, 0) on exchange - 54982i with MessageCounter:2. [1635857801.187377][3508:3513] CHIP:IN: - Sending encrypted msg 0xffff737ed930 with MessageCounter:2 to - 0x0000000000000001 at monotonic time: 2817381 msec - [1635857801.187496][3508:3513] CHIP:EM: Flushed pending ack for - MessageCounter:2 on exchange 54982i [1635857801.187720][3508:3508] - CHIP:CTL: Shutting down the commissioner - [1635857801.187783][3508:3508] CHIP:CTL: Shutting down the controller - [1635857801.190092][3508:3508] CHIP:CTL: Shutting down the System - State, this will teardown the CHIP Stack - [1635857801.190156][3508:3508] CHIP:SPT: VerifyOrDie failure at - ../third_party/connectedhomeip/src/messaging/ExchangeContext.cpp:211: - mExchangeMgr != nullptr && GetReferenceCount() > 0" + device for a single attribute of any data type supported." + verification: | + sudo ./chip-tool onoff subscribe on-time 0 100 0 1 1 + + TH Side + [1650620003.657208][2221:2221] CHIP:DMG: StatusResponseMessage = + [1650620003.657272][2221:2221] CHIP:DMG: { + [1650620003.657310][2221:2221] CHIP:DMG: Status = 0x0, + [1650620003.657346][2221:2221] CHIP:DMG: InteractionModelRevision = 1 + [1650620003.657380][2221:2221] CHIP:DMG: } disabled: true - label: "DUT sends the subscription request message to TH TH sends a report data DUT sends the status response back to TH" - verification: - "TH here is all-cluster/lighting app that the the DUT can subscribe - to. 1. Verify the on refernce application receives Subscription - request Msg [1633048577.053891][19753:19753] CHIP:DMG: IM RH moving to - [Initialized] [1633048577.053928][19753:19753] CHIP:DMG: - SubscribeRequest = [1633048577.053951][19753:19753] CHIP:DMG: { - [1633048577.053972][19753:19753] CHIP:DMG: AttributePathList = - [1633048577.053997][19753:19753] CHIP:DMG: [ - [1633048577.054020][19753:19753] CHIP:DMG: AttributePath = - [1633048577.054052][19753:19753] CHIP:DMG: { - [1633048577.054083][19753:19753] CHIP:DMG: NodeId = 0xbc5c01, - [1633048577.054118][19753:19753] CHIP:DMG: EndpointId = 0x0, - [1633048577.054152][19753:19753] CHIP:DMG: ClusterId = 0x6, - [1633048577.054185][19753:19753] CHIP:DMG: FieldTag = 0x0, - [1633048577.054269][19753:19753] CHIP:DMG: } - [1633048577.054304][19753:19753] CHIP:DMG: - [1633048577.054330][19753:19753] CHIP:DMG: ], - [1633048577.054407][19753:19753] CHIP:DMG: - [1633048577.054432][19753:19753] CHIP:DMG: MinIntervalSeconds = 0xa, - [1633048577.054487][19753:19753] CHIP:DMG: kMaxInterval = 0x12c, - [1633048577.054512][19753:19753] CHIP:DMG: } 3. Verify on the DUT (if - DUT supports log) that you recieve response data - [1633048577.057997][19753:19753] CHIP:EM: Removed CHIP - MessageCounter:0000000D from RetransTable - [1633048577.058036][19753:19753] CHIP:DMG: StatusResponse = - [1633048577.058060][19753:19753] CHIP:DMG: { - [1633048577.058081][19753:19753] CHIP:DMG: Status = 0x0, - [1633048577.058102][19753:19753] CHIP:DMG: } - [1633048577.058126][19753:19753] CHIP:DMG: In state - AwaitingReportResponse, receive status response, status code is 0 4. - On the controller(DUT) we get the SubscribeResponse, make sure - SubscriptionId is same as in above step 2. - [1633066406.050309][1602230:1602238] CHIP:DMG: SubscribeResponse = - [1633066406.050347][1602230:1602238] CHIP:DMG: { - [1633066406.050381][1602230:1602238] CHIP:DMG: SubscriptionId = - 0x81c9743c808f7049, [1633066406.050424][1602230:1602238] CHIP:DMG: - MinIntervalFloorSeconds = 0xa, [1633066406.050460][1602230:1602238] - CHIP:DMG: MaxIntervalCeilin" + verification: | + '' ./chip-tool levelcontrol subscribe on-level 0 100 0 1 1 + TH side + [1650620108.691178][2221:2221] CHIP:DMG: StatusResponseMessage = + [1650620108.691207][2221:2221] CHIP:DMG: { + [1650620108.691231][2221:2221] CHIP:DMG: Status = 0x0, + [1650620108.691256][2221:2221] CHIP:DMG: InteractionModelRevision = 1 + [1650620108.691279][2221:2221] CHIP:DMG: } + [1650620108.691304][2221:2221] CHIP:IM: Received status response, status is 0x00 (SUCCESS) disabled: true - label: @@ -173,47 +54,42 @@ tests: an attribute of data type boolean. Modify that attribute on the TH. TH should send the modified data to the DUT. Repeat the above steps multiple times (3 times)." - verification: - "1. Activate the subscription on the DUT 2. Modify the attribute value - on the TH by sending below cmd Ex: chip-device-ctrl > ./chip-tool - onoff off 1 0 3. Wait 10 secs (as we gave the 10 sec Min interval in - the above cmd) You should recieve ReadAttributesResponse with - ReportData [1633065482.893594][1591764:1591772] CHIP:DMG: ReportData = - [1633065482.893622][1591764:1591772] CHIP:DMG: { - [1633065482.893647][1591764:1591772] CHIP:DMG: SubscriptionId = - 0x1b46258c2ba9407b, [1633065482.893671][1591764:1591772] CHIP:DMG: - AttributeDataList = [1633065482.893697][1591764:1591772] CHIP:DMG: [ - [1633065482.893720][1591764:1591772] CHIP:DMG: AttributeDataElement = - [1633065482.893771][1591764:1591772] CHIP:DMG: { - [1633065482.893802][1591764:1591772] CHIP:DMG: AttributePath = - [1633065482.893838][1591764:1591772] CHIP:DMG: { - [1633065482.893874][1591764:1591772] CHIP:DMG: NodeId = 0x0, - [1633065482.893911][1591764:1591772] CHIP:DMG: EndpointId = 0x1, - [1633065482.893948][1591764:1591772] CHIP:DMG: ClusterId = 0x6, - [1633065482.893983][1591764:1591772] CHIP:DMG: FieldTag = 0x0, - [1633065482.894016][1591764:1591772] CHIP:DMG: } - [1633065482.894055][1591764:1591772] CHIP:DMG: - [1633065482.894091][1591764:1591772] CHIP:DMG: Data = false, - [1633065482.894125][1591764:1591772] CHIP:DMG: DataElementVersion = - 0x0, [1633065482.894156][1591764:1591772] CHIP:DMG: }, - [1633065482.894188][1591764:1591772] CHIP:DMG: - [1633065482.894211][1591764:1591772] CHIP:DMG: ], - [1633065482.894239][1591764:1591772] CHIP:DMG: - [1633065482.894260][1591764:1591772] CHIP:DMG: } - [1633065482.894712][1591764:1591772] CHIP:ZCL: ReadAttributesResponse: - [1633065482.894752][1591764:1591772] CHIP:ZCL: ClusterId: 0x0000_0006 - [1633065482.894779][1591764:1591772] CHIP:ZCL: - IMReadReportAttributesResponseCallback: Missing success callback - [1633065482.894799][1591764:1591772] CHIP:ZCL: - IMReadReportAttributesResponseCallback: Missing TLV Data Filter 4. On - teh server side (all-cluster app) you should recieve Status response, - Status code 0x0 [1633066022.932308][21226:21226] CHIP:DMG: - StatusResponse = [1633066022.932366][21226:21226] CHIP:DMG: { - [1633066022.932416][21226:21226] CHIP:DMG: Status = 0x0, - [1633066022.932468][21226:21226] CHIP:DMG: } 5. After the report - received, Repeat step2 with different values , like on and then off - and then on , you should get ReadAttributesResponse with ReportData - like mentioned in step3." + verification: | + In case of chip tool, here is an example command to use + '' ./chip-tool basic write local-config-disabled 1 1 0 + '' ./chip-tool basic subscribe local-config-disabled 0 100 1 0 + + [1650620484.058559][2221:2221] CHIP:DMG: StatusResponseMessage = + [1650620484.058598][2221:2221] CHIP:DMG: { + [1650620484.058632][2221:2221] CHIP:DMG: Status = 0x0, + [1650620484.058669][2221:2221] CHIP:DMG: InteractionModelRevision = 1 + [1650620484.058703][2221:2221] CHIP:DMG: } + [1650620484.058738][2221:2221] CHIP:IM: Received status response, status is 0x00 (SUCCESS) + + + Verify the above command multiple times by changing attribute value(3 times) + disabled: true + + - label: + "[OPTIONAL] Activate the subscription between the DUT and the TH for + an attribute of data type string. Modify that attribute on the TH. TH + should send the modified data to the DUT. Repeat the above steps + multiple times (3 times). 3" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool basic write node-label 1 1 0 + '' ./chip-tool basic subscribe node-label 0 100 0 1 0 + [1650620543.500119][2221:2221] CHIP:DMG: StatusResponseMessage = + [1650620543.500147][2221:2221] CHIP:DMG: { + [1650620543.500172][2221:2221] CHIP:DMG: Status = 0x0, + [1650620543.500198][2221:2221] CHIP:DMG: InteractionModelRevision = 1 + [1650620543.500222][2221:2221] CHIP:DMG: } + [1650620543.500248][2221:2221] CHIP:IM: Received status response, status is 0x00 (SUCCESS) + + + + Verify the above command multiple times by changing attribute value(3 times) disabled: true - label: @@ -221,9 +97,40 @@ tests: an attribute of data type unsigned integer. Modify that attribute on the TH. TH should send the modified data to the DUT. Repeat the above steps multiple times (3 times)." - verification: - "1. Pick a cluster that has unsigned integer attribute and repeat the - above step" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool any write-by-id 0x0008 0x0010 1 1 1 + '' ./chip-tool any subscribe-by-id 0x0008 0x0010 0 100 0 1 1 + [1650620581.445609][2221:2221] CHIP:DMG: StatusResponseMessage = + [1650620581.445659][2221:2221] CHIP:DMG: { + [1650620581.445701][2221:2221] CHIP:DMG: Status = 0x0, + [1650620581.445746][2221:2221] CHIP:DMG: InteractionModelRevision = 1 + [1650620581.445789][2221:2221] CHIP:DMG: } + [1650620581.445833][2221:2221] CHIP:IM: Received status response, status is 0x00 (SUCCESS) + + + Verify the above command multiple times by changing attribute value(3 times) + disabled: true + + - label: + "[OPTIONAL] Activate the subscription between the DUT and the TH for + an attribute of data type signed integer. Modify that attribute on the + TH. TH should send the modified data to the DUT. Repeat the above + steps multiple times (3 times)." + verification: | + sudo ./chip-tool any write-by-id 0x0008 0x0010 1 1 1 + sudo ./chip-tool any write-by-id 0x0008 0x0010 4 1 1 + sudo ./chip-tool any write-by-id 0x0008 0x0010 5 1 1 + disabled: true + + - label: + "[OPTIONAL] Activate the subscription between the DUT and the TH for + an attribute of data type Floating Point. Modify that attribute on the + TH. TH should send the modified data to the DUT. Repeat the above + steps multiple times (3 times)." + verification: | + DUT implementation required to verify read an attribute of data type floating point disabled: true - label: @@ -232,19 +139,43 @@ tests: of the maximum interval. After the maximum interval, TH sends a report data with the subscription id created during the subscription activation." - verification: - "1. configure the max interval timeout for few seconds on the DUT 2. - create a situation that the accessory cant reach controller for 20 - secs (like removing ethernet cable ..etc) 3. After the timer expiry we - should see the repor on the controller like below > - [1633722365.411081][731663:731671] CHIP:DMG: Subscription Liveness - timeout with peer node 0xbc614e, shutting down - [1633722365.411147][731663:731671] CHIP:ZCL: ReadAttributesResponse: - [1633722365.411168][731663:731671] CHIP:ZCL: ClusterId: 0x0000_0000 - [1633722365.411193][731663:731671] CHIP:ZCL: - IMReadReportAttributesResponseCallback: Missing success callback - [1633722365.411214][731663:731671] CHIP:ZCL: - IMReadReportAttributesResponseCallback: Missing TLV Data Filter - [1633722365.411242][731663:731671] CHIP:DMG: Client[0] moving to - [UNINIT] 4." + verification: | + This is not testable in normal scenario, and needs to be tested as part of Unit test. his test step to be removed from the manual execution. + disabled: true + + - label: + "DUT sends a subscription request message to the target node/reference + device for multiple attributes(3 attributes)." + verification: | + '' ./chip-tool pumpconfigurationandcontrol subscribe max-pressure 0 100 0 1 1 + '' ./chip-tool pumpconfigurationandcontrol subscribe max-speed 0 100 0 1 1 + '' ./chip-tool pumpconfigurationandcontrol subscribe max-flow 0 100 0 1 1 + '' ./chip-tool pumpconfigurationandcontrol subscribe min-const-pressure 0 100 0 1 1 + disabled: true + + - label: + "Activate the subscription between the DUT and the TH for an attribute + Force the TH to send a report data with no data and Suppress Response + set to True" + verification: | + This is not testable in normal scenario, and needs to be tested as part of Unit test. his test step to be removed from the manual execution. + disabled: true + + - label: + "[OPTIONAL] Activate the subscription between the DUT and the TH for + an attribute of data type list. Modify that attribute on the TH. TH + should send the modified data to the DUT. Repeat the above steps + multiple times (3 times)." + verification: | + '' ./chip-tool modeselect subscribe supported-modes 0 100 0 1 1 + '' ./chip-tool modeselect subscribe supported-modes 1 100 0 1 1 + '' ./chip-tool modeselect subscribe supported-modes 2 100 0 1 1 + disabled: true + + - label: + "DUT sends a subscription request message to the TH for a single + attribute of any data type supported. Reboot the DUT." + verification: | + '' ./chip-tool pumpconfigurationandcontrol subscribe max-speed 0 100 0 1 1 + after reboot the DUT verify once that the TH does not send a report data message to the DUT disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_IDM_4_2.yaml b/src/app/tests/suites/certification/Test_TC_IDM_4_2.yaml index dd810661ff9d8d..dcff683d30201a 100644 --- a/src/app/tests/suites/certification/Test_TC_IDM_4_2.yaml +++ b/src/app/tests/suites/certification/Test_TC_IDM_4_2.yaml @@ -24,27 +24,81 @@ tests: - label: "TH sends a subscription message to the DUT. DUT sends a report data action to the TH" - verification: - "In case of chip tool, here is an example command to use sudo - ./chip-tool onoff subscribe on-time 0 100 0 1 1" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool onoff subscribe on-time 0 100 0 1 1 + [1649154120.826290][16352:16357] CHIP:DMG: ReportDataMessage = + [1649154120.826323][16352:16357] CHIP:DMG: { + [1649154120.826353][16352:16357] CHIP:DMG: SubscriptionId = 0xb7c7315880309e65, + [1649154120.826391][16352:16357] CHIP:DMG: AttributeReportIBs = + [1649154120.826431][16352:16357] CHIP:DMG: [ + [1649154120.826461][16352:16357] CHIP:DMG: AttributeReportIB = + [1649154120.826504][16352:16357] CHIP:DMG: { + [1649154120.826538][16352:16357] CHIP:DMG: AttributeDataIB = + [1649154120.826581][16352:16357] CHIP:DMG: { + [1649154120.826621][16352:16357] CHIP:DMG: DataVersion = 0x53788f7b, + [1649154120.826664][16352:16357] CHIP:DMG: AttributePathIB = + [1649154120.826705][16352:16357] CHIP:DMG: { + [1649154120.826747][16352:16357] CHIP:DMG: Endpoint = 0x1, + [1649154120.826793][16352:16357] CHIP:DMG: Cluster = 0x6, + [1649154120.826853][16352:16357] CHIP:DMG: Attribute = 0x0000_4001, + [1649154120.826914][16352:16357] CHIP:DMG: } + [1649154120.827058][16352:16357] CHIP:DMG: + [1649154120.827124][16352:16357] CHIP:DMG: Data = 0, + [1649154120.827190][16352:16357] CHIP:DMG: }, + [1649154120.827258][16352:16357] CHIP:DMG: + [1649154120.827309][16352:16357] CHIP:DMG: }, + [1649154120.827369][16352:16357] CHIP:DMG: + [1649154120.827413][16352:16357] CHIP:DMG: ], + [1649154120.827470][16352:16357] CHIP:DMG: + [1649154120.827514][16352:16357] CHIP:DMG: InteractionModelRevision = 1 + [1649154120.827560][16352:16357] CHIP:DMG: } disabled: true - label: "TH sends a subscription message to the DUT. DUT sends a report data action to the TH TH sends a status response" - verification: - "In case of chip tool, here is an example command to use sudo - ./chip-tool onoff subscribe on-time 0 100 0 1 1" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool onoff subscribe on-time 0 100 0 1 1 + [1649154179.610990][16364:16369] CHIP:DMG: SubscribeResponseMessage = + [1649154179.611028][16364:16369] CHIP:DMG: { + [1649154179.611062][16364:16369] CHIP:DMG: SubscriptionId = 0xbf7f880103de5b3b, + [1649154179.611100][16364:16369] CHIP:DMG: MinIntervalFloorSeconds = 0x0, + [1649154179.611136][16364:16369] CHIP:DMG: MaxIntervalCeilingSeconds = 0x64, + [1649154179.611173][16364:16369] CHIP:DMG: InteractionModelRevision = 1 + [1649154179.611206][16364:16369] CHIP:DMG: } + disabled: true + + - label: + "DUT and TH activate the subscription. Change the value of the + attribute which is being subscribed on the DUT by manually changing + some settings on the device. Example: Temperature sensor may update + the value of the room temperature. Turning on/off on a light bulb." + verification: | + This testr needs to be tested by changing the controls available in the DUT and then read the value. And can't be tested with Soft DUT & has dependency of Vendor specific DUT support. disabled: true - label: "DUT and TH activate the subscription. Change the value of the attribute which is being subscribed on the DUT by sending an IMWrite or Invoke message to the DUT from the TH." - verification: - "In case of chip tool, here is an example command to use sudo - ./chip-tool levelcontrol write on-level 2 1 1 sudo ./chip-tool - levelcontrol subscribe on-level 0 100 0 1 1" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool levelcontrol write on-level 2 1 1 + '' ./chip-tool levelcontrol subscribe on-level 0 100 0 1 1 + disabled: true + + - label: + 'DUT and TH activate the subscription. Change the value of the + attribute which is being subscribed on the DUT. TH force sends a + status response with an "inactive subscription". Change the value of + the attribute which is being subscribed on the DUT.' + verification: | + This is not testable in normal scenario, and needs to be tested as part of Unit test. his test step to be removed from the manual execution. disabled: true - label: @@ -53,11 +107,12 @@ tests: should send the report data with the modified attribute value. Repeat the above steps multiple times (3 times) before the max interval time specified during the subscription activation." - verification: - "In case of chip tool, here is an example command to use sudo - ./chip-tool basic write local-config-disabled 1 1 0 sudo ./chip-tool - basic subscribe local-config-disabled 0 100 0 1 0 Verify the above - command multiple times(3 times)" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool basic write local-config-disabled 1 1 0 + '' ./chip-tool basic subscribe local-config-disabled 0 100 0 1 0 + Verify the above command multiple times(3 times) disabled: true - label: @@ -66,11 +121,13 @@ tests: DUT should send the report data with the modified attribute value Repeat the above steps multiple times (3 times) before the max interval time specified during the subscription activation." - verification: - "In case of chip tool, here is an example command to use sudo - ./chip-tool basic write node-label 1 1 0 sudo ./chip-tool basic - subscribe node-label 0 100 0 1 0 Verify the above command multiple - times(3 times)" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool basic write node-label 1 1 0 + '' ./chip-tool basic subscribe node-label 0 100 0 1 0 + + Verify the above command multiple times(3 times) disabled: true - label: @@ -79,11 +136,12 @@ tests: the DUT. DUT should send the report data with the modified attribute value. Repeat the above steps multiple times (3 times) before the max interval time specified during the subscription activation.' - verification: - "In case of chip tool, here is an example command to use sudo - ./chip-tool any write-by-id 0x0008 0x0010 1 1 1 sudo ./chip-tool any - subscribe-by-id 0x0008 0x0010 0 100 0 1 1 Verify the above command - multiple times(3 times)" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool any write-by-id 0x0008 0x0010 1 1 1 + '' ./chip-tool any subscribe-by-id 0x0008 0x0010 0 100 0 1 1 + Verify the above command multiple times(3 times) disabled: true - label: @@ -92,8 +150,8 @@ tests: the DUT. DUT should send the report data with the modified attribute value. Repeat the above steps multiple times (3 times)before the max interval time specified during the subscription activation.' - verification: - "wirte to an attribute of type signed integer to the Harness" + verification: | + wirte to an attribute of type signed integer to the Harness disabled: true - label: @@ -102,26 +160,49 @@ tests: the DUT. DUT should send the report data with the modified attribute value. Repeat the above steps multiple times (3 times) before the max interval time specified during the subscription activation.' - verification: "wirte to an attribute of type floating to the Harness" + verification: | + wirte to an attribute of type floating to the Harness + disabled: true + + - label: + "Activate the subscription between the DUT and the TH for any + attribute After the Maximum interval time is elapsed, TH should send + another subscription request message with different parameters than + before. Change the value of the attribute requested on the DUT." + verification: | + '' ./chip-tool basic write local-config-disabled 1 1 0 + '' ./chip-tool basic subscribe local-config-disabled 0 100 0 1 0 + '' ./chip-tool basic write local-config-disabled 2 1 0 + '' ./chip-tool basic subscribe local-config-disabled 0 100 0 1 0 disabled: true - label: "Activate the subscription between the DUT and the TH for any attribute After the Maximum interval time is elapsed, change the value of the attribute requested on the DUT." - verification: - "In case of chip tool, here is an example command to use sudo - ./chip-tool levelcontrol write on-level 2 1 1 sudo ./chip-tool - levelcontrol subscribe on-level 0 100 0 1 1" + verification: | + This is not testable in normal scenario, and needs to be tested as part of Unit test. his test step to be removed from the manual execution. + disabled: true + + - label: + "Activate the subscription between the DUT and the TH for an attribute + Reboot the DUT. Change the value of the attribute on the DUT." + verification: | + '' ./chip-tool basic write node-label 5 1 0 + '' ./chip-tool basic subscribe node-label 0 100 0 1 0 + Reboot the DUT + '' ./chip-tool basic write node-label 1 1 0 + '' ./chip-tool basic subscribe node-label 0 100 0 1 0 disabled: true - label: "Activate the subscription between the DUT and the TH for an attribute There are no attribute value changes before MaxInterval elapses." - verification: - "In case of chip tool, here is an example command to use sudo - ./chip-tool any write-by-id 0x0204 0 1 1 1 sudo ./chip-tool any - subscribe-by-id 0x0204 0 1 1 1" + verification: | + In case of chip tool, here is an example command to use + + '' ./chip-tool any write-by-id 0x0204 0 1 1 1 + '' ./chip-tool any subscribe-by-id 0x0204 0 1 1 1 disabled: true - label: @@ -130,7 +211,10 @@ tests: should send the report data with the modified attribute value. Repeat the above steps multiple times (3 times) before the max interval time specified during the subscription activation." - verification: "wirte to an attribute of type list integer to the Harness" + verification: | + '' ./chip-tool modeselect subscribe supported-modes 0 100 0 1 1 + '' ./chip-tool modeselect subscribe supported-modes 1 100 0 1 1 + '' ./chip-tool modeselect subscribe supported-modes 2 100 0 1 1 disabled: true - label: @@ -139,7 +223,8 @@ tests: between DUT and the TH. Initiate another subscription request action to the DUT for another attribute with the KeepSubscriptions flag set to True. Change both the attribute values on the DUT." - verification: "https://github.com/project-chip/connectedhomeip/issues/15845" + verification: | + '' ./chip-tool onoff subscribestart-up-on-off null 1 1 --suppressResponse 1 disabled: true - label: @@ -148,7 +233,25 @@ tests: between DUT and the TH. Initiate another subscription request action to the DUT for the same attribute with the KeepSubscriptions flag set to True. Change both the attribute values on the DUT." - verification: "https://github.com/project-chip/connectedhomeip/issues/15845" + verification: | + '' ./chip-tool onoff subscribe start-up-on-off 1 1 --suppressResponse 1 + disabled: true + + - label: + "TH sends a subscription request action for multiple + attributes/events. (1 attribute, 1 event). Change the value of the + attribute and trigger an action on the DUT to trigger the event." + verification: | + '' ./chip-tool basic subscribe node-label 0 100 0 1 0 + '' ./chip-tool any subscribe-event-by-id 0x0033 0x01 0 100 0 1 1(trigger an action on the DUT to trigger the event) + disabled: true + + - label: + "TH sends a subscription request action for attribute wildcard - + AttributePath = [[Endpoint = EndpointID, Cluster = ClusterID]]. Change + all or few of the attributes on the DUT" + verification: | + ./chip-tool any subscribe-by-id 0xFFFFFFFF 0xFFFFFFFF 0 100 0 1 0xFFFF disabled: true - label: @@ -158,7 +261,7 @@ tests: with the data version. Tear down the subscription for that attribute. Start another subscription with the DataVersionFilter field set to the data version received above." - verification: - "Unsupported in TE8 - https://github.com/project-chip/connectedhomeip/issues/15812" + verification: | + '' ./chip-tool basic subscribe node-label 0 100 0 1 0 + '' ./chip-tool basic subscribe local-config-disabled 0 200 0 1 0 --data-version 0x42d4af15 disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_IDM_5_1.yaml b/src/app/tests/suites/certification/Test_TC_IDM_5_1.yaml index 2b1015027e4868..cdc9ff1801c13f 100644 --- a/src/app/tests/suites/certification/Test_TC_IDM_5_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_IDM_5_1.yaml @@ -13,8 +13,7 @@ # 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: - 19.7.1. [TC-IDM-5.1] Timed Request Action from DUT to TH [DUT - Controller] +name: 3.7.1. [TC-IDM-5.1] Timed Request Action from DUT to TH [DUT - Controller] config: nodeId: 0x12344321 @@ -27,41 +26,71 @@ tests: Request Message to the TH after receiving the status response message from the TH. The Time Request Message should contain a timeout value in milliseconds. (Example - 200 milliseconds)" - verification: - "Chip-tool as controller , here is the example command you can use - sudo ./chip-tool onoff on 0x9f2bf1a1e3cc12c7 1 - --timedInteractionTimeoutMs 100 on the TH (reference all cluster app) - you should see [1641535680.295759][3878:3878] CHIP:DMG: - TimedRequestMessage = [1641535680.295785][3878:3878] CHIP:DMG: { - [1641535680.295806][3878:3878] CHIP:DMG: TimeoutMs = 0x64, - [1641535680.295828][3878:3878] CHIP:DMG: } DUT should receive the - status response messge [1641535680.296922][30856:30861] CHIP:DMG: - StatusResponseMessage = [1641535680.296965][30856:30861] CHIP:DMG: { - [1641535680.297002][30856:30861] CHIP:DMG: Status = 0x0, - [1641535680.297040][30856:30861] CHIP:DMG: } TH receives - InvokeRequestMessage [1641535680.297385][3878:3878] CHIP:DMG: - InvokeRequestMessage = [1641535680.297408][3878:3878] CHIP:DMG: { - [1641535680.297429][3878:3878] CHIP:DMG: suppressResponse = false, - [1641535680.297453][3878:3878] CHIP:DMG: timedRequest = true, - [1641535680.297475][3878:3878] CHIP:DMG: InvokeRequests = - [1641535680.297503][3878:3878] CHIP:DMG: [ - [1641535680.297525][3878:3878] CHIP:DMG: CommandDataIB = - [1641535680.297554][3878:3878] CHIP:DMG: { - [1641535680.297579][3878:3878] CHIP:DMG: CommandPathIB = - [1641535680.297610][3878:3878] CHIP:DMG: { - [1641535680.297644][3878:3878] CHIP:DMG: EndpointId = 0x1, - [1641535680.297676][3878:3878] CHIP:DMG: ClusterId = 0x6, - [1641535680.297706][3878:3878] CHIP:DMG: CommandId = 0x1, - [1641535680.297738][3878:3878] CHIP:DMG: }, + verification: | + Chip-tool as controller , here is the example command you can use + ./chip-tool onoff on 1 1 --timedInteractionTimeoutMs 200 + + Verify the DUT sent the invoke message to the TH after the specified timeout value for above command + + on the TH (reference all cluster app) you should see + + [1649683321.645175][2241:2241] CHIP:DMG: TimedRequestMessage = + [1649683321.645225][2241:2241] CHIP:DMG: { + [1649683321.645269][2241:2241] CHIP:DMG: TimeoutMs = 0xc8, + [1649683321.645317][2241:2241] CHIP:DMG: InteractionModelRevision = 1 + [1649683321.645360][2241:2241] CHIP:DMG: } + + [1649683321.647287][2241:2241] CHIP:DMG: InvokeRequestMessage = + [1649683321.647333][2241:2241] CHIP:DMG: { + [1649683321.647375][2241:2241] CHIP:DMG: suppressResponse = false, + [1649683321.647425][2241:2241] CHIP:DMG: timedRequest = true, + [1649683321.647470][2241:2241] CHIP:DMG: InvokeRequests = + [1649683321.647525][2241:2241] CHIP:DMG: [ + [1649683321.647571][2241:2241] CHIP:DMG: CommandDataIB = + [1649683321.647624][2241:2241] CHIP:DMG: { + [1649683321.647672][2241:2241] CHIP:DMG: CommandPathIB = + [1649683321.647719][2241:2241] CHIP:DMG: { + [1649683321.647776][2241:2241] CHIP:DMG: EndpointId = 0x1, + [1649683321.647838][2241:2241] CHIP:DMG: ClusterId = 0x6, + [1649683321.647899][2241:2241] CHIP:DMG: CommandId = 0x1, + [1649683321.647957][2241:2241] CHIP:DMG: }, + [1649683321.648020][2241:2241] CHIP:DMG: + [1649683321.648072][2241:2241] CHIP:DMG: CommandData = + [1649683321.648134][2241:2241] CHIP:DMG: { + [1649683321.648196][2241:2241] CHIP:DMG: }, + [1649683321.648251][2241:2241] CHIP:DMG: }, + [1649683321.648309][2241:2241] CHIP:DMG: + [1649683321.648353][2241:2241] CHIP:DMG: ], + [1649683321.648407][2241:2241] CHIP:DMG: + [1649683321.648454][2241:2241] CHIP:DMG: InteractionModelRevision = 1 + [1649683321.648499][2241:2241] CHIP:DMG: }, + + + TH receives InvokeRequestMessage + + [1641535680.297385][3878:3878] CHIP:DMG: InvokeRequestMessage = + [1641535680.297408][3878:3878] CHIP:DMG: { + [1641535680.297429][3878:3878] CHIP:DMG: suppressResponse = false, + [1641535680.297453][3878:3878] CHIP:DMG: timedRequest = true, + [1641535680.297475][3878:3878] CHIP:DMG: InvokeRequests = + [1641535680.297503][3878:3878] CHIP:DMG: [ + [1641535680.297525][3878:3878] CHIP:DMG: CommandDataIB = + [1641535680.297554][3878:3878] CHIP:DMG: { + [1641535680.297579][3878:3878] CHIP:DMG: CommandPathIB = + [1641535680.297610][3878:3878] CHIP:DMG: { + [1641535680.297644][3878:3878] CHIP:DMG: EndpointId = 0x1, + [1641535680.297676][3878:3878] CHIP:DMG: ClusterId = 0x6, + [1641535680.297706][3878:3878] CHIP:DMG: CommandId = 0x1, + [1641535680.297738][3878:3878] CHIP:DMG: }, [1641535680.297771][3878:3878] CHIP:DMG: - [1641535680.297797][3878:3878] CHIP:DMG: CommandData = - [1641535680.297825][3878:3878] CHIP:DMG: { - [1641535680.297853][3878:3878] CHIP:DMG: }, - [1641535680.297880][3878:3878] CHIP:DMG: }, + [1641535680.297797][3878:3878] CHIP:DMG: CommandData = + [1641535680.297825][3878:3878] CHIP:DMG: { + [1641535680.297853][3878:3878] CHIP:DMG: }, + [1641535680.297880][3878:3878] CHIP:DMG: }, [1641535680.297909][3878:3878] CHIP:DMG: - [1641535680.297931][3878:3878] CHIP:DMG: ], + [1641535680.297931][3878:3878] CHIP:DMG: ], [1641535680.297957][3878:3878] CHIP:DMG: - [1641535680.297976][3878:3878] CHIP:DMG: }," + [1641535680.297976][3878:3878] CHIP:DMG: }, disabled: true - label: @@ -69,35 +98,60 @@ tests: Message to the TH after receiving the status response message from the TH. The Time Request Message should contain a timeout value in milliseconds. (Example - 200 milliseconds)" - verification: - "Chip-tool as controller , here is the example command to write an - attribute you can use sudo ./chip-tool onoff write on-time 1 - 0x9f2bf1a1e3cc12c7 1 --timedInteractionTimeoutMs 100 on the TH - (reference all cluster app) you should see - [1641535415.492509][3878:3878] CHIP:DMG: TimedRequestMessage = - [1641535415.492560][3878:3878] CHIP:DMG: { - [1641535415.492584][3878:3878] CHIP:DMG: TimeoutMs = 0x64, - [1641535415.492606][3878:3878] CHIP:DMG: } - [1641535415.494355][3878:3878] CHIP:DMG: WriteRequestMessage = - [1641535415.494388][3878:3878] CHIP:DMG: { - [1641535415.494410][3878:3878] CHIP:DMG: timedRequest = true, - [1641535415.494442][3878:3878] CHIP:DMG: AttributeDataIBs = - [1641535415.494519][3878:3878] CHIP:DMG: [ - [1641535415.494602][3878:3878] CHIP:DMG: AttributeDataIB = - [1641535415.494641][3878:3878] CHIP:DMG: { - [1641535415.494668][3878:3878] CHIP:DMG: DataVersion = 0x0, - [1641535415.494746][3878:3878] CHIP:DMG: AttributePathIB = - [1641535415.494811][3878:3878] CHIP:DMG: { - [1641535415.494854][3878:3878] CHIP:DMG: Endpoint = 0x1, - [1641535415.494887][3878:3878] CHIP:DMG: Cluster = 0x6, - [1641535415.494927][3878:3878] CHIP:DMG: Attribute = 0x0000_4001, - [1641535415.494993][3878:3878] CHIP:DMG: } + verification: | + Chip-tool as controller , here is the example command to write an attribute you can use + + ./chip-tool levelcontrol read on-level 1 1 + + ./chip-tool levelcontrol write on-level 1 1 1 --timedInteractionTimeoutMs 200 + + on the TH (reference all cluster app) you should see + + 1649684576.547631][2241:2241] CHIP:DMG: TimedRequestMessage = + [1649684576.547669][2241:2241] CHIP:DMG: { + [1649684576.547700][2241:2241] CHIP:DMG: TimeoutMs = 0xc8, + [1649684576.547734][2241:2241] CHIP:DMG: InteractionModelRevision = 1 + [1649684576.547766][2241:2241] CHIP:DMG: } + [1649684576.547801][2241:2241] CHIP:DMG: Got Timed Request with timeout 200: handler 0xaaaaee795bd0 exchange 60329r + + [1649684576.549548][2241:2241] CHIP:IM: Received Write request + [1649684576.549577][2241:2241] CHIP:DMG: IM WH moving to [Initialized] + [1649684576.549635][2241:2241] CHIP:DMG: WriteRequestMessage = + [1649684576.549670][2241:2241] CHIP:DMG: { + [1649684576.549700][2241:2241] CHIP:DMG: suppressResponse = false, + [1649684576.549736][2241:2241] CHIP:DMG: timedRequest = true, + [1649684576.549769][2241:2241] CHIP:DMG: AttributeDataIBs = + [1649684576.549809][2241:2241] CHIP:DMG: [ + [1649684576.549842][2241:2241] CHIP:DMG: AttributeDataIB = + [1649684576.549976][2241:2241] CHIP:DMG: { + [1649684576.550016][2241:2241] CHIP:DMG: AttributePathIB = + [1649684576.550060][2241:2241] CHIP:DMG: { + [1649684576.550103][2241:2241] CHIP:DMG: Endpoint = 0x1, + [1649684576.550149][2241:2241] CHIP:DMG: Cluster = 0x8, + [1649684576.550194][2241:2241] CHIP:DMG: Attribute = 0x0000_0011, + [1649684576.550237][2241:2241] CHIP:DMG: } + [1649684576.550282][2241:2241] CHIP:DMG: + [1649684576.550330][2241:2241] CHIP:DMG: Data = 1, + [1649684576.550376][2241:2241] CHIP:DMG: }, + [1649684576.550419][2241:2241] CHIP:DMG: + [1649684576.550451][2241:2241] CHIP:DMG: ], + [1649684576.550491][2241:2241] CHIP:DMG: + [1649684576.550524][2241:2241] CHIP:DMG: moreChunkedMessages = false, + [1649684576.550558][2241:2241] CHIP:DMG: InteractionModelRevision = 1 + [1649684576.550590][2241:2241] CHIP:DMG: }, + [1649684576.550690][2241:2241] CHIP:DMG: AccessControl: checking f=1 a=c s=0x000000000001B669 t= c=0x0000_0008 e=1 p=o + AttributePathIB = + [1641535415.494811][3878:3878] CHIP:DMG: { + [1641535415.494854][3878:3878] CHIP:DMG: Endpoint = 0x1, + [1641535415.494887][3878:3878] CHIP:DMG: Cluster = 0x6, + [1641535415.494927][3878:3878] CHIP:DMG: Attribute = 0x0000_4001, + [1641535415.494993][3878:3878] CHIP:DMG: } [1641535415.495060][3878:3878] CHIP:DMG: - [1641535415.495092][3878:3878] CHIP:DMG: Data = 1, - [1641535415.495129][3878:3878] CHIP:DMG: }, + [1641535415.495092][3878:3878] CHIP:DMG: Data = 1, + [1641535415.495129][3878:3878] CHIP:DMG: }, [1641535415.495187][3878:3878] CHIP:DMG: - [1641535415.495219][3878:3878] CHIP:DMG: ], + [1641535415.495219][3878:3878] CHIP:DMG: ], [1641535415.495248][3878:3878] CHIP:DMG: - [1641535415.495323][3878:3878] CHIP:DMG: isFabricFiltered = false, - [1641535415.495345][3878:3878] CHIP:DMG: }," + [1641535415.495323][3878:3878] CHIP:DMG: isFabricFiltered = false, + [1641535415.495345][3878:3878] CHIP:DMG: }, disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_IDM_5_2.yaml b/src/app/tests/suites/certification/Test_TC_IDM_5_2.yaml index d09bd6f67a6557..9ad08c5d7c16b4 100644 --- a/src/app/tests/suites/certification/Test_TC_IDM_5_2.yaml +++ b/src/app/tests/suites/certification/Test_TC_IDM_5_2.yaml @@ -13,7 +13,7 @@ # 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: 19.7.2. [TC-IDM-5.2] Timed Request Action TH to DUT +name: 3.7.2. [TC-IDM-5.2] Timed Request Action TH to DUT config: nodeId: 0x12344321 @@ -24,21 +24,43 @@ tests: - label: "TH sends a Timed Request Message with the timeout value set. (Example - 200 milliseconds)." - verification: - "./chip-tool basic mfg-specific-ping 1 0 --commissioner-name alpha - --timedInteractionTimeoutMs -200 TimedRequestMessage = - [1641535747.977210][3603:3603] CHIP:DMG: { - [1641535747.977247][3603:3603] CHIP:DMG: TimeoutMs = 0xff38, - [1641535747.977294][3603:3603] CHIP:DMG: } - [1641535747.977334][3603:3603] CHIP:DMG: Got Timed Request with - timeout 65336: handler 0xaaaae9085698 exchange 25353r" + verification: | + for below example command is verified by using write interaction + ./chip-tool onoff on 1 1 --timedInteractionTimeoutMs 200 disabled: true - label: "TH sends a Timed Request Message with the timeout value set. (Example - 200 milliseconds). Wait for the status response message to be - received. Wait for 5 seconds and then send a Write Request Message to - the DUT." - verification: - "Chip-tool yet to implement timed interaction for write request" + received. Wait for 5 seconds(Timer has expired) and then send a Write + Request Message to the DUT." + verification: | + here is the example command you can use + + '' ./chip-tool onoff on 1 1 --repeat-delay-ms 5000 --timedInteractionTimeoutMs 200 + + Verify we are getting status response and UNSUPPORTED_ACCESS from TH to DUT for above command + + [1649686333.696111][3252:3257] CHIP:DMG: StatusResponseMessage = + [1649686333.696178][3252:3257] CHIP:DMG: { + [1649686333.696236][3252:3257] CHIP:DMG: Status = 0x0, + [1649686333.696311][3252:3257] CHIP:DMG: InteractionModelRevision = 1 + [1649686333.696375][3252:3257] CHIP:DMG: } + [1649686333.696434][3252:3257] CHIP:IM: Received status response, status is 0x00 (SUCCESS) + [1649686333.696513][3252:3257] CHIP:EM: Piggybacking Ack for MessageCounter:3570360 on exchange: 28108i + [1649686333.696626][3252:3257] CHIP:IN: Prepared secure message 0xaaaae019e098 to 0x0000000000000001 (1) of type 0x8 and protocolId (0, 1) on exchange 28108i with MessageCounter:6840786. + [1649686333.696711][3252:3257] CHIP:IN: Sending encrypted msg 0xaaaae019e098 with MessageCounter:6840786 to 0x0000000000000001 (1) at monotonic time: 0000000000CE3312 msec + [1649686333.696989][3252:3257] CHIP:DMG: ICR moving to [CommandSen] + [1649686333.698938][3252:3257] CHIP:EM: Received message of type 0x1 with protocolId (0, 1) and MessageCounter:3570361 on exchange 28108i + [1649686333.699013][3252:3257] CHIP:EM: Found matching exchange: 28108i, Delegate: 0xffff68005c30 + [1649686333.699089][3252:3257] CHIP:EM: Rxd Ack; Removing MessageCounter:6840786 from Retrans Table on exchange 28108i + [1649686333.699147][3252:3257] CHIP:EM: Removed CHIP MessageCounter:6840786 from RetransTable on exchange 28108i + [1649686333.699215][3252:3257] CHIP:DMG: ICR moving to [ResponseRe] + [1649686333.699294][3252:3257] CHIP:DMG: StatusResponseMessage = + [1649686333.699354][3252:3257] CHIP:DMG: { + [1649686333.699410][3252:3257] CHIP:DMG: Status = 0x7e, + [1649686333.699471][3252:3257] CHIP:DMG: InteractionModelRevision = 1 + [1649686333.699528][3252:3257] CHIP:DMG: } + [1649686333.699585][3252:3257] CHIP:IM: Received status response, status is 0x7e (UNSUPPORTED_ACCESS) + [1649686333.699661][3252:3257] CHIP:TOO: Error: IM Error 0x0000057E: General error: 0x7e (UNSUPPORTED_ACCESS) disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_SC_4_5.yaml b/src/app/tests/suites/certification/Test_TC_SC_4_5.yaml index 9f385e2189f443..1267e89eedfd00 100644 --- a/src/app/tests/suites/certification/Test_TC_SC_4_5.yaml +++ b/src/app/tests/suites/certification/Test_TC_SC_4_5.yaml @@ -24,47 +24,53 @@ tests: - label: "TH is instructed to start advertising two or more services using DNS-SD" - verification: - "1. On the raspi controller, publish matter service, using below - command $avahi-publish-service 87E1B004E235A130-8FC7772401CD0696 - _matter._tcp 22222 SII=3000 SAI=2000 T=0" + verification: | + 1. On the raspi controller, publish matter service, using below command + + $avahi-publish-service 87E1B004E235A130-8FC7772401CD0696 _matter._tcp 22222 CRI=3000 CRA=4000 T=0 disabled: true - label: "By any means, DUT is instructed to perform an unicast UDP query to the DNS-SD Discovery Proxy on TH for services" - verification: - "1. Proviosion the node(accessory/device) to thread network 2. Open - the matter shell in the SDK and run resolve command, Verify if the - device detects the published IP address and the Common Txt Key/Value - Pairs , as advertised in the service. Ref below example. uart:~$ - matter dns resolve 9791300599901692208 10360380464321857174 Resolving - ... uart:~$ I: 127317 [DIS]Node ID resolved for 0x8FC7772401CD0696 to - [fd7b:a81b:9770:0:dea6:32ff:fe8d:7072]:22222 DNS resolve for - 87E1B004E235A130-8FC7772401CD0696 succeeded: Hostname: - ubuntuserverAcce IP address: fd7b:a81b:9770:0:dea6:32ff:fe8d:7072 - Port: 22222 MRP retry interval (idle): 3000ms MRP retry interval - (active): 4000ms Supports TCP: no" + verification: | + 1. Proviosion the node(accessory/device) to thread network + + 2. Open the matter shell in the SDK and run resolve command, Verify if the device detects the published IP address and the Common Txt Key/Value Pairs , as advertised in the service. Ref below example. + + + uart:~$ matter dns resolve 9791300599901692208 10360380464321857174 + Resolving ... + uart:~$ I: 127317 [DIS]Node ID resolved for 0x8FC7772401CD0696 to [fd7b:a81b:9770:0:dea6:32ff:fe8d:7072]:22222 + DNS resolve for 87E1B004E235A130-8FC7772401CD0696 succeeded: + Hostname: ubuntuserverAcce + IP address: fd7b:a81b:9770:0:dea6:32ff:fe8d:7072 + Port: 22222 + MRP retry interval (idle): 3000ms + MRP retry interval (active): 4000ms + Supports TCP: no disabled: true - label: "TH performs a change in one of the services configured at step 1" - verification: - "1. On the raspi controller, publish matter service chanding the T - value 1, using below command $avahi-publish-service - 87E1B004E235A130-8FC7772401CD0696 _matter._tcp 22222 SII=3000 SAI=2000 - T=1" + verification: | + 1. On the raspi controller, publish matter service chanding the T value 1, using below command + + $avahi-publish-service 87E1B004E235A130-8FC7772401CD0696 _matter._tcp 22222 CRI=3000 CRA=4000 T=1 disabled: true - label: "DUT must receive a notification with new data" - verification: - "1. Open the matter shell in the SDK and run resolve command, Verify - if the device detects updated values in the service, i..e Support TCP - is '1'(Yes) uart:~$ matter dns resolve 9791300599901692208 - 10360380464321857174 Resolving ... uart:~$ I: 542364 [DIS]Node ID - resolved for 0x8FC7772401CD0696 to - [fd7b:a81b:9770:0:dea6:32ff:fe8d:7072]:22222 DNS resolve for - 87E1B004E235A130-8FC7772401CD0696 succeeded: Hostname: - ubuntuserverAcce IP address: fd7b:a81b:9770:0:dea6:32ff:fe8d:7072 - Port: 22222 MRP retry interval (idle): 3000ms MRP retry interval - (active): 4000ms Supports TCP: yes" + verification: | + 1. Open the matter shell in the SDK and run resolve command, Verify if the device detects updated values in the service, i..e Support TCP is '1'(Yes) + + + uart:~$ matter dns resolve 9791300599901692208 10360380464321857174 + Resolving ... + uart:~$ I: 542364 [DIS]Node ID resolved for 0x8FC7772401CD0696 to [fd7b:a81b:9770:0:dea6:32ff:fe8d:7072]:22222 + DNS resolve for 87E1B004E235A130-8FC7772401CD0696 succeeded: + Hostname: ubuntuserverAcce + IP address: fd7b:a81b:9770:0:dea6:32ff:fe8d:7072 + Port: 22222 + MRP retry interval (idle): 3000ms + MRP retry interval (active): 4000ms + Supports TCP: yes disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_SC_4_9.yaml b/src/app/tests/suites/certification/Test_TC_SC_4_9.yaml index ad7fbdf100f9af..14fd90cc943330 100644 --- a/src/app/tests/suites/certification/Test_TC_SC_4_9.yaml +++ b/src/app/tests/suites/certification/Test_TC_SC_4_9.yaml @@ -22,39 +22,38 @@ config: tests: - label: "TH_CR1 starts a commissioning process with DUT_CE" - verification: - "provision the DUT using chip-tool. Ref to provisioning instructions" + verification: | + provision the DUT using chip-tool. Ref to provisioning instructions disabled: true - label: "TH_CR1 opens a commissioning window on DUT_CE using a commissioning timeout of PIXIT_COMM_WIN seconds using ECM" - verification: - "Refer to Multi-admin tests (either TC-MF-1.3 OR TC-MF-1.4) on the - steps to add 2nd admin on the node Open Commissioning window on DUT - using BCM sudo ./out/debug/chip-tool administratorcommissioning - open-basic-commissioning-window 10 99998888 0" + verification: | + Refer to Multi-admin tests (either TC-MF-1.3 OR TC-MF-1.4) on the steps to add 2nd admin on the node + Open Commissioning window on DUT using BCM or ECM + + ./chip-tool pairing open-commissioning-window 1 1 200 1000 3840 disabled: true - label: "TH_CR2 starts a commissioning process with DUT_CE" - verification: - "Refer to Multi-admin tests on the steps to add 2nd admin on the node. - Get another chip-tool instance on a machine connected behind the - border router. Make sure IPV4 interface are disabled on the border - router. We need to make sure chip-tool on IPV6 network talk to the - Wifi device with LWIP stack on the wifi network." + verification: | + Refer to Multi-admin tests on the steps to add 2nd admin on the node. Get another chip-tool instance on a machine connected behind the border router. Make sure IPV4 interface are disabled on the border router. We need to make sure chip-tool on IPV6 network talk to the Wifi device with LWIP stack on the wifi network. + ./chip-tool pairing manualcode 1 36177160937 disabled: true - label: "TH_CR1 writes and reads the Basic Information Clusters NodeLabel mandatory attribute of DUT_CE" - verification: "Read/Write attributes frm the 1st controller" + verification: | + ./chip-tool basic write node-label te8 1 0 + ./chip-tool basic read node-label 1 0 disabled: true - label: "TH_CR2 writes and reads the Basic Information Clusters NodeLabel mandatory attribute of DUT_CE" - verification: - "Read/Write attributes frm the 2nd controller that is on thread - network." + verification: | + ./chip-tool basic write node-label te8 2 0 + ./chip-tool basic read node-label 2 0 disabled: true diff --git a/src/app/tests/suites/tests.js b/src/app/tests/suites/tests.js index a04b80fd0f109a..39e5b889389fac 100644 --- a/src/app/tests/suites/tests.js +++ b/src/app/tests/suites/tests.js @@ -96,7 +96,6 @@ function getManualTests() { 'Test_TC_DM_1_2', 'Test_TC_DM_1_4', 'Test_TC_DM_2_1', - 'Test_TC_DM_2_3', 'Test_TC_DM_2_4', 'Test_TC_DM_3_2', 'Test_TC_DM_3_4', diff --git a/zzz_generated/chip-tool/zap-generated/test/Commands.h b/zzz_generated/chip-tool/zap-generated/test/Commands.h index 7c065491adcfdf..ebf45d97c812a2 100644 --- a/zzz_generated/chip-tool/zap-generated/test/Commands.h +++ b/zzz_generated/chip-tool/zap-generated/test/Commands.h @@ -292,7 +292,6 @@ class ManualTestList : public Command printf("Test_TC_DM_1_2\n"); printf("Test_TC_DM_1_4\n"); printf("Test_TC_DM_2_1\n"); - printf("Test_TC_DM_2_3\n"); printf("Test_TC_DM_2_4\n"); printf("Test_TC_DM_3_2\n"); printf("Test_TC_DM_3_4\n"); @@ -61848,62 +61847,6 @@ class Test_TC_DM_2_1Suite : public TestCommand } }; -class Test_TC_DM_2_3Suite : public TestCommand -{ -public: - Test_TC_DM_2_3Suite(CredentialIssuerCommands * credsIssuerConfig) : TestCommand("Test_TC_DM_2_3", 0, credsIssuerConfig) - { - AddArgument("nodeId", 0, UINT64_MAX, &mNodeId); - AddArgument("cluster", &mCluster); - AddArgument("endpoint", 0, UINT16_MAX, &mEndpoint); - AddArgument("timeout", 0, UINT16_MAX, &mTimeout); - } - - ~Test_TC_DM_2_3Suite() {} - - chip::System::Clock::Timeout GetWaitDuration() const override - { - return chip::System::Clock::Seconds16(mTimeout.ValueOr(kTimeoutInSeconds)); - } - -private: - chip::Optional mNodeId; - chip::Optional mCluster; - chip::Optional mEndpoint; - chip::Optional mTimeout; - - chip::EndpointId GetEndpoint(chip::EndpointId endpoint) { return mEndpoint.HasValue() ? mEndpoint.Value() : endpoint; } - - // - // Tests methods - // - - void OnResponse(const chip::app::StatusIB & status, chip::TLV::TLVReader * data) override - { - bool shouldContinue = false; - - switch (mTestIndex - 1) - { - default: - LogErrorOnFailure(ContinueOnChipMainThread(CHIP_ERROR_INVALID_ARGUMENT)); - } - - if (shouldContinue) - { - ContinueOnChipMainThread(CHIP_NO_ERROR); - } - } - - CHIP_ERROR DoTestStep(uint16_t testIndex) override - { - using namespace chip::app::Clusters; - switch (testIndex) - { - } - return CHIP_NO_ERROR; - } -}; - class Test_TC_DM_2_4Suite : public TestCommand { public: @@ -73233,7 +73176,6 @@ void registerCommandsTests(Commands & commands, CredentialIssuerCommands * creds make_unique(credsIssuerConfig), make_unique(credsIssuerConfig), make_unique(credsIssuerConfig), - make_unique(credsIssuerConfig), make_unique(credsIssuerConfig), make_unique(credsIssuerConfig), make_unique(credsIssuerConfig),