[TC-FLW-2.1] MaxMeasuredValue attribute value mismatches from specification #27543
Labels
app-clusters
Application cluster work
bug
Something isn't working
cert blocker
examples
needs owner
needs triage
spec
Mismatch between spec and implementation
Milestone
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
Verify the commissioning completed with success on TH(chip-tool) from DUT
TH reads from the DUT the MinMeasuredValue attribute : ./chip-tool flowmeasurement read min-measured-value 1 1
TH reads from the DUT the MaxMeasuredValue attribute : ./chip-tool flowmeasurement read max-measured-value 1 1
Bug prevalence
Everytime
GitHub hash of the SDK that was being used
Master - 7806dd1
Platform
raspi
Platform Version(s)
RPI4 8GB RAM
Summary
As per specifications, MaxMeasuredValue attribute represents the maximum value that can be measured for the MeasuredValue attribute and value should be in the range of MinMeasuredValue+1 to 65534.
In Master commit Minmeasured value is 0. Maxmeasured value should be in the range of 1 to 65534(MinMeasuredValue + 1 to 65534). But the currently Maxmeasured value is 0.
PFA Spec screenshot
./chip-tool flowmeasurement read min-measured-value 1 1
./chip-tool flowmeasurement read max-measured-value 1 1
PFA reference log :
TC-FLW-2.1.txt
The text was updated successfully, but these errors were encountered: