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

Tolerance attribute not present for Mac_Chip_Tool in Flow Measurement Cluster, Relative Humidity Measurement Cluster, Temperature Measurement Cluster #9794

Closed
Garik098 opened this issue Sep 17, 2021 · 2 comments · Fixed by #10967

Comments

@Garik098
Copy link

While checking the Tolerance attribute on FlowMeasurement Cluster, RelativeHumidityMeasurement Cluster and TemperatureMeasurement Cluster, the attribute is not present for the Mac_Chip_Tool even though it is present to check via ZCLread.

FlowMeasurement Cluster:
Testcase: 3.2.1. [TC-FLW-2.1] Attributes with server as DUT
Step: 4
ZCL Command: zclread FlowMeasurement Tolerance 12344321 1 0

RelativeHumidityMeasurement Cluster:
TestCase: 3.2.1. [TC-RH-2.1] Attributes with server as DUT
Step: 3
ZCL Command: zclread RelativeHumidityMeasurement Tolerance 12344321 1 0

TemperatureMeasurement Cluster:
Testcase: 3.2.1. [TC-TM-2.1] Attributes with server as DUT
Step: 3
ZCL Command: zclread TemperatureMeasurement Tolerance 12344321 1 0

Here are the attachments for the missing Tolerance attribute,

FlowMeasurement

RelativehumidityMeasurement

TemperatureMeasurement

>
@franck-apple franck-apple assigned ghost Oct 18, 2021
@Garik098
Copy link
Author

TE#6 testing update:

Observing the same issue as above in TE#6 testing as well.

@ghost
Copy link

ghost commented Oct 26, 2021

Well, this is a general issue, because most of the time only the mandatory attributes where enabled. So I can fix this. But there are a lot of different clusters where you might encounter the same problem.

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.

1 participant