[TE9] Get UNSUPPORTED_ATTRIBUTE of read command on DL-3.1 #18492
Assignees
Labels
Comments
|
It's probably better to use the example door lock app for testing door lock bits.... |
|
@bzbarsky-apple
`############### Step 8 ###############``############### Step 20 ###############``############### Step 22 ###############` |
|
@cabin15 Thank you! Those are definitely wrong: they should either succeed or return UNSUPPORTED_ATTRIBUTE... |
|
And to be clear, these are optional attributes, so the tests should allow them to not exist. @cjandhyala can you please make sure the test plans handle these attributes being missing (including the LOG feature not being supported) properly? |
|
@bzbarsky-apple @andy31415 , the test plan needs to be updated. Not a SDK issue. @cabin15 pls chk with the test plan owner and close the issue. |
|
SDK Spec Review: Assigning to @bzbarsky-apple to update lock items. |
bzbarsky-apple
added a commit
to bzbarsky-apple/connectedhomeip
that referenced
this issue
Jun 1, 2022
* The LOG feature is "[Zigbee]" in the device library, and the Door Lock cluster spec says: "If Events are supported the logging feature SHALL NOT be supported.". That means the following attributes are not part of Matter: * NumberOfLogRecordsSupported * EnableLogging and neither are the following commands: * Get Log Record * Get Log Record Response * The NOT feature is "[Zigbee]" in the device library. Again, events replace it in Matter. That means the following attributes are not part of Matter: * KeypadOperationEventMask * RemoteOperationEventMask * ManualOperationEventMask * RFIDOperationEventMask * KeypadProgrammingEventMask * RemoteProgrammingEventMask * RFIDProgrammingEventMask and neither are the following commands: * Operating Event Notification * Programming Event Notification * The Alarms conformance is Zigbee-only in the device library, so the AlarmMask attribute is not part of Matter. * The USR feature is required in Matter if any of PIN, RID, FPG, FACE are supported. That means anything conditioned on !USR and those features is not part of Matter. Specifically, that is the following commands: * Set PIN Code * Get PIN Code * Get PIN Code Response * Clear PIN Code * Clear All PIN Codes * Set User Status * Get User Status * Get User Status Response * Set User Type * Get User Type * Get User Type Response * Set RFID Code * Get RFID Code * Get RFID Code Response * Clear RFID Code * Clear All RFID Codes Fixes project-chip#18492 by making it clear that these are not part of Matter and hence not to be tested in Matter certification.
bzbarsky-apple
added a commit
to bzbarsky-apple/connectedhomeip
that referenced
this issue
Jun 2, 2022
* The LOG feature is "[Zigbee]" in the device library, and the Door Lock cluster spec says: "If Events are supported the logging feature SHALL NOT be supported.". That means the following attributes are not part of Matter: * NumberOfLogRecordsSupported * EnableLogging and neither are the following commands: * Get Log Record * Get Log Record Response * The NOT feature is "[Zigbee]" in the device library. Again, events replace it in Matter. That means the following attributes are not part of Matter: * KeypadOperationEventMask * RemoteOperationEventMask * ManualOperationEventMask * RFIDOperationEventMask * KeypadProgrammingEventMask * RemoteProgrammingEventMask * RFIDProgrammingEventMask and neither are the following commands: * Operating Event Notification * Programming Event Notification * The Alarms conformance is Zigbee-only in the device library, so the AlarmMask attribute is not part of Matter. * The USR feature is required in Matter if any of PIN, RID, FPG, FACE are supported. That means anything conditioned on !USR and those features is not part of Matter. Specifically, that is the following commands: * Set PIN Code * Get PIN Code * Get PIN Code Response * Clear PIN Code * Clear All PIN Codes * Set User Status * Get User Status * Get User Status Response * Set User Type * Get User Type * Get User Type Response * Set RFID Code * Get RFID Code * Get RFID Code Response * Clear RFID Code * Clear All RFID Codes Fixes project-chip#18492 by making it clear that these are not part of Matter and hence not to be tested in Matter certification.
bzbarsky-apple
added a commit
to bzbarsky-apple/connectedhomeip
that referenced
this issue
Jun 2, 2022
* The LOG feature is "[Zigbee]" in the device library, and the Door Lock cluster spec says: "If Events are supported the logging feature SHALL NOT be supported.". That means the following attributes are not part of Matter: * NumberOfLogRecordsSupported * EnableLogging and neither are the following commands: * Get Log Record * Get Log Record Response * The NOT feature is "[Zigbee]" in the device library. Again, events replace it in Matter. That means the following attributes are not part of Matter: * KeypadOperationEventMask * RemoteOperationEventMask * ManualOperationEventMask * RFIDOperationEventMask * KeypadProgrammingEventMask * RemoteProgrammingEventMask * RFIDProgrammingEventMask and neither are the following commands: * Operating Event Notification * Programming Event Notification * The Alarms conformance is Zigbee-only in the device library, so the AlarmMask attribute is not part of Matter. * The USR feature is required in Matter if any of PIN, RID, FPG, FACE are supported. That means anything conditioned on !USR and those features is not part of Matter. Specifically, that is the following commands: * Set PIN Code * Get PIN Code * Get PIN Code Response * Clear PIN Code * Clear All PIN Codes * Set User Status * Get User Status * Get User Status Response * Set User Type * Get User Type * Get User Type Response * Set RFID Code * Get RFID Code * Get RFID Code Response * Clear RFID Code * Clear All RFID Codes Fixes project-chip#18492 by making it clear that these are not part of Matter and hence not to be tested in Matter certification.
andy31415
pushed a commit
that referenced
this issue
Jun 2, 2022
* The LOG feature is "[Zigbee]" in the device library, and the Door Lock cluster spec says: "If Events are supported the logging feature SHALL NOT be supported.". That means the following attributes are not part of Matter: * NumberOfLogRecordsSupported * EnableLogging and neither are the following commands: * Get Log Record * Get Log Record Response * The NOT feature is "[Zigbee]" in the device library. Again, events replace it in Matter. That means the following attributes are not part of Matter: * KeypadOperationEventMask * RemoteOperationEventMask * ManualOperationEventMask * RFIDOperationEventMask * KeypadProgrammingEventMask * RemoteProgrammingEventMask * RFIDProgrammingEventMask and neither are the following commands: * Operating Event Notification * Programming Event Notification * The Alarms conformance is Zigbee-only in the device library, so the AlarmMask attribute is not part of Matter. * The USR feature is required in Matter if any of PIN, RID, FPG, FACE are supported. That means anything conditioned on !USR and those features is not part of Matter. Specifically, that is the following commands: * Set PIN Code * Get PIN Code * Get PIN Code Response * Clear PIN Code * Clear All PIN Codes * Set User Status * Get User Status * Get User Status Response * Set User Type * Get User Type * Get User Type Response * Set RFID Code * Get RFID Code * Get RFID Code Response * Clear RFID Code * Clear All RFID Codes Fixes #18492 by making it clear that these are not part of Matter and hence not to be tested in Matter certification.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
Controller: My DUT
Controlee: all-clusters-app of test Harness image on rpi4
When reading attribute of doorlock cluster from all-clusters-app, my DUT got UNSUPPORTED_ATTRIBUTE return.
Belows are the attribute that failed to read.
Expected result
ReportDataMesage should be displayed like below.
May 11 08:19:15 = chip-service[10172]: ReportDataMessage =
May 11 08:19:15 = chip-service[10172]: {
May 11 08:19:15 = chip-service[10172]: AttributeReportIBs =
May 11 08:19:15 = chip-service[10172]: [
May 11 08:19:15 = chip-service[10172]: AttributeReportIB =
May 11 08:19:15 = chip-service[10172]: {
May 11 08:19:15 = chip-service[10172]: AttributeDataIB =
May 11 08:19:15 = chip-service[10172]: {
May 11 08:19:15 = chip-service[10172]: DataVersion = 0xc5550562,
May 11 08:19:15 = chip-service[10172]: AttributePathIB =
May 11 08:19:15 = chip-service[10172]: {
May 11 08:19:15 = chip-service[10172]: Endpoint = 0x1,
May 11 08:19:15 = chip-service[10172]: Cluster = 0x101,
May 11 08:19:15 = chip-service[10172]: Attribute = 0x0000_0001,
May 11 08:19:15 = chip-service[10172]: }
May 11 08:19:15 = chip-service[10172]:
May 11 08:19:15 = chip-service[10172]: Data = 0,
May 11 08:19:15 = chip-service[10172]: },
May 11 08:19:15 = chip-service[10172]:
May 11 08:19:15 = chip-service[10172]: },
May 11 08:19:15 = chip-service[10172]:
May 11 08:19:15 = chip-service[10172]: ],
May 11 08:19:15 = chip-service[10172]:
May 11 08:19:15 = chip-service[10172]: SuppressResponse = true,
May 11 08:19:15 = chip-service[10172]: InteractionModelRevision = 1
May 11 08:19:15 = chip-service[10172]: }
May 11 08:19:15 = chip-service[10172]: ----------->Endpoint: 1 Cluster: 0x0000_0101 Attribute 0x0000_0001DataVersion: 3310683490
May 11 08:19:15 = chip-service[10172]: attributeValue: 0
Actual result
May 11 08:28:03 = chip-service[10172]: Response Failure: IM Error 0x00000586: General error: 0x86 (UNSUPPORTED_ATTRIBUTE)Observation:
It is reproduced same using chip-tool on test harness.
TE9-TC-DL-3.1.txt
The text was updated successfully, but these errors were encountered: