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

[CERT-TEST-FAILURE] - TC-DEM-1.1 - Test failed #31578

Closed
KishokG opened this issue Jan 22, 2024 · 3 comments · Fixed by #31663
Closed

[CERT-TEST-FAILURE] - TC-DEM-1.1 - Test failed #31578

KishokG opened this issue Jan 22, 2024 · 3 comments · Fixed by #31663
Assignees
Labels
app-clusters Application cluster work bug Something isn't working cert blocker energy DEM needs triage

Comments

@KishokG
Copy link

KishokG commented Jan 22, 2024

Feature Area

Other

Test Case

TC-DEM-1.1

Reproduction steps

  1. Bring up the DUT with All-clusters-app.
  2. Pair the DUT using chip-tool through "Onnetwork" transport.
  3. Run the command ./chip-tool deviceenergymanagement read feature-map 1 1

Expected Outcome:

[1705565302.904580][7054:7056] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0098 Attribute 0x0000_FFFC DataVersion: 1117764527
[1705565302.904631][7054:7056] CHIP:TOO: FeatureMap: 31

Actual Outcome:

[1705565302.904580][7054:7056] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0098 Attribute 0x0000_FFFC DataVersion: 1117764527
[1705565302.904631][7054:7056] CHIP:TOO: FeatureMap: 127

Bug prevalence

Whenever I try to read FeatureMap.

GitHub hash of the SDK that was being used

0ff709f

Platform

raspi

Anything else?

In SPEC, the ForecastAdjustment(FA) and ConstraintBasedAdjustment(CON) feature is PROVISIONAL but in ACA these features are enabled. So FA and CON features has to be disabled in ACA as it is provisional.

Specification Reference:
image

@jamesharrow
Copy link
Contributor

I think this Issue may be raised incorrectly since in order to support PA,STA, PAU features you need to support SFR or PFR as well.
If you support PFR you may optionally also support SFR, and vice versa (if you support SFR you may optionally also support PFR).

So at the very least the expected value should allow 0x1F (both SFR & PFR), 0x1b (PFR is on), or 0x17 (SFR is on).

The other question is just because a feature is marked as provisional in the AppClusters spec, should we be stopping these features being enabled and failing them? @cecille raised this question yesterday.
The current test plan says that they shall not be set. But maybe the test plan needs changing here?

@jamesharrow
Copy link
Contributor

NOTE:
The test spec PR https://github.com/CHIP-Specifications/chip-test-plans/pull/3866 should have been used for the testing.

@jamesharrow
Copy link
Contributor

Based on discussion with Cecille, and clarification that '31' is a decimal value = 0x1F.
I will update the EnergyManagementApp to remove bits 5 & 6

jamesharrow added a commit to jamesharrow/connectedhomeip that referenced this issue Jan 24, 2024
@jamesharrow jamesharrow added app-clusters Application cluster work energy DEM labels Jan 24, 2024
@jamesharrow jamesharrow moved this from Todo to In Progress in [Grouping] Energy Management Jan 24, 2024
@mergify mergify bot closed this as completed in #31663 Jan 25, 2024
mergify bot pushed a commit that referenced this issue Jan 25, 2024
@github-project-automation github-project-automation bot moved this from Open Cert Blockers to Complete in [Certification] Blockers Jan 25, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Done in [Grouping] Energy Management Jan 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment