Closed Ashwinigrl closed 3 months ago
Based on discussion in DM TT and EM TT on 1st Aug - we plan now to disallow the OnMode and StartUpMode attributes in the DEMM, EVSEM and WHMM clusters - I will reference this issue in the PR.
These attributes don't make sense for DEM, EVSE and WHM - like the Microwave Oven etc.
Feature Area
Other
Test Case
TC-EEVSEM-3.3
Reproduction steps
Execute the below mentioned command to put DUT into a commissionable state :
./chip-all-clusters-app
Once DUT reach the commissionable state sent below mentioned command on TH.
./chip-tool pairing onnetwork 1 20202021
Once after successful pairing provide the below commands:
./chip-tool energyevsemode read start-up-mode 1 1
./chip-tool energyevsemode read on-mode 1 1
./chip-tool onoff write start-up-on-off 1 1 1
Physically power cycle the device
./chip-tool energyevsemode read start-up-mode 1 1
./chip-tool energyevsemode read current-mode 1 1
Actual Outcome:
Expected Outcome:
Bug prevalence
Whenever I do
GitHub hash of the SDK that was being used
f6022e4b0ff020835f02b85e13875e51a0de3d19
Platform
raspi
Anything else?
As per the Modebase Spec, If the On/Off feature is supported and the On/Off cluster attribute StartUpOnOff is present, with a value of On (turn on at power up), then the CurrentMode attribute SHALL be set to the OnMode attribute value when the server is supplied with power, except if the OnMode attribute is null. However, in the Energy EVSE Mode Cluster, the value of the CurrentMode is not being set to the OnMode value after powering up the DUT in the current SDK.
Test step that require Review: Step 12
Spec References:
Test plan References:
Note: This functionality is working fine in other mode-based clusters, such as the Laundry Washer Mode Cluster and the Dishwasher Mode Cluster
Reference Log: TC-EEVSEM-3.3.txt