Part 1: feature/temperature measurement cluster

[ghost]

Problem

Update the temperature measurement cluster implementation. It still used the old emberAfPlugin API.

Change overview

• added emberAfTemperatureMeasurementClusterServerInitCallback support
• update temperature-measurement-server.cpp impl.
• best effort fix of temperature-example app (not tested, because lack of HW)

Testing

Tested on custom accessory with real temperature sensor. Test setup was similar to TE2.

HW Platform

Nordic nRF52840

Notes

Related PRs

• Part 4: feature/binary input basic cluster #7032
• Part 2: feature/relative humidity measurement cluster #7028
• Part 3: feature/air pressure measurement cluster #7030

[vivien-apple]

Should we check that value is between MinMeasureValue and MaxMeasuredValue or 0x8000 (unknown) ?

One way to get this feature without any efforts would be to update the EmberAfAttributeMetadata of the attribute to points to the value of MinMeasureValue and MaxMeasureValue, based on the definition from the XML cluster definition, but I don't think this is supported at the moment.

[ghost]

I think we should leverage the GENERATED_ATTRIBUTES table which is generated in endpoints_config.h for the default min max values. And also add this checks as part of the general code in the attribute storage?

[vivien-apple]

I think we should leverage the GENERATED_ATTRIBUTES table which is generated in endpoints_config.h for the default min max values. And also add this checks as part of the general code in the attribute storage?

I do agree. But at the moment the min/max value from the attribute store only support absolute values, not values relative to others attributes.

[vivien-apple]

Approving for TE3.

Note that I think src/app/clusters/temperature-measurement-server should be removed completely. It seems like the result of this PR is mostly to expose a set of accessors to facilitate the manipulation of the temperature measurement cluster attributes.
It makes perfect sense to facilitate it imho, but I would rather prefer to autogenerate helpers code such as what is proposed in #7183, instead of having a lot of new clusters introduced into src/app/clusters.

[bzbarsky-apple]

No need to add it here if there is not in fact an init callback.

[github-actions]

Size increase report for "esp32-example-build" from b4d7048

File	Section	File	VM
chip-all-clusters-app.elf	.flash.rodata	-24	-24
chip-all-clusters-app.elf	.flash.text	-84	-84

Full report output

BLOAT REPORT

Files found only in the build output:
    report.csv

Comparing ./master_artifact/chip-pigweed-app.elf and ./pull_artifact/chip-pigweed-app.elf:

sections,vmsize,filesize

Comparing ./master_artifact/chip-all-clusters-app.elf and ./pull_artifact/chip-all-clusters-app.elf:

sections,vmsize,filesize
.debug_str,0,266
.debug_loc,0,172
.debug_line,0,55
.debug_frame,0,48
.debug_info,0,37
[Unmapped],0,24
.debug_aranges,0,16
.debug_ranges,0,16
.xt.prop._ZTVN4chip11DeviceLayer37DeviceNetworkProvisioningDelegateImplE,0,-1
.flash.rodata,-24,-24
.symtab,0,-32
.flash.text,-84,-84
.strtab,0,-116
.debug_abbrev,0,-149