Add aqara E1 Thermostat v0.0.0_1030

[juliansteenbakker]

OTA file

20230221165005_OTA_lumi.airrtc.agl001_0.0.0_1030_20230220_712488.ota.zip

Manufacturer name

Aqara

Release notes

No response

How to handle existing images of the same type

Keep all (standard)

Optional metadata

No response

Checklist

• The OTA image provided is in a supported format (e.g., .zigbee, .ota, or a ZIP containing one of these)
• I have filled out the release notes to the best of my ability
• The OTA image is tested and verified to work on a physical device

Additional information

No response

[TheJulianJES]

Thanks for submitting the update! If I recall correctly, the E1 thermostat has some weird quirks where it reports a wrong version on the sw_build_id attribute. That doesn't matter for us, but I can't remember if the OTA query current_file_version (and current_file_version attribute on the OTA cluster) report the correct firmware versions, matching the one from the images.

I have some E1 thermostats somewhere, so I'll see if I can find that out.

Also for reference, here are all E1 TRV PRs for the Z2M OTA repo. I'm not sure if there were any issues with the updates:

• Add lumi.airrtc.agl001 0.0.0_0925 OTA Koenkk/zigbee-OTA#195
• Change URL of OTA file for Xiaomi SRTS-A01 Koenkk/zigbee-OTA#272
• Update OTA file for Xiaomi SRTS-A01 Koenkk/zigbee-OTA#275
• Update OTA file for Xiaomi SRTS-A01 Koenkk/zigbee-OTA#269

[TheJulianJES]

Ugh, yeah. Z2M hardcodes some Aqara model IDs to use a different current_file_version from an Aqara-specific attribute report.

• Original implementation in zigbee-herdsman-converters: Koenkk/zigbee-herdsman-converters@e15715e
• Later moved to zigbee-herdsman (as OTA logic lives here now): https://github.com/Koenkk/zigbee-herdsman/blob/4a3d508e9de844079c664cbc85e90341d873ffc0/src/controller/model/device.ts#L1507-L1517

The device reports 30 (or some other low number) for the current_file_version, but the images all use a much higher one. So even when the update is already installed, the update entity will still show "update available". That's what we need to fix before rolling it out to everyone.

We definitely don't want any device-specific logic in zigpy. You could already hijack the OTA current_file_version attribute read as well as the OTA query command using quirks, but that isn't that great.
I think there was some intention to basically allow for overriding (certain properties of) update entities using quirks. We'll have to look into that before we can continue with this OTA.

If needed, it can already be applied locally. For that, see the advanced provider here: https://github.com/zigpy/zigpy/wiki/OTA-Configuration. After installing it, the OTA file can be removed, or the "update to the same version" can be ignored.

[juliansteenbakker]

Thanks for the detailed info! I guess the bypass using quirks is depending on this PR right? zigpy/zha-device-handlers#4604

[Hedda]

I guess the bypass using quirks is depending on this PR right? zigpy/zha-device-handlers#4604

For reference, FYI, there is also another PR from the same zha-quirk author that will add further enhancements (which depends on it):

• Aqara E1 TRV: Add feature enhancements (heartbeat, running_state, calibrate) zha-device-handlers#4657

  • Migrate Aqara E1 TRV (AGL001) to QuirkBuilder v2 API zha-device-handlers#4604

(Looks like those among other improvements will add base class handles standard attributes for firmware version + more).

"Both PRs passed CI and are ready for review. Together they would significantly improve the Aqara E1 TRV experience in ZHA."