From 1219374d8a9ef68c0e53943242beeb2617018748 Mon Sep 17 00:00:00 2001 From: manjunath-grl <102359958+manjunath-grl@users.noreply.github.com> Date: Fri, 3 Nov 2023 23:42:47 +0530 Subject: [PATCH] Manual script issue fix oct 30 (#30120) * Fixes issue: 34, 46, 47, 48, 49, 50 Modified tests: TC_ACE_1_5 TC_BRBINFO_2_2 TC_CADMIN_1_5 TC_CNET_4_10 TC_CNET_4_11 TC_CNET_4_20 TC_CNET_4_5 TC_CNET_4_9 TC_DGWIFI_3_2_Simulated TC_DRLK_2_10 TC_G_2_2 TC_SWTCH_2_2 * Modified tests: TC_ACT_3_2 TC_DRLK_3_2 * Restyled by whitespace --------- Co-authored-by: Restyled.io --- src/app/tests/suites/certification/PICS.yaml | 2 +- .../suites/certification/Test_TC_ACE_1_5.yaml | 12 +- .../suites/certification/Test_TC_ACT_3_2.yaml | 157 +- .../certification/Test_TC_BRBINFO_2_2.yaml | 2 +- .../certification/Test_TC_CADMIN_1_5.yaml | 2 +- .../certification/Test_TC_CNET_4_10.yaml | 2 +- .../certification/Test_TC_CNET_4_11.yaml | 8 +- .../certification/Test_TC_CNET_4_20.yaml | 2 +- .../certification/Test_TC_CNET_4_5.yaml | 8 +- .../certification/Test_TC_CNET_4_9.yaml | 2 +- .../Test_TC_DGWIFI_3_2_Simulated.yaml | 2 +- .../certification/Test_TC_DRLK_2_10.yaml | 5 +- .../certification/Test_TC_DRLK_3_2.yaml | 1201 ++++++++------- .../suites/certification/Test_TC_G_2_2.yaml | 2 +- .../certification/Test_TC_SWTCH_2_2.yaml | 1290 ++++++++++------- .../tests/suites/certification/ci-pics-values | 2 +- .../zap-generated/test/Commands.h | 22 +- .../app1/zap-generated/test/Commands.h | 2 +- .../app2/zap-generated/test/Commands.h | 2 +- 19 files changed, 1437 insertions(+), 1288 deletions(-) diff --git a/src/app/tests/suites/certification/PICS.yaml b/src/app/tests/suites/certification/PICS.yaml index d94eada4ad6415..1137d1dee7c5e3 100644 --- a/src/app/tests/suites/certification/PICS.yaml +++ b/src/app/tests/suites/certification/PICS.yaml @@ -7311,7 +7311,7 @@ PICS: "Reset the following attributes to 0; BeaconLostCount, BeaconRxCount, PacketMulticastRxCount, PacketMulticastTxCount, PacketUnicastRxCount, PacketUnicastTxCount" - id: DGWIFI.S.C00.Tx + id: DGWIFI.C.C00.Tx # Window Covering Cluster Test Plan - label: diff --git a/src/app/tests/suites/certification/Test_TC_ACE_1_5.yaml b/src/app/tests/suites/certification/Test_TC_ACE_1_5.yaml index 4bbecd559ca785..05ab09f80501e5 100644 --- a/src/app/tests/suites/certification/Test_TC_ACE_1_5.yaml +++ b/src/app/tests/suites/certification/Test_TC_ACE_1_5.yaml @@ -254,7 +254,9 @@ tests: cluster: "Descriptor" attribute: "DeviceTypeList" - - label: "Step 8: TH1 reads basic cluster - expect UNSUPPORTED_ACCESS" + - label: + "Step 8: TH1 reads DUT Endpoint 0 Basic Information cluster VendorID + attribute - expect UNSUPPORTED_ACCESS" command: "readAttribute" cluster: "Basic Information" attribute: "VendorID" @@ -291,7 +293,9 @@ tests: - name: "expectedValue" value: "y" - - label: "Step 10: TH2 reads basic cluster - expect SUCCESS" + - label: + "Step 10: TH2 reads DUT Endpoint 0 Basic Information cluster VendorID + attribute - expect SUCCESS" identity: "beta" PICS: PICS_SDK_CI_ONLY command: "readAttribute" @@ -299,7 +303,9 @@ tests: attribute: "VendorID" #Issue https://github.com/CHIP-Specifications/chip-certification-tool/issues/768 - - label: "Step 10: TH2 reads basic cluster - expect SUCCESS" + - label: + "Step 10: TH2 reads DUT Endpoint 0 Basic Information cluster VendorID + attribute - expect SUCCESS" verification: | ./chip-tool basicinformation read vendor-id 2 0 --commissioner-name beta diff --git a/src/app/tests/suites/certification/Test_TC_ACT_3_2.yaml b/src/app/tests/suites/certification/Test_TC_ACT_3_2.yaml index 42f492697ff450..e6390348f7148e 100644 --- a/src/app/tests/suites/certification/Test_TC_ACT_3_2.yaml +++ b/src/app/tests/suites/certification/Test_TC_ACT_3_2.yaml @@ -45,97 +45,88 @@ tests: 1. First read action-list by following command - ./chip-tool actions read action-list 1 1 --trace_decode 1 - - Via the TH (bridge-app), verify the ActionList attribute that contains ActionListStructs. - - [1686033574.850552][39104:39106] CHIP:DMG: ReportDataMessage = - [1686033574.850639][39104:39106] CHIP:DMG: { - [1686033574.850689][39104:39106] CHIP:DMG: AttributeReportIBs = - [1686033574.850802][39104:39106] CHIP:DMG: [ - [1686033574.850861][39104:39106] CHIP:DMG: AttributeReportIB = - [1686033574.850976][39104:39106] CHIP:DMG: { - [1686033574.851039][39104:39106] CHIP:DMG: AttributeDataIB = - [1686033574.851133][39104:39106] CHIP:DMG: { - [1686033574.851206][39104:39106] CHIP:DMG: DataVersion = 0x17ed8ce2, - [1686033574.851299][39104:39106] CHIP:DMG: AttributePathIB = - [1686033574.851375][39104:39106] CHIP:DMG: { - [1686033574.851450][39104:39106] CHIP:DMG: Endpoint = 0x1, - [1686033574.851557][39104:39106] CHIP:DMG: Cluster = 0x25, - [1686033574.851658][39104:39106] CHIP:DMG: Attribute = 0x0000_0000, - [1686033574.851736][39104:39106] CHIP:DMG: } - [1686033574.851838][39104:39106] CHIP:DMG: - [1686033574.851914][39104:39106] CHIP:DMG: Data = [ - [1686033574.852009][39104:39106] CHIP:DMG: - [1686033574.852090][39104:39106] CHIP:DMG: { - [1686033574.852194][39104:39106] CHIP:DMG: 0x0 = 4097, - [1686033574.852287][39104:39106] CHIP:DMG: 0x1 = "Room 1 On" (9 chars), - [1686033574.852393][39104:39106] CHIP:DMG: 0x2 = 3, - [1686033574.852482][39104:39106] CHIP:DMG: 0x3 = 57345, - [1686033574.852588][39104:39106] CHIP:DMG: 0x4 = 1, - [1686033574.852692][39104:39106] CHIP:DMG: 0x5 = 0, - [1686033574.852780][39104:39106] CHIP:DMG: }, - [1686033574.852880][39104:39106] CHIP:DMG: { - [1686033574.852963][39104:39106] CHIP:DMG: 0x0 = 4098, - [1686033574.853070][39104:39106] CHIP:DMG: 0x1 = "Turn On Room 2" (14 chars), - [1686033574.853158][39104:39106] CHIP:DMG: 0x2 = 3, - [1686033574.853311][39104:39106] CHIP:DMG: 0x3 = 57346, - [1686033574.853428][39104:39106] CHIP:DMG: 0x4 = 1, - [1686033574.853516][39104:39106] CHIP:DMG: 0x5 = 0, - [1686033574.853621][39104:39106] CHIP:DMG: }, - [1686033574.853703][39104:39106] CHIP:DMG: ], - [1686033574.853792][39104:39106] CHIP:DMG: }, - [1686033574.853887][39104:39106] CHIP:DMG: - [1686033574.853969][39104:39106] CHIP:DMG: }, - [1686033574.854059][39104:39106] CHIP:DMG: - [1686033574.854137][39104:39106] CHIP:DMG: ], - [1686033574.854225][39104:39106] CHIP:DMG: - [1686033574.854283][39104:39106] CHIP:DMG: SuppressResponse = true, - [1686033574.854342][39104:39106] CHIP:DMG: InteractionModelRevision = 1 - [1686033574.854395][39104:39106] CHIP:DMG: } - + ./chip-tool actions read action-list 1 1 + + Via the TH (bridge-app), verify the ActionList attribute response. + + [1698725144.232190][1963:1963] CHIP:IM: Received Read request + [1698725144.232296][1963:1963] CHIP:DMG: ReadRequestMessage = + [1698725144.232352][1963:1963] CHIP:DMG: { + [1698725144.232410][1963:1963] CHIP:DMG: AttributePathIBs = + [1698725144.232484][1963:1963] CHIP:DMG: [ + [1698725144.232544][1963:1963] CHIP:DMG: AttributePathIB = + [1698725144.232608][1963:1963] CHIP:DMG: { + [1698725144.232688][1963:1963] CHIP:DMG: Endpoint = 0x1, + [1698725144.232758][1963:1963] CHIP:DMG: Cluster = 0x25, + [1698725144.232828][1963:1963] CHIP:DMG: Attribute = 0x0000_0000, + [1698725144.232893][1963:1963] CHIP:DMG: } + [1698725144.232959][1963:1963] CHIP:DMG: + [1698725144.233018][1963:1963] CHIP:DMG: ], + [1698725144.233083][1963:1963] CHIP:DMG: + [1698725144.233142][1963:1963] CHIP:DMG: isFabricFiltered = true, + [1698725144.233199][1963:1963] CHIP:DMG: InteractionModelRevision = 11 + [1698725144.233252][1963:1963] CHIP:DMG: }, + + + ./chip-tool actions read endpoint-lists 1 1 + + Via the TH (chip-tool), verify the EndpointLists attribute that contains EndpointListStructs. + + [1698729275.160463][1963:1963] CHIP:IM: Received Read request + [1698729275.160560][1963:1963] CHIP:DMG: ReadRequestMessage = + [1698729275.160618][1963:1963] CHIP:DMG: { + [1698729275.160668][1963:1963] CHIP:DMG: AttributePathIBs = + [1698729275.160729][1963:1963] CHIP:DMG: [ + [1698729275.160785][1963:1963] CHIP:DMG: AttributePathIB = + [1698729275.160848][1963:1963] CHIP:DMG: { + [1698729275.160912][1963:1963] CHIP:DMG: Endpoint = 0x1, + [1698729275.160992][1963:1963] CHIP:DMG: Cluster = 0x25, + [1698729275.161070][1963:1963] CHIP:DMG: Attribute = 0x0000_0001, + [1698729275.161143][1963:1963] CHIP:DMG: } + [1698729275.161211][1963:1963] CHIP:DMG: + [1698729275.161270][1963:1963] CHIP:DMG: ], + [1698729275.161335][1963:1963] CHIP:DMG: + [1698729275.161395][1963:1963] CHIP:DMG: isFabricFiltered = true, + [1698729275.161452][1963:1963] CHIP:DMG: InteractionModelRevision = 11 + [1698729275.161505][1963:1963] CHIP:DMG: }, 2. Use the above obtained ActionID to verify the following commands - ./chip-tool actions instant-action 4097 1 1 --trace_decode 1 + ./chip-tool actions instant-action 4097 1 1 disabled: true - label: "Step 1: DUT issues an InstantAction command to TH" PICS: ACT.C.C00.Tx verification: | - ./chip-tool actions instant-action 4097 1 1 --trace_decode 1 - - Via the TH (bridge-app), verify the SUCCESS response for InstantAction. - - [1686033693.327962][39117:39119] CHIP:DMG: InvokeResponseMessage = - [1686033693.328040][39117:39119] CHIP:DMG: { - [1686033693.328094][39117:39119] CHIP:DMG: suppressResponse = false, - [1686033693.328151][39117:39119] CHIP:DMG: InvokeResponseIBs = - [1686033693.328248][39117:39119] CHIP:DMG: [ - [1686033693.328307][39117:39119] CHIP:DMG: InvokeResponseIB = - [1686033693.328407][39117:39119] CHIP:DMG: { - [1686033693.328469][39117:39119] CHIP:DMG: CommandStatusIB = - [1686033693.328561][39117:39119] CHIP:DMG: { - [1686033693.328632][39117:39119] CHIP:DMG: CommandPathIB = - [1686033693.328708][39117:39119] CHIP:DMG: { - [1686033693.328807][39117:39119] CHIP:DMG: EndpointId = 0x1, - [1686033693.328887][39117:39119] CHIP:DMG: ClusterId = 0x25, - [1686033693.328987][39117:39119] CHIP:DMG: CommandId = 0x0, - [1686033693.329062][39117:39119] CHIP:DMG: }, - [1686033693.329167][39117:39119] CHIP:DMG: - [1686033693.329237][39117:39119] CHIP:DMG: StatusIB = - [1686033693.329376][39117:39119] CHIP:DMG: { - [1686033693.329454][39117:39119] CHIP:DMG: status = 0x00 (SUCCESS), - [1686033693.329551][39117:39119] CHIP:DMG: }, - [1686033693.329629][39117:39119] CHIP:DMG: - [1686033693.329716][39117:39119] CHIP:DMG: }, - [1686033693.329794][39117:39119] CHIP:DMG: - [1686033693.329876][39117:39119] CHIP:DMG: }, - [1686033693.329950][39117:39119] CHIP:DMG: - [1686033693.330005][39117:39119] CHIP:DMG: ], - [1686033693.330101][39117:39119] CHIP:DMG: - [1686033693.330158][39117:39119] CHIP:DMG: InteractionModelRevision = 1 - [1686033693.330241][39117:39119] CHIP:DMG: }, + ./chip-tool actions instant-action 4097 1 1 + + Via the TH (bridge-app), verify the InstantAction response that contains ActionID . + + [1698724321.817293][1963:1963] CHIP:DMG: InvokeRequestMessage = + [1698724321.817361][1963:1963] CHIP:DMG: { + [1698724321.817413][1963:1963] CHIP:DMG: suppressResponse = false, + [1698724321.817475][1963:1963] CHIP:DMG: timedRequest = false, + [1698724321.817532][1963:1963] CHIP:DMG: InvokeRequests = + [1698724321.817603][1963:1963] CHIP:DMG: [ + [1698724321.817659][1963:1963] CHIP:DMG: CommandDataIB = + [1698724321.817723][1963:1963] CHIP:DMG: { + [1698724321.817782][1963:1963] CHIP:DMG: CommandPathIB = + [1698724321.817974][1963:1963] CHIP:DMG: { + [1698724321.818045][1963:1963] CHIP:DMG: EndpointId = 0x1, + [1698724321.818141][1963:1963] CHIP:DMG: ClusterId = 0x25, + [1698724321.818232][1963:1963] CHIP:DMG: CommandId = 0x0, + [1698724321.818319][1963:1963] CHIP:DMG: }, + [1698724321.818399][1963:1963] CHIP:DMG: + [1698724321.818462][1963:1963] CHIP:DMG: CommandFields = + [1698724321.818537][1963:1963] CHIP:DMG: { + [1698724321.818607][1963:1963] CHIP:DMG: 0x0 = 4097, + [1698724321.818697][1963:1963] CHIP:DMG: }, + [1698724321.818767][1963:1963] CHIP:DMG: }, + [1698724321.818838][1963:1963] CHIP:DMG: + [1698724321.818894][1963:1963] CHIP:DMG: ], + [1698724321.818963][1963:1963] CHIP:DMG: + [1698724321.819017][1963:1963] CHIP:DMG: InteractionModelRevision = 11 + [1698724321.819088][1963:1963] CHIP:DMG: }, disabled: true - label: "Step 2: DUT issues an StartAction command to TH" diff --git a/src/app/tests/suites/certification/Test_TC_BRBINFO_2_2.yaml b/src/app/tests/suites/certification/Test_TC_BRBINFO_2_2.yaml index e742a2a98e52a5..ac8fdc5a79ede3 100644 --- a/src/app/tests/suites/certification/Test_TC_BRBINFO_2_2.yaml +++ b/src/app/tests/suites/certification/Test_TC_BRBINFO_2_2.yaml @@ -32,7 +32,7 @@ tests: 3. TH reads Reachable attribute from DUT and saves for future use - 4. TH subscribes to StartUp, ShutDown, ReachableChanged and Leave events on the Basic cluster of the DUT + 4. TH subscribes to StartUp, ShutDown, ReachableChanged and Leave events on the Bridged Device Basic Information cluster of the DUT 5. TH saves the FabricIndex during commissioning disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_CADMIN_1_5.yaml b/src/app/tests/suites/certification/Test_TC_CADMIN_1_5.yaml index 045bb85fa92f10..c5974efc25bbec 100644 --- a/src/app/tests/suites/certification/Test_TC_CADMIN_1_5.yaml +++ b/src/app/tests/suites/certification/Test_TC_CADMIN_1_5.yaml @@ -345,7 +345,7 @@ tests: On TH_CR3 send the below command Below is the example when using chip tool as controller (considering 36177160937 as the manual code generated by 1st controller) - ./chip-tool pairing code 1 36177160937 --commissioner-name gamma + ./chip-tool pairing code 3 36177160937 --commissioner-name gamma verify you got the following message in the TH_CR3(chip-tool) log CHIP:SC: PASESession timed out while waiting for a response from the peer. Expected message type was 33 diff --git a/src/app/tests/suites/certification/Test_TC_CNET_4_10.yaml b/src/app/tests/suites/certification/Test_TC_CNET_4_10.yaml index b9d5fed77a9909..0bdd84f83d5ab7 100644 --- a/src/app/tests/suites/certification/Test_TC_CNET_4_10.yaml +++ b/src/app/tests/suites/certification/Test_TC_CNET_4_10.yaml @@ -157,7 +157,7 @@ tests: "Step 9: TH sends ConnectNetwork command to the DUT with NetworkID field set to the extended PAN ID of PIXIT.CNET.THREAD_1ST_OPERATIONALDATASET and Breadcrumb field set to 2" - PICS: CNET.S.C04.Rsp + PICS: CNET.S.C04.Rsp && CNET.S.C06.Rsp verification: | ./chip-tool networkcommissioning connect-network hex: 1 0 diff --git a/src/app/tests/suites/certification/Test_TC_CNET_4_11.yaml b/src/app/tests/suites/certification/Test_TC_CNET_4_11.yaml index 69e25476c127e1..64d6cacf5c05c1 100644 --- a/src/app/tests/suites/certification/Test_TC_CNET_4_11.yaml +++ b/src/app/tests/suites/certification/Test_TC_CNET_4_11.yaml @@ -110,11 +110,11 @@ tests: field set to 1" PICS: CNET.S.C02.Rsp && CNET.S.C05.Tx verification: | - ./chip-tool networkcommissioning add-or-update-wi-fi-network hex: 1 0 + ./chip-tool networkcommissioning add-or-update-wi-fi-network hex: 1 0 Below is an example: - ./chip-tool networkcommissioning add-or-update-wi-fi-network Sbee_Moto Sunsuraj 1 0 --Breadcrumb 1 ( second network) + ./chip-tool networkcommissioning add-or-update-wi-fi-network hex:536265655F4D6F746F Sunsuraj 1 0 --Breadcrumb 1 ( second network) Via the TH (chip-tool), Verify the NetworkConfigResponse that contains Networking Status value as 0 (success). @@ -286,10 +286,10 @@ tests: field set to 1" PICS: CNET.S.C02.Rsp && CNET.S.C05.Tx verification: | - ./chip-tool networkcommissioning add-or-update-wi-fi-network-network hex: 1 0 + ./chip-tool networkcommissioning add-or-update-wi-fi-network-network hex: 1 0 Below is an example: - ./chip-tool networkcommissioning add-or-update-wi-fi-network Sbee_Moto Sunsuraj 1 0 --Breadcrumb 1 ( second network) + ./chip-tool networkcommissioning add-or-update-wi-fi-network hex:536265655F4D6F746F Sunsuraj 1 0 --Breadcrumb 1 ( second network) Via the TH (chip-tool), Verify the NetworkConfigResponse that contains Networking Status value as 0 (success). diff --git a/src/app/tests/suites/certification/Test_TC_CNET_4_20.yaml b/src/app/tests/suites/certification/Test_TC_CNET_4_20.yaml index 1446d5ccb4bb43..1484d0738baf74 100644 --- a/src/app/tests/suites/certification/Test_TC_CNET_4_20.yaml +++ b/src/app/tests/suites/certification/Test_TC_CNET_4_20.yaml @@ -119,7 +119,7 @@ tests: - label: "Step 3: DUT sends the AddOrUpdateWiFiNetwork command to the TH" PICS: CNET.C.C02.Tx verification: | - ./chip-tool networkcommissioning add-or-update-wi-fi-network-network hex: 1 0 + ./chip-tool networkcommissioning add-or-update-wi-fi-network-network hex: 1 0 Below is an example: diff --git a/src/app/tests/suites/certification/Test_TC_CNET_4_5.yaml b/src/app/tests/suites/certification/Test_TC_CNET_4_5.yaml index d50e856b4c2501..9ef9cefc40617a 100644 --- a/src/app/tests/suites/certification/Test_TC_CNET_4_5.yaml +++ b/src/app/tests/suites/certification/Test_TC_CNET_4_5.yaml @@ -41,7 +41,7 @@ tests: T_ACCESSPOINT_CRE DENTIALS 3. Breadcrumb field set to 1" PICS: CNET.S.C02.Rsp verification: | - ./chip-tool networkcommissioning add-or-update-wi-fi-network hex: 1 0 + ./chip-tool networkcommissioning add-or-update-wi-fi-network hex: 1 0 Below is an example: @@ -58,9 +58,9 @@ tests: "Step 2: TH sends RemoveNetwork command to the DUT with NetworkID field set to PIXIT.CNET.WIFI_1ST_ACCE SSPOINT_SSID and Breadcrumb field set to 1" - PICS: CNET.S.C02.Rsp + PICS: CNET.S.C04.Rsp verification: | - ./chip-tool networkcommissioning remove hex: 1 0 + ./chip-tool networkcommissioning remove-network hex: 1 0 Below is an example: @@ -79,7 +79,7 @@ tests: field set to 1" PICS: CNET.S.C06.Rsp verification: | - ./chip-tool networkcommissioning connect hex: 1 0 + ./chip-tool networkcommissioning connect-network hex: 1 0 Below is an example: diff --git a/src/app/tests/suites/certification/Test_TC_CNET_4_9.yaml b/src/app/tests/suites/certification/Test_TC_CNET_4_9.yaml index 5963e9bbae6801..1bb06e91f05c31 100644 --- a/src/app/tests/suites/certification/Test_TC_CNET_4_9.yaml +++ b/src/app/tests/suites/certification/Test_TC_CNET_4_9.yaml @@ -164,7 +164,7 @@ tests: "Step 9: TH sends ConnectNetwork command to the DUT with NetworkID field set to PIXIT.CNET.WIFI_1ST_ACCESSPOINT_SSID and Breadcrumb field set to 2" - PICS: CNET.S.C04.Rsp + PICS: CNET.S.C04.Rsp && CNET.S.C06.Rsp verification: | ./chip-tool networkcommissioning connect-network hex: 1 0 diff --git a/src/app/tests/suites/certification/Test_TC_DGWIFI_3_2_Simulated.yaml b/src/app/tests/suites/certification/Test_TC_DGWIFI_3_2_Simulated.yaml index 905d7f1b03f3ad..6580facaee8340 100644 --- a/src/app/tests/suites/certification/Test_TC_DGWIFI_3_2_Simulated.yaml +++ b/src/app/tests/suites/certification/Test_TC_DGWIFI_3_2_Simulated.yaml @@ -28,5 +28,5 @@ tests: # command: "WaitForCommissioning" - label: "DUT sends ResetCounts command to TH" - PICS: DGWIFI.S.C00.Tx + PICS: DGWIFI.C.C00.Tx wait: "ResetCounts" diff --git a/src/app/tests/suites/certification/Test_TC_DRLK_2_10.yaml b/src/app/tests/suites/certification/Test_TC_DRLK_2_10.yaml index f561d9130e46ce..d6b889127d80a6 100644 --- a/src/app/tests/suites/certification/Test_TC_DRLK_2_10.yaml +++ b/src/app/tests/suites/certification/Test_TC_DRLK_2_10.yaml @@ -607,8 +607,9 @@ tests: - label: "Step 5e: TH sends Set Credential Command to DUT with the following - fields: OperationType as 0-Add Credential as 1 1- PIN, Index - CredentialData as 123456 UserIndex as 1 UserStatus as 0 UserType as 0" + fields: 1.OperationType as 0 2.Credential as 1 1- PIN, Index + 3.CredentialData as 123456 4.UserIndex as 1 5.UserStatus as null + 6.UserType as null" PICS: DRLK.S.F08 && DRLK.S.C22.Rsp && DRLK.S.C23.Tx verification: | ./chip-tool doorlock clear-credential '{ "credentialType" : 1 , "credentialIndex" : 2 }' 1 1 --timedInteractionTimeoutMs 1000 diff --git a/src/app/tests/suites/certification/Test_TC_DRLK_3_2.yaml b/src/app/tests/suites/certification/Test_TC_DRLK_3_2.yaml index 3c38efe9802c5d..515b36078dbbb1 100644 --- a/src/app/tests/suites/certification/Test_TC_DRLK_3_2.yaml +++ b/src/app/tests/suites/certification/Test_TC_DRLK_3_2.yaml @@ -40,779 +40,720 @@ tests: - label: "Step 1: DUT sends Lock Door command to TH." PICS: DRLK.C.C00.Tx verification: | - ./chip-tool doorlock lock-door 1 1 --timedInteractionTimeoutMs 1000 --trace_decode 1 + ./chip-tool doorlock lock-door 1 1 --timedInteractionTimeoutMs 1000 Verify TH receives Lock Door command with SUCCESS response on TH(lock-app) log: - [1685673050.566811][2584:2586] CHIP:DMG: InvokeResponseMessage = - [1685673050.566867][2584:2586] CHIP:DMG: { - [1685673050.566921][2584:2586] CHIP:DMG: suppressResponse = false, - [1685673050.566977][2584:2586] CHIP:DMG: InvokeResponseIBs = - [1685673050.567050][2584:2586] CHIP:DMG: [ - [1685673050.567107][2584:2586] CHIP:DMG: InvokeResponseIB = - [1685673050.567186][2584:2586] CHIP:DMG: { - [1685673050.567248][2584:2586] CHIP:DMG: CommandStatusIB = - [1685673050.567320][2584:2586] CHIP:DMG: { - [1685673050.567387][2584:2586] CHIP:DMG: CommandPathIB = - [1685673050.567464][2584:2586] CHIP:DMG: { - [1685673050.567540][2584:2586] CHIP:DMG: EndpointId = 0x1, - [1685673050.567625][2584:2586] CHIP:DMG: ClusterId = 0x101, - [1685673050.567706][2584:2586] CHIP:DMG: CommandId = 0x0, - [1685673050.567784][2584:2586] CHIP:DMG: }, - [1685673050.567870][2584:2586] CHIP:DMG: - [1685673050.567938][2584:2586] CHIP:DMG: StatusIB = - [1685673050.568015][2584:2586] CHIP:DMG: { - [1685673050.568092][2584:2586] CHIP:DMG: status = 0x00 (SUCCESS), - [1685673050.568171][2584:2586] CHIP:DMG: }, - [1685673050.568246][2584:2586] CHIP:DMG: - [1685673050.568313][2584:2586] CHIP:DMG: }, - [1685673050.568389][2584:2586] CHIP:DMG: - [1685673050.568451][2584:2586] CHIP:DMG: }, - [1685673050.568524][2584:2586] CHIP:DMG: - [1685673050.568578][2584:2586] CHIP:DMG: ], - [1685673050.568650][2584:2586] CHIP:DMG: - [1685673050.568707][2584:2586] CHIP:DMG: InteractionModelRevision = 1 - [1685673050.568761][2584:2586] CHIP:DMG: }, + [1698646727.274715][11887:11887] CHIP:DMG: InvokeRequestMessage = + [1698646727.274753][11887:11887] CHIP:DMG: { + [1698646727.274788][11887:11887] CHIP:DMG: suppressResponse = false, + [1698646727.274829][11887:11887] CHIP:DMG: timedRequest = true, + [1698646727.274867][11887:11887] CHIP:DMG: InvokeRequests = + [1698646727.274916][11887:11887] CHIP:DMG: [ + [1698646727.274955][11887:11887] CHIP:DMG: CommandDataIB = + [1698646727.274998][11887:11887] CHIP:DMG: { + [1698646727.275119][11887:11887] CHIP:DMG: CommandPathIB = + [1698646727.275180][11887:11887] CHIP:DMG: { + [1698646727.275229][11887:11887] CHIP:DMG: EndpointId = 0x1, + [1698646727.275279][11887:11887] CHIP:DMG: ClusterId = 0x101, + [1698646727.275398][11887:11887] CHIP:DMG: CommandId = 0x0, + [1698646727.275447][11887:11887] CHIP:DMG: }, + [1698646727.275498][11887:11887] CHIP:DMG: + [1698646727.275591][11887:11887] CHIP:DMG: CommandFields = + [1698646727.275639][11887:11887] CHIP:DMG: { + [1698646727.275687][11887:11887] CHIP:DMG: }, + [1698646727.275765][11887:11887] CHIP:DMG: }, + [1698646727.275817][11887:11887] CHIP:DMG: + [1698646727.275854][11887:11887] CHIP:DMG: ], + [1698646727.275900][11887:11887] CHIP:DMG: + [1698646727.275977][11887:11887] CHIP:DMG: InteractionModelRevision = 11 + [1698646727.276053][11887:11887] CHIP:DMG: }, disabled: true - label: "Step 2: DUT sends Unlock Door command to TH." PICS: DRLK.C.C01.Tx verification: | - ./chip-tool doorlock unlock-door 1 1 --timedInteractionTimeoutMs 1000 --trace_decode 1 + ./chip-tool doorlock unlock-door 1 1 --timedInteractionTimeoutMs 1000 Verify TH receives Unlock Door command with SUCCESS response on TH(lock-app) log: - [1685673083.557613][2593:2595] CHIP:DMG: InvokeResponseMessage = - [1685673083.557668][2593:2595] CHIP:DMG: { - [1685673083.557724][2593:2595] CHIP:DMG: suppressResponse = false, - [1685673083.557834][2593:2595] CHIP:DMG: InvokeResponseIBs = - [1685673083.557915][2593:2595] CHIP:DMG: [ - [1685673083.557973][2593:2595] CHIP:DMG: InvokeResponseIB = - [1685673083.558070][2593:2595] CHIP:DMG: { - [1685673083.558133][2593:2595] CHIP:DMG: CommandStatusIB = - [1685673083.558222][2593:2595] CHIP:DMG: { - [1685673083.558306][2593:2595] CHIP:DMG: CommandPathIB = - [1685673083.558399][2593:2595] CHIP:DMG: { - [1685673083.558493][2593:2595] CHIP:DMG: EndpointId = 0x1, - [1685673083.558589][2593:2595] CHIP:DMG: ClusterId = 0x101, - [1685673083.558685][2593:2595] CHIP:DMG: CommandId = 0x1, - [1685673083.558775][2593:2595] CHIP:DMG: }, - [1685673083.558878][2593:2595] CHIP:DMG: - [1685673083.558962][2593:2595] CHIP:DMG: StatusIB = - [1685673083.559058][2593:2595] CHIP:DMG: { - [1685673083.559150][2593:2595] CHIP:DMG: status = 0x00 (SUCCESS), - [1685673083.559243][2593:2595] CHIP:DMG: }, - [1685673083.559335][2593:2595] CHIP:DMG: - [1685673083.559418][2593:2595] CHIP:DMG: }, - [1685673083.559513][2593:2595] CHIP:DMG: - [1685673083.559582][2593:2595] CHIP:DMG: }, - [1685673083.559663][2593:2595] CHIP:DMG: - [1685673083.559720][2593:2595] CHIP:DMG: ], - [1685673083.559792][2593:2595] CHIP:DMG: - [1685673083.559848][2593:2595] CHIP:DMG: InteractionModelRevision = 1 - [1685673083.559903][2593:2595] CHIP:DMG: }, + [1698646754.942170][11887:11887] CHIP:DMG: InvokeRequestMessage = + [1698646754.942214][11887:11887] CHIP:DMG: { + [1698646754.942241][11887:11887] CHIP:DMG: suppressResponse = false, + [1698646754.942284][11887:11887] CHIP:DMG: timedRequest = true, + [1698646754.942314][11887:11887] CHIP:DMG: InvokeRequests = + [1698646754.942351][11887:11887] CHIP:DMG: [ + [1698646754.942397][11887:11887] CHIP:DMG: CommandDataIB = + [1698646754.942443][11887:11887] CHIP:DMG: { + [1698646754.942490][11887:11887] CHIP:DMG: CommandPathIB = + [1698646754.942527][11887:11887] CHIP:DMG: { + [1698646754.942563][11887:11887] CHIP:DMG: EndpointId = 0x1, + [1698646754.942613][11887:11887] CHIP:DMG: ClusterId = 0x101, + [1698646754.942650][11887:11887] CHIP:DMG: CommandId = 0x1, + [1698646754.942686][11887:11887] CHIP:DMG: }, + [1698646754.942735][11887:11887] CHIP:DMG: + [1698646754.942768][11887:11887] CHIP:DMG: CommandFields = + [1698646754.942803][11887:11887] CHIP:DMG: { + [1698646754.942838][11887:11887] CHIP:DMG: }, + [1698646754.942882][11887:11887] CHIP:DMG: }, + [1698646754.942918][11887:11887] CHIP:DMG: + [1698646754.942946][11887:11887] CHIP:DMG: ], + [1698646754.942992][11887:11887] CHIP:DMG: + [1698646754.943021][11887:11887] CHIP:DMG: InteractionModelRevision = 11 + [1698646754.943048][11887:11887] CHIP:DMG: }, disabled: true - label: "Step 3: DUT sends Unlock with Timeout command to TH." PICS: DRLK.C.C03.Tx verification: | - ./chip-tool doorlock unlock-with-timeout 60 1 1 --timedInteractionTimeoutMs 1000 --trace_decode 1 + ./chip-tool doorlock unlock-with-timeout 60 1 1 --timedInteractionTimeoutMs 1000 Verify TH receives Unlock with Timeout command with SUCCESS response on TH(lock-app) log: - [1685673101.154705][2596:2598] CHIP:DMG: InvokeResponseMessage = - [1685673101.154760][2596:2598] CHIP:DMG: { - [1685673101.154813][2596:2598] CHIP:DMG: suppressResponse = false, - [1685673101.154869][2596:2598] CHIP:DMG: InvokeResponseIBs = - [1685673101.154941][2596:2598] CHIP:DMG: [ - [1685673101.154998][2596:2598] CHIP:DMG: InvokeResponseIB = - [1685673101.155074][2596:2598] CHIP:DMG: { - [1685673101.155135][2596:2598] CHIP:DMG: CommandStatusIB = - [1685673101.155206][2596:2598] CHIP:DMG: { - [1685673101.155273][2596:2598] CHIP:DMG: CommandPathIB = - [1685673101.155349][2596:2598] CHIP:DMG: { - [1685673101.155426][2596:2598] CHIP:DMG: EndpointId = 0x1, - [1685673101.155501][2596:2598] CHIP:DMG: ClusterId = 0x101, - [1685673101.155586][2596:2598] CHIP:DMG: CommandId = 0x3, - [1685673101.155660][2596:2598] CHIP:DMG: }, - [1685673101.155743][2596:2598] CHIP:DMG: - [1685673101.155812][2596:2598] CHIP:DMG: StatusIB = - [1685673101.155886][2596:2598] CHIP:DMG: { - [1685673101.155965][2596:2598] CHIP:DMG: status = 0x00 (SUCCESS), - [1685673101.156041][2596:2598] CHIP:DMG: }, - [1685673101.156115][2596:2598] CHIP:DMG: - [1685673101.156183][2596:2598] CHIP:DMG: }, - [1685673101.156259][2596:2598] CHIP:DMG: - [1685673101.156321][2596:2598] CHIP:DMG: }, - [1685673101.156392][2596:2598] CHIP:DMG: - [1685673101.156447][2596:2598] CHIP:DMG: ], - [1685673101.156517][2596:2598] CHIP:DMG: - [1685673101.156573][2596:2598] CHIP:DMG: InteractionModelRevision = 1 - [1685673101.156629][2596:2598] CHIP:DMG: }, + [1698646961.411111][11905:11905] CHIP:DMG: InvokeRequestMessage = + [1698646961.411145][11905:11905] CHIP:DMG: { + [1698646961.411175][11905:11905] CHIP:DMG: suppressResponse = false, + [1698646961.411212][11905:11905] CHIP:DMG: timedRequest = true, + [1698646961.411246][11905:11905] CHIP:DMG: InvokeRequests = + [1698646961.411291][11905:11905] CHIP:DMG: [ + [1698646961.411328][11905:11905] CHIP:DMG: CommandDataIB = + [1698646961.411374][11905:11905] CHIP:DMG: { + [1698646961.411478][11905:11905] CHIP:DMG: CommandPathIB = + [1698646961.411527][11905:11905] CHIP:DMG: { + [1698646961.411572][11905:11905] CHIP:DMG: EndpointId = 0x1, + [1698646961.411616][11905:11905] CHIP:DMG: ClusterId = 0x101, + [1698646961.411694][11905:11905] CHIP:DMG: CommandId = 0x3, + [1698646961.411776][11905:11905] CHIP:DMG: }, + [1698646961.411824][11905:11905] CHIP:DMG: + [1698646961.411861][11905:11905] CHIP:DMG: CommandFields = + [1698646961.411903][11905:11905] CHIP:DMG: { + [1698646961.411972][11905:11905] CHIP:DMG: 0x0 = 60, + [1698646961.412053][11905:11905] CHIP:DMG: }, + [1698646961.412093][11905:11905] CHIP:DMG: }, + [1698646961.412136][11905:11905] CHIP:DMG: + [1698646961.412169][11905:11905] CHIP:DMG: ], + [1698646961.412211][11905:11905] CHIP:DMG: + [1698646961.412244][11905:11905] CHIP:DMG: InteractionModelRevision = 11 + [1698646961.412277][11905:11905] CHIP:DMG: }, disabled: true - label: "Step 4: DUT sends Set Week Day Schedule command to TH." PICS: DRLK.C.F04 && DRLK.C.C0b.Tx verification: | - ./chip-tool doorlock set-user 0 1 xxx 6452 1 0 0 1 1 --timedInteractionTimeoutMs 1000 --trace_decode 1 + ./chip-tool doorlock set-user 0 1 xxx 6452 1 0 0 1 1 --timedInteractionTimeoutMs 1000 Verify TH receives Set user command with SUCCESS response on TH(lock-app) log: - [1685673117.936503][2600:2602] CHIP:DMG: InvokeResponseMessage = - [1685673117.936560][2600:2602] CHIP:DMG: { - [1685673117.936615][2600:2602] CHIP:DMG: suppressResponse = false, - [1685673117.936672][2600:2602] CHIP:DMG: InvokeResponseIBs = - [1685673117.936747][2600:2602] CHIP:DMG: [ - [1685673117.936803][2600:2602] CHIP:DMG: InvokeResponseIB = - [1685673117.936880][2600:2602] CHIP:DMG: { - [1685673117.936941][2600:2602] CHIP:DMG: CommandStatusIB = - [1685673117.937029][2600:2602] CHIP:DMG: { - [1685673117.937106][2600:2602] CHIP:DMG: CommandPathIB = - [1685673117.937199][2600:2602] CHIP:DMG: { - [1685673117.937292][2600:2602] CHIP:DMG: EndpointId = 0x1, - [1685673117.937389][2600:2602] CHIP:DMG: ClusterId = 0x101, - [1685673117.937486][2600:2602] CHIP:DMG: CommandId = 0x1a, - [1685673117.937577][2600:2602] CHIP:DMG: }, - [1685673117.937680][2600:2602] CHIP:DMG: - [1685673117.937755][2600:2602] CHIP:DMG: StatusIB = - [1685673117.938008][2600:2602] CHIP:DMG: { - [1685673117.938101][2600:2602] CHIP:DMG: status = 0x00 (SUCCESS), - [1685673117.938194][2600:2602] CHIP:DMG: }, - [1685673117.938286][2600:2602] CHIP:DMG: - [1685673117.938368][2600:2602] CHIP:DMG: }, - [1685673117.938462][2600:2602] CHIP:DMG: - [1685673117.938530][2600:2602] CHIP:DMG: }, - [1685673117.938610][2600:2602] CHIP:DMG: - [1685673117.938667][2600:2602] CHIP:DMG: ], - [1685673117.938737][2600:2602] CHIP:DMG: - [1685673117.938795][2600:2602] CHIP:DMG: InteractionModelRevision = 1 - [1685673117.938850][2600:2602] CHIP:DMG: }, - - - ./chip-tool doorlock set-week-day-schedule 1 1 2 15 45 16 55 1 1 --trace_decode 1 + [1698646982.058610][11905:11905] CHIP:DMG: InvokeRequestMessage = + [1698646982.058637][11905:11905] CHIP:DMG: { + [1698646982.058661][11905:11905] CHIP:DMG: suppressResponse = false, + [1698646982.058690][11905:11905] CHIP:DMG: timedRequest = true, + [1698646982.058717][11905:11905] CHIP:DMG: InvokeRequests = + [1698646982.058754][11905:11905] CHIP:DMG: [ + [1698646982.058780][11905:11905] CHIP:DMG: CommandDataIB = + [1698646982.058811][11905:11905] CHIP:DMG: { + [1698646982.058839][11905:11905] CHIP:DMG: CommandPathIB = + [1698646982.058876][11905:11905] CHIP:DMG: { + [1698646982.058910][11905:11905] CHIP:DMG: EndpointId = 0x1, + [1698646982.058944][11905:11905] CHIP:DMG: ClusterId = 0x101, + [1698646982.058979][11905:11905] CHIP:DMG: CommandId = 0x1a, + [1698646982.059011][11905:11905] CHIP:DMG: }, + [1698646982.059072][11905:11905] CHIP:DMG: + [1698646982.059104][11905:11905] CHIP:DMG: CommandFields = + [1698646982.059137][11905:11905] CHIP:DMG: { + [1698646982.059192][11905:11905] CHIP:DMG: 0x0 = 0, + [1698646982.059232][11905:11905] CHIP:DMG: 0x1 = 1, + [1698646982.059270][11905:11905] CHIP:DMG: 0x2 = "xxx" (3 chars), + [1698646982.059333][11905:11905] CHIP:DMG: 0x3 = 6452, + [1698646982.059371][11905:11905] CHIP:DMG: 0x4 = 1, + [1698646982.059406][11905:11905] CHIP:DMG: 0x5 = 0, + [1698646982.059467][11905:11905] CHIP:DMG: 0x6 = 0, + [1698646982.059503][11905:11905] CHIP:DMG: }, + [1698646982.059534][11905:11905] CHIP:DMG: }, + [1698646982.059571][11905:11905] CHIP:DMG: + [1698646982.059625][11905:11905] CHIP:DMG: ], + [1698646982.059662][11905:11905] CHIP:DMG: + [1698646982.059714][11905:11905] CHIP:DMG: InteractionModelRevision = 11 + [1698646982.059763][11905:11905] CHIP:DMG: }, + + ./chip-tool doorlock set-week-day-schedule 1 1 2 15 45 16 55 1 1 Verify TH receives Set Week Day Schedule command with SUCCESS response on TH(lock-app) log: - [1685673143.421323][2604:2606] CHIP:DMG: InvokeResponseMessage = - [1685673143.421380][2604:2606] CHIP:DMG: { - [1685673143.421437][2604:2606] CHIP:DMG: suppressResponse = false, - [1685673143.421495][2604:2606] CHIP:DMG: InvokeResponseIBs = - [1685673143.421569][2604:2606] CHIP:DMG: [ - [1685673143.421628][2604:2606] CHIP:DMG: InvokeResponseIB = - [1685673143.421705][2604:2606] CHIP:DMG: { - [1685673143.421893][2604:2606] CHIP:DMG: CommandStatusIB = - [1685673143.421975][2604:2606] CHIP:DMG: { - [1685673143.422043][2604:2606] CHIP:DMG: CommandPathIB = - [1685673143.422121][2604:2606] CHIP:DMG: { - [1685673143.422197][2604:2606] CHIP:DMG: EndpointId = 0x1, - [1685673143.422277][2604:2606] CHIP:DMG: ClusterId = 0x101, - [1685673143.422357][2604:2606] CHIP:DMG: CommandId = 0xb, - [1685673143.422432][2604:2606] CHIP:DMG: }, - [1685673143.422517][2604:2606] CHIP:DMG: - [1685673143.422586][2604:2606] CHIP:DMG: StatusIB = - [1685673143.422660][2604:2606] CHIP:DMG: { - [1685673143.422737][2604:2606] CHIP:DMG: status = 0x00 (SUCCESS), - [1685673143.422812][2604:2606] CHIP:DMG: }, - [1685673143.422887][2604:2606] CHIP:DMG: - [1685673143.422954][2604:2606] CHIP:DMG: }, - [1685673143.423030][2604:2606] CHIP:DMG: - [1685673143.423092][2604:2606] CHIP:DMG: }, - [1685673143.423162][2604:2606] CHIP:DMG: - [1685673143.423218][2604:2606] CHIP:DMG: ], - [1685673143.423289][2604:2606] CHIP:DMG: - [1685673143.423345][2604:2606] CHIP:DMG: InteractionModelRevision = 1 - [1685673143.423400][2604:2606] CHIP:DMG: }, + [1698647005.052611][11905:11905] CHIP:DMG: InvokeRequestMessage = + [1698647005.052642][11905:11905] CHIP:DMG: { + [1698647005.052668][11905:11905] CHIP:DMG: suppressResponse = false, + [1698647005.052700][11905:11905] CHIP:DMG: timedRequest = false, + [1698647005.052728][11905:11905] CHIP:DMG: InvokeRequests = + [1698647005.052783][11905:11905] CHIP:DMG: [ + [1698647005.052813][11905:11905] CHIP:DMG: CommandDataIB = + [1698647005.052845][11905:11905] CHIP:DMG: { + [1698647005.052889][11905:11905] CHIP:DMG: CommandPathIB = + [1698647005.052931][11905:11905] CHIP:DMG: { + [1698647005.052980][11905:11905] CHIP:DMG: EndpointId = 0x1, + [1698647005.053019][11905:11905] CHIP:DMG: ClusterId = 0x101, + [1698647005.053057][11905:11905] CHIP:DMG: CommandId = 0xb, + [1698647005.053103][11905:11905] CHIP:DMG: }, + [1698647005.053142][11905:11905] CHIP:DMG: + [1698647005.053174][11905:11905] CHIP:DMG: CommandFields = + [1698647005.053209][11905:11905] CHIP:DMG: { + [1698647005.053258][11905:11905] CHIP:DMG: 0x0 = 1, + [1698647005.053297][11905:11905] CHIP:DMG: 0x1 = 1, + [1698647005.053347][11905:11905] CHIP:DMG: 0x2 = 2, + [1698647005.053386][11905:11905] CHIP:DMG: 0x3 = 15, + [1698647005.053424][11905:11905] CHIP:DMG: 0x4 = 45, + [1698647005.053462][11905:11905] CHIP:DMG: 0x5 = 16, + [1698647005.053512][11905:11905] CHIP:DMG: 0x6 = 55, + [1698647005.053549][11905:11905] CHIP:DMG: }, + [1698647005.053593][11905:11905] CHIP:DMG: }, + [1698647005.053636][11905:11905] CHIP:DMG: + [1698647005.053669][11905:11905] CHIP:DMG: ], + [1698647005.053809][11905:11905] CHIP:DMG: + [1698647005.053864][11905:11905] CHIP:DMG: InteractionModelRevision = 11 + [1698647005.053898][11905:11905] CHIP:DMG: }, disabled: true - label: "Step 5: DUT sends Get Week Day Schedule command to TH." PICS: DRLK.C.F04 && DRLK.C.C0c.Tx verification: | - ./chip-tool doorlock get-week-day-schedule 1 1 1 1 --trace_decode 1 + ./chip-tool doorlock get-week-day-schedule 1 1 1 1 Verify TH receives Get Week Day Schedule command response on TH(lock-app) log: - [1685673169.698639][2609:2611] CHIP:DMG: InvokeResponseMessage = - [1685673169.698694][2609:2611] CHIP:DMG: { - [1685673169.698748][2609:2611] CHIP:DMG: suppressResponse = false, - [1685673169.698804][2609:2611] CHIP:DMG: InvokeResponseIBs = - [1685673169.698882][2609:2611] CHIP:DMG: [ - [1685673169.698940][2609:2611] CHIP:DMG: InvokeResponseIB = - [1685673169.699023][2609:2611] CHIP:DMG: { - [1685673169.699083][2609:2611] CHIP:DMG: CommandDataIB = - [1685673169.699151][2609:2611] CHIP:DMG: { - [1685673169.699211][2609:2611] CHIP:DMG: CommandPathIB = - [1685673169.699288][2609:2611] CHIP:DMG: { - [1685673169.699363][2609:2611] CHIP:DMG: EndpointId = 0x1, - [1685673169.699443][2609:2611] CHIP:DMG: ClusterId = 0x101, - [1685673169.699521][2609:2611] CHIP:DMG: CommandId = 0xc, - [1685673169.699596][2609:2611] CHIP:DMG: }, - [1685673169.699787][2609:2611] CHIP:DMG: - [1685673169.699917][2609:2611] CHIP:DMG: CommandFields = - [1685673169.700000][2609:2611] CHIP:DMG: { - [1685673169.700080][2609:2611] CHIP:DMG: 0x0 = 1, - [1685673169.700162][2609:2611] CHIP:DMG: 0x1 = 1, - [1685673169.700243][2609:2611] CHIP:DMG: 0x2 = 0, - [1685673169.700324][2609:2611] CHIP:DMG: 0x3 = 2, - [1685673169.700451][2609:2611] CHIP:DMG: 0x4 = 15, - [1685673169.700535][2609:2611] CHIP:DMG: 0x5 = 45, - [1685673169.700616][2609:2611] CHIP:DMG: 0x6 = 16, - [1685673169.700697][2609:2611] CHIP:DMG: 0x7 = 55, - [1685673169.700835][2609:2611] CHIP:DMG: }, - [1685673169.700908][2609:2611] CHIP:DMG: }, - [1685673169.700991][2609:2611] CHIP:DMG: - [1685673169.701053][2609:2611] CHIP:DMG: }, - [1685673169.701130][2609:2611] CHIP:DMG: - [1685673169.701186][2609:2611] CHIP:DMG: ], - [1685673169.701265][2609:2611] CHIP:DMG: - [1685673169.701320][2609:2611] CHIP:DMG: InteractionModelRevision = 1 - [1685673169.701375][2609:2611] CHIP:DMG: }, + [1698647031.575773][11905:11905] CHIP:DMG: InvokeRequestMessage = + [1698647031.575813][11905:11905] CHIP:DMG: { + [1698647031.575848][11905:11905] CHIP:DMG: suppressResponse = false, + [1698647031.575886][11905:11905] CHIP:DMG: timedRequest = false, + [1698647031.575925][11905:11905] CHIP:DMG: InvokeRequests = + [1698647031.575974][11905:11905] CHIP:DMG: [ + [1698647031.576012][11905:11905] CHIP:DMG: CommandDataIB = + [1698647031.576055][11905:11905] CHIP:DMG: { + [1698647031.576095][11905:11905] CHIP:DMG: CommandPathIB = + [1698647031.576140][11905:11905] CHIP:DMG: { + [1698647031.576192][11905:11905] CHIP:DMG: EndpointId = 0x1, + [1698647031.576242][11905:11905] CHIP:DMG: ClusterId = 0x101, + [1698647031.576320][11905:11905] CHIP:DMG: CommandId = 0xc, + [1698647031.576372][11905:11905] CHIP:DMG: }, + [1698647031.576424][11905:11905] CHIP:DMG: + [1698647031.576466][11905:11905] CHIP:DMG: CommandFields = + [1698647031.576513][11905:11905] CHIP:DMG: { + [1698647031.576563][11905:11905] CHIP:DMG: 0x0 = 1, + [1698647031.576613][11905:11905] CHIP:DMG: 0x1 = 1, + [1698647031.576665][11905:11905] CHIP:DMG: }, + [1698647031.576708][11905:11905] CHIP:DMG: }, + [1698647031.576755][11905:11905] CHIP:DMG: + [1698647031.576792][11905:11905] CHIP:DMG: ], + [1698647031.576835][11905:11905] CHIP:DMG: + [1698647031.576866][11905:11905] CHIP:DMG: InteractionModelRevision = 11 + [1698647031.576896][11905:11905] CHIP:DMG: }, disabled: true - label: "Step 6: DUT sends Clear Week Day Schedule command to TH." PICS: DRLK.C.F04 && DRLK.C.C0d.Tx verification: | - ./chip-tool doorlock clear-week-day-schedule 1 1 1 1 --trace_decode 1 + ./chip-tool doorlock clear-week-day-schedule 1 1 1 1 Verify TH receives Clear Week Day Schedule command with SUCCESS response on TH(lock-app) log: - [1685673196.080189][2614:2616] CHIP:DMG: InvokeResponseMessage = - [1685673196.080247][2614:2616] CHIP:DMG: { - [1685673196.080303][2614:2616] CHIP:DMG: suppressResponse = false, - [1685673196.080383][2614:2616] CHIP:DMG: InvokeResponseIBs = - [1685673196.080455][2614:2616] CHIP:DMG: [ - [1685673196.080533][2614:2616] CHIP:DMG: InvokeResponseIB = - [1685673196.080616][2614:2616] CHIP:DMG: { - [1685673196.080696][2614:2616] CHIP:DMG: CommandStatusIB = - [1685673196.080768][2614:2616] CHIP:DMG: { - [1685673196.080836][2614:2616] CHIP:DMG: CommandPathIB = - [1685673196.080933][2614:2616] CHIP:DMG: { - [1685673196.081030][2614:2616] CHIP:DMG: EndpointId = 0x1, - [1685673196.081112][2614:2616] CHIP:DMG: ClusterId = 0x101, - [1685673196.081213][2614:2616] CHIP:DMG: CommandId = 0xd, - [1685673196.081284][2614:2616] CHIP:DMG: }, - [1685673196.081362][2614:2616] CHIP:DMG: - [1685673196.081448][2614:2616] CHIP:DMG: StatusIB = - [1685673196.081519][2614:2616] CHIP:DMG: { - [1685673196.081616][2614:2616] CHIP:DMG: status = 0x00 (SUCCESS), - [1685673196.081692][2614:2616] CHIP:DMG: }, - [1685673196.081822][2614:2616] CHIP:DMG: - [1685673196.081891][2614:2616] CHIP:DMG: }, - [1685673196.081991][2614:2616] CHIP:DMG: - [1685673196.082053][2614:2616] CHIP:DMG: }, - [1685673196.082125][2614:2616] CHIP:DMG: - [1685673196.082202][2614:2616] CHIP:DMG: ], - [1685673196.082276][2614:2616] CHIP:DMG: - [1685673196.082331][2614:2616] CHIP:DMG: InteractionModelRevision = 1 - [1685673196.082409][2614:2616] CHIP:DMG: }, + [1698646775.513834][11887:11887] CHIP:DMG: InvokeRequestMessage = + [1698646775.513862][11887:11887] CHIP:DMG: { + [1698646775.513884][11887:11887] CHIP:DMG: suppressResponse = false, + [1698646775.513911][11887:11887] CHIP:DMG: timedRequest = false, + [1698646775.513942][11887:11887] CHIP:DMG: InvokeRequests = + [1698646775.513982][11887:11887] CHIP:DMG: [ + [1698646775.514007][11887:11887] CHIP:DMG: CommandDataIB = + [1698646775.514033][11887:11887] CHIP:DMG: { + [1698646775.514059][11887:11887] CHIP:DMG: CommandPathIB = + [1698646775.514088][11887:11887] CHIP:DMG: { + [1698646775.514118][11887:11887] CHIP:DMG: EndpointId = 0x1, + [1698646775.514152][11887:11887] CHIP:DMG: ClusterId = 0x101, + [1698646775.514184][11887:11887] CHIP:DMG: CommandId = 0xd, + [1698646775.514214][11887:11887] CHIP:DMG: }, + [1698646775.514245][11887:11887] CHIP:DMG: + [1698646775.514272][11887:11887] CHIP:DMG: CommandFields = + [1698646775.514301][11887:11887] CHIP:DMG: { + [1698646775.514332][11887:11887] CHIP:DMG: 0x0 = 1, + [1698646775.514364][11887:11887] CHIP:DMG: 0x1 = 1, + [1698646775.514396][11887:11887] CHIP:DMG: }, + [1698646775.514422][11887:11887] CHIP:DMG: }, + [1698646775.514453][11887:11887] CHIP:DMG: + [1698646775.514477][11887:11887] CHIP:DMG: ], + [1698646775.514507][11887:11887] CHIP:DMG: + [1698646775.514529][11887:11887] CHIP:DMG: InteractionModelRevision = 11 + [1698646775.514552][11887:11887] CHIP:DMG: }, disabled: true - label: "Step 7: DUT sends Set Year Day Schedule command to TH." PICS: DRLK.C.F04 && DRLK.C.C0e.Tx verification: | - ./chip-tool doorlock set-year-day-schedule 1 1 1080 2100 1 1 --trace_decode 1 + ./chip-tool doorlock set-year-day-schedule 1 1 1080 2100 1 1 Verify TH receives Set Year Day Schedule command with SUCCESS response on TH(lock-app) log: - [1685673212.614964][2617:2619] CHIP:DMG: InvokeResponseMessage = - [1685673212.615020][2617:2619] CHIP:DMG: { - [1685673212.615096][2617:2619] CHIP:DMG: suppressResponse = false, - [1685673212.615154][2617:2619] CHIP:DMG: InvokeResponseIBs = - [1685673212.615227][2617:2619] CHIP:DMG: [ - [1685673212.615306][2617:2619] CHIP:DMG: InvokeResponseIB = - [1685673212.615385][2617:2619] CHIP:DMG: { - [1685673212.615466][2617:2619] CHIP:DMG: CommandStatusIB = - [1685673212.615544][2617:2619] CHIP:DMG: { - [1685673212.615611][2617:2619] CHIP:DMG: CommandPathIB = - [1685673212.615707][2617:2619] CHIP:DMG: { - [1685673212.615784][2617:2619] CHIP:DMG: EndpointId = 0x1, - [1685673212.615884][2617:2619] CHIP:DMG: ClusterId = 0x101, - [1685673212.615962][2617:2619] CHIP:DMG: CommandId = 0xe, - [1685673212.616061][2617:2619] CHIP:DMG: }, - [1685673212.616147][2617:2619] CHIP:DMG: - [1685673212.616237][2617:2619] CHIP:DMG: StatusIB = - [1685673212.616314][2617:2619] CHIP:DMG: { - [1685673212.616411][2617:2619] CHIP:DMG: status = 0x00 (SUCCESS), - [1685673212.616487][2617:2619] CHIP:DMG: }, - [1685673212.616583][2617:2619] CHIP:DMG: - [1685673212.616651][2617:2619] CHIP:DMG: }, - [1685673212.616747][2617:2619] CHIP:DMG: - [1685673212.616809][2617:2619] CHIP:DMG: }, - [1685673212.616902][2617:2619] CHIP:DMG: - [1685673212.616959][2617:2619] CHIP:DMG: ], - [1685673212.617030][2617:2619] CHIP:DMG: - [1685673212.617109][2617:2619] CHIP:DMG: InteractionModelRevision = 1 - [1685673212.617164][2617:2619] CHIP:DMG: }, + [1698646805.099727][11887:11887] CHIP:DMG: InvokeRequestMessage = + [1698646805.099759][11887:11887] CHIP:DMG: { + [1698646805.099786][11887:11887] CHIP:DMG: suppressResponse = false, + [1698646805.099817][11887:11887] CHIP:DMG: timedRequest = false, + [1698646805.099847][11887:11887] CHIP:DMG: InvokeRequests = + [1698646805.099885][11887:11887] CHIP:DMG: [ + [1698646805.099914][11887:11887] CHIP:DMG: CommandDataIB = + [1698646805.099946][11887:11887] CHIP:DMG: { + [1698646805.099976][11887:11887] CHIP:DMG: CommandPathIB = + [1698646805.100015][11887:11887] CHIP:DMG: { + [1698646805.100051][11887:11887] CHIP:DMG: EndpointId = 0x1, + [1698646805.100089][11887:11887] CHIP:DMG: ClusterId = 0x101, + [1698646805.100126][11887:11887] CHIP:DMG: CommandId = 0xe, + [1698646805.100161][11887:11887] CHIP:DMG: }, + [1698646805.100196][11887:11887] CHIP:DMG: + [1698646805.100227][11887:11887] CHIP:DMG: CommandFields = + [1698646805.100260][11887:11887] CHIP:DMG: { + [1698646805.100427][11887:11887] CHIP:DMG: 0x0 = 1, + [1698646805.100471][11887:11887] CHIP:DMG: 0x1 = 1, + [1698646805.100510][11887:11887] CHIP:DMG: 0x2 = 1080, + [1698646805.100548][11887:11887] CHIP:DMG: 0x3 = 2100, + [1698646805.100585][11887:11887] CHIP:DMG: }, + [1698646805.100618][11887:11887] CHIP:DMG: }, + [1698646805.100656][11887:11887] CHIP:DMG: + [1698646805.100684][11887:11887] CHIP:DMG: ], + [1698646805.100721][11887:11887] CHIP:DMG: + [1698646805.100749][11887:11887] CHIP:DMG: InteractionModelRevision = 11 + [1698646805.100777][11887:11887] CHIP:DMG: }, disabled: true - label: "Step 8: DUT sends Get Year Day Schedule command to TH." PICS: DRLK.C.F04 && DRLK.C.C0f.Tx verification: | - ./chip-tool doorlock get-year-day-schedule 1 1 1 1 --trace_decode 1 + ./chip-tool doorlock get-year-day-schedule 1 1 1 1 Verify TH receives Get Year Day Schedule command response on TH(lock-app) log: - [1685673233.319349][2622:2624] CHIP:DMG: InvokeResponseMessage = - [1685673233.319404][2622:2624] CHIP:DMG: { - [1685673233.319458][2622:2624] CHIP:DMG: suppressResponse = false, - [1685673233.319515][2622:2624] CHIP:DMG: InvokeResponseIBs = - [1685673233.319592][2622:2624] CHIP:DMG: [ - [1685673233.319648][2622:2624] CHIP:DMG: InvokeResponseIB = - [1685673233.319732][2622:2624] CHIP:DMG: { - [1685673233.319792][2622:2624] CHIP:DMG: CommandDataIB = - [1685673233.319863][2622:2624] CHIP:DMG: { - [1685673233.319987][2622:2624] CHIP:DMG: CommandPathIB = - [1685673233.320066][2622:2624] CHIP:DMG: { - [1685673233.320144][2622:2624] CHIP:DMG: EndpointId = 0x1, - [1685673233.320223][2622:2624] CHIP:DMG: ClusterId = 0x101, - [1685673233.320303][2622:2624] CHIP:DMG: CommandId = 0xf, - [1685673233.320379][2622:2624] CHIP:DMG: }, - [1685673233.320458][2622:2624] CHIP:DMG: - [1685673233.320524][2622:2624] CHIP:DMG: CommandFields = - [1685673233.320598][2622:2624] CHIP:DMG: { - [1685673233.320678][2622:2624] CHIP:DMG: 0x0 = 1, - [1685673233.320758][2622:2624] CHIP:DMG: 0x1 = 1, - [1685673233.320840][2622:2624] CHIP:DMG: 0x2 = 0, - [1685673233.320992][2622:2624] CHIP:DMG: 0x3 = 1080, - [1685673233.321075][2622:2624] CHIP:DMG: 0x4 = 2100, - [1685673233.321155][2622:2624] CHIP:DMG: }, - [1685673233.321226][2622:2624] CHIP:DMG: }, - [1685673233.321310][2622:2624] CHIP:DMG: - [1685673233.321372][2622:2624] CHIP:DMG: }, - [1685673233.321450][2622:2624] CHIP:DMG: - [1685673233.321506][2622:2624] CHIP:DMG: ], - [1685673233.321581][2622:2624] CHIP:DMG: - [1685673233.321637][2622:2624] CHIP:DMG: InteractionModelRevision = 1 - [1685673233.321691][2622:2624] CHIP:DMG: }, + [1698647099.466619][11905:11905] CHIP:DMG: InvokeRequestMessage = + [1698647099.466652][11905:11905] CHIP:DMG: { + [1698647099.466679][11905:11905] CHIP:DMG: suppressResponse = false, + [1698647099.466709][11905:11905] CHIP:DMG: timedRequest = false, + [1698647099.466751][11905:11905] CHIP:DMG: InvokeRequests = + [1698647099.466787][11905:11905] CHIP:DMG: [ + [1698647099.466814][11905:11905] CHIP:DMG: CommandDataIB = + [1698647099.466842][11905:11905] CHIP:DMG: { + [1698647099.466880][11905:11905] CHIP:DMG: CommandPathIB = + [1698647099.466921][11905:11905] CHIP:DMG: { + [1698647099.466966][11905:11905] CHIP:DMG: EndpointId = 0x1, + [1698647099.467000][11905:11905] CHIP:DMG: ClusterId = 0x101, + [1698647099.467047][11905:11905] CHIP:DMG: CommandId = 0xf, + [1698647099.467080][11905:11905] CHIP:DMG: }, + [1698647099.467124][11905:11905] CHIP:DMG: + [1698647099.467155][11905:11905] CHIP:DMG: CommandFields = + [1698647099.467197][11905:11905] CHIP:DMG: { + [1698647099.467232][11905:11905] CHIP:DMG: 0x0 = 1, + [1698647099.467277][11905:11905] CHIP:DMG: 0x1 = 1, + [1698647099.467311][11905:11905] CHIP:DMG: }, + [1698647099.467352][11905:11905] CHIP:DMG: }, + [1698647099.467386][11905:11905] CHIP:DMG: + [1698647099.467411][11905:11905] CHIP:DMG: ], + [1698647099.467455][11905:11905] CHIP:DMG: + [1698647099.467481][11905:11905] CHIP:DMG: InteractionModelRevision = 11 + [1698647099.467517][11905:11905] CHIP:DMG: }, disabled: true - label: "Step 9: DUT sends Clear Year Day Schedule command to TH." PICS: DRLK.C.F04 && DRLK.C.C10.Tx verification: | - ./chip-tool doorlock clear-year-day-schedule 1 1 1 1 --trace_decode 1 + ./chip-tool doorlock clear-year-day-schedule 1 1 1 1 Verify TH receives Clear Year Day Schedule command with SUCCESS response on TH(lock-app) log: - [1685673250.141106][2626:2628] CHIP:DMG: InvokeResponseMessage = - [1685673250.141162][2626:2628] CHIP:DMG: { - [1685673250.141215][2626:2628] CHIP:DMG: suppressResponse = false, - [1685673250.141271][2626:2628] CHIP:DMG: InvokeResponseIBs = - [1685673250.141342][2626:2628] CHIP:DMG: [ - [1685673250.141399][2626:2628] CHIP:DMG: InvokeResponseIB = - [1685673250.141479][2626:2628] CHIP:DMG: { - [1685673250.141539][2626:2628] CHIP:DMG: CommandStatusIB = - [1685673250.141608][2626:2628] CHIP:DMG: { - [1685673250.141672][2626:2628] CHIP:DMG: CommandPathIB = - [1685673250.141746][2626:2628] CHIP:DMG: { - [1685673250.141871][2626:2628] CHIP:DMG: EndpointId = 0x1, - [1685673250.141952][2626:2628] CHIP:DMG: ClusterId = 0x101, - [1685673250.142031][2626:2628] CHIP:DMG: CommandId = 0x10, - [1685673250.142104][2626:2628] CHIP:DMG: }, - [1685673250.142189][2626:2628] CHIP:DMG: - [1685673250.142254][2626:2628] CHIP:DMG: StatusIB = - [1685673250.142325][2626:2628] CHIP:DMG: { - [1685673250.142402][2626:2628] CHIP:DMG: status = 0x00 (SUCCESS), - [1685673250.142567][2626:2628] CHIP:DMG: }, - [1685673250.142648][2626:2628] CHIP:DMG: - [1685673250.142716][2626:2628] CHIP:DMG: }, - [1685673250.142794][2626:2628] CHIP:DMG: - [1685673250.142853][2626:2628] CHIP:DMG: }, - [1685673250.142924][2626:2628] CHIP:DMG: - [1685673250.143047][2626:2628] CHIP:DMG: ], - [1685673250.143123][2626:2628] CHIP:DMG: - [1685673250.143179][2626:2628] CHIP:DMG: InteractionModelRevision = 1 - [1685673250.143233][2626:2628] CHIP:DMG: }, + [1698647125.062059][11905:11905] CHIP:DMG: InvokeRequestMessage = + [1698647125.062092][11905:11905] CHIP:DMG: { + [1698647125.062121][11905:11905] CHIP:DMG: suppressResponse = false, + [1698647125.062156][11905:11905] CHIP:DMG: timedRequest = false, + [1698647125.062187][11905:11905] CHIP:DMG: InvokeRequests = + [1698647125.062229][11905:11905] CHIP:DMG: [ + [1698647125.062260][11905:11905] CHIP:DMG: CommandDataIB = + [1698647125.062295][11905:11905] CHIP:DMG: { + [1698647125.062328][11905:11905] CHIP:DMG: CommandPathIB = + [1698647125.062373][11905:11905] CHIP:DMG: { + [1698647125.062412][11905:11905] CHIP:DMG: EndpointId = 0x1, + [1698647125.062452][11905:11905] CHIP:DMG: ClusterId = 0x101, + [1698647125.062492][11905:11905] CHIP:DMG: CommandId = 0x10, + [1698647125.062530][11905:11905] CHIP:DMG: }, + [1698647125.062570][11905:11905] CHIP:DMG: + [1698647125.062603][11905:11905] CHIP:DMG: CommandFields = + [1698647125.062642][11905:11905] CHIP:DMG: { + [1698647125.062682][11905:11905] CHIP:DMG: 0x0 = 1, + [1698647125.062723][11905:11905] CHIP:DMG: 0x1 = 1, + [1698647125.062764][11905:11905] CHIP:DMG: }, + [1698647125.062800][11905:11905] CHIP:DMG: }, + [1698647125.062839][11905:11905] CHIP:DMG: + [1698647125.062869][11905:11905] CHIP:DMG: ], + [1698647125.062909][11905:11905] CHIP:DMG: + [1698647125.062939][11905:11905] CHIP:DMG: InteractionModelRevision = 11 + [1698647125.062969][11905:11905] CHIP:DMG: }, disabled: true - label: "Step 10: DUT sends Set Holiday Day Schedule command to TH." PICS: DRLK.C.F04 && DRLK.C.C11.Tx verification: | - ./chip-tool doorlock set-holiday-schedule 1 20 30 0 1 1 --trace_decode 1 + ./chip-tool doorlock set-holiday-schedule 1 20 30 0 1 1 Verify TH receives Set Holiday Day Schedule command with SUCCESS response on TH(lock-app) log: - [1685673266.868536][2630:2632] CHIP:DMG: InvokeResponseMessage = - [1685673266.868592][2630:2632] CHIP:DMG: { - [1685673266.868645][2630:2632] CHIP:DMG: suppressResponse = false, - [1685673266.868772][2630:2632] CHIP:DMG: InvokeResponseIBs = - [1685673266.868851][2630:2632] CHIP:DMG: [ - [1685673266.868908][2630:2632] CHIP:DMG: InvokeResponseIB = - [1685673266.868985][2630:2632] CHIP:DMG: { - [1685673266.869181][2630:2632] CHIP:DMG: CommandStatusIB = - [1685673266.869255][2630:2632] CHIP:DMG: { - [1685673266.869323][2630:2632] CHIP:DMG: CommandPathIB = - [1685673266.869399][2630:2632] CHIP:DMG: { - [1685673266.869475][2630:2632] CHIP:DMG: EndpointId = 0x1, - [1685673266.869554][2630:2632] CHIP:DMG: ClusterId = 0x101, - [1685673266.869632][2630:2632] CHIP:DMG: CommandId = 0x11, - [1685673266.869708][2630:2632] CHIP:DMG: }, - [1685673266.869819][2630:2632] CHIP:DMG: - [1685673266.869887][2630:2632] CHIP:DMG: StatusIB = - [1685673266.869965][2630:2632] CHIP:DMG: { - [1685673266.870041][2630:2632] CHIP:DMG: status = 0x00 (SUCCESS), - [1685673266.870115][2630:2632] CHIP:DMG: }, - [1685673266.870190][2630:2632] CHIP:DMG: - [1685673266.870256][2630:2632] CHIP:DMG: }, - [1685673266.870332][2630:2632] CHIP:DMG: - [1685673266.870392][2630:2632] CHIP:DMG: }, - [1685673266.870463][2630:2632] CHIP:DMG: - [1685673266.870518][2630:2632] CHIP:DMG: ], - [1685673266.870589][2630:2632] CHIP:DMG: - [1685673266.870644][2630:2632] CHIP:DMG: InteractionModelRevision = 1 - [1685673266.870698][2630:2632] CHIP:DMG: }, + [1698647147.130306][11905:11905] CHIP:DMG: InvokeRequestMessage = + [1698647147.130327][11905:11905] CHIP:DMG: { + [1698647147.130345][11905:11905] CHIP:DMG: suppressResponse = false, + [1698647147.130367][11905:11905] CHIP:DMG: timedRequest = false, + [1698647147.130386][11905:11905] CHIP:DMG: InvokeRequests = + [1698647147.130412][11905:11905] CHIP:DMG: [ + [1698647147.130431][11905:11905] CHIP:DMG: CommandDataIB = + [1698647147.130453][11905:11905] CHIP:DMG: { + [1698647147.130473][11905:11905] CHIP:DMG: CommandPathIB = + [1698647147.130503][11905:11905] CHIP:DMG: { + [1698647147.130527][11905:11905] CHIP:DMG: EndpointId = 0x1, + [1698647147.130551][11905:11905] CHIP:DMG: ClusterId = 0x101, + [1698647147.130576][11905:11905] CHIP:DMG: CommandId = 0x11, + [1698647147.130598][11905:11905] CHIP:DMG: }, + [1698647147.130623][11905:11905] CHIP:DMG: + [1698647147.130644][11905:11905] CHIP:DMG: CommandFields = + [1698647147.130667][11905:11905] CHIP:DMG: { + [1698647147.130693][11905:11905] CHIP:DMG: 0x0 = 1, + [1698647147.130718][11905:11905] CHIP:DMG: 0x1 = 20, + [1698647147.130743][11905:11905] CHIP:DMG: 0x2 = 30, + [1698647147.130767][11905:11905] CHIP:DMG: 0x3 = 0, + [1698647147.130792][11905:11905] CHIP:DMG: }, + [1698647147.130813][11905:11905] CHIP:DMG: }, + [1698647147.130839][11905:11905] CHIP:DMG: + [1698647147.130858][11905:11905] CHIP:DMG: ], + [1698647147.130883][11905:11905] CHIP:DMG: + [1698647147.130902][11905:11905] CHIP:DMG: InteractionModelRevision = 11 + [1698647147.130920][11905:11905] CHIP:DMG: }, disabled: true - label: "Step 11: DUT sends Get Holiday Day Schedule command to TH." PICS: DRLK.C.F04 && DRLK.C.C12.Tx verification: | - ./chip-tool doorlock get-holiday-schedule 1 1 1 --trace_decode 1 + ./chip-tool doorlock get-holiday-schedule 1 1 1 Verify TH receives Get Holiday Day Schedule command response on TH(lock-app) log: - [1685673297.404334][2637:2639] CHIP:DMG: InvokeResponseMessage = - [1685673297.404389][2637:2639] CHIP:DMG: { - [1685673297.404442][2637:2639] CHIP:DMG: suppressResponse = false, - [1685673297.404499][2637:2639] CHIP:DMG: InvokeResponseIBs = - [1685673297.404575][2637:2639] CHIP:DMG: [ - [1685673297.404632][2637:2639] CHIP:DMG: InvokeResponseIB = - [1685673297.404716][2637:2639] CHIP:DMG: { - [1685673297.404776][2637:2639] CHIP:DMG: CommandDataIB = - [1685673297.404848][2637:2639] CHIP:DMG: { - [1685673297.404915][2637:2639] CHIP:DMG: CommandPathIB = - [1685673297.404997][2637:2639] CHIP:DMG: { - [1685673297.405075][2637:2639] CHIP:DMG: EndpointId = 0x1, - [1685673297.405155][2637:2639] CHIP:DMG: ClusterId = 0x101, - [1685673297.405233][2637:2639] CHIP:DMG: CommandId = 0x12, - [1685673297.405307][2637:2639] CHIP:DMG: }, - [1685673297.405385][2637:2639] CHIP:DMG: - [1685673297.405451][2637:2639] CHIP:DMG: CommandFields = - [1685673297.405524][2637:2639] CHIP:DMG: { - [1685673297.405602][2637:2639] CHIP:DMG: 0x0 = 1, - [1685673297.405683][2637:2639] CHIP:DMG: 0x1 = 0, - [1685673297.405803][2637:2639] CHIP:DMG: 0x2 = 20, - [1685673297.405889][2637:2639] CHIP:DMG: 0x3 = 30, - [1685673297.405970][2637:2639] CHIP:DMG: 0x4 = 0, - [1685673297.406051][2637:2639] CHIP:DMG: }, - [1685673297.406122][2637:2639] CHIP:DMG: }, - [1685673297.406202][2637:2639] CHIP:DMG: - [1685673297.406262][2637:2639] CHIP:DMG: }, - [1685673297.406336][2637:2639] CHIP:DMG: - [1685673297.406391][2637:2639] CHIP:DMG: ], - [1685673297.406467][2637:2639] CHIP:DMG: - [1685673297.406524][2637:2639] CHIP:DMG: InteractionModelRevision = 1 - [1685673297.406578][2637:2639] CHIP:DMG: }, + [1698647166.323919][11905:11905] CHIP:DMG: InvokeRequestMessage = + [1698647166.323940][11905:11905] CHIP:DMG: { + [1698647166.323958][11905:11905] CHIP:DMG: suppressResponse = false, + [1698647166.323979][11905:11905] CHIP:DMG: timedRequest = false, + [1698647166.323998][11905:11905] CHIP:DMG: InvokeRequests = + [1698647166.324022][11905:11905] CHIP:DMG: [ + [1698647166.324041][11905:11905] CHIP:DMG: CommandDataIB = + [1698647166.324064][11905:11905] CHIP:DMG: { + [1698647166.324084][11905:11905] CHIP:DMG: CommandPathIB = + [1698647166.324110][11905:11905] CHIP:DMG: { + [1698647166.324158][11905:11905] CHIP:DMG: EndpointId = 0x1, + [1698647166.324184][11905:11905] CHIP:DMG: ClusterId = 0x101, + [1698647166.324208][11905:11905] CHIP:DMG: CommandId = 0x12, + [1698647166.324231][11905:11905] CHIP:DMG: }, + [1698647166.324256][11905:11905] CHIP:DMG: + [1698647166.324277][11905:11905] CHIP:DMG: CommandFields = + [1698647166.324348][11905:11905] CHIP:DMG: { + [1698647166.324374][11905:11905] CHIP:DMG: 0x0 = 1, + [1698647166.324399][11905:11905] CHIP:DMG: }, + [1698647166.324420][11905:11905] CHIP:DMG: }, + [1698647166.324445][11905:11905] CHIP:DMG: + [1698647166.324464][11905:11905] CHIP:DMG: ], + [1698647166.324488][11905:11905] CHIP:DMG: + [1698647166.324506][11905:11905] CHIP:DMG: InteractionModelRevision = 11 + [1698647166.324525][11905:11905] CHIP:DMG: }, disabled: true - label: "Step 12: DUT sends Clear Holiday Day Schedule command to TH." PICS: DRLK.C.F04 && DRLK.C.C13.Tx verification: | - ./chip-tool doorlock clear-holiday-schedule 1 1 1 --trace_decode 1 + ./chip-tool doorlock clear-holiday-schedule 1 1 1 Verify TH receives Clear Holiday Day Schedule command with SUCCESS response on TH(lock-app) log: - [1685673314.255117][2642:2644] CHIP:DMG: InvokeResponseMessage = - [1685673314.255174][2642:2644] CHIP:DMG: { - [1685673314.255230][2642:2644] CHIP:DMG: suppressResponse = false, - [1685673314.255286][2642:2644] CHIP:DMG: InvokeResponseIBs = - [1685673314.255360][2642:2644] CHIP:DMG: [ - [1685673314.255417][2642:2644] CHIP:DMG: InvokeResponseIB = - [1685673314.255494][2642:2644] CHIP:DMG: { - [1685673314.255553][2642:2644] CHIP:DMG: CommandStatusIB = - [1685673314.255625][2642:2644] CHIP:DMG: { - [1685673314.255690][2642:2644] CHIP:DMG: CommandPathIB = - [1685673314.255765][2642:2644] CHIP:DMG: { - [1685673314.255840][2642:2644] CHIP:DMG: EndpointId = 0x1, - [1685673314.255919][2642:2644] CHIP:DMG: ClusterId = 0x101, - [1685673314.255996][2642:2644] CHIP:DMG: CommandId = 0x13, - [1685673314.256071][2642:2644] CHIP:DMG: }, - [1685673314.256154][2642:2644] CHIP:DMG: - [1685673314.256219][2642:2644] CHIP:DMG: StatusIB = - [1685673314.256293][2642:2644] CHIP:DMG: { - [1685673314.256371][2642:2644] CHIP:DMG: status = 0x00 (SUCCESS), - [1685673314.256446][2642:2644] CHIP:DMG: }, - [1685673314.256521][2642:2644] CHIP:DMG: - [1685673314.256589][2642:2644] CHIP:DMG: }, - [1685673314.256665][2642:2644] CHIP:DMG: - [1685673314.256724][2642:2644] CHIP:DMG: }, - [1685673314.256796][2642:2644] CHIP:DMG: - [1685673314.256851][2642:2644] CHIP:DMG: ], - [1685673314.256921][2642:2644] CHIP:DMG: - [1685673314.256976][2642:2644] CHIP:DMG: InteractionModelRevision = 1 - [1685673314.257030][2642:2644] CHIP:DMG: }, + [1698647186.638119][11905:11905] CHIP:DMG: InvokeRequestMessage = + [1698647186.638155][11905:11905] CHIP:DMG: { + [1698647186.638186][11905:11905] CHIP:DMG: suppressResponse = false, + [1698647186.638240][11905:11905] CHIP:DMG: timedRequest = false, + [1698647186.638275][11905:11905] CHIP:DMG: InvokeRequests = + [1698647186.638320][11905:11905] CHIP:DMG: [ + [1698647186.638355][11905:11905] CHIP:DMG: CommandDataIB = + [1698647186.638406][11905:11905] CHIP:DMG: { + [1698647186.638444][11905:11905] CHIP:DMG: CommandPathIB = + [1698647186.638498][11905:11905] CHIP:DMG: { + [1698647186.638548][11905:11905] CHIP:DMG: EndpointId = 0x1, + [1698647186.638605][11905:11905] CHIP:DMG: ClusterId = 0x101, + [1698647186.638653][11905:11905] CHIP:DMG: CommandId = 0x13, + [1698647186.638715][11905:11905] CHIP:DMG: }, + [1698647186.638761][11905:11905] CHIP:DMG: + [1698647186.638811][11905:11905] CHIP:DMG: CommandFields = + [1698647186.638852][11905:11905] CHIP:DMG: { + [1698647186.638909][11905:11905] CHIP:DMG: 0x0 = 1, + [1698647186.638953][11905:11905] CHIP:DMG: }, + [1698647186.639008][11905:11905] CHIP:DMG: }, + [1698647186.639053][11905:11905] CHIP:DMG: + [1698647186.639087][11905:11905] CHIP:DMG: ], + [1698647186.639142][11905:11905] CHIP:DMG: + [1698647186.639178][11905:11905] CHIP:DMG: InteractionModelRevision = 11 + [1698647186.639223][11905:11905] CHIP:DMG: }, disabled: true - label: "Step 13: DUT sends Set USer command to TH." PICS: DRLK.C.F08 && DRLK.C.C1a.Tx verification: | - ./chip-tool doorlock set-user 0 2 xxx 6452 1 0 0 1 1 --timedInteractionTimeoutMs 1000 --trace_decode 1 + ./chip-tool doorlock set-user 0 2 xxx 6452 1 0 0 1 1 --timedInteractionTimeoutMs 1000 Verify TH receives Set User command with SUCCESS response on TH(lock-app) log: - [1685673332.573601][2645:2647] CHIP:DMG: InvokeResponseMessage = - [1685673332.573656][2645:2647] CHIP:DMG: { - [1685673332.573709][2645:2647] CHIP:DMG: suppressResponse = false, - [1685673332.573902][2645:2647] CHIP:DMG: InvokeResponseIBs = - [1685673332.573982][2645:2647] CHIP:DMG: [ - [1685673332.574040][2645:2647] CHIP:DMG: InvokeResponseIB = - [1685673332.574116][2645:2647] CHIP:DMG: { - [1685673332.574175][2645:2647] CHIP:DMG: CommandStatusIB = - [1685673332.574245][2645:2647] CHIP:DMG: { - [1685673332.574312][2645:2647] CHIP:DMG: CommandPathIB = - [1685673332.574390][2645:2647] CHIP:DMG: { - [1685673332.574466][2645:2647] CHIP:DMG: EndpointId = 0x1, - [1685673332.574545][2645:2647] CHIP:DMG: ClusterId = 0x101, - [1685673332.574623][2645:2647] CHIP:DMG: CommandId = 0x1a, - [1685673332.574697][2645:2647] CHIP:DMG: }, - [1685673332.574780][2645:2647] CHIP:DMG: - [1685673332.574848][2645:2647] CHIP:DMG: StatusIB = - [1685673332.574922][2645:2647] CHIP:DMG: { - [1685673332.575013][2645:2647] CHIP:DMG: status = 0x00 (SUCCESS), - [1685673332.575108][2645:2647] CHIP:DMG: }, - [1685673332.575202][2645:2647] CHIP:DMG: - [1685673332.575276][2645:2647] CHIP:DMG: }, - [1685673332.575357][2645:2647] CHIP:DMG: - [1685673332.575417][2645:2647] CHIP:DMG: }, - [1685673332.575488][2645:2647] CHIP:DMG: - [1685673332.575543][2645:2647] CHIP:DMG: ], - [1685673332.575612][2645:2647] CHIP:DMG: - [1685673332.575667][2645:2647] CHIP:DMG: InteractionModelRevision = 1 - [1685673332.575721][2645:2647] CHIP:DMG: }, + [1698647215.994171][11905:11905] CHIP:DMG: InvokeRequestMessage = + [1698647215.994229][11905:11905] CHIP:DMG: { + [1698647215.994264][11905:11905] CHIP:DMG: suppressResponse = false, + [1698647215.994319][11905:11905] CHIP:DMG: timedRequest = true, + [1698647215.994358][11905:11905] CHIP:DMG: InvokeRequests = + [1698647215.994426][11905:11905] CHIP:DMG: [ + [1698647215.994466][11905:11905] CHIP:DMG: CommandDataIB = + [1698647215.994516][11905:11905] CHIP:DMG: { + [1698647215.994571][11905:11905] CHIP:DMG: CommandPathIB = + [1698647215.994617][11905:11905] CHIP:DMG: { + [1698647215.994679][11905:11905] CHIP:DMG: EndpointId = 0x1, + [1698647215.994730][11905:11905] CHIP:DMG: ClusterId = 0x101, + [1698647215.994792][11905:11905] CHIP:DMG: CommandId = 0x1a, + [1698647215.994840][11905:11905] CHIP:DMG: }, + [1698647215.994888][11905:11905] CHIP:DMG: + [1698647215.994946][11905:11905] CHIP:DMG: CommandFields = + [1698647215.994993][11905:11905] CHIP:DMG: { + [1698647215.995054][11905:11905] CHIP:DMG: 0x0 = 0, + [1698647215.995106][11905:11905] CHIP:DMG: 0x1 = 2, + [1698647215.995174][11905:11905] CHIP:DMG: 0x2 = "xxx" (3 chars), + [1698647215.995225][11905:11905] CHIP:DMG: 0x3 = 6452, + [1698647215.995290][11905:11905] CHIP:DMG: 0x4 = 1, + [1698647215.995341][11905:11905] CHIP:DMG: 0x5 = 0, + [1698647215.995406][11905:11905] CHIP:DMG: 0x6 = 0, + [1698647215.995455][11905:11905] CHIP:DMG: }, + [1698647215.995513][11905:11905] CHIP:DMG: }, + [1698647215.995566][11905:11905] CHIP:DMG: + [1698647215.995617][11905:11905] CHIP:DMG: ], + [1698647215.995670][11905:11905] CHIP:DMG: + [1698647215.995720][11905:11905] CHIP:DMG: InteractionModelRevision = 11 + [1698647215.995759][11905:11905] CHIP:DMG: }, disabled: true - label: "Step 14: DUT sends Get User to TH." PICS: DRLK.C.F08 && DRLK.C.C1b.Tx verification: | - ./chip-tool doorlock get-user 2 1 1 --timedInteractionTimeoutMs 1000 --trace_decode 1 + ./chip-tool doorlock get-user 2 1 1 --timedInteractionTimeoutMs 1000 Verify TH receives Get User command response on TH(lock-app) log: - [1685673354.071762][2648:2650] CHIP:DMG: InvokeResponseMessage = - [1685673354.071817][2648:2650] CHIP:DMG: { - [1685673354.071870][2648:2650] CHIP:DMG: suppressResponse = false, - [1685673354.071926][2648:2650] CHIP:DMG: InvokeResponseIBs = - [1685673354.072011][2648:2650] CHIP:DMG: [ - [1685673354.072068][2648:2650] CHIP:DMG: InvokeResponseIB = - [1685673354.072156][2648:2650] CHIP:DMG: { - [1685673354.072216][2648:2650] CHIP:DMG: CommandDataIB = - [1685673354.072285][2648:2650] CHIP:DMG: { - [1685673354.072352][2648:2650] CHIP:DMG: CommandPathIB = - [1685673354.072428][2648:2650] CHIP:DMG: { - [1685673354.072502][2648:2650] CHIP:DMG: EndpointId = 0x1, - [1685673354.072582][2648:2650] CHIP:DMG: ClusterId = 0x101, - [1685673354.072658][2648:2650] CHIP:DMG: CommandId = 0x1c, - [1685673354.072733][2648:2650] CHIP:DMG: }, - [1685673354.072807][2648:2650] CHIP:DMG: - [1685673354.072875][2648:2650] CHIP:DMG: CommandFields = - [1685673354.072948][2648:2650] CHIP:DMG: { - [1685673354.073024][2648:2650] CHIP:DMG: 0x0 = 2, - [1685673354.073111][2648:2650] CHIP:DMG: 0x1 = "xxx" (3 chars), - [1685673354.073299][2648:2650] CHIP:DMG: 0x2 = 6452, - [1685673354.073384][2648:2650] CHIP:DMG: 0x3 = 1, - [1685673354.073465][2648:2650] CHIP:DMG: 0x4 = 0, - [1685673354.073546][2648:2650] CHIP:DMG: 0x5 = 0, - [1685673354.073667][2648:2650] CHIP:DMG: 0x6 = [ - [1685673354.073749][2648:2650] CHIP:DMG: - [1685673354.073959][2648:2650] CHIP:DMG: ], - [1685673354.074042][2648:2650] CHIP:DMG: 0x7 = 1, - [1685673354.074121][2648:2650] CHIP:DMG: 0x8 = 1, - [1685673354.074201][2648:2650] CHIP:DMG: 0x9 = NULL - [1685673354.074281][2648:2650] CHIP:DMG: }, - [1685673354.074350][2648:2650] CHIP:DMG: }, - [1685673354.074439][2648:2650] CHIP:DMG: - [1685673354.074501][2648:2650] CHIP:DMG: }, - [1685673354.074583][2648:2650] CHIP:DMG: - [1685673354.074638][2648:2650] CHIP:DMG: ], - [1685673354.074725][2648:2650] CHIP:DMG: - [1685673354.074781][2648:2650] CHIP:DMG: InteractionModelRevision = 1 - [1685673354.074836][2648:2650] CHIP:DMG: }, + [1698647231.998669][11905:11905] CHIP:DMG: InvokeRequestMessage = + [1698647231.998703][11905:11905] CHIP:DMG: { + [1698647231.998735][11905:11905] CHIP:DMG: suppressResponse = false, + [1698647231.998772][11905:11905] CHIP:DMG: timedRequest = true, + [1698647231.998806][11905:11905] CHIP:DMG: InvokeRequests = + [1698647231.998850][11905:11905] CHIP:DMG: [ + [1698647231.998884][11905:11905] CHIP:DMG: CommandDataIB = + [1698647231.998923][11905:11905] CHIP:DMG: { + [1698647231.998959][11905:11905] CHIP:DMG: CommandPathIB = + [1698647231.999001][11905:11905] CHIP:DMG: { + [1698647231.999044][11905:11905] CHIP:DMG: EndpointId = 0x1, + [1698647231.999088][11905:11905] CHIP:DMG: ClusterId = 0x101, + [1698647231.999191][11905:11905] CHIP:DMG: CommandId = 0x1b, + [1698647231.999235][11905:11905] CHIP:DMG: }, + [1698647231.999316][11905:11905] CHIP:DMG: + [1698647231.999355][11905:11905] CHIP:DMG: CommandFields = + [1698647231.999429][11905:11905] CHIP:DMG: { + [1698647231.999475][11905:11905] CHIP:DMG: 0x0 = 2, + [1698647231.999543][11905:11905] CHIP:DMG: }, + [1698647231.999586][11905:11905] CHIP:DMG: }, + [1698647231.999653][11905:11905] CHIP:DMG: + [1698647231.999713][11905:11905] CHIP:DMG: ], + [1698647231.999759][11905:11905] CHIP:DMG: + [1698647231.999793][11905:11905] CHIP:DMG: InteractionModelRevision = 11 + [1698647231.999825][11905:11905] CHIP:DMG: }, disabled: true - label: "Step 15: DUT sends Clear User command to TH.a" PICS: DRLK.C.F08 && DRLK.C.C1d.Tx verification: | - ./chip-tool doorlock clear-user 2 1 1 --timedInteractionTimeoutMs 1000 --trace_decode 1 + ./chip-tool doorlock clear-user 2 1 1 --timedInteractionTimeoutMs 1000 Verify TH receives Clear User command with SUCCESS response on TH(lock-app) log: - [1685673377.373571][2656:2658] CHIP:DMG: InvokeResponseMessage = - [1685673377.373626][2656:2658] CHIP:DMG: { - [1685673377.373680][2656:2658] CHIP:DMG: suppressResponse = false, - [1685673377.373736][2656:2658] CHIP:DMG: InvokeResponseIBs = - [1685673377.373862][2656:2658] CHIP:DMG: [ - [1685673377.373923][2656:2658] CHIP:DMG: InvokeResponseIB = - [1685673377.374005][2656:2658] CHIP:DMG: { - [1685673377.374066][2656:2658] CHIP:DMG: CommandStatusIB = - [1685673377.374135][2656:2658] CHIP:DMG: { - [1685673377.374204][2656:2658] CHIP:DMG: CommandPathIB = - [1685673377.374279][2656:2658] CHIP:DMG: { - [1685673377.374357][2656:2658] CHIP:DMG: EndpointId = 0x1, - [1685673377.374435][2656:2658] CHIP:DMG: ClusterId = 0x101, - [1685673377.374514][2656:2658] CHIP:DMG: CommandId = 0x1d, - [1685673377.374587][2656:2658] CHIP:DMG: }, - [1685673377.374669][2656:2658] CHIP:DMG: - [1685673377.374738][2656:2658] CHIP:DMG: StatusIB = - [1685673377.374813][2656:2658] CHIP:DMG: { - [1685673377.374889][2656:2658] CHIP:DMG: status = 0x00 (SUCCESS), - [1685673377.374964][2656:2658] CHIP:DMG: }, - [1685673377.375039][2656:2658] CHIP:DMG: - [1685673377.375107][2656:2658] CHIP:DMG: }, - [1685673377.375182][2656:2658] CHIP:DMG: - [1685673377.375241][2656:2658] CHIP:DMG: }, - [1685673377.375313][2656:2658] CHIP:DMG: - [1685673377.375369][2656:2658] CHIP:DMG: ], - [1685673377.375437][2656:2658] CHIP:DMG: - [1685673377.375489][2656:2658] CHIP:DMG: InteractionModelRevision = 1 - [1685673377.375543][2656:2658] CHIP:DMG: }, + [1698647262.792533][11905:11905] CHIP:DMG: InvokeRequestMessage = + [1698647262.792569][11905:11905] CHIP:DMG: { + [1698647262.792600][11905:11905] CHIP:DMG: suppressResponse = false, + [1698647262.792637][11905:11905] CHIP:DMG: timedRequest = true, + [1698647262.792671][11905:11905] CHIP:DMG: InvokeRequests = + [1698647262.792715][11905:11905] CHIP:DMG: [ + [1698647262.792750][11905:11905] CHIP:DMG: CommandDataIB = + [1698647262.792841][11905:11905] CHIP:DMG: { + [1698647262.792917][11905:11905] CHIP:DMG: CommandPathIB = + [1698647262.792993][11905:11905] CHIP:DMG: { + [1698647262.793040][11905:11905] CHIP:DMG: EndpointId = 0x1, + [1698647262.793085][11905:11905] CHIP:DMG: ClusterId = 0x101, + [1698647262.793130][11905:11905] CHIP:DMG: CommandId = 0x1d, + [1698647262.793172][11905:11905] CHIP:DMG: }, + [1698647262.793216][11905:11905] CHIP:DMG: + [1698647262.793290][11905:11905] CHIP:DMG: CommandFields = + [1698647262.793332][11905:11905] CHIP:DMG: { + [1698647262.793401][11905:11905] CHIP:DMG: 0x0 = 2, + [1698647262.793485][11905:11905] CHIP:DMG: }, + [1698647262.793527][11905:11905] CHIP:DMG: }, + [1698647262.793569][11905:11905] CHIP:DMG: + [1698647262.793603][11905:11905] CHIP:DMG: ], + [1698647262.793679][11905:11905] CHIP:DMG: + [1698647262.793717][11905:11905] CHIP:DMG: InteractionModelRevision = 11 + [1698647262.793750][11905:11905] CHIP:DMG: }, disabled: true - label: "Step 16: DUT sends Set Credential command to TH.a" PICS: DRLK.C.F08 && DRLK.C.C22.Tx verification: | - ./chip-tool doorlock set-credential 0 '{ "credentialType" : 1 , "credentialIndex" : 1 }' 123456 1 0 0 1 1 --timedInteractionTimeoutMs 1000 --trace_decode 1 + ./chip-tool doorlock set-credential 0 '{ "credentialType" : 1 , "credentialIndex" : 1 }' 123456 1 0 0 1 1 --timedInteractionTimeoutMs 1000 Verify TH receives Set Credential command response on TH(lock-app) log: - [1685673397.369211][2660:2662] CHIP:DMG: InvokeResponseMessage = - [1685673397.369266][2660:2662] CHIP:DMG: { - [1685673397.369320][2660:2662] CHIP:DMG: suppressResponse = false, - [1685673397.369375][2660:2662] CHIP:DMG: InvokeResponseIBs = - [1685673397.369448][2660:2662] CHIP:DMG: [ - [1685673397.369504][2660:2662] CHIP:DMG: InvokeResponseIB = - [1685673397.369584][2660:2662] CHIP:DMG: { - [1685673397.369644][2660:2662] CHIP:DMG: CommandDataIB = - [1685673397.369712][2660:2662] CHIP:DMG: { - [1685673397.369829][2660:2662] CHIP:DMG: CommandPathIB = - [1685673397.369908][2660:2662] CHIP:DMG: { - [1685673397.369981][2660:2662] CHIP:DMG: EndpointId = 0x1, - [1685673397.370061][2660:2662] CHIP:DMG: ClusterId = 0x101, - [1685673397.370138][2660:2662] CHIP:DMG: CommandId = 0x23, - [1685673397.370212][2660:2662] CHIP:DMG: }, - [1685673397.370289][2660:2662] CHIP:DMG: - [1685673397.370356][2660:2662] CHIP:DMG: CommandFields = - [1685673397.370428][2660:2662] CHIP:DMG: { - [1685673397.370506][2660:2662] CHIP:DMG: 0x0 = 133, - [1685673397.370586][2660:2662] CHIP:DMG: 0x1 = NULL - [1685673397.370665][2660:2662] CHIP:DMG: 0x2 = 2, - [1685673397.370743][2660:2662] CHIP:DMG: }, - [1685673397.370812][2660:2662] CHIP:DMG: }, - [1685673397.370892][2660:2662] CHIP:DMG: - [1685673397.370951][2660:2662] CHIP:DMG: }, - [1685673397.371023][2660:2662] CHIP:DMG: - [1685673397.371078][2660:2662] CHIP:DMG: ], - [1685673397.371150][2660:2662] CHIP:DMG: - [1685673397.371208][2660:2662] CHIP:DMG: InteractionModelRevision = 1 - [1685673397.371263][2660:2662] CHIP:DMG: }, + [1698647281.453556][11905:11905] CHIP:DMG: InvokeRequestMessage = + [1698647281.453576][11905:11905] CHIP:DMG: { + [1698647281.453593][11905:11905] CHIP:DMG: suppressResponse = false, + [1698647281.453614][11905:11905] CHIP:DMG: timedRequest = true, + [1698647281.453634][11905:11905] CHIP:DMG: InvokeRequests = + [1698647281.453661][11905:11905] CHIP:DMG: [ + [1698647281.453681][11905:11905] CHIP:DMG: CommandDataIB = + [1698647281.453703][11905:11905] CHIP:DMG: { + [1698647281.453735][11905:11905] CHIP:DMG: CommandPathIB = + [1698647281.453762][11905:11905] CHIP:DMG: { + [1698647281.453791][11905:11905] CHIP:DMG: EndpointId = 0x1, + [1698647281.453822][11905:11905] CHIP:DMG: ClusterId = 0x101, + [1698647281.453851][11905:11905] CHIP:DMG: CommandId = 0x22, + [1698647281.453880][11905:11905] CHIP:DMG: }, + [1698647281.453907][11905:11905] CHIP:DMG: + [1698647281.453929][11905:11905] CHIP:DMG: CommandFields = + [1698647281.453957][11905:11905] CHIP:DMG: { + [1698647281.453987][11905:11905] CHIP:DMG: 0x0 = 0, + [1698647281.454016][11905:11905] CHIP:DMG: 0x1 = + [1698647281.454046][11905:11905] CHIP:DMG: { + [1698647281.454077][11905:11905] CHIP:DMG: 0x0 = 1, + [1698647281.454109][11905:11905] CHIP:DMG: 0x1 = 1, + [1698647281.454141][11905:11905] CHIP:DMG: }, + [1698647281.454172][11905:11905] CHIP:DMG: 0x2 = [ + [1698647281.454202][11905:11905] CHIP:DMG: 0x31, 0x32, 0x33, 0x34, 0x35, 0x36, + [1698647281.454232][11905:11905] CHIP:DMG: ] (6 bytes) + [1698647281.454263][11905:11905] CHIP:DMG: 0x3 = 1, + [1698647281.454290][11905:11905] CHIP:DMG: 0x4 = 0, + [1698647281.454320][11905:11905] CHIP:DMG: 0x5 = 0, + [1698647281.454349][11905:11905] CHIP:DMG: }, + [1698647281.454376][11905:11905] CHIP:DMG: }, + [1698647281.454403][11905:11905] CHIP:DMG: + [1698647281.454422][11905:11905] CHIP:DMG: ], + [1698647281.454448][11905:11905] CHIP:DMG: + [1698647281.454467][11905:11905] CHIP:DMG: InteractionModelRevision = 11 + [1698647281.454485][11905:11905] CHIP:DMG: }, disabled: true - label: "Step 17: DUT sends Get Credential to TH." PICS: DRLK.C.F08 && DRLK.C.C24.Tx verification: | - ./chip-tool doorlock get-credential-status '{ "credentialType" : 1 , "credentialIndex" : 1 }' 1 1 --timedInteractionTimeoutMs 1000 --trace_decode 1 + ./chip-tool doorlock get-credential-status '{ "credentialType" : 1 , "credentialIndex" : 1 }' 1 1 --timedInteractionTimeoutMs 1000 Verify TH receives Get Credential command response on TH(lock-app) log: - [1685673421.665556][2664:2666] CHIP:DMG: InvokeResponseMessage = - [1685673421.665610][2664:2666] CHIP:DMG: { - [1685673421.665662][2664:2666] CHIP:DMG: suppressResponse = false, - [1685673421.665720][2664:2666] CHIP:DMG: InvokeResponseIBs = - [1685673421.665921][2664:2666] CHIP:DMG: [ - [1685673421.665982][2664:2666] CHIP:DMG: InvokeResponseIB = - [1685673421.666061][2664:2666] CHIP:DMG: { - [1685673421.666121][2664:2666] CHIP:DMG: CommandDataIB = - [1685673421.666195][2664:2666] CHIP:DMG: { - [1685673421.666261][2664:2666] CHIP:DMG: CommandPathIB = - [1685673421.666335][2664:2666] CHIP:DMG: { - [1685673421.666411][2664:2666] CHIP:DMG: EndpointId = 0x1, - [1685673421.666490][2664:2666] CHIP:DMG: ClusterId = 0x101, - [1685673421.666652][2664:2666] CHIP:DMG: CommandId = 0x25, - [1685673421.666732][2664:2666] CHIP:DMG: }, - [1685673421.666812][2664:2666] CHIP:DMG: - [1685673421.666881][2664:2666] CHIP:DMG: CommandFields = - [1685673421.666961][2664:2666] CHIP:DMG: { - [1685673421.667041][2664:2666] CHIP:DMG: 0x0 = false, - [1685673421.667122][2664:2666] CHIP:DMG: 0x1 = NULL - [1685673421.667203][2664:2666] CHIP:DMG: 0x2 = NULL - [1685673421.667282][2664:2666] CHIP:DMG: 0x3 = NULL - [1685673421.667362][2664:2666] CHIP:DMG: 0x4 = NULL - [1685673421.667439][2664:2666] CHIP:DMG: }, - [1685673421.667509][2664:2666] CHIP:DMG: }, - [1685673421.667590][2664:2666] CHIP:DMG: - [1685673421.667722][2664:2666] CHIP:DMG: }, - [1685673421.667808][2664:2666] CHIP:DMG: - [1685673421.667865][2664:2666] CHIP:DMG: ], - [1685673421.667939][2664:2666] CHIP:DMG: - [1685673421.667995][2664:2666] CHIP:DMG: InteractionModelRevision = 1 - [1685673421.668049][2664:2666] CHIP:DMG: }, + [1698647325.882227][11905:11905] CHIP:DMG: InvokeRequestMessage = + [1698647325.882264][11905:11905] CHIP:DMG: { + [1698647325.882299][11905:11905] CHIP:DMG: suppressResponse = false, + [1698647325.882339][11905:11905] CHIP:DMG: timedRequest = true, + [1698647325.882377][11905:11905] CHIP:DMG: InvokeRequests = + [1698647325.882427][11905:11905] CHIP:DMG: [ + [1698647325.882465][11905:11905] CHIP:DMG: CommandDataIB = + [1698647325.882518][11905:11905] CHIP:DMG: { + [1698647325.882559][11905:11905] CHIP:DMG: CommandPathIB = + [1698647325.882606][11905:11905] CHIP:DMG: { + [1698647325.882656][11905:11905] CHIP:DMG: EndpointId = 0x1, + [1698647325.882706][11905:11905] CHIP:DMG: ClusterId = 0x101, + [1698647325.882754][11905:11905] CHIP:DMG: CommandId = 0x24, + [1698647325.882800][11905:11905] CHIP:DMG: }, + [1698647325.882849][11905:11905] CHIP:DMG: + [1698647325.882890][11905:11905] CHIP:DMG: CommandFields = + [1698647325.882935][11905:11905] CHIP:DMG: { + [1698647325.882981][11905:11905] CHIP:DMG: 0x0 = + [1698647325.883029][11905:11905] CHIP:DMG: { + [1698647325.883080][11905:11905] CHIP:DMG: 0x0 = 1, + [1698647325.883133][11905:11905] CHIP:DMG: 0x1 = 1, + [1698647325.883185][11905:11905] CHIP:DMG: }, + [1698647325.883232][11905:11905] CHIP:DMG: }, + [1698647325.883276][11905:11905] CHIP:DMG: }, + [1698647325.883324][11905:11905] CHIP:DMG: + [1698647325.883361][11905:11905] CHIP:DMG: ], + [1698647325.883409][11905:11905] CHIP:DMG: + [1698647325.883446][11905:11905] CHIP:DMG: InteractionModelRevision = 11 + [1698647325.883483][11905:11905] CHIP:DMG: }, disabled: true - label: "Step 18: DUT sends Clear Credential command to TH." PICS: DRLK.C.F08 && DRLK.C.C26.Tx verification: | - ./chip-tool doorlock clear-credential '{ "credentialType" : 1 , "credentialIndex" : 1 }' 1 1 --timedInteractionTimeoutMs 1000 --trace_decode 1 + ./chip-tool doorlock clear-credential '{ "credentialType" : 1 , "credentialIndex" : 1 }' 1 1 --timedInteractionTimeoutMs 1000 Verify TH receives Clear Credential command with SUCCESS response on TH(lock-app) log: - [1685673444.692000][2668:2670] CHIP:DMG: InvokeResponseMessage = - [1685673444.692055][2668:2670] CHIP:DMG: { - [1685673444.692109][2668:2670] CHIP:DMG: suppressResponse = false, - [1685673444.692164][2668:2670] CHIP:DMG: InvokeResponseIBs = - [1685673444.692235][2668:2670] CHIP:DMG: [ - [1685673444.692292][2668:2670] CHIP:DMG: InvokeResponseIB = - [1685673444.692368][2668:2670] CHIP:DMG: { - [1685673444.692429][2668:2670] CHIP:DMG: CommandStatusIB = - [1685673444.692518][2668:2670] CHIP:DMG: { - [1685673444.692597][2668:2670] CHIP:DMG: CommandPathIB = - [1685673444.692691][2668:2670] CHIP:DMG: { - [1685673444.692783][2668:2670] CHIP:DMG: EndpointId = 0x1, - [1685673444.692879][2668:2670] CHIP:DMG: ClusterId = 0x101, - [1685673444.692974][2668:2670] CHIP:DMG: CommandId = 0x26, - [1685673444.693065][2668:2670] CHIP:DMG: }, - [1685673444.693164][2668:2670] CHIP:DMG: - [1685673444.693239][2668:2670] CHIP:DMG: StatusIB = - [1685673444.693330][2668:2670] CHIP:DMG: { - [1685673444.693517][2668:2670] CHIP:DMG: status = 0x00 (SUCCESS), - [1685673444.693608][2668:2670] CHIP:DMG: }, - [1685673444.693700][2668:2670] CHIP:DMG: - [1685673444.693934][2668:2670] CHIP:DMG: }, - [1685673444.694029][2668:2670] CHIP:DMG: - [1685673444.694099][2668:2670] CHIP:DMG: }, - [1685673444.694183][2668:2670] CHIP:DMG: - [1685673444.694241][2668:2670] CHIP:DMG: ], - [1685673444.694410][2668:2670] CHIP:DMG: - [1685673444.694467][2668:2670] CHIP:DMG: InteractionModelRevision = 1 - [1685673444.694522][2668:2670] CHIP:DMG: }, - - - ./chip-tool doorlock clear-user 1 1 1 --timedInteractionTimeoutMs 1000 --trace_decode 1 + [1698647366.030707][11905:11905] CHIP:DMG: InvokeRequestMessage = + [1698647366.030759][11905:11905] CHIP:DMG: { + [1698647366.030791][11905:11905] CHIP:DMG: suppressResponse = false, + [1698647366.030828][11905:11905] CHIP:DMG: timedRequest = true, + [1698647366.030876][11905:11905] CHIP:DMG: InvokeRequests = + [1698647366.030923][11905:11905] CHIP:DMG: [ + [1698647366.030970][11905:11905] CHIP:DMG: CommandDataIB = + [1698647366.031012][11905:11905] CHIP:DMG: { + [1698647366.031063][11905:11905] CHIP:DMG: CommandPathIB = + [1698647366.031107][11905:11905] CHIP:DMG: { + [1698647366.031150][11905:11905] CHIP:DMG: EndpointId = 0x1, + [1698647366.031209][11905:11905] CHIP:DMG: ClusterId = 0x101, + [1698647366.031253][11905:11905] CHIP:DMG: CommandId = 0x26, + [1698647366.031310][11905:11905] CHIP:DMG: }, + [1698647366.031354][11905:11905] CHIP:DMG: + [1698647366.031404][11905:11905] CHIP:DMG: CommandFields = + [1698647366.031445][11905:11905] CHIP:DMG: { + [1698647366.031495][11905:11905] CHIP:DMG: 0x0 = + [1698647366.031548][11905:11905] CHIP:DMG: { + [1698647366.031608][11905:11905] CHIP:DMG: 0x0 = 1, + [1698647366.031669][11905:11905] CHIP:DMG: 0x1 = 1, + [1698647366.031729][11905:11905] CHIP:DMG: }, + [1698647366.031773][11905:11905] CHIP:DMG: }, + [1698647366.031811][11905:11905] CHIP:DMG: }, + [1698647366.031869][11905:11905] CHIP:DMG: + [1698647366.031903][11905:11905] CHIP:DMG: ], + [1698647366.031960][11905:11905] CHIP:DMG: + [1698647366.031994][11905:11905] CHIP:DMG: InteractionModelRevision = 11 + [1698647366.032040][11905:11905] CHIP:DMG: }, + disabled: true + + - label: "Step 19: DUT sends Clear User command to TH.a " + PICS: DRLK.C.F08 && DRLK.C.C1d.Tx + verification: | + ./chip-tool doorlock clear-user 1 1 1 --timedInteractionTimeoutMs 1000 Verify TH receives Clear User command with SUCCESS response on TH(lock-app) log: - [1685673467.295855][2674:2676] CHIP:DMG: InvokeResponseMessage = - [1685673467.295906][2674:2676] CHIP:DMG: { - [1685673467.295986][2674:2676] CHIP:DMG: suppressResponse = false, - [1685673467.296044][2674:2676] CHIP:DMG: InvokeResponseIBs = - [1685673467.296116][2674:2676] CHIP:DMG: [ - [1685673467.296194][2674:2676] CHIP:DMG: InvokeResponseIB = - [1685673467.296271][2674:2676] CHIP:DMG: { - [1685673467.296361][2674:2676] CHIP:DMG: CommandStatusIB = - [1685673467.296432][2674:2676] CHIP:DMG: { - [1685673467.296519][2674:2676] CHIP:DMG: CommandPathIB = - [1685673467.296595][2674:2676] CHIP:DMG: { - [1685673467.296692][2674:2676] CHIP:DMG: EndpointId = 0x1, - [1685673467.296772][2674:2676] CHIP:DMG: ClusterId = 0x101, - [1685673467.296872][2674:2676] CHIP:DMG: CommandId = 0x1d, - [1685673467.296947][2674:2676] CHIP:DMG: }, - [1685673467.297053][2674:2676] CHIP:DMG: - [1685673467.297121][2674:2676] CHIP:DMG: StatusIB = - [1685673467.297217][2674:2676] CHIP:DMG: { - [1685673467.297295][2674:2676] CHIP:DMG: status = 0x00 (SUCCESS), - [1685673467.297392][2674:2676] CHIP:DMG: }, - [1685673467.297468][2674:2676] CHIP:DMG: - [1685673467.297554][2674:2676] CHIP:DMG: }, - [1685673467.297632][2674:2676] CHIP:DMG: - [1685673467.297692][2674:2676] CHIP:DMG: }, - [1685673467.297836][2674:2676] CHIP:DMG: - [1685673467.297895][2674:2676] CHIP:DMG: ], - [1685673467.297997][2674:2676] CHIP:DMG: - [1685673467.298055][2674:2676] CHIP:DMG: InteractionModelRevision = 1 - [1685673467.298109][2674:2676] CHIP:DMG: }, + [1698647393.727713][11905:11905] CHIP:DMG: InvokeRequestMessage = + [1698647393.727764][11905:11905] CHIP:DMG: { + [1698647393.727796][11905:11905] CHIP:DMG: suppressResponse = false, + [1698647393.727833][11905:11905] CHIP:DMG: timedRequest = true, + [1698647393.727881][11905:11905] CHIP:DMG: InvokeRequests = + [1698647393.727926][11905:11905] CHIP:DMG: [ + [1698647393.727973][11905:11905] CHIP:DMG: CommandDataIB = + [1698647393.728014][11905:11905] CHIP:DMG: { + [1698647393.728061][11905:11905] CHIP:DMG: CommandPathIB = + [1698647393.728105][11905:11905] CHIP:DMG: { + [1698647393.728147][11905:11905] CHIP:DMG: EndpointId = 0x1, + [1698647393.728191][11905:11905] CHIP:DMG: ClusterId = 0x101, + [1698647393.728247][11905:11905] CHIP:DMG: CommandId = 0x1d, + [1698647393.728322][11905:11905] CHIP:DMG: }, + [1698647393.728382][11905:11905] CHIP:DMG: + [1698647393.728420][11905:11905] CHIP:DMG: CommandFields = + [1698647393.728475][11905:11905] CHIP:DMG: { + [1698647393.728520][11905:11905] CHIP:DMG: 0x0 = 1, + [1698647393.728565][11905:11905] CHIP:DMG: }, + [1698647393.728617][11905:11905] CHIP:DMG: }, + [1698647393.728659][11905:11905] CHIP:DMG: + [1698647393.728706][11905:11905] CHIP:DMG: ], + [1698647393.728749][11905:11905] CHIP:DMG: + [1698647393.728794][11905:11905] CHIP:DMG: InteractionModelRevision = 11 + [1698647393.728829][11905:11905] CHIP:DMG: }, disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_G_2_2.yaml b/src/app/tests/suites/certification/Test_TC_G_2_2.yaml index a3c8a70e81316a..9cc0cd99ce620d 100644 --- a/src/app/tests/suites/certification/Test_TC_G_2_2.yaml +++ b/src/app/tests/suites/certification/Test_TC_G_2_2.yaml @@ -304,7 +304,7 @@ tests: - label: "Step 1c: TH cleans up the groups by sending the RemoveAllGroups - command to the DUT on PIXIT.MOD.ENDPOINT" + command to the DUT on PIXIT.G.ENDPOINT" verification: | ./chip-tool groups remove-all-groups 1 0 diff --git a/src/app/tests/suites/certification/Test_TC_SWTCH_2_2.yaml b/src/app/tests/suites/certification/Test_TC_SWTCH_2_2.yaml index ffd8849ca25d08..35e48f646d470a 100644 --- a/src/app/tests/suites/certification/Test_TC_SWTCH_2_2.yaml +++ b/src/app/tests/suites/certification/Test_TC_SWTCH_2_2.yaml @@ -47,66 +47,43 @@ tests: - label: "Step 2a: Set up subscription to SwitchLatched event" PICS: SWTCH.S.F00 verification: | - On Raspi platform to trigger the event give the below command by opening an another terminal in DUT - (Below is the example command developed in all-clusters-app to generate the event, Vendor DUT should have the capability to generate this event) - - echo '{"Name":"SwitchLatched","NewPosition":1}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) - - Verify DUT generated the SwitchLachted event : - - [1687169759.564727][21941:21943] CHIP:-: Received payload: "{"Name":"SwitchLatched","NewPosition":1}" - [1687169759.565067][21941:21941] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 5f83636d - [1687169759.565099][21941:21941] CHIP:-: The latching switch is moved to a new position:1 - [1687169759.565108][21941:21941] CHIP:ZCL: SwitchServer: OnSwitchLatch - Please use Interactive mode to Verify the subscription of an event Here the command to enter interactive mode:-- - 1. ./chip-tool interactive start - 2. switch subscribe-event switch-latched 1 100 1 1 + ./chip-tool interactive start - Verify SwitchLatched event On TH(chip-tool) Log and below is the sample log provided for the raspi platform: + Set up the subscription between DUT and TH by sending the command mentioned below, and verify that the subscription is activated successfully - [1659527630.476706][4774:4779] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0000 - [1659527630.476742][4774:4779] CHIP:TOO: Event number: 4 - [1659527630.476771][4774:4779] CHIP:TOO: Priority: Info - [1659527630.476799][4774:4779] CHIP:TOO: Timestamp: 29687894 - [1659527630.476887][4774:4779] CHIP:TOO: SwitchLatched: { - [1659527630.476934][4774:4779] CHIP:TOO: NewPosition: 1 - [1659527630.476969][4774:4779] CHIP:TOO: } + switch subscribe-event switch-latched 1 100 1 1 + + [1697604266.130621][7393:7395] CHIP:DMG: SubscribeResponseMessage = + [1697604266.130624][7393:7395] CHIP:DMG: { + [1697604266.130628][7393:7395] CHIP:DMG: SubscriptionId = 0xf6d55121, + [1697604266.130632][7393:7395] CHIP:DMG: MaxInterval = 0x64, + [1697604266.130636][7393:7395] CHIP:DMG: InteractionModelRevision = 11 + [1697604266.130640][7393:7395] CHIP:DMG: } disabled: true - label: "Step 2b: Operator sets switch to first position" PICS: SWTCH.S.F00 verification: | - On Raspi platform to trigger the event give the below command by opening an another terminal in DUT + On Raspi platform to trigger the event, give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor DUT should have the capability to generate this event) echo '{"Name":"SwitchLatched","NewPosition":0}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) DUT generated the SwitchLatched event with NewPosition 0: - [1686289860.323236][30125:30127] CHIP:-: Received payload: "{"Name":"SwitchLatched","NewPosition":0}" - [1686289860.323565][30125:30125] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 89759737 - [1686289860.323602][30125:30125] CHIP:-: The latching switch is moved to a new position:0 - [1686289860.323618][30125:30125] CHIP:ZCL: SwitchServer: OnSwitchLatch - - ./chip-tool switch read-event switch-latched 1 1 - - Verify SwitchLatched event with NewPosition set to 0 on TH(Chip-tool) log and below is the sample log provided for the raspi platform: - - [1687257759.711008][17346:17348] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0000 - [1687257759.711011][17346:17348] CHIP:TOO: Event number: 5 - [1687257759.711013][17346:17348] CHIP:TOO: Priority: Info - [1687257759.711015][17346:17348] CHIP:TOO: Timestamp: 1687256995382 - [1687257759.711018][17346:17348] CHIP:TOO: SwitchLatched: { - [1687257759.711021][17346:17348] CHIP:TOO: NewPosition: 0 - [1687257759.711024][17346:17348] CHIP:TOO: } + [1697604377.953057][7384:7386] CHIP:-: Received payload: "{"Name":"SwitchLatched","NewPosition":0}" + [1697604377.955361][7384:7384] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4dbcc0a9 + [1697604377.955421][7384:7384] CHIP:-: The latching switch is moved to a new position:0 + [1697604377.955430][7384:7384] CHIP:ZCL: SwitchServer: OnSwitchLatch + [1697604377.955474][7384:7384] CHIP:EVL: LogEvent event number: 0x0000000000000006 priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x0 Epoch timestamp: 0x0000018B411B1D63 disabled: true - label: "Step 2c: Read CurrentPosition attribute" PICS: SWTCH.S.F00 verification: | - ./chip-tool switch read current-position 1 1 + switch read current-position 1 1 Verify CurrentPosition value is 0 in TH(chip-tool) Log and below is the sample log provided for the raspi platform: @@ -124,29 +101,28 @@ tests: DUT generated the SwitchLatched event with NewPosition set to 1: - [1659600080.279936][7312:7321] CHIP:-: Received payload: "{"Name":"SwitchLatched","NewPosition":1}" - [1659600080.280318][7312:7312] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 1755409c - [1659600080.280376][7312:7312] CHIP:-: The latching switch is moved to a new position:1 - [1659600080.280412][7312:7312] CHIP:ZCL: SwitchServer: OnSwitchLatch - [1659600080.280503][7312:7312] CHIP:EVL: LogEvent event number: 0x0000000000020005 priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x0 Sys timestamp: 0x0000000000EB91B3 + [1697604732.758383][7384:7386] CHIP:-: Received payload: "{"Name":"SwitchLatched","NewPosition":1}" + [1697604732.758668][7384:7384] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4dbcc0aa + [1697604732.758703][7384:7384] CHIP:-: The latching switch is moved to a new position:1 + [1697604732.758712][7384:7384] CHIP:ZCL: SwitchServer: OnSwitchLatch + [1697604732.758757][7384:7384] CHIP:EVL: LogEvent event number: 0x0000000000000007 priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x0 Epoch timestamp: 0x0000018B41208756 - ./chip-tool switch read-event switch-latched 1 1 + switch read-event switch-latched 1 1 - Verify SwitchLatched event with NewPosition set to 1 on TH(Chip-tool) log and below is the sample log provided for the raspi platform: + Verify TH receives SwitchLatched event with NewPosition set to 1 on TH(Chip-tool) log and below is the sample log provided for the raspi platform: - [1687257297.110327][17168:17170] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0000 - [1687257297.110330][17168:17170] CHIP:TOO: Event number: 7 - [1687257297.110333][17168:17170] CHIP:TOO: Priority: Info - [1687257297.110336][17168:17170] CHIP:TOO: Timestamp: 1687257190679 - [1687257297.110341][17168:17170] CHIP:TOO: SwitchLatched: { - [1687257297.110345][17168:17170] CHIP:TOO: NewPosition: 1 - [1687257297.110349][17168:17170] CHIP:TOO: } + [1687257297.110327][17168:17170] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0000 [1687257297.110330][17168:17170] CHIP:TOO: Event number: 7 + [1687257297.110333][17168:17170] CHIP:TOO: Priority: Info + [1687257297.110336][17168:17170] CHIP:TOO: Timestamp: 1687257190679 + [1687257297.110341][17168:17170] CHIP:TOO: SwitchLatched: { + [1687257297.110345][17168:17170] CHIP:TOO: NewPosition: 1 + [1687257297.110349][17168:17170] CHIP:TOO: } disabled: true - label: "Step 2e: Read CurrentPosition attribute" PICS: SWTCH.S.F00 verification: | - ./chip-tool switch read current-position 1 1 + switch read current-position 1 1 Verify CurrentPosition value is 1 in TH(chip-tool) Log and below is the sample log provided for the raspi platform: @@ -159,40 +135,45 @@ tests: sets switch to next position - Read CurrentPosition attribute" PICS: SWTCH.S.F00 verification: | - On Raspi platform to trigger the event give the below command by opening an another terminal in DUT - (Below is the example command developed in all-clusters-app to generate the event, Vendor DUT should have the capability to generate this event) + If NumberOfPositions>2, then Set switch to next position Otherwise skip this step. - echo '{"Name":"SwitchLatched","NewPosition":2}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) + For checking the number of positions that switch supports, Please read the NumberOfPositions attribute From TC-SWTCH-2.1 in step 2a . - DUT generated the SwitchLatched event with NewPosition set to 2: + switch read number-of-positions 1 1 - [1659600438.058928][7312:7321] CHIP:-: Received payload: "{"Name":"SwitchLatched","NewPosition":2}" - [1659600438.059436][7312:7312] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 1755409d - [1659600438.059519][7312:7312] CHIP:-: The latching switch is moved to a new position:2 - [1659600438.059644][7312:7312] CHIP:ZCL: SwitchServer: OnSwitchLatch - [1659600438.059857][7312:7312] CHIP:EVL: LogEvent event number: 0x0000000000020006 priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x0 Sys timestamp: 0x0000000000F10746 + Verify the "NumberOfPositions" attribute value On TH(Chip-tool) Log and below is the sample log provided for the raspi platform: - ./chip-tool switch read-event switch-latched 1 1 + [1697605547.057869][7525:7527] CHIP:DMG: } + [1697605547.058012][7525:7527] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Attribute 0x0000_0000 DataVersion: 1304215724 + [1697605547.058063][7525:7527] CHIP:TOO: NumberOfPositions: 2 - Verify SwitchLatched event with NewPosition set to 2 on TH(Chip-tool) log and below is the sample log provided for the raspi platform: - - [1687257759.711126][17346:17348] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0000 - [1687257759.711129][17346:17348] CHIP:TOO: Event number: 8 - [1687257759.711131][17346:17348] CHIP:TOO: Priority: Info - [1687257759.711133][17346:17348] CHIP:TOO: Timestamp: 1687257552953 - [1687257759.711136][17346:17348] CHIP:TOO: SwitchLatched: { - [1687257759.711140][17346:17348] CHIP:TOO: NewPosition: 2 - [1687257759.711141][17346:17348] CHIP:TOO: } - - In the current SDK development, Max number of positions is configured as 2, hence the current test step should fail as NewPosition reached more than the Max NumberOfPositions. - If the DUT supports more number of positions, then for the command in previous step, position should increase to the next level. Below is the sample command to execute, if the DUT supports NumberOfPositions > 2 . + On Raspi platform to trigger the event give the below command by opening an another terminal in DUT + (Below is the example command developed in all-clusters-app to generate the event, Vendor DUT should have the capability to generate this event) - ./chip-tool switch read current-position 1 1 + echo '{"Name":"SwitchLatched","NewPosition":2}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) - Verify CurrentPosition value is 2 On TH(chip-tool) Log and below is the sample log provided for the raspi platform: + DUT generated the SwitchLatched event with NewPosition set to 2: - [1659600502.023560][4306:4311] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Attribute 0x0000_0001 DataVersion: 391463069 - [1687847841.651568][19369:19371] CHIP:TOO: CurrentPosition: 2 + [1697615458.515582][7384:7386] CHIP:-: Received payload: "{"Name":"SwitchLatched","NewPosition":2}" + [1697615458.515822][7384:7384] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4dbcc0c5 + [1697615458.515854][7384:7384] CHIP:-: The latching switch is moved to a new position:3 + [1697615458.515867][7384:7384] CHIP:ZCL: SwitchServer: OnSwitchLatch + [1697615458.516014][7384:7384] CHIP:EVL: Dropped 1 event from buffer with priority 1 and event number 0x000000000000000B due to overflow: event priority_level: 1 + [1697615458.516081][7384:7384] CHIP:EVL: Copy Event to next buffer with priority 1 + [1697615458.516110][7384:7384] CHIP:EVL: LogEvent event number: 0x0000000000000024 priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x0 Epoch timestamp: 0x0000018B41C430D3 + + switch read-event switch-latched 1 1 + + Verify TH receives SwitchLatched event with NewPosition set to 3 on TH(Chip-tool) log and below is the sample log provided for the raspi platform: + + [1697615514.717194][7767:7769] CHIP:DMG: } + [1697615514.717359][7767:7769] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0000 + [1697615514.717371][7767:7769] CHIP:TOO: Event number: 36 + [1697615514.717383][7767:7769] CHIP:TOO: Priority: Info + [1697615514.717396][7767:7769] CHIP:TOO: Timestamp: 1697615458515 + [1697615514.717430][7767:7769] CHIP:TOO: SwitchLatched: { + [1697615514.717449][7767:7769] CHIP:TOO: NewPosition: 2 + [1697615514.717464][7767:7769] CHIP:TOO: } disabled: true - label: @@ -201,6 +182,18 @@ tests: next position, - Read CurrentPosition attribute" PICS: SWTCH.S.F00 verification: | + If NumberOfPositions>3, then Set the switch to next position Otherwise skip this step. + + For checking the number of positions that switch supports, Please read the NumberOfPositions attribute From TC-SWTCH-2.1 in step 2a . + + switch read number-of-positions 1 1 + + Verify the "NumberOfPositions" attribute value On TH(Chip-tool) Log and below is the sample log provided for the raspi platform: + + [1697605547.057869][7525:7527] CHIP:DMG: } + [1697605547.058012][7525:7527] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Attribute 0x0000_0000 DataVersion: 1304215724 + [1697605547.058063][7525:7527] CHIP:TOO: NumberOfPositions: 2 + In Raspi platform to change the switch to third position use the below sample command, its required to use equivalent command on the respective DUT. Open one more terminal on DUT side to execute the echo command . echo '{"Name":"SwitchLatched","NewPosition":3}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) @@ -213,7 +206,7 @@ tests: [1659600438.059644][7312:7312] CHIP:ZCL: SwitchServer: OnSwitchLatch [1659600438.059857][7312:7312] CHIP:EVL: LogEvent event number: 0x0000000000020006 priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x0 Sys timestamp: 0x0000000000F10746 - ./chip-tool switch read-event switch-latched 1 1 + switch read-event switch-latched 1 1 Verify SwitchLatched event with NewPosition set to 3 on TH(Chip-tool) log and below is the sample log provided for the raspi platform: @@ -224,15 +217,6 @@ tests: [1687258513.235235][17561:17563] CHIP:TOO: SwitchLatched: { [1687258513.235238][17561:17563] CHIP:TOO: NewPosition: 3 [1687258513.235239][17561:17563] CHIP:TOO: } - - In the current SDK development, Max number of positions are configured as 2, hence the current test step should fail as its reached more than the numberof position. If the DUT supports more number of positions, then for the above command, it should increase to the next level. Below is the sample command to execute , if the DUT supports more than 2 NumberOfPositions. - - ./chip-tool switch read current-position 1 1 - - Verify CurrentPosition value is 3 On TH(chip-tool) Log and below is the sample log provided for the raspi platform and below is the sample log provided for the raspi platform: - - [1659600502.023560][4306:4311] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Attribute 0x0000_0001 DataVersion: 391463069 - [1687847873.385882][19378:19380] CHIP:TOO: CurrentPosition: 3 disabled: true - label: "Step 2h: Operator returns switch to first position" @@ -244,28 +228,30 @@ tests: DUT generated the SwitchLatched event with NewPosition set to 0: - [1659599703.232994][7312:7321] CHIP:-: Received payload: "{"Name":"SwitchLatched","NewPosition":0}" - [1659599703.233543][7312:7312] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 1755409b - [1659599703.233624][7312:7312] CHIP:-: The latching switch is moved to a new position:0 - [1659599703.233682][7312:7312] CHIP:ZCL: SwitchServer: OnSwitchLatch + [1697606147.106734][7384:7386] CHIP:-: Received payload: "{"Name":"SwitchLatched","NewPosition":0}" + [1697606147.106976][7384:7384] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4dbcc0ae + [1697606147.107012][7384:7384] CHIP:-: The latching switch is moved to a new position:0 + [1697606147.107023][7384:7384] CHIP:ZCL: SwitchServer: OnSwitchLatch + [1697606147.107137][7384:7384] CHIP:EVL: Copy Event to next buffer with priority 1 + [1697606147.107170][7384:7384] CHIP:EVL: LogEvent event number: 0x000000000000000B priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x0 Epoch timestamp: 0x0000018B41361C23 - ./chip-tool switch read-event switch-latched 1 1 + switch read-event switch-latched 1 1 - Verify SwitchLatched event with NewPosition set to 0 on TH(Chip-tool) log and below is the sample log provided for the raspi platform: + Verify TH receives SwitchLatched event with NewPosition set to 0 on TH(Chip-tool) log and below is the sample log provided for the raspi platform: - [1687258655.138839][17617:17619] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0000 - [1687258655.138841][17617:17619] CHIP:TOO: Event number: 10 - [1687258655.138844][17617:17619] CHIP:TOO: Priority: Info - [1687258655.138846][17617:17619] CHIP:TOO: Timestamp: 1687258651896 - [1687258655.138849][17617:17619] CHIP:TOO: SwitchLatched: { - [1687258655.138851][17617:17619] CHIP:TOO: NewPosition: 0 - [1687258655.138853][17617:17619] CHIP:TOO: } + [1697606183.274301][7536:7538] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0000 + [1697606183.274313][7536:7538] CHIP:TOO: Event number: 11 + [1697606183.274320][7536:7538] CHIP:TOO: Priority: Info + [1697606183.274325][7536:7538] CHIP:TOO: Timestamp: 1697606147107 + [1697606183.274350][7536:7538] CHIP:TOO: SwitchLatched: { + [1697606183.274362][7536:7538] CHIP:TOO: NewPosition: 0 + [1697606183.274373][7536:7538] CHIP:TOO: } disabled: true - label: "Step 2i: Read CurrentPosition attribute" PICS: SWTCH.S.F00 verification: | - ./chip-tool switch read current-position 1 1 + switch read current-position 1 1 Verify CurrentPosition value is 0 On TH(chip-tool) Log and below is the sample log provided for the raspi platform: @@ -278,33 +264,20 @@ tests: verification: | Note : Please skip this step if LATCH SWITCH feature is implemented, because a device can support either a latching switch or a momentary switch. - On Raspi platform to trigger the event give the below command by opening an another terminal in DUT - (Below is the example command developed in all-clusters-app to generate the event, Vendor DUT should have the capability to generate this event) - - echo '{"Name":"InitialPress","NewPosition":0}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) - - DUT generated the InitialPress event with NewPosition set to 0: - - [1659612230.311864][7312:7321] CHIP:-: Received payload: "{"Name":"InitialPress","NewPosition":0}" - [1659612230.312345][7312:7312] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 175540a4 - [1659612230.312422][7312:7312] CHIP:-: The new position when the momentary switch starts to be pressed:0 - [1659612230.312472][7312:7312] CHIP:ZCL: SwitchServer: OnInitialPress - - Please use Interactive mode to Verify the subscription of an event Here the command to enter interactive mode:-- - 1. ./chip-tool interactive start - 2. switch subscribe-event initial-press 1 100 1 1 + ./chip-tool interactive start + + Set up the subscription between DUT and TH by sending the command mentioned below, and verify that the subscription is activated successfully - Verify InitialPress event with NewPosition set to 0 On TH(chip-tool) Log and below is the sample log provided for the raspi platform: + switch subscribe-event initial-press 1 100 1 1 - [1659612272.121119][4957:4962] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0001 - [1659612272.121143][4957:4962] CHIP:TOO: Event number: 131085 - [1659612272.121164][4957:4962] CHIP:TOO: Priority: Info - [1659612272.121186][4957:4962] CHIP:TOO: Timestamp: 27588291 - [1659612272.121313][4957:4962] CHIP:TOO: InitialPress: { - [1659612272.121347][4957:4962] CHIP:TOO: NewPosition: 0 - [1659612272.121369][4957:4962] CHIP:TOO: } + [1697606330.206997][7536:7538] CHIP:DMG: SubscribeResponseMessage = + [1697606330.207001][7536:7538] CHIP:DMG: { + [1697606330.207004][7536:7538] CHIP:DMG: SubscriptionId = 0x460ae381, + [1697606330.207008][7536:7538] CHIP:DMG: MaxInterval = 0x64, + [1697606330.207011][7536:7538] CHIP:DMG: InteractionModelRevision = 11 + [1697606330.207014][7536:7538] CHIP:DMG: } disabled: true - label: "Step 3b: Operator does not operate switch" @@ -316,7 +289,7 @@ tests: - label: "Step 3c: Read CurrentPosition attribute" PICS: SWTCH.S.F01 verification: | - ./chip-tool switch read current-position 1 1 + switch read current-position 1 1 Verify CurrentPosition value is 0 On TH (chip-tool) Log and below is the sample log provided for the raspi platform: @@ -336,17 +309,30 @@ tests: DUT generated the InitialPress event with NewPosition set to 1: - [1659612460.072098][7312:7321] CHIP:-: Received payload: "{"Name":"InitialPress","NewPosition":1}" - [1659612460.072562][7312:7312] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 175540a5 - [1659612460.072646][7312:7312] CHIP:-: The new position when the momentary switch starts to be pressed:1 - [1659612460.072706][7312:7312] CHIP:ZCL: SwitchServer: OnInitialPress - [1659612460.073008][7312:7312] CHIP:EVL: Copy Event to next buffer with priority 1 + [1697606594.815345][7384:7386] CHIP:-: Received payload: "{"Name":"InitialPress","NewPosition":1}" + [1697606594.815586][7384:7384] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4dbcc0af + [1697606594.815620][7384:7384] CHIP:-: The new position when the momentary switch starts to be pressed:1 + [1697606594.815631][7384:7384] CHIP:ZCL: SwitchServer: OnInitialPress + [1697606594.815743][7384:7384] CHIP:EVL: Copy Event to next buffer with priority 1 + [1697606594.815773][7384:7384] CHIP:EVL: LogEvent event number: 0x000000000000000C priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x1 Epoch timestamp: 0x0000018B413CF0FF + + switch read-event initial-press 1 1 + + Verify TH receives InitialPress event with NewPosition set to 1 on TH(Chip-tool) log and below is the sample log provided for the raspi platform: + + [1697606630.390750][7536:7538] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0001 + [1697606630.390763][7536:7538] CHIP:TOO: Event number: 12 + [1697606630.390771][7536:7538] CHIP:TOO: Priority: Info + [1697606630.390780][7536:7538] CHIP:TOO: Timestamp: 1697606594815 + [1697606630.390822][7536:7538] CHIP:TOO: InitialPress: { + [1697606630.390840][7536:7538] CHIP:TOO: NewPosition: 1 + [1697606630.390851][7536:7538] CHIP:TOO: } disabled: true - label: "Step 3e: Read CurrentPosition attribute" PICS: SWTCH.S.F01 verification: | - ./chip-tool switch read current-position 1 1 + switch read current-position 1 1 Verify CurrentPosition value is 1 On TH(chip-tool) Log and below is the sample log provided for the raspi platform: @@ -364,19 +350,20 @@ tests: echo '{"Name":"ShortRelease","PreviousPosition":1}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) - Verify ShortRelease event with PreviousPosition set to 1 on DUT(all-cluster-app) log and below is the sample log provided for the raspi platform: + DUT generated the ShortRelease event with PreviousPosition set to 1: - [1669874154.289653][2239:2241] CHIP:-: Received payload: "{"Name":"ShortRelease","PreviousPosition":1}" - [1669874154.290189][2239:2239] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 2c2733fa - [1669874154.290274][2239:2239] CHIP:-: The the previous value of the CurrentPosition when the momentary switch has been released:1 - [1669874154.290329][2239:2239] CHIP:ZCL: SwitchServer: OnShortRelease - [1669874154.290460][2239:2239] CHIP:EVL: LogEvent event number: 0x000000000000000C priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x3 Sys timestamp: 0x00000000004B0B8D + [1697606778.141141][7384:7386] CHIP:-: Received payload: "{"Name":"ShortRelease","PreviousPosition":1}" + [1697606778.141356][7384:7384] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4dbcc0b0 + [1697606778.141394][7384:7384] CHIP:-: The the previous value of the CurrentPosition when the momentary switch has been released:1 + [1697606778.141410][7384:7384] CHIP:ZCL: SwitchServer: OnShortRelease + [1697606778.141548][7384:7384] CHIP:EVL: Copy Event to next buffer with priority 1 + [1697606778.141592][7384:7384] CHIP:EVL: LogEvent event number: 0x000000000000000D priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x3 Epoch timestamp: 0x0000018B413FBD1D disabled: true - label: "Step 3g: Read CurrentPosition attribute" PICS: SWTCH.S.F01 verification: | - ./chip-tool switch read current-position 1 1 + switch read current-position 1 1 Verify CurrentPosition value is 0 On TH(chip-tool) Log and below is the sample log provided for the raspi platform: @@ -390,29 +377,31 @@ tests: verification: | Note : Please skip this step if LATCH SWITCH feature is implemented, because a device can support either a latching switch or a momentary switch. - On Raspi platform to trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor DUT should have capability to generate this event) - - Verify InitialPress and ShortRelease events has been subscribed: - - echo '{"Name":"InitialPress","NewPosition":1}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) + Please use Interactive mode to Verify the subscription of an event + Here the command to enter interactive mode:-- + 1. ./chip-tool interactive start - Verify InitialPress event with NewPosition set to 1 on DUT(all-cluster-app) log and below is the sample log provided for the raspi platform: + Set up the subscription between DUT and TH by sending the command mentioned below, and verify that the subscription is activated successfully - [1659686596.526276][2530:2538] CHIP:-: Received payload: "{"Name":"InitialPress","NewPosition":1}" - [1659686596.526734][2530:2530] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to ee5e771a - [1659686596.526820][2530:2530] CHIP:-: The new position when the momentary switch starts to be pressed:1 - [1659686596.526881][2530:2530] CHIP:ZCL: SwitchServer: OnInitialPress + switch subscribe-event initial-press 1 100 1 1 - On Raspi platform to trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor DUT should have capability to generate this event) + [1697607013.770976][7736:7738] CHIP:DMG: SubscribeResponseMessage = + [1697607013.770988][7736:7738] CHIP:DMG: { + [1697607013.770998][7736:7738] CHIP:DMG: SubscriptionId = 0xfba47d40, + [1697607013.771010][7736:7738] CHIP:DMG: MaxInterval = 0x64, + [1697607013.771021][7736:7738] CHIP:DMG: InteractionModelRevision = 11 + [1697607013.771030][7736:7738] CHIP:DMG: } - echo '{"Name":"ShortRelease","PreviousPosition":1}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) + Set up the subscription between DUT and TH by sending the command mentioned below, and verify that the subscription is activated successfully - Verify ShortRelease event with PreviousPosition set to 1 on DUT(all-cluster-app) log and below is the sample log provided for the raspi platform: + switch subscribe-event short-release 1 100 1 1 - [1659686852.011134][2530:2538] CHIP:-: Received payload: "{"Name":"ShortRelease","PreviousPosition":1}" - [1659686852.011424][2530:2530] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to ee5e771b - [1659686852.011466][2530:2530] CHIP:-: The the previous value of the CurrentPosition when the momentary switch has been released:1 - [1659686852.011490][2530:2530] CHIP:ZCL: SwitchServer: OnShortRelease + [1697607082.641213][7736:7738] CHIP:DMG: SubscribeResponseMessage = + [1697607082.641216][7736:7738] CHIP:DMG: { + [1697607082.641221][7736:7738] CHIP:DMG: SubscriptionId = 0xbe6a8e5d, + [1697607082.641225][7736:7738] CHIP:DMG: MaxInterval = 0x64, + [1697607082.641229][7736:7738] CHIP:DMG: InteractionModelRevision = 11 + [1697607082.641233][7736:7738] CHIP:DMG: } disabled: true - label: "Step 4b: Operator does not operate switch" @@ -426,21 +415,31 @@ tests: verification: | Note : Please skip this step if LATCH SWITCH feature is implemented, because a device can support either a latching switch or a momentary switch. - Please use Interactive mode to Verify the subscription of an event - Here the command to enter interactive mode:-- + On Raspi platform To trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor Dut should have capability to generate this event) - 1. ./chip-tool interactive start - 2. switch subscribe-event initial-press 1 100 1 1 - Verify InitialPress event with NewPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: + echo '{"Name":"InitialPress","NewPosition":1}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) + + DUT generated the InitialPress event with NewPosition set to 1: - [1659686631.947247][3045:3050] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0001 - [1659686631.947272][3045:3050] CHIP:TOO: Event number: 23 - [1659686631.947296][3045:3050] CHIP:TOO: Priority: Info - [1659686631.947320][3045:3050] CHIP:TOO: Timestamp: 9048822 - [1659686631.947348][3045:3050] CHIP:TOO: InitialPress: { - [1659686631.947374][3045:3050] CHIP:TOO: NewPosition: 1 - [1659686631.947397][3045:3050] CHIP:TOO: } + [1697607350.058984][7384:7386] CHIP:-: Received payload: "{"Name":"InitialPress","NewPosition":1}" + [1697607350.059268][7384:7384] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4dbcc0b2 + [1697607350.059302][7384:7384] CHIP:-: The new position when the momentary switch starts to be pressed:1 + [1697607350.059311][7384:7384] CHIP:ZCL: SwitchServer: OnInitialPress + [1697607350.059431][7384:7384] CHIP:EVL: Copy Event to next buffer with priority 1 + [1697607350.059466][7384:7384] CHIP:EVL: LogEvent event number: 0x000000000000000F priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x1 Epoch timestamp: 0x0000018B4148772B + + switch read-event initial-press 1 1 + + Verify TH receive InitialPress event with NewPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: + + [1697607828.913031][7767:7769] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0001 + [1697607828.913034][7767:7769] CHIP:TOO: Event number: 17 + [1697607828.913037][7767:7769] CHIP:TOO: Priority: Info + [1697607828.913040][7767:7769] CHIP:TOO: Timestamp: 1697607697125 + [1697607828.913046][7767:7769] CHIP:TOO: InitialPress: { + [1697607828.913050][7767:7769] CHIP:TOO: NewPosition: 1 + [1697607828.913054][7767:7769] CHIP:TOO: } disabled: true - label: "Step 4d: Operator releases switch" @@ -448,21 +447,30 @@ tests: verification: | Note : Please skip this step if LATCH SWITCH feature is implemented, because a device can support either a latching switch or a momentary switch. - Please use Interactive mode to Verify the subscription of an event - Here the command to enter interactive mode:-- + On Raspi platform To trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor Dut should have capability to generate this event) - 1. ./chip-tool interactive start - 2. switch subscribe-event short-release 1 100 1 1 --keepSubscriptions true + echo '{"Name":"ShortRelease","PreviousPosition":1}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) + + DUT generated the ShortRelease event with PreviousPosition set to 1: + + [1697607957.484361][7384:7386] CHIP:-: Received payload: "{"Name":"ShortRelease","PreviousPosition":1}" + [1697607957.484562][7384:7384] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4dbcc0b6 + [1697607957.484610][7384:7384] CHIP:-: The the previous value of the CurrentPosition when the momentary switch has been released:1 + [1697607957.484622][7384:7384] CHIP:ZCL: SwitchServer: OnShortRelease + [1697607957.484732][7384:7384] CHIP:EVL: Copy Event to next buffer with priority 1 + [1697607957.484765][7384:7384] CHIP:EVL: LogEvent event number: 0x0000000000000013 priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x3 Epoch timestamp: 0x0000018B4151BBEC - Verify ShortRelease event with PreviousPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: + switch read-event short-release 1 1 - [1659686907.770389][3061:3066] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0003 - [1659686907.770413][3061:3066] CHIP:TOO: Event number: 24 - [1659686907.770434][3061:3066] CHIP:TOO: Priority: Info - [1659686907.770456][3061:3066] CHIP:TOO: Timestamp: 9304307 - [1659686907.770482][3061:3066] CHIP:TOO: ShortRelease: { - [1659686907.770506][3061:3066] CHIP:TOO: PreviousPosition: 1 - [1659686907.770528][3061:3066] CHIP:TOO: } + Verify TH receive ShortRelease event with PreviousPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: + + [1697608045.926586][7767:7769] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0003 + [1697608045.926590][7767:7769] CHIP:TOO: Event number: 19 + [1697608045.926593][7767:7769] CHIP:TOO: Priority: Info + [1697608045.926596][7767:7769] CHIP:TOO: Timestamp: 1697607957484 + [1697608045.926601][7767:7769] CHIP:TOO: ShortRelease: { + [1697608045.926605][7767:7769] CHIP:TOO: PreviousPosition: 1 + [1697608045.926608][7767:7769] CHIP:TOO: } disabled: true - label: @@ -476,28 +484,26 @@ tests: echo '{"Name":"InitialPress","NewPosition":1}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) - Verify InitialPress event with NewPosition set to 1 on DUT(all-cluster-app) log and below is the sample log provided for the raspi platform: - - [1659686596.526276][2530:2538] CHIP:-: Received payload: "{"Name":"InitialPress","NewPosition":1}" - [1659686596.526734][2530:2530] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to ee5e771a - [1659686596.526820][2530:2530] CHIP:-: The new position when the momentary switch starts to be pressed:1 - [1659686596.526881][2530:2530] CHIP:ZCL: SwitchServer: OnInitialPress + DUT generated the InitialPress event with NewPosition set to 1: - Please use Interactive mode to Verify the subscription of an event - Here the command to enter interactive mode:-- + [1697608104.080281][7384:7386] CHIP:-: Received payload: "{"Name":"InitialPress","NewPosition":1}" + [1697608104.080508][7384:7384] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4dbcc0b7 + [1697608104.080548][7384:7384] CHIP:-: The new position when the momentary switch starts to be pressed:1 + [1697608104.080561][7384:7384] CHIP:ZCL: SwitchServer: OnInitialPress + [1697608104.080675][7384:7384] CHIP:EVL: Copy Event to next buffer with priority 1 + [1697608104.080709][7384:7384] CHIP:EVL: LogEvent event number: 0x0000000000000014 priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x1 Epoch timestamp: 0x0000018B4153F890 - 1. ./chip-tool interactive start - 2. switch subscribe-event initial-press 1 100 1 1 + switch read-event initial-press 1 1 Verify InitialPress event with NewPosition set to 1 on TH (chip-tool) log and below is the sample log provided for the raspi platform: - [1659692069.006090][3668:3674] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0001 - [1659692069.006114][3668:3674] CHIP:TOO: Event number: 26 - [1659692069.006138][3668:3674] CHIP:TOO: Priority: Info - [1659692069.006160][3668:3674] CHIP:TOO: Timestamp: 14513708 - [1659692069.006187][3668:3674] CHIP:TOO: InitialPress: { - [1659692069.006211][3668:3674] CHIP:TOO: NewPosition: 1 - [1659692069.006233][3668:3674] CHIP:TOO: } + [1697608164.378204][7767:7769] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0001 + [1697608164.378207][7767:7769] CHIP:TOO: Event number: 20 + [1697608164.378209][7767:7769] CHIP:TOO: Priority: Info + [1697608164.378211][7767:7769] CHIP:TOO: Timestamp: 1697608104080 + [1697608164.378214][7767:7769] CHIP:TOO: InitialPress: { + [1697608164.378217][7767:7769] CHIP:TOO: NewPosition: 1 + [1697608164.378219][7767:7769] CHIP:TOO: } disabled: true - label: "Step 4f: Operator releases switch" @@ -509,28 +515,26 @@ tests: echo '{"Name":"ShortRelease","PreviousPosition":1}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) - Verify ShortRelease event with PreviousPosition set to 1 on DUT(all-cluster-app) log and below is the sample log provided for the raspi platform: - - [1659686852.011134][2530:2538] CHIP:-: Received payload: "{"Name":"ShortRelease","PreviousPosition":1}" - [1659686852.011424][2530:2530] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to ee5e771b - [1659686852.011466][2530:2530] CHIP:-: The the previous value of the CurrentPosition when the momentary switch has been released:1 - [1659686852.011490][2530:2530] CHIP:ZCL: SwitchServer: OnShortRelease + DUT generated the ShortRelease event with PreviousPosition set to 1: - Please use Interactive mode to Verify the subscription of an event - Here the command to enter interactive mode:-- + [1697608242.275996][7384:7386] CHIP:-: Received payload: "{"Name":"ShortRelease","PreviousPosition":1}" + [1697608242.276246][7384:7384] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4dbcc0b8 + [1697608242.276280][7384:7384] CHIP:-: The the previous value of the CurrentPosition when the momentary switch has been released:1 + [1697608242.276296][7384:7384] CHIP:ZCL: SwitchServer: OnShortRelease + [1697608242.276424][7384:7384] CHIP:EVL: Copy Event to next buffer with priority 1 + [1697608242.276468][7384:7384] CHIP:EVL: LogEvent event number: 0x0000000000000015 priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x3 Epoch timestamp: 0x0000018B41561464 - 1. ./chip-tool interactive start - 2. switch subscribe-event short-release 1 100 1 1 + switch read-event short-release 1 1 - Verify ShortRelease event with PreviousPosition set to 1 on TH (chip-tool) log and below is the sample log provided for the raspi platform: + Verify TH receives ShortRelease event with PreviousPosition set to 1 on TH (chip-tool) log and below is the sample log provided for the raspi platform: - [1659692123.069593][3675:3680] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0003 - [1659692123.069616][3675:3680] CHIP:TOO: Event number: 27 - [1659692123.069639][3675:3680] CHIP:TOO: Priority: Info - [1659692123.069660][3675:3680] CHIP:TOO: Timestamp: 14562409 - [1659692123.069687][3675:3680] CHIP:TOO: ShortRelease: { - [1659692123.069711][3675:3680] CHIP:TOO: PreviousPosition: 1 - [1659692123.069734][3675:3680] CHIP:TOO: } + [1697608382.457912][7767:7769] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0003 + [1697608382.457915][7767:7769] CHIP:TOO: Event number: 21 + [1697608382.457917][7767:7769] CHIP:TOO: Priority: Info + [1697608382.457919][7767:7769] CHIP:TOO: Timestamp: 1697608242276 + [1697608382.457923][7767:7769] CHIP:TOO: ShortRelease: { + [1697608382.457927][7767:7769] CHIP:TOO: PreviousPosition: 1 + [1697608382.457929][7767:7769] CHIP:TOO: } disabled: true - label: @@ -540,49 +544,54 @@ tests: verification: | Note : Please skip this step if LATCH SWITCH feature is implemented, because a device can support either a latching switch or a momentary switch. - On Raspi platform to trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor DUT should have capability to generate this event) - - echo '{"Name":"InitialPress","NewPosition":1}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) - - Verify InitialPress event with NewPosition set to 1 on DUT(all-cluster-app) log and below is the sample log provided for the raspi platform: + Please use Interactive mode to Verify the subscription of an event + Here the command to enter interactive mode:-- + ./chip-tool interactive start - [1659693098.031462][2530:2538] CHIP:-: Received payload: "{"Name":"InitialPress","NewPosition":1}" - [1659693098.031812][2530:2530] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to ee5e7724 - [1659693098.031859][2530:2530] CHIP:-: The new position when the momentary switch starts to be pressed:1 - [1659693098.031888][2530:2530] CHIP:ZCL: SwitchServer: OnInitialPress + Set up the subscription between DUT and TH by sending the command mentioned below, and verify that the subscription is activated successfully - On Raspi platform to trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor DUT should have capability to generate this event) + switch subscribe-event initial-press 1 100 1 1 - echo '{"Name":"LongPress","NewPosition":1}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) - Verify LongPress event with NewPosition set to 1 on DUT(all-cluster-app) log and below is the sample log provided for the raspi platform: + [1697608480.015747][7767:7769] CHIP:DMG: SubscribeResponseMessage = + [1697608480.015750][7767:7769] CHIP:DMG: { + [1697608480.015753][7767:7769] CHIP:DMG: SubscriptionId = 0x9c490538, + [1697608480.015756][7767:7769] CHIP:DMG: MaxInterval = 0x64, + [1697608480.015758][7767:7769] CHIP:DMG: InteractionModelRevision = 11 + [1697608480.015761][7767:7769] CHIP:DMG: } - 1659693130.924755][2530:2538] CHIP:-: Received payload: "{"Name":"LongPress","NewPosition":1}" - [1659693130.925030][2530:2530] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to ee5e7725 - [1659693130.925064][2530:2530] CHIP:-: The new position when the momentary switch has been pressed for a long time:1 - [1659693130.925313][2530:2530] CHIP:ZCL: SwitchServer: OnLongPress + Set up the subscription between DUT and TH by sending the command mentioned below, and verify that the subscription is activated successfully - On Raspi platform to trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor DUT should have capability to generate this event) + switch subscribe-event long-press 1 100 1 1 - echo '{"Name":"ShortRelease","PreviousPosition":1}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) + [1697608527.530605][7767:7769] CHIP:DMG: SubscribeResponseMessage = + [1697608527.530609][7767:7769] CHIP:DMG: { + [1697608527.530613][7767:7769] CHIP:DMG: SubscriptionId = 0xaa07867b, + [1697608527.530619][7767:7769] CHIP:DMG: MaxInterval = 0x64, + [1697608527.530623][7767:7769] CHIP:DMG: InteractionModelRevision = 11 + [1697608527.530628][7767:7769] CHIP:DMG: } - Verify ShortRelease event with PreviousPosition set to 1 on DUT(all-cluster-app) log and below is the sample log provided for the raspi platform: + Set up the subscription between DUT and TH by sending the command mentioned below, and verify that the subscription is activated successfully - [1659693174.708920][2530:2538] CHIP:-: Received payload: "{"Name":"ShortRelease","PreviousPosition":1}" - [1659693174.709388][2530:2530] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to ee5e7726 - [1659693174.709479][2530:2530] CHIP:-: The the previous value of the CurrentPosition when the momentary switch has been released:1 - [1659693174.709539][2530:2530] CHIP:ZCL: SwitchServer: OnShortRelease + switch subscribe-event short-release 1 100 1 1 - On Raspi platform to trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor DUT should have capability to generate this event) + [1697608580.243388][7767:7769] CHIP:DMG: SubscribeResponseMessage = + [1697608580.243391][7767:7769] CHIP:DMG: { + [1697608580.243394][7767:7769] CHIP:DMG: SubscriptionId = 0x9b71447a, + [1697608580.243397][7767:7769] CHIP:DMG: MaxInterval = 0x64, + [1697608580.243400][7767:7769] CHIP:DMG: InteractionModelRevision = 11 + [1697608580.243402][7767:7769] CHIP:DMG: } - echo '{"Name":"LongRelease","PreviousPosition":1}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) + Set up the subscription between DUT and TH by sending the command mentioned below, and verify that the subscription is activated successfully - Verify LongRelease event with PreviousPosition set to 1 on DUT(all-cluster-app) log and below is the sample log provided for the raspi platform: + switch subscribe-event long-release 1 100 1 1 - [1674036547.915803][19172:19174] CHIP:-: Received payload: "{"Name":"LongRelease","PreviousPosition":1}" - [1674036547.916262][19172:19172] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 40105288 - [1674036547.916347][19172:19172] CHIP:-: The the previous value of the CurrentPosition when the momentary switch has been released after having been pressed for a long time:1 - [1674036547.916493][19172:19172] CHIP:ZCL: SwitchServer: OnLongRelease + [1697608657.944735][7767:7769] CHIP:DMG: SubscribeResponseMessage = + [1697608657.944738][7767:7769] CHIP:DMG: { + [1697608657.944741][7767:7769] CHIP:DMG: SubscriptionId = 0x3d884dce, + [1697608657.944745][7767:7769] CHIP:DMG: MaxInterval = 0x64, + [1697608657.944748][7767:7769] CHIP:DMG: InteractionModelRevision = 11 + [1697608657.944751][7767:7769] CHIP:DMG: } disabled: true - label: "Step 5b: Operator does not operate switch" @@ -596,21 +605,30 @@ tests: verification: | Note : Please skip this step if LATCH SWITCH feature is implemented, because a device can support either a latching switch or a momentary switch. - Please use Interactive mode to Verify the subscription of an event - Here the command to enter interactive mode:-- + On Raspi platform To trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor Dut should have capability to generate this event) - 1. ./chip-tool interactive start - 2. switch subscribe-event initial-press 1 100 1 1 + echo '{"Name":"InitialPress","NewPosition":1}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) - Verify InitialPress event with NewPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: + DUT generated the InitialPress event with NewPosition set to 1: + + [1697608754.628837][7384:7386] CHIP:-: Received payload: "{"Name":"InitialPress","NewPosition":1}" + [1697608754.629085][7384:7384] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4dbcc0b9 + [1697608754.629120][7384:7384] CHIP:-: The new position when the momentary switch starts to be pressed:1 + [1697608754.629132][7384:7384] CHIP:ZCL: SwitchServer: OnInitialPress + [1697608754.629247][7384:7384] CHIP:EVL: Copy Event to next buffer with priority 1 + [1697608754.629277][7384:7384] CHIP:EVL: LogEvent event number: 0x0000000000000016 priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x1 Epoch timestamp: 0x0000018B415DE5C5 + + switch read-event initial-press 1 1 - [1659692507.869323][3696:3701] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0001 - [1659692507.869342][3696:3701] CHIP:TOO: Event number: 28 - [1659692507.869361][3696:3701] CHIP:TOO: Priority: Info - [1659692507.869379][3696:3701] CHIP:TOO: Timestamp: 14905717 - [1659692507.869402][3696:3701] CHIP:TOO: InitialPress: { - [1659692507.869421][3696:3701] CHIP:TOO: NewPosition: 1 - [1659692507.869440][3696:3701] CHIP:TOO: } + Verify TH receives InitialPress event with NewPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: + + [1697608808.722369][7767:7769] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0001 + [1697608808.722371][7767:7769] CHIP:TOO: Event number: 22 + [1697608808.722374][7767:7769] CHIP:TOO: Priority: Info + [1697608808.722376][7767:7769] CHIP:TOO: Timestamp: 1697608754629 + [1697608808.722380][7767:7769] CHIP:TOO: InitialPress: { + [1697608808.722383][7767:7769] CHIP:TOO: NewPosition: 1 + [1697608808.722385][7767:7769] CHIP:TOO: } disabled: true - label: "Step 5d: Operator releases switch" @@ -618,21 +636,30 @@ tests: verification: | Note : Please skip this step if LATCH SWITCH feature is implemented, because a device can support either a latching switch or a momentary switch. - Please use Interactive mode to Verify the subscription of an event - Here the command to enter interactive mode:-- + On Raspi platform To trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor Dut should have capability to generate this event) - 1. ./chip-tool interactive start - 2. switch subscribe-event short-release 1 100 1 1 + echo '{"Name":"ShortRelease","PreviousPosition":1}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) + + DUT generated the ShortRelease event with PreviousPosition set to 1: - Verify ShortRelease event with PreviousPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: + [1697608936.890550][7384:7386] CHIP:-: Received payload: "{"Name":"ShortRelease","PreviousPosition":1}" + [1697608936.890789][7384:7384] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4dbcc0ba + [1697608936.890824][7384:7384] CHIP:-: The the previous value of the CurrentPosition when the momentary switch has been released:1 + [1697608936.890833][7384:7384] CHIP:ZCL: SwitchServer: OnShortRelease + [1697608936.890948][7384:7384] CHIP:EVL: Copy Event to next buffer with priority 1 + [1697608936.890983][7384:7384] CHIP:EVL: LogEvent event number: 0x0000000000000017 priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x3 Epoch timestamp: 0x0000018B4160ADBA - [1659692890.665344][3721:3726] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0003 - [1659692890.665369][3721:3726] CHIP:TOO: Event number: 31 - [1659692890.665392][3721:3726] CHIP:TOO: Priority: Info - [1659692890.665416][3721:3726] CHIP:TOO: Timestamp: 15332747 - [1659692890.665444][3721:3726] CHIP:TOO: ShortRelease: { - [1659692890.665470][3721:3726] CHIP:TOO: PreviousPosition: 1 - [1659692890.665494][3721:3726] CHIP:TOO: } + switch read-event short-release 1 1 + + Verify TH receives ShortRelease event with PreviousPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: + + [1697608970.793400][7767:7769] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0003 + [1697608970.793402][7767:7769] CHIP:TOO: Event number: 23 + [1697608970.793405][7767:7769] CHIP:TOO: Priority: Info + [1697608970.793408][7767:7769] CHIP:TOO: Timestamp: 1697608936890 + [1697608970.793414][7767:7769] CHIP:TOO: ShortRelease: { + [1697608970.793417][7767:7769] CHIP:TOO: PreviousPosition: 1 + [1697608970.793421][7767:7769] CHIP:TOO: } disabled: true - label: @@ -642,37 +669,59 @@ tests: verification: | Note : Please skip this step if LATCH SWITCH feature is implemented, because a device can support either a latching switch or a momentary switch. - Please use Interactive mode to Verify the subscription of an event - Here the command to enter interactive mode:-- + On Raspi platform To trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor Dut should have capability to generate this event) - 1. ./chip-tool interactive start - 2. switch subscribe-event initial-press 1 100 1 1 + echo '{"Name":"InitialPress","NewPosition":1}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) + + DUT generated the InitialPress event with NewPosition set to 1: + + [1697609110.498463][7384:7386] CHIP:-: Received payload: "{"Name":"InitialPress","NewPosition":1}" + [1697609110.498726][7384:7384] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4dbcc0bb + [1697609110.498757][7384:7384] CHIP:-: The new position when the momentary switch starts to be pressed:1 + [1697609110.498766][7384:7384] CHIP:ZCL: SwitchServer: OnInitialPress + [1697609110.498925][7384:7384] CHIP:EVL: Copy Event to next buffer with priority 2 + [1697609110.499002][7384:7384] CHIP:EVL: Copy Event to next buffer with priority 1 + [1697609110.499030][7384:7384] CHIP:EVL: LogEvent event number: 0x0000000000000018 priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x1 Epoch timestamp: 0x0000018B416353E2 + + switch read-event initial-press 1 1 Verify InitialPress event with NewPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: - [1659692507.869323][3696:3701] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0001 - [1659692507.869342][3696:3701] CHIP:TOO: Event number: 28 - [1659692507.869361][3696:3701] CHIP:TOO: Priority: Info - [1659692507.869379][3696:3701] CHIP:TOO: Timestamp: 14905717 - [1659692507.869402][3696:3701] CHIP:TOO: InitialPress: { - [1659692507.869421][3696:3701] CHIP:TOO: NewPosition: 1 - [1659692507.869440][3696:3701] CHIP:TOO: } + [1697609188.273452][7767:7769] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0001 + [1697609188.273455][7767:7769] CHIP:TOO: Event number: 24 + [1697609188.273457][7767:7769] CHIP:TOO: Priority: Info + [1697609188.273459][7767:7769] CHIP:TOO: Timestamp: 1697609110498 + [1697609188.273463][7767:7769] CHIP:TOO: InitialPress: { + [1697609188.273466][7767:7769] CHIP:TOO: NewPosition: 1 + [1697609188.273469][7767:7769] CHIP:TOO: } - Please use Interactive mode to Verify the subscription of an event - Here the command to enter interactive mode:-- + On Raspi platform To trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor Dut should have capability to generate this event) - 1. ./chip-tool interactive start - 2. switch subscribe-event long-press 1 100 1 1 + echo '{"Name":"LongPress","NewPosition":1}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) + + DUT generated the longPress event with NewPosition set to 1: + + [1697609280.508624][7384:7386] CHIP:-: Received payload: "{"Name":"LongPress","NewPosition":1}" + [1697609280.508890][7384:7384] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4dbcc0bc + [1697609280.508924][7384:7384] CHIP:-: The new position when the momentary switch has been pressed for a long time:1 + [1697609280.508933][7384:7384] CHIP:ZCL: SwitchServer: OnLongPress + [1697609280.509078][7384:7384] CHIP:EVL: Dropped 1 event from buffer with priority 1 and event number 0x0000000000000001 due to overflow: event priority_level: 1 + [1697609280.509144][7384:7384] CHIP:EVL: Copy Event to next buffer with priority 1 + [1697609280.509174][7384:7384] CHIP:EVL: LogEvent event number: 0x0000000000000019 priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x2 Epoch timestamp: 0x0000018B4165EBFC + [1697609280.509203][7384:7384] CHIP:DMG: Endpoint 1, Cluster 0x0000_005C update version to e31eae9f + + + switch read-event long-press 1 1 - Verify longPress event with NewPosition set to 1 on TH (chip-tool) log and below is the sample log provided for the raspi platform: + Verify TH receives longPress event with NewPosition set to 1 on TH (chip-tool) log and below is the sample log provided for the raspi platform: - [1659692638.993482][3706:3712] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0002 - [1659692638.993504][3706:3712] CHIP:TOO: Event number: 30 - [1659692638.993525][3706:3712] CHIP:TOO: Priority: Info - [1659692638.993545][3706:3712] CHIP:TOO: Timestamp: 15084506 - [1659692638.993571][3706:3712] CHIP:TOO: LongPress: { - [1659692638.993593][3706:3712] CHIP:TOO: NewPosition: 1 - [1659692638.993615][3706:3712] CHIP:TOO: } + [1697609316.967370][7767:7769] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0002 + [1697609316.967375][7767:7769] CHIP:TOO: Event number: 25 + [1697609316.967376][7767:7769] CHIP:TOO: Priority: Info + [1697609316.967380][7767:7769] CHIP:TOO: Timestamp: 1697609280508 + [1697609316.967391][7767:7769] CHIP:TOO: LongPress: { + [1697609316.967397][7767:7769] CHIP:TOO: NewPosition: 1 + [1697609316.967402][7767:7769] CHIP:TOO: } disabled: true - label: "Step 5f: Operator releases switch" @@ -680,21 +729,31 @@ tests: verification: | Note : Please skip this step if LATCH SWITCH feature is implemented, because a device can support either a latching switch or a momentary switch. - Please use Interactive mode to Verify the subscription of an event - Here the command to enter interactive mode:-- + On Raspi platform To trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor Dut should have capability to generate this event) - 1. ./chip-tool interactive start - 2. switch subscribe-event long-release 1 100 1 1 + echo '{"Name":"LongRelease","PreviousPosition":1}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) + + DUT generated the LongRelease event with previousPosition set to 1: - Verify LongRelease event with previousPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: + [1697609417.101354][7384:7386] CHIP:-: Received payload: "{"Name":"LongRelease","PreviousPosition":1}" + [1697609417.101563][7384:7384] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4dbcc0bd + [1697609417.101600][7384:7384] CHIP:-: The the previous value of the CurrentPosition when the momentary switch has been released after having been pressed for a long time:1 + [1697609417.101614][7384:7384] CHIP:ZCL: SwitchServer: OnLongRelease + [1697609417.101765][7384:7384] CHIP:EVL: Dropped 1 event from buffer with priority 1 and event number 0x0000000000000004 due to overflow: event priority_level: 1 + [1697609417.101831][7384:7384] CHIP:EVL: Copy Event to next buffer with priority 1 + [1697609417.101862][7384:7384] CHIP:EVL: LogEvent event number: 0x000000000000001C priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x4 Epoch timestamp: 0x0000018B4168018D - [1659693001.739969][3732:3737] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0004 - [1659693001.740012][3732:3737] CHIP:TOO: Event number: 32 - [1659693001.740049][3732:3737] CHIP:TOO: Priority: Info - [1659693001.740087][3732:3737] CHIP:TOO: Timestamp: 15438774 - [1659693001.740134][3732:3737] CHIP:TOO: LongRelease: { - [1659693001.740174][3732:3737] CHIP:TOO: PreviousPosition: 1 - [1659693001.740212][3732:3737] CHIP:TOO: } + switch read-event long-release 1 1 + + Verify TH receives LongRelease event with previousPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: + + [1697609485.675506][7767:7769] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0004 + [1697609485.675509][7767:7769] CHIP:TOO: Event number: 28 + [1697609485.675511][7767:7769] CHIP:TOO: Priority: Info + [1697609485.675513][7767:7769] CHIP:TOO: Timestamp: 1697609417101 + [1697609485.675531][7767:7769] CHIP:TOO: LongRelease: { + [1697609485.675538][7767:7769] CHIP:TOO: PreviousPosition: 1 + [1697609485.675542][7767:7769] CHIP:TOO: } disabled: true - label: @@ -704,51 +763,54 @@ tests: verification: | Note : Please skip this step if LATCH SWITCH feature is implemented, because a device can support either a latching switch or a momentary switch. - On Raspi platform to trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor DUT should have capability to generate this event) - - echo '{"Name":"InitialPress","NewPosition":1}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) + Please use Interactive mode to Verify the subscription of an event + Here the command to enter interactive mode:-- - Verify InitialPress event with NewPosition set to 1 on DUT(all-cluster-app) log and below is the sample log provided for the raspi platform: + ./chip-tool interactive start - [1659693098.031462][2530:2538] CHIP:-: Received payload: "{"Name":"InitialPress","NewPosition":1}" - [1659693098.031812][2530:2530] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to ee5e7724 - [1659693098.031859][2530:2530] CHIP:-: The new position when the momentary switch starts to be pressed:1 - [1659693098.031888][2530:2530] CHIP:ZCL: SwitchServer: OnInitialPress + Set up the subscription between DUT and TH by sending the command mentioned below, and verify that the subscription is activated successfully - On Raspi platform to trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor DUT should have capability to generate this event) + switch subscribe-event initial-press 1 100 1 1 - echo '{"Name":"ShortRelease","PreviousPosition":1}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) + [1697609572.733866][7767:7769] CHIP:DMG: SubscribeResponseMessage = + [1697609572.733870][7767:7769] CHIP:DMG: { + [1697609572.733872][7767:7769] CHIP:DMG: SubscriptionId = 0xdb9c2f95, + [1697609572.733875][7767:7769] CHIP:DMG: MaxInterval = 0x64, + [1697609572.733878][7767:7769] CHIP:DMG: InteractionModelRevision = 11 + [1697609572.733880][7767:7769] CHIP:DMG: } - Verify ShortRelease event with PreviousPosition set to 1 on DUT(all-cluster-app) log and below is the sample log provided for the raspi platform: + Set up the subscription between DUT and TH by sending the command mentioned below, and verify that the subscription is activated successfully - [1659694387.719620][2530:2538] CHIP:-: Received payload: "{"Name":"ShortRelease","PreviousPosition":1}" - [1659694387.720095][2530:2530] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to ee5e7729 - [1659694387.720237][2530:2530] CHIP:-: The the previous value of the CurrentPosition when the momentary switch has been released:1 - [1659694387.720304][2530:2530] CHIP:ZCL: SwitchServer: OnShortRelease + switch subscribe-event short-release 1 100 1 1 - On Raspi platform to trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor DUT should have capability to generate this event) + [1697609772.052026][7767:7769] CHIP:DMG: SubscribeResponseMessage = + [1697609772.052029][7767:7769] CHIP:DMG: { + [1697609772.052032][7767:7769] CHIP:DMG: SubscriptionId = 0xd48293d0, + [1697609772.052035][7767:7769] CHIP:DMG: MaxInterval = 0x64, + [1697609772.052038][7767:7769] CHIP:DMG: InteractionModelRevision = 11 + [1697609772.052040][7767:7769] CHIP:DMG: } - echo '{"Name":"MultiPressComplete","PreviousPosition":1,"TotalNumberOfPressesCounted":1}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) + Set up the subscription between DUT and TH by sending the command mentioned below, and verify that the subscription is activated successfully - Verify MultiPressComplete event with PreviousPosition set to 1 on DUT(all-cluster-app) log and below is the sample log provided for the raspi platform: + switch subscribe-event multi-press-ongoing 1 100 1 1 - [1659694592.347850][2530:2538] CHIP:-: Received payload: "{"Name":"MultiPressComplete","PreviousPosition":1,"TotalNumberOfPressesCounted":1}" - [1659694592.348389][2530:2530] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to ee5e772b - [1659694592.348481][2530:2530] CHIP:-: The new position when the momentary switch has been pressed in a multi-press sequence:1 + [1697609745.441125][7767:7769] CHIP:DMG: SubscribeResponseMessage = + [1697609745.441128][7767:7769] CHIP:DMG: { + [1697609745.441131][7767:7769] CHIP:DMG: SubscriptionId = 0x2161432e, + [1697609745.441134][7767:7769] CHIP:DMG: MaxInterval = 0x64, + [1697609745.441136][7767:7769] CHIP:DMG: InteractionModelRevision = 11 + [1697609745.441139][7767:7769] CHIP:DMG: } - On Raspi platform to trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor DUT should have capability to generate this event) + Set up the subscription between DUT and TH by sending the command mentioned below, and verify that the subscription is activated successfully - echo '{"Name":"MultiPressOngoing","NewPosition":1,"CurrentNumberOfPressesCounted":2}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) + switch subscribe-event multi-press-complete 1 100 1 1 - Verify MultiPressOngoing event with NewPosition set to 1 on DUT(all-cluster-app) log and below is the sample log provided for the raspi platform: - - [1659695302.038797][2530:2538] CHIP:-: Received payload: "{"Name":"MultiPressOngoing","NewPosition":1,"CurrentNumberOfPressesCounted":2}" - [1659695302.039933][2530:2530] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to ee5e7730 - [1659695302.040020][2530:2530] CHIP:-: The new position when the momentary switch has been pressed in a multi-press sequence:1 - [1659695302.040078][2530:2530] CHIP:-: 2 times the momentary switch has been pressed - [1659695302.040131][2530:2530] CHIP:ZCL: SwitchServer: OnMultiPressOngoing - [1659694592.348541][2530:2530] CHIP:-: 1 times the momentary switch has been pressed - [1659694592.348585][2530:2530] CHIP:ZCL: SwitchServer: OnMultiPressOngoing + [1697609646.344664][7767:7769] CHIP:DMG: SubscribeResponseMessage = + [1697609646.344669][7767:7769] CHIP:DMG: { + [1697609646.344674][7767:7769] CHIP:DMG: SubscriptionId = 0x9177cb65, + [1697609646.344679][7767:7769] CHIP:DMG: MaxInterval = 0x64, + [1697609646.344684][7767:7769] CHIP:DMG: InteractionModelRevision = 11 + [1697609646.344688][7767:7769] CHIP:DMG: } disabled: true - label: "Step 6b: Operator does not operate switch" @@ -762,20 +824,30 @@ tests: verification: | Note : Please skip this step if LATCH SWITCH feature is implemented, because a device can support either a latching switch or a momentary switch. - Please use Interactive mode to Verify the subscription of an event - Here the command to enter interactive mode:-- + On Raspi platform To trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor Dut should have capability to generate this event) - 1. ./chip-tool interactive start - 2. switch subscribe-event initial-press 1 100 1 1 + echo '{"Name":"InitialPress","NewPosition":1}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) - Verify InitialPress event with NewPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: + DUT generated the InitialPress event with NewPosition set to 1: + + [1697609895.678486][7384:7386] CHIP:-: Received payload: "{"Name":"InitialPress","NewPosition":1}" + [1697609895.678744][7384:7384] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4dbcc0be + [1697609895.678786][7384:7384] CHIP:-: The new position when the momentary switch starts to be pressed:1 + [1697609895.678800][7384:7384] CHIP:ZCL: SwitchServer: OnInitialPress + [1697609895.678917][7384:7384] CHIP:EVL: Copy Event to next buffer with priority 1 + [1697609895.678949][7384:7384] CHIP:EVL: LogEvent event number: 0x000000000000001D priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x1 Epoch timestamp: 0x0000018B416F4EFE - [1659694345.040034][3787:3792] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0001 - [1659694345.040059][3787:3792] CHIP:TOO: Event number: 37 - [1659694345.040083][3787:3792] CHIP:TOO: Priority: Info - [1659694345.040106][3787:3792] CHIP:TOO: Timestamp: 16729153 - [1659694345.040135][3787:3792] CHIP:TOO: InitialPress: { - [1659694345.040160][3787:3792] CHIP:TOO: NewPosition: 1 + switch read-event initial-press 1 1 + + Verify TH receives InitialPress event with NewPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: + + [1697609943.498311][7767:7769] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0001 + [1697609943.498313][7767:7769] CHIP:TOO: Event number: 29 + [1697609943.498315][7767:7769] CHIP:TOO: Priority: Info + [1697609943.498317][7767:7769] CHIP:TOO: Timestamp: 1697609895678 + [1697609943.498320][7767:7769] CHIP:TOO: InitialPress: { + [1697609943.498323][7767:7769] CHIP:TOO: NewPosition: 1 + [1697609943.498325][7767:7769] CHIP:TOO: } disabled: true - label: "Step 6d: Operator releases switch" @@ -783,39 +855,59 @@ tests: verification: | Note : Please skip this step if LATCH SWITCH feature is implemented, because a device can support either a latching switch or a momentary switch. - Please use Interactive mode to Verify the subscription of an event - Here the command to enter interactive mode:-- + On Raspi platform To trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor Dut should have capability to generate this event) - 1. ./chip-tool interactive start - 2. switch subscribe-event short-release 1 100 1 1 - Verify ShortRelease event with PreviousPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: + echo '{"Name":"ShortRelease","PreviousPosition":1}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) - [1659694426.794832][3797:3802] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0003 - [1659694426.794853][3797:3802] CHIP:TOO: Event number: 38 - [1659694426.794873][3797:3802] CHIP:TOO: Priority: Info - [1659694426.794891][3797:3802] CHIP:TOO: Timestamp: 16840016 - [1659694426.794914][3797:3802] CHIP:TOO: ShortRelease: { - [1659694426.794934][3797:3802] CHIP:TOO: PreviousPosition: 1 - [1659694426.794952][3797:3802] CHIP:TOO: } + DUT generated the ShortRelease event with PreviousPosition set to 1: + [1697610020.642902][7384:7386] CHIP:-: Received payload: "{"Name":"ShortRelease","PreviousPosition":1}" + [1697610020.643151][7384:7384] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4dbcc0bf + [1697610020.643184][7384:7384] CHIP:-: The the previous value of the CurrentPosition when the momentary switch has been released:1 + [1697610020.643194][7384:7384] CHIP:ZCL: SwitchServer: OnShortRelease + [1697610020.643356][7384:7384] CHIP:EVL: Dropped 1 event from buffer with priority 1 and event number 0x0000000000000005 due to overflow: event priority_level: 1 + [1697610020.643427][7384:7384] CHIP:EVL: Copy Event to next buffer with priority 1 + [1697610020.643456][7384:7384] CHIP:EVL: LogEvent event number: 0x000000000000001E priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x3 Epoch timestamp: 0x0000018B41713723 - Please use Interactive mode to Verify the subscription of an event - Here the command to enter interactive mode:-- + switch read-event short-release 1 1 - 1. ./chip-tool interactive start - 2. switch subscribe-event multi-press-complete 1 100 1 1 + Verify TH receives ShortRelease event with PreviousPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: - Verify MultiPressComplete event with PreviousPosition set to 1 and TotalNumberOfPressesCounted set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: + [1697610069.134658][7767:7769] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0003 + [1697610069.134661][7767:7769] CHIP:TOO: Event number: 30 + [1697610069.134663][7767:7769] CHIP:TOO: Priority: Info + [1697610069.134665][7767:7769] CHIP:TOO: Timestamp: 1697610020643 + [1697610069.134669][7767:7769] CHIP:TOO: ShortRelease: { + [1697610069.134672][7767:7769] CHIP:TOO: PreviousPosition: 1 + [1697610069.134675][7767:7769] CHIP:TOO: } - [1659695330.923244][3912:3918] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0005 - [1659695330.923264][3912:3918] CHIP:TOO: Event number: 45 - [1659695330.923283][3912:3918] CHIP:TOO: Priority: Info - [1659695330.923302][3912:3918] CHIP:TOO: Timestamp: 17754336 - [1659695330.923326][3912:3918] CHIP:TOO: MultiPressComplete: { - [1659695330.923346][3912:3918] CHIP:TOO: PrevioiusPosition: 1 - [1659695330.923366][3912:3918] CHIP:TOO: TotalNumberOfPressesCounted: 1 - [1659695330.923385][3912:3918] CHIP:TOO: } + On Raspi platform To trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor Dut should have capability to generate this event) + + echo '{"Name":"MultiPressComplete","PreviousPosition":1,"TotalNumberOfPressesCounted":1}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) + + DUT generated the MultiPressComplete event with PreviousPosition set to 1: + + [1697610133.480979][7384:7386] CHIP:-: Received payload: "{"Name":"MultiPressComplete","PreviousPosition":1,"TotalNumberOfPressesCounted":1}" + [1697610133.481239][7384:7384] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4dbcc0c0 + [1697610133.481271][7384:7384] CHIP:-: The previous position when the momentary switch has been pressed in a multi-press sequence:1 + [1697610133.481280][7384:7384] CHIP:-: 1 times the momentary switch has been pressed + [1697610133.481287][7384:7384] CHIP:ZCL: SwitchServer: OnMultiPressComplete + [1697610133.481399][7384:7384] CHIP:EVL: Copy Event to next buffer with priority 1 + [1697610133.481431][7384:7384] CHIP:EVL: LogEvent event number: 0x000000000000001F priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x6 Epoch timestamp: 0x0000018B4172EFE9 + + switch read-event multi-press-complete 1 1 + + Verify TH receives MultiPressComplete event with PreviousPosition set to 1 and TotalNumberOfPressesCounted set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: + + [1697610193.287175][7767:7769] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0006 + [1697610193.287187][7767:7769] CHIP:TOO: Event number: 31 + [1697610193.287198][7767:7769] CHIP:TOO: Priority: Info + [1697610193.287207][7767:7769] CHIP:TOO: Timestamp: 1697610133481 + [1697610193.287241][7767:7769] CHIP:TOO: MultiPressComplete: { + [1697610193.287261][7767:7769] CHIP:TOO: PreviousPosition: 1 + [1697610193.287273][7767:7769] CHIP:TOO: TotalNumberOfPressesCounted: 1 + [1697610193.287285][7767:7769] CHIP:TOO: } disabled: true - label: "Step 6e: Operator operates switch (press briefly)" @@ -823,21 +915,30 @@ tests: verification: | Note : Please skip this step if LATCH SWITCH feature is implemented, because a device can support either a latching switch or a momentary switch. - Please use Interactive mode to Verify the subscription of an event - Here the command to enter interactive mode:-- + On Raspi platform To trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor Dut should have capability to generate this event) - 1. ./chip-tool interactive start - 2. switch subscribe-event initial-press 1 100 1 1 + echo '{"Name":"InitialPress","NewPosition":1}' > /tmp/chip_all_clusters_ (PID of DUT) - Verify InitialPress event with NewPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: + DUT generated the InitialPress event with NewPosition set to 1: - [1659695901.066563][3955:3960] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0001 - [1659695901.066583][3955:3960] CHIP:TOO: Event number: 46 - [1659695901.066602][3955:3960] CHIP:TOO: Priority: Info - [1659695901.066643][3955:3960] CHIP:TOO: Timestamp: 18095747 - [1659695901.066669][3955:3960] CHIP:TOO: InitialPress: { - [1659695901.066689][3955:3960] CHIP:TOO: NewPosition: 1 - [1659695901.066708][3955:3960] CHIP:TOO: } + [1697609895.678486][7384:7386] CHIP:-: Received payload: "{"Name":"InitialPress","NewPosition":1}" + [1697609895.678744][7384:7384] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4dbcc0be + [1697609895.678786][7384:7384] CHIP:-: The new position when the momentary switch starts to be pressed:1 + [1697609895.678800][7384:7384] CHIP:ZCL: SwitchServer: OnInitialPress + [1697609895.678917][7384:7384] CHIP:EVL: Copy Event to next buffer with priority 1 + [1697609895.678949][7384:7384] CHIP:EVL: LogEvent event number: 0x000000000000001D priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x1 Epoch timestamp: 0x0000018B416F4EFE + + switch read-event initial-press 1 1 + + Verify TH receives InitialPress event with NewPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: + + [1697609943.498311][7767:7769] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0001 + [1697609943.498313][7767:7769] CHIP:TOO: Event number: 29 + [1697609943.498315][7767:7769] CHIP:TOO: Priority: Info + [1697609943.498317][7767:7769] CHIP:TOO: Timestamp: 1697609895678 + [1697609943.498320][7767:7769] CHIP:TOO: InitialPress: { + [1697609943.498323][7767:7769] CHIP:TOO: NewPosition: 1 + [1697609943.498325][7767:7769] CHIP:TOO: } disabled: true - label: "Step 6f: Operator releases switch" @@ -845,21 +946,31 @@ tests: verification: | Note : Please skip this step if LATCH SWITCH feature is implemented, because a device can support either a latching switch or a momentary switch. - Please use Interactive mode to Verify the subscription of an event - Here the command to enter interactive mode:-- + On Raspi platform To trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor Dut should have capability to generate this event) - 1. ./chip-tool interactive start - 2. switch subscribe-event short-release 1 100 1 1 + echo '{"Name":"ShortRelease","PreviousPosition":1}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) + + DUT generated the ShortRelease event with PreviousPosition set to 1: - Verify ShortRelease event with PreviousPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: + [1697610020.642902][7384:7386] CHIP:-: Received payload: "{"Name":"ShortRelease","PreviousPosition":1}" + [1697610020.643151][7384:7384] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4dbcc0bf + [1697610020.643184][7384:7384] CHIP:-: The the previous value of the CurrentPosition when the momentary switch has been released:1 + [1697610020.643194][7384:7384] CHIP:ZCL: SwitchServer: OnShortRelease + [1697610020.643356][7384:7384] CHIP:EVL: Dropped 1 event from buffer with priority 1 and event number 0x0000000000000005 due to overflow: event priority_level: 1 + [1697610020.643427][7384:7384] CHIP:EVL: Copy Event to next buffer with priority 1 + [1697610020.643456][7384:7384] CHIP:EVL: LogEvent event number: 0x000000000000001E priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x3 Epoch timestamp: 0x0000018B41713723 - [1659694426.794832][3797:3802] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0003 - [1659694426.794853][3797:3802] CHIP:TOO: Event number: 38 - [1659694426.794873][3797:3802] CHIP:TOO: Priority: Info - [1659694426.794891][3797:3802] CHIP:TOO: Timestamp: 16840016 - [1659694426.794914][3797:3802] CHIP:TOO: ShortRelease: { - [1659694426.794934][3797:3802] CHIP:TOO: PreviousPosition: 1 - [1659694426.794952][3797:3802] CHIP:TOO: } + switch read-event short-release 1 1 + + Verify TH receives ShortRelease event with PreviousPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: + + [1697610069.134658][7767:7769] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0003 + [1697610069.134661][7767:7769] CHIP:TOO: Event number: 30 + [1697610069.134663][7767:7769] CHIP:TOO: Priority: Info + [1697610069.134665][7767:7769] CHIP:TOO: Timestamp: 1697610020643 + [1697610069.134669][7767:7769] CHIP:TOO: ShortRelease: { + [1697610069.134672][7767:7769] CHIP:TOO: PreviousPosition: 1 + [1697610069.134675][7767:7769] CHIP:TOO: } disabled: true - label: @@ -869,37 +980,58 @@ tests: verification: | Note : Please skip this step if LATCH SWITCH feature is implemented, because a device can support either a latching switch or a momentary switch. - Please use Interactive mode to Verify the subscription of an event - Here the command to enter interactive mode:-- + On Raspi platform To trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor Dut should have capability to generate this event) - 1. ./chip-tool interactive start - 2. switch subscribe-event initial-press 1 100 1 1 + echo '{"Name":"InitialPress","NewPosition":1}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) - Verify InitialPress event with NewPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: + DUT generated the InitialPress event with NewPosition set to 1: - [1659694345.040034][3787:3792] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0001 - [1659694345.040059][3787:3792] CHIP:TOO: Event number: 37 - [1659694345.040083][3787:3792] CHIP:TOO: Priority: Info - [1659694345.040106][3787:3792] CHIP:TOO: Timestamp: 16729153 - [1659694345.040135][3787:3792] CHIP:TOO: InitialPress: { - [1659694345.040160][3787:3792] CHIP:TOO: NewPosition: 1 + [1697609895.678486][7384:7386] CHIP:-: Received payload: "{"Name":"InitialPress","NewPosition":1}" + [1697609895.678744][7384:7384] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4dbcc0be + [1697609895.678786][7384:7384] CHIP:-: The new position when the momentary switch starts to be pressed:1 + [1697609895.678800][7384:7384] CHIP:ZCL: SwitchServer: OnInitialPress + [1697609895.678917][7384:7384] CHIP:EVL: Copy Event to next buffer with priority 1 + [1697609895.678949][7384:7384] CHIP:EVL: LogEvent event number: 0x000000000000001D priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x1 Epoch timestamp: 0x0000018B416F4EFE - Please use Interactive mode to Verify the subscription of an event - Here the command to enter interactive mode:-- + switch read-event initial-press 1 1 - 1. ./chip-tool interactive start - 2. switch subscribe-event multi-press-ongoing 1 100 1 1 + Verify TH receives InitialPress event with NewPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: - Verify MultiPressongoing event with NewPosition set to 1 and CurrentNumberOfPressesCounted set to 2 on TH chip-tool log and below is the sample log provided for the raspi platform: + [1697609943.498311][7767:7769] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0001 + [1697609943.498313][7767:7769] CHIP:TOO: Event number: 29 + [1697609943.498315][7767:7769] CHIP:TOO: Priority: Info + [1697609943.498317][7767:7769] CHIP:TOO: Timestamp: 1697609895678 + [1697609943.498320][7767:7769] CHIP:TOO: InitialPress: { + [1697609943.498323][7767:7769] CHIP:TOO: NewPosition: 1 + [1697609943.498325][7767:7769] CHIP:TOO: } - [1659695330.923244][3912:3918] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0005 - [1659695330.923264][3912:3918] CHIP:TOO: Event number: 45 - [1659695330.923283][3912:3918] CHIP:TOO: Priority: Info - [1659695330.923302][3912:3918] CHIP:TOO: Timestamp: 17754336 - [1659695330.923326][3912:3918] CHIP:TOO: MultiPressOngoing: { - [1659695330.923346][3912:3918] CHIP:TOO: NewPosition: 1 - [1659695330.923366][3912:3918] CHIP:TOO: CurrentNumberOfPressesCounted: 2 - [1659695330.923385][3912:3918] CHIP:TOO: } + On Raspi platform To trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor Dut should have capability to generate this event) + + echo '{"Name":"MultiPressOngoing","NewPosition":1,"CurrentNumberOfPressesCounted":2}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) + + DUT generated the MultiPressongoing event with NewPosition set to 1: + + [1697610439.738698][7384:7386] CHIP:-: Received payload: "{"Name":"MultiPressOngoing","NewPosition":1,"CurrentNumberOfPressesCounted":2}" + [1697610439.738953][7384:7384] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4dbcc0c1 + [1697610439.738982][7384:7384] CHIP:-: The new position when the momentary switch has been pressed in a multi-press sequence:1 + [1697610439.738995][7384:7384] CHIP:-: 2 times the momentary switch has been pressed + [1697610439.739001][7384:7384] CHIP:ZCL: SwitchServer: OnMultiPressOngoing + [1697610439.739129][7384:7384] CHIP:EVL: Dropped 1 event from buffer with priority 1 and event number 0x0000000000000006 due to overflow: event priority_level: 1 + [1697610439.739190][7384:7384] CHIP:EVL: Copy Event to next buffer with priority 1 + [1697610439.739220][7384:7384] CHIP:EVL: LogEvent event number: 0x0000000000000020 priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x5 Epoch timestamp: 0x0000018B41779C3B + + switch read-event multi-press-ongoing 1 1 + + Verify TH receives MultiPressongoing event with NewPosition set to 1 and CurrentNumberOfPressesCounted set to 2 on TH chip-tool log and below is the sample log provided for the raspi platform: + + [1697610464.005842][7767:7769] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0005 + [1697610464.005846][7767:7769] CHIP:TOO: Event number: 32 + [1697610464.005848][7767:7769] CHIP:TOO: Priority: Info + [1697610464.005850][7767:7769] CHIP:TOO: Timestamp: 1697610439739 + [1697610464.005861][7767:7769] CHIP:TOO: MultiPressOngoing: { + [1697610464.005866][7767:7769] CHIP:TOO: NewPosition: 1 + [1697610464.005869][7767:7769] CHIP:TOO: CurrentNumberOfPressesCounted: 2 + [1697610464.005872][7767:7769] CHIP:TOO: } disabled: true - label: "Step 6h: Operator releases switch" @@ -907,43 +1039,59 @@ tests: verification: | Note : Please skip this step if LATCH SWITCH feature is implemented, because a device can support either a latching switch or a momentary switch. - Please use Interactive mode to Verify the subscription of an event - Here the command to enter interactive mode:-- - - 1. ./chip-tool interactive start - 2. switch subscribe-event short-release 1 100 1 1 + On Raspi platform To trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor Dut should have capability to generate this event) - Verify ShortRelease event with PreviousPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: + echo '{"Name":"ShortRelease","PreviousPosition":1}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) - [1659696223.568247][3981:3986] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0003 - [1659696223.568272][3981:3986] CHIP:TOO: Event number: 53 - [1659696223.568296][3981:3986] CHIP:TOO: Priority: Info - [1659696223.568319][3981:3986] CHIP:TOO: Timestamp: 18666186 - [1659696223.568348][3981:3986] CHIP:TOO: ShortRelease: { - [1659696223.568373][3981:3986] CHIP:TOO: PreviousPosition: 1 - [1659696223.568397][3981:3986] CHIP:TOO: } + DUT generated the ShortRelease event with PreviousPosition set to 1: + [1697610020.642902][7384:7386] CHIP:-: Received payload: "{"Name":"ShortRelease","PreviousPosition":1}" + [1697610020.643151][7384:7384] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4dbcc0bf + [1697610020.643184][7384:7384] CHIP:-: The the previous value of the CurrentPosition when the momentary switch has been released:1 + [1697610020.643194][7384:7384] CHIP:ZCL: SwitchServer: OnShortRelease + [1697610020.643356][7384:7384] CHIP:EVL: Dropped 1 event from buffer with priority 1 and event number 0x0000000000000005 due to overflow: event priority_level: 1 + [1697610020.643427][7384:7384] CHIP:EVL: Copy Event to next buffer with priority 1 + [1697610020.643456][7384:7384] CHIP:EVL: LogEvent event number: 0x000000000000001E priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x3 Epoch timestamp: 0x0000018B41713723 - On Raspi platform to trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor DUT should have capability to generate this event) + switch read-event short-release 1 1 - echo '{"Name":"MultiPressComplete","PreviousPosition":1,"TotalNumberOfPressesCounted":2}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) + Verify TH receives ShortRelease event with PreviousPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: - Please use Interactive mode to Verify the subscription of an event - Here the command to enter interactive mode:-- + [1697610069.134658][7767:7769] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0003 + [1697610069.134661][7767:7769] CHIP:TOO: Event number: 30 + [1697610069.134663][7767:7769] CHIP:TOO: Priority: Info + [1697610069.134665][7767:7769] CHIP:TOO: Timestamp: 1697610020643 + [1697610069.134669][7767:7769] CHIP:TOO: ShortRelease: { + [1697610069.134672][7767:7769] CHIP:TOO: PreviousPosition: 1 + [1697610069.134675][7767:7769] CHIP:TOO: } - 1. ./chip-tool interactive start - 2. switch subscribe-event multi-press-complete 1 100 1 1 + On Raspi platform To trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor Dut should have capability to generate this event) - Verify MultiPressComplete event with PreviousPosition set to 1 and TotalNumberOfPressesCounted set to 2 on TH chip-tool log and below is the sample log provided for the raspi platform: + echo '{"Name":"MultiPressComplete","PreviousPosition":1,"TotalNumberOfPressesCounted":2}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) - [1659695330.923244][3912:3918] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0005 - [1659695330.923264][3912:3918] CHIP:TOO: Event number: 45 - [1659695330.923283][3912:3918] CHIP:TOO: Priority: Info - [1659695330.923302][3912:3918] CHIP:TOO: Timestamp: 17754336 - [1659695330.923326][3912:3918] CHIP:TOO: MultiPressComplete: { - [1659695330.923346][3912:3918] CHIP:TOO: PrevioiusPosition: 1 - [1659695330.923366][3912:3918] CHIP:TOO: TotalNumberOfPressesCounted: 2 - [1659695330.923385][3912:3918] CHIP:TOO: } + DUT generated the MultiPressComplete event with PreviousPosition set to 1 and TotalNumberOfPressesCounted set to 2 : + + [1697610593.918223][7384:7386] CHIP:-: Received payload: "{"Name":"MultiPressComplete","PreviousPosition":1,"TotalNumberOfPressesCounted":2}" + [1697610593.918505][7384:7384] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4dbcc0c2 + [1697610593.918536][7384:7384] CHIP:-: The previous position when the momentary switch has been pressed in a multi-press sequence:1 + [1697610593.918545][7384:7384] CHIP:-: 2 times the momentary switch has been pressed + [1697610593.918552][7384:7384] CHIP:ZCL: SwitchServer: OnMultiPressComplete + [1697610593.918693][7384:7384] CHIP:EVL: Dropped 1 event from buffer with priority 1 and event number 0x0000000000000007 due to overflow: event priority_level: 1 + [1697610593.918774][7384:7384] CHIP:EVL: Copy Event to next buffer with priority 1 + [1697610593.918814][7384:7384] CHIP:EVL: LogEvent event number: 0x0000000000000021 priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x6 Epoch timestamp: 0x0000018B4179F67E + + switch read-event multi-press-complete 1 1 + + Verify TH receives MultiPressComplete event with PreviousPosition set to 1 and TotalNumberOfPressesCounted set to 2 on TH chip-tool log and below is the sample log provided for the raspi platform: + + [1697610633.998752][7767:7769] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0006 + [1697610633.998762][7767:7769] CHIP:TOO: Event number: 33 + [1697610633.998769][7767:7769] CHIP:TOO: Priority: Info + [1697610633.998776][7767:7769] CHIP:TOO: Timestamp: 1697610593918 + [1697610633.998792][7767:7769] CHIP:TOO: MultiPressComplete: { + [1697610633.998803][7767:7769] CHIP:TOO: PreviousPosition: 1 + [1697610633.998811][7767:7769] CHIP:TOO: TotalNumberOfPressesCounted: 2 + [1697610633.998821][7767:7769] CHIP:TOO: } disabled: true - label: @@ -955,25 +1103,34 @@ tests: disabled: true - label: "Step 6j: Operator operates switch (press briefly)" - PICS: SWTCH.S.F01 && SWTCH.S.F04 + PICS: "" verification: | Note : Please skip this step if LATCH SWITCH feature is implemented, because a device can support either a latching switch or a momentary switch. - Please use Interactive mode to Verify the subscription of an event - Here the command to enter interactive mode:-- + On Raspi platform To trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor Dut should have capability to generate this event) - 1. ./chip-tool interactive start - 2. switch subscribe-event initial-press 1 100 1 1 + echo '{"Name":"InitialPress","NewPosition":1}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) - Verify InitialPress event with NewPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: + DUT generated the InitialPress event with NewPosition set to 1: + + [1697609895.678486][7384:7386] CHIP:-: Received payload: "{"Name":"InitialPress","NewPosition":1}" + [1697609895.678744][7384:7384] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4dbcc0be + [1697609895.678786][7384:7384] CHIP:-: The new position when the momentary switch starts to be pressed:1 + [1697609895.678800][7384:7384] CHIP:ZCL: SwitchServer: OnInitialPress + [1697609895.678917][7384:7384] CHIP:EVL: Copy Event to next buffer with priority 1 + [1697609895.678949][7384:7384] CHIP:EVL: LogEvent event number: 0x000000000000001D priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x1 Epoch timestamp: 0x0000018B416F4EFE + + switch read-event initial-press 1 1 - [1659695901.066563][3955:3960] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0001 - [1659695901.066583][3955:3960] CHIP:TOO: Event number: 46 - [1659695901.066602][3955:3960] CHIP:TOO: Priority: Info - [1659695901.066643][3955:3960] CHIP:TOO: Timestamp: 18095747 - [1659695901.066669][3955:3960] CHIP:TOO: InitialPress: { - [1659695901.066689][3955:3960] CHIP:TOO: NewPosition: 1 - [1659695901.066708][3955:3960] CHIP:TOO: } + Verify TH receives InitialPress event with NewPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: + + [1697609943.498311][7767:7769] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0001 + [1697609943.498313][7767:7769] CHIP:TOO: Event number: 29 + [1697609943.498315][7767:7769] CHIP:TOO: Priority: Info + [1697609943.498317][7767:7769] CHIP:TOO: Timestamp: 1697609895678 + [1697609943.498320][7767:7769] CHIP:TOO: InitialPress: { + [1697609943.498323][7767:7769] CHIP:TOO: NewPosition: 1 + [1697609943.498325][7767:7769] CHIP:TOO: } disabled: true - label: "Step 6k: Operator releases switch" @@ -981,21 +1138,31 @@ tests: verification: | Note : Please skip this step if LATCH SWITCH feature is implemented, because a device can support either a latching switch or a momentary switch. - Please use Interactive mode to Verify the subscription of an event - Here the command to enter interactive mode:-- + On Raspi platform To trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor Dut should have capability to generate this event) - 1. ./chip-tool interactive start - 2. switch subscribe-event short-release 1 100 1 1 + echo '{"Name":"ShortRelease","PreviousPosition":1}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) + + DUT generated the ShortRelease event with PreviousPosition set to 1: + + [1697610020.642902][7384:7386] CHIP:-: Received payload: "{"Name":"ShortRelease","PreviousPosition":1}" + [1697610020.643151][7384:7384] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4dbcc0bf + [1697610020.643184][7384:7384] CHIP:-: The the previous value of the CurrentPosition when the momentary switch has been released:1 + [1697610020.643194][7384:7384] CHIP:ZCL: SwitchServer: OnShortRelease + [1697610020.643356][7384:7384] CHIP:EVL: Dropped 1 event from buffer with priority 1 and event number 0x0000000000000005 due to overflow: event priority_level: 1 + [1697610020.643427][7384:7384] CHIP:EVL: Copy Event to next buffer with priority 1 + [1697610020.643456][7384:7384] CHIP:EVL: LogEvent event number: 0x000000000000001E priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x3 Epoch timestamp: 0x0000018B41713723 - Verify ShortRelease event with PreviousPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: + switch read-event short-release 1 1 - [1659694426.794832][3797:3802] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0003 - [1659694426.794853][3797:3802] CHIP:TOO: Event number: 38 - [1659694426.794873][3797:3802] CHIP:TOO: Priority: Info - [1659694426.794891][3797:3802] CHIP:TOO: Timestamp: 16840016 - [1659694426.794914][3797:3802] CHIP:TOO: ShortRelease: { - [1659694426.794934][3797:3802] CHIP:TOO: PreviousPosition: 1 - [1659694426.794952][3797:3802] CHIP:TOO: } + Verify TH receives ShortRelease event with PreviousPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: + + [1697610069.134658][7767:7769] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0003 + [1697610069.134661][7767:7769] CHIP:TOO: Event number: 30 + [1697610069.134663][7767:7769] CHIP:TOO: Priority: Info + [1697610069.134665][7767:7769] CHIP:TOO: Timestamp: 1697610020643 + [1697610069.134669][7767:7769] CHIP:TOO: ShortRelease: { + [1697610069.134672][7767:7769] CHIP:TOO: PreviousPosition: 1 + [1697610069.134675][7767:7769] CHIP:TOO: } disabled: true - label: @@ -1005,26 +1172,47 @@ tests: verification: | Note : Please skip this step if LATCH SWITCH feature is implemented, because a device can support either a latching switch or a momentary switch. - Please use Interactive mode to Verify the subscription of an event - Here the command to enter interactive mode:-- + On Raspi platform To trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor Dut should have capability to generate this event) - 1. ./chip-tool interactive start - 2. switch subscribe-event initial-press 1 100 1 1 + echo '{"Name":"InitialPress","NewPosition":1}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) - Verify InitialPress event with NewPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: + DUT generated the InitialPress event with NewPosition set to 1: - [1659694345.040034][3787:3792] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0001 - [1659694345.040059][3787:3792] CHIP:TOO: Event number: 37 - [1659694345.040083][3787:3792] CHIP:TOO: Priority: Info - [1659694345.040106][3787:3792] CHIP:TOO: Timestamp: 16729153 - [1659694345.040135][3787:3792] CHIP:TOO: InitialPress: { - [1659694345.040160][3787:3792] CHIP:TOO: NewPosition: 1 + [1697609895.678486][7384:7386] CHIP:-: Received payload: "{"Name":"InitialPress","NewPosition":1}" + [1697609895.678744][7384:7384] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4dbcc0be + [1697609895.678786][7384:7384] CHIP:-: The new position when the momentary switch starts to be pressed:1 + [1697609895.678800][7384:7384] CHIP:ZCL: SwitchServer: OnInitialPress + [1697609895.678917][7384:7384] CHIP:EVL: Copy Event to next buffer with priority 1 + [1697609895.678949][7384:7384] CHIP:EVL: LogEvent event number: 0x000000000000001D priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x1 Epoch timestamp: 0x0000018B416F4EFE - Please use Interactive mode to Verify the subscription of an event - Here the command to enter interactive mode:-- + switch read-event initial-press 1 1 - 1. ./chip-tool interactive start - 2. switch subscribe-event multi-press-ongoing 1 100 1 1 + Verify TH receives InitialPress event with NewPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: + + [1697609943.498311][7767:7769] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0001 + [1697609943.498313][7767:7769] CHIP:TOO: Event number: 29 + [1697609943.498315][7767:7769] CHIP:TOO: Priority: Info + [1697609943.498317][7767:7769] CHIP:TOO: Timestamp: 1697609895678 + [1697609943.498320][7767:7769] CHIP:TOO: InitialPress: { + [1697609943.498323][7767:7769] CHIP:TOO: NewPosition: 1 + [1697609943.498325][7767:7769] CHIP:TOO: } + + On Raspi platform To trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor Dut should have capability to generate this event) + + echo '{"Name":"MultiPressOngoing","NewPosition":1,"CurrentNumberOfPressesCounted":2}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) + + DUT generated the MultiPressongoing event with NewPosition set to 1 and CurrentNumberOfPressesCounted set to 2: + + [1697611293.571665][7384:7386] CHIP:-: Received payload: "{"Name":"MultiPressOngoing","NewPosition":1,"CurrentNumberOfPressesCounted":2}" + [1697611293.571907][7384:7384] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4dbcc0c4 + [1697611293.571940][7384:7384] CHIP:-: The new position when the momentary switch has been pressed in a multi-press sequence:1 + [1697611293.571949][7384:7384] CHIP:-: 2 times the momentary switch has been pressed + [1697611293.571955][7384:7384] CHIP:ZCL: SwitchServer: OnMultiPressOngoing + [1697611293.572127][7384:7384] CHIP:EVL: Dropped 1 event from buffer with priority 1 and event number 0x000000000000000A due to overflow: event priority_level: 1 + [1697611293.572215][7384:7384] CHIP:EVL: Copy Event to next buffer with priority 1 + [1697611293.572258][7384:7384] CHIP:EVL: LogEvent event number: 0x0000000000000023 priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x5 Epoch timestamp: 0x0000018B4184A383 + + switch read-event multi-press-ongoing 1 1 Verify MultiPressongoing event with NewPosition set to 1 and CurrentNumberOfPressesCounted set to 2 on TH chip-tool log and below is the sample log provided for the raspi platform: @@ -1043,21 +1231,31 @@ tests: verification: | Note : Please skip this step if LATCH SWITCH feature is implemented, because a device can support either a latching switch or a momentary switch. - Please use Interactive mode to Verify the subscription of an event - Here the command to enter interactive mode:-- + On Raspi platform To trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor Dut should have capability to generate this event) - 1. ./chip-tool interactive start - 2. switch subscribe-event short-release 1 100 1 1 + echo '{"Name":"ShortRelease","PreviousPosition":1}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) + + DUT generated the ShortRelease event with PreviousPosition set to 1: + + [1697610020.642902][7384:7386] CHIP:-: Received payload: "{"Name":"ShortRelease","PreviousPosition":1}" + [1697610020.643151][7384:7384] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4dbcc0bf + [1697610020.643184][7384:7384] CHIP:-: The the previous value of the CurrentPosition when the momentary switch has been released:1 + [1697610020.643194][7384:7384] CHIP:ZCL: SwitchServer: OnShortRelease + [1697610020.643356][7384:7384] CHIP:EVL: Dropped 1 event from buffer with priority 1 and event number 0x0000000000000005 due to overflow: event priority_level: 1 + [1697610020.643427][7384:7384] CHIP:EVL: Copy Event to next buffer with priority 1 + [1697610020.643456][7384:7384] CHIP:EVL: LogEvent event number: 0x000000000000001E priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x3 Epoch timestamp: 0x0000018B41713723 - Verify ShortRelease event with PreviousPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: + switch read-event short-release 1 1 - [1659694426.794832][3797:3802] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0003 - [1659694426.794853][3797:3802] CHIP:TOO: Event number: 38 - [1659694426.794873][3797:3802] CHIP:TOO: Priority: Info - [1659694426.794891][3797:3802] CHIP:TOO: Timestamp: 16840016 - [1659694426.794914][3797:3802] CHIP:TOO: ShortRelease: { - [1659694426.794934][3797:3802] CHIP:TOO: PreviousPosition: 1 - [1659694426.794952][3797:3802] CHIP:TOO: } + Verify TH receives ShortRelease event with PreviousPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: + + [1697610069.134658][7767:7769] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0003 + [1697610069.134661][7767:7769] CHIP:TOO: Event number: 30 + [1697610069.134663][7767:7769] CHIP:TOO: Priority: Info + [1697610069.134665][7767:7769] CHIP:TOO: Timestamp: 1697610020643 + [1697610069.134669][7767:7769] CHIP:TOO: ShortRelease: { + [1697610069.134672][7767:7769] CHIP:TOO: PreviousPosition: 1 + [1697610069.134675][7767:7769] CHIP:TOO: } disabled: true - label: @@ -1067,26 +1265,36 @@ tests: verification: | Note : Please skip this step if LATCH SWITCH feature is implemented, because a device can support either a latching switch or a momentary switch. - Please use Interactive mode to Verify the subscription of an event - Here the command to enter interactive mode:-- + On Raspi platform To trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor Dut should have capability to generate this event) - 1. ./chip-tool interactive start - 2. switch subscribe-event initial-press 1 100 1 1 + echo '{"Name":"InitialPress","NewPosition":1}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) - Verify InitialPress event with NewPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: + DUT generated the InitialPress event with NewPosition set to 1: + + [1697609895.678486][7384:7386] CHIP:-: Received payload: "{"Name":"InitialPress","NewPosition":1}" + [1697609895.678744][7384:7384] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4dbcc0be + [1697609895.678786][7384:7384] CHIP:-: The new position when the momentary switch starts to be pressed:1 + [1697609895.678800][7384:7384] CHIP:ZCL: SwitchServer: OnInitialPress + [1697609895.678917][7384:7384] CHIP:EVL: Copy Event to next buffer with priority 1 + [1697609895.678949][7384:7384] CHIP:EVL: LogEvent event number: 0x000000000000001D priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x1 Epoch timestamp: 0x0000018B416F4EFE - [1659694345.040034][3787:3792] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0001 - [1659694345.040059][3787:3792] CHIP:TOO: Event number: 37 - [1659694345.040083][3787:3792] CHIP:TOO: Priority: Info - [1659694345.040106][3787:3792] CHIP:TOO: Timestamp: 16729153 - [1659694345.040135][3787:3792] CHIP:TOO: InitialPress: { - [1659694345.040160][3787:3792] CHIP:TOO: NewPosition: 1 + switch read-event initial-press 1 1 - In Raspi platform to change the switch to second position use the below command, Pls use equivalent command on the respective DUT.open one more terminal on DUT side execute the echo command on that terminal. + Verify TH receives InitialPress event with NewPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: + + [1697609943.498311][7767:7769] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0001 + [1697609943.498313][7767:7769] CHIP:TOO: Event number: 29 + [1697609943.498315][7767:7769] CHIP:TOO: Priority: Info + [1697609943.498317][7767:7769] CHIP:TOO: Timestamp: 1697609895678 + [1697609943.498320][7767:7769] CHIP:TOO: InitialPress: { + [1697609943.498323][7767:7769] CHIP:TOO: NewPosition: 1 + [1697609943.498325][7767:7769] CHIP:TOO: } + + On Raspi platform To trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor Dut should have capability to generate this event) echo '{"Name":"MultiPressOngoing","NewPosition":1,"CurrentNumberOfPressesCounted":3}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) - Verify MultiPressongoing event with NewPosition set to 1 and CurrentNumberOfPressesCounted set to 3 on TH (all-cluster-app) log and below is the sample log provided for the raspi platform: + DUT generated the MultiPressongoing event with NewPosition set to 1 and CurrentNumberOfPressesCounted set to 3: [1686290991.699382][30125:30127] CHIP:-: Received payload: "{"Name":"MultiPressOngoing","NewPosition":1,"CurrentNumberOfPressesCounted":3}" [1686290991.699646][30125:30125] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 89759738 @@ -1094,13 +1302,9 @@ tests: [1686290991.699687][30125:30125] CHIP:-: 3 times the momentary switch has been pressed [1686290991.699694][30125:30125] CHIP:ZCL: SwitchServer: OnMultiPressOngoing - Please use Interactive mode to Verify the subscription of an event - Here the command to enter interactive mode:-- - - 1. ./chip-tool interactive start - 2. switch subscribe-event multi-press-ongoing 1 100 1 1 + switch read-event multi-press-ongoing 1 1 - Verify MultiPressongoing event with NewPosition set to 1 and CurrentNumberOfPressesCounted set to 3 on TH chip-tool log and below is the sample log provided for the raspi platform: + Verify TH receives MultiPressongoing event with NewPosition set to 1 and CurrentNumberOfPressesCounted set to 3 on TH chip-tool log and below is the sample log provided for the raspi platform: [1659698336.786184][4081:4086] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0005 [1659698336.786209][4081:4086] CHIP:TOO: Event number: 57 @@ -1117,21 +1321,31 @@ tests: verification: | Note : Please skip this step if LATCH SWITCH feature is implemented, because a device can support either a latching switch or a momentary switch. - Please use Interactive mode to Verify the subscription of an event - Here the command to enter interactive mode:-- + On Raspi platform To trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor Dut should have capability to generate this event) - 1. ./chip-tool interactive start - 2. switch subscribe-event short-release 1 100 1 1 + echo '{"Name":"ShortRelease","PreviousPosition":1}' > /tmp/chip_all_clusters_fifo_ (PID of DUT) + + DUT generated the ShortRelease event with PreviousPosition set to 1: + + [1697610020.642902][7384:7386] CHIP:-: Received payload: "{"Name":"ShortRelease","PreviousPosition":1}" + [1697610020.643151][7384:7384] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4dbcc0bf + [1697610020.643184][7384:7384] CHIP:-: The the previous value of the CurrentPosition when the momentary switch has been released:1 + [1697610020.643194][7384:7384] CHIP:ZCL: SwitchServer: OnShortRelease + [1697610020.643356][7384:7384] CHIP:EVL: Dropped 1 event from buffer with priority 1 and event number 0x0000000000000005 due to overflow: event priority_level: 1 + [1697610020.643427][7384:7384] CHIP:EVL: Copy Event to next buffer with priority 1 + [1697610020.643456][7384:7384] CHIP:EVL: LogEvent event number: 0x000000000000001E priority: 1, endpoint id: 0x1 cluster id: 0x0000_003B event id: 0x3 Epoch timestamp: 0x0000018B41713723 + + switch read-event short-release 1 1 - Verify ShortRelease event with PreviousPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: + Verify TH receives ShortRelease event with PreviousPosition set to 1 on TH chip-tool log and below is the sample log provided for the raspi platform: - [1659696223.568247][3981:3986] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0003 - [1659696223.568272][3981:3986] CHIP:TOO: Event number: 53 - [1659696223.568296][3981:3986] CHIP:TOO: Priority: Info - [1659696223.568319][3981:3986] CHIP:TOO: Timestamp: 18666186 - [1659696223.568348][3981:3986] CHIP:TOO: ShortRelease: { - [1659696223.568373][3981:3986] CHIP:TOO: PreviousPosition: 1 - [1659696223.568397][3981:3986] CHIP:TOO: } + [1697610069.134658][7767:7769] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0003 + [1697610069.134661][7767:7769] CHIP:TOO: Event number: 30 + [1697610069.134663][7767:7769] CHIP:TOO: Priority: Info + [1697610069.134665][7767:7769] CHIP:TOO: Timestamp: 1697610020643 + [1697610069.134669][7767:7769] CHIP:TOO: ShortRelease: { + [1697610069.134672][7767:7769] CHIP:TOO: PreviousPosition: 1 + [1697610069.134675][7767:7769] CHIP:TOO: } On Raspi platform To trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor Dut should have capability to generate this event) @@ -1144,13 +1358,9 @@ tests: [1659694592.348389][2530:2530] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to ee5e772b [1659694592.348481][2530:2530] CHIP:-: The new position when the momentary switch has been pressed in a multi-press sequence:1 - Please use Interactive mode to Verify the subscription of an event - Here the command to enter interactive mode:-- - - 1. ./chip-tool interactive start - 2. switch subscribe-event multi-press-complete 1 100 1 1 + switch read-event multi-press-complete 1 1 - Verify MultiPressonComplete event with PreviousPosition set to 1 and TotalNumberOfPressesCounted set to 3 on TH (chip-tool) log and below is the sample log provided for the raspi platform: + Verify TH receives MultiPressonComplete event with PreviousPosition set to 1 and TotalNumberOfPressesCounted set to 3 on TH (chip-tool) log and below is the sample log provided for the raspi platform: [1659695330.923244][3912:3918] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_003B Event 0x0000_0005 [1659695330.923264][3912:3918] CHIP:TOO: Event number: 45 diff --git a/src/app/tests/suites/certification/ci-pics-values b/src/app/tests/suites/certification/ci-pics-values index a4dcce73f08600..eb629bb708fdde 100644 --- a/src/app/tests/suites/certification/ci-pics-values +++ b/src/app/tests/suites/certification/ci-pics-values @@ -1134,7 +1134,7 @@ DGWIFI.S.A000b=1 DGWIFI.S.A000c=1 # Client DGWIFI.C=1 -DGWIFI.S.C00.Tx=0 +DGWIFI.C.C00.Tx=0 # Events DGWIFI.S.E00=1 DGWIFI.S.E01=1 diff --git a/zzz_generated/darwin-framework-tool/zap-generated/test/Commands.h b/zzz_generated/darwin-framework-tool/zap-generated/test/Commands.h index 1bb19ddf8d4d96..71266e224a1a6a 100644 --- a/zzz_generated/darwin-framework-tool/zap-generated/test/Commands.h +++ b/zzz_generated/darwin-framework-tool/zap-generated/test/Commands.h @@ -4813,8 +4813,8 @@ class Test_TC_ACE_1_5 : public TestCommandBridge { err = TestStep7Th1ReadsDescriptorClusterExpectSuccess_14(); break; case 15: - ChipLogProgress(chipTool, " ***** Test Step 15 : Step 8: TH1 reads basic cluster - expect UNSUPPORTED_ACCESS\n"); - err = TestStep8Th1ReadsBasicClusterExpectUnsupportedAccess_15(); + ChipLogProgress(chipTool, " ***** Test Step 15 : Step 8: TH1 reads DUT Endpoint 0 Basic Information cluster VendorID attribute - expect UNSUPPORTED_ACCESS\n"); + err = TestStep8Th1ReadsDutEndpoint0BasicInformationClusterVendorIDAttributeExpectUnsupportedAccess_15(); break; case 16: ChipLogProgress(chipTool, " ***** Test Step 16 : Step 9: TH2 reads descriptor cluster - expect UNSUPPORTED_ACCESS\n"); @@ -4833,20 +4833,20 @@ class Test_TC_ACE_1_5 : public TestCommandBridge { err = TestStep9Th2ReadsDescriptorClusterExpectUnsupportedAccess_17(); break; case 18: - ChipLogProgress(chipTool, " ***** Test Step 18 : Step 10: TH2 reads basic cluster - expect SUCCESS\n"); + ChipLogProgress(chipTool, " ***** Test Step 18 : Step 10: TH2 reads DUT Endpoint 0 Basic Information cluster VendorID attribute - expect SUCCESS\n"); if (ShouldSkip("PICS_SDK_CI_ONLY")) { NextTest(); return; } - err = TestStep10Th2ReadsBasicClusterExpectSuccess_18(); + err = TestStep10Th2ReadsDutEndpoint0BasicInformationClusterVendorIDAttributeExpectSuccess_18(); break; case 19: - ChipLogProgress(chipTool, " ***** Test Step 19 : Step 10: TH2 reads basic cluster - expect SUCCESS\n"); + ChipLogProgress(chipTool, " ***** Test Step 19 : Step 10: TH2 reads DUT Endpoint 0 Basic Information cluster VendorID attribute - expect SUCCESS\n"); if (ShouldSkip("PICS_SKIP_SAMPLE_APP")) { NextTest(); return; } - err = TestStep10Th2ReadsBasicClusterExpectSuccess_19(); + err = TestStep10Th2ReadsDutEndpoint0BasicInformationClusterVendorIDAttributeExpectSuccess_19(); break; case 20: ChipLogProgress(chipTool, " ***** Test Step 20 : Step 11: TH1 resets ACL to default\n"); @@ -5286,7 +5286,7 @@ class Test_TC_ACE_1_5 : public TestCommandBridge { return CHIP_NO_ERROR; } - CHIP_ERROR TestStep8Th1ReadsBasicClusterExpectUnsupportedAccess_15() + CHIP_ERROR TestStep8Th1ReadsDutEndpoint0BasicInformationClusterVendorIDAttributeExpectUnsupportedAccess_15() { MTRBaseDevice * device = GetDevice("alpha"); @@ -5294,7 +5294,7 @@ class Test_TC_ACE_1_5 : public TestCommandBridge { VerifyOrReturnError(cluster != nil, CHIP_ERROR_INCORRECT_STATE); [cluster readAttributeVendorIDWithCompletion:^(NSNumber * _Nullable value, NSError * _Nullable err) { - NSLog(@"Step 8: TH1 reads basic cluster - expect UNSUPPORTED_ACCESS Error: %@", err); + NSLog(@"Step 8: TH1 reads DUT Endpoint 0 Basic Information cluster VendorID attribute - expect UNSUPPORTED_ACCESS Error: %@", err); VerifyOrReturn(CheckValue("status", err ? ([err.domain isEqualToString:MTRInteractionErrorDomain] ? err.code : EMBER_ZCL_STATUS_FAILURE) : 0, EMBER_ZCL_STATUS_UNSUPPORTED_ACCESS)); NextTest(); @@ -5330,7 +5330,7 @@ class Test_TC_ACE_1_5 : public TestCommandBridge { return UserPrompt("alpha", value); } - CHIP_ERROR TestStep10Th2ReadsBasicClusterExpectSuccess_18() + CHIP_ERROR TestStep10Th2ReadsDutEndpoint0BasicInformationClusterVendorIDAttributeExpectSuccess_18() { MTRBaseDevice * device = GetDevice("beta"); @@ -5338,7 +5338,7 @@ class Test_TC_ACE_1_5 : public TestCommandBridge { VerifyOrReturnError(cluster != nil, CHIP_ERROR_INCORRECT_STATE); [cluster readAttributeVendorIDWithCompletion:^(NSNumber * _Nullable value, NSError * _Nullable err) { - NSLog(@"Step 10: TH2 reads basic cluster - expect SUCCESS Error: %@", err); + NSLog(@"Step 10: TH2 reads DUT Endpoint 0 Basic Information cluster VendorID attribute - expect SUCCESS Error: %@", err); VerifyOrReturn(CheckValue("status", err ? err.code : 0, 0)); @@ -5348,7 +5348,7 @@ class Test_TC_ACE_1_5 : public TestCommandBridge { return CHIP_NO_ERROR; } - CHIP_ERROR TestStep10Th2ReadsBasicClusterExpectSuccess_19() + CHIP_ERROR TestStep10Th2ReadsDutEndpoint0BasicInformationClusterVendorIDAttributeExpectSuccess_19() { chip::app::Clusters::LogCommands::Commands::UserPrompt::Type value; diff --git a/zzz_generated/placeholder/app1/zap-generated/test/Commands.h b/zzz_generated/placeholder/app1/zap-generated/test/Commands.h index 09f959a75058dc..35de801fb5d94d 100644 --- a/zzz_generated/placeholder/app1/zap-generated/test/Commands.h +++ b/zzz_generated/placeholder/app1/zap-generated/test/Commands.h @@ -320,7 +320,7 @@ class Test_TC_DGWIFI_3_2_SimulatedSuite : public TestCommand { case 0: { LogStep(0, "DUT sends ResetCounts command to TH"); - VerifyOrDo(!ShouldSkip("DGWIFI.S.C00.Tx"), return ContinueOnChipMainThread(CHIP_NO_ERROR)); + VerifyOrDo(!ShouldSkip("DGWIFI.C.C00.Tx"), return ContinueOnChipMainThread(CHIP_NO_ERROR)); return WaitCommand(GetEndpoint(0), WiFiNetworkDiagnostics::Id, WiFiNetworkDiagnostics::Commands::ResetCounts::Id); } } diff --git a/zzz_generated/placeholder/app2/zap-generated/test/Commands.h b/zzz_generated/placeholder/app2/zap-generated/test/Commands.h index 09f959a75058dc..35de801fb5d94d 100644 --- a/zzz_generated/placeholder/app2/zap-generated/test/Commands.h +++ b/zzz_generated/placeholder/app2/zap-generated/test/Commands.h @@ -320,7 +320,7 @@ class Test_TC_DGWIFI_3_2_SimulatedSuite : public TestCommand { case 0: { LogStep(0, "DUT sends ResetCounts command to TH"); - VerifyOrDo(!ShouldSkip("DGWIFI.S.C00.Tx"), return ContinueOnChipMainThread(CHIP_NO_ERROR)); + VerifyOrDo(!ShouldSkip("DGWIFI.C.C00.Tx"), return ContinueOnChipMainThread(CHIP_NO_ERROR)); return WaitCommand(GetEndpoint(0), WiFiNetworkDiagnostics::Id, WiFiNetworkDiagnostics::Commands::ResetCounts::Id); } }