Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SQA] TC-DM-4.3 TH fails to read the Networks & InterfaceEnabled attributes from the DUT #17535

Closed
Survensa opened this issue Apr 20, 2022 · 0 comments · Fixed by #17802
Closed
Assignees

Comments

@Survensa
Copy link

Issue : As per the test case TC-DM-4.3 step 7 & 8, TH should read the Networks attribute list and InterfaceEnabled attribute from the DUT

Referance : https://github.com/CHIP-Specifications/chip-test-plans/blob/master/src/devicemanagement.adoc#test-procedure-13

Commit used : 20e1a4a
Platform : Ethernet (RPI)

Command used :

  1. To read Networks attribute list - ./chip-tool networkcommissioning read networks 1 0
  • Expected outcome : 1 entries
  • Actual outcome : 0 entries

Error log :

[1650443874.189508][7592:7597] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0031 Attribute 0x0000_0001 DataVersion: 1433014033
[1650443874.189593][7592:7597] CHIP:TOO:   Networks: 0 entries
[1650443874.189705][7592:7597] CHIP:EM: Sending Standalone Ack for MessageCounter:2361310 on exchange 58583i
  1. To read InterfaceEnabled attribute - ./chip-tool networkcommissioning read interface-enabled 1 0
  • Expected outcome : InterfaceEnabled: TRUE
  • Actual outcome : InterfaceEnabled: FALSE

Error log :

[1650443943.690887][7602:7607] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0031 Attribute 0x0000_0004 DataVersion: 1433014033
[1650443943.690945][7602:7607] CHIP:TOO:   InterfaceEnabled: FALSE
[1650443943.691055][7602:7607] CHIP:EM: Sending Standalone Ack for MessageCounter:4040988 on exchange 36954i

Full log :
TC_NC-4.3.txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants