ZHA OTA Firmware Update / Upgrade

[Bigrob55]

What are the details of the device you wish up upgrade the firmware on?

[GleDel]

Mostly Aquara devices:

• door sensors (lumi.sensor_magnet.aq2)
• FP1 sensors (lumi.motion.ac01)
• Smart plugs (lumi.plug.maeu01)
• Temperature/humidity Sensors (lumi.weather)

And a couple of smart outlets from Blitzwolf:

• TS011F (by _TZ3000_amdymr7l )

[victorigualada]

Thanks for pointing that out. Fixed now!

[Hedda]

FYI, an Home Assistant developer is currently working on support for ZHA UI update platform and zigpy OTA dependencies to allow for easy OTAU updates per Zigbee device, and once implemented it will be enabled by default for products where manufacturers provide public links to firmware images (which sadly is not that many as of yet so consider contacting manufacturers for products that you buy and encourage them to do so):

ZHA integration UI options to apply OTA firmware update (OTAU) per Zigbee device?

Request Home Assistant frontend devs add UI options to ZHA integration for OTA firmware update(s). Please see related zigpy development discussion → https://github.com/zigpy/zigpy/discussions/951 Back-story; This feature request for ZHA’s UI to feature “Update Device Firmware” function for OTA firmware updates of Zigbee devices is a continuation of the ZHA OTA updates notification idea related to “zha-toolkit” discussion with @le_top here → [Feature] Notify OTA updates · Issue #24 · mdeweerd/z…

OTA Information for Manufacturers

OTA Device Firmware Updates

Update OTA handling

Add update platform to ZHA (bumps zigpy to 0.61.0)

[Hedda]

FYI, those pull requests by dmulcahey has now been merged so this should be in Home Assistant 2024.2

Add update platform to ZHA (bumps zigpy to 0.61.0)

Update OTA handling

2024.2: Beta release notes

Update entities for ZHA devices

ZHA (Zigbee Home Automation, our built-in Zigbee integration) now provides update entities to Home Assistant!

This means you can get notified when a device has a firmware update available, and you can trigger the update from Home Assistant!

Noticed the weird version numbers? Unfortunately, that is how version numbers in the Zigbee standard work and look, we currently have no way to translate them to something more human-readable format.

Currently, it supports updating Inovelli, OSRAM/Ledvance, Sonoff, and ThirdReality devices, and we are looking at adding support for more brands in the future.

Note! Manufacturers must add public URL in zigpy for OTA update images for automatic download, see:

• OTA Information for Manufacturers · zigpy/zigpy Wiki · GitHub

Sadly not many manufacturers are publishing their OTA images publicly yet. If you are a user of their products then consider contacting manufacturers and encourage them to do so for all their products.

Otherwise the end user must manually provide the OTAU files from unofficial sources, if so, check out:

• OTA Device Firmware Updates · zigpy/zigpy Wiki · GitHub

[cjano]

would appreciate too if someone could explain why to TZ3000_gvn91tmx TS011F you should chose file with this in filename zg_tl8258, not sure how this is working, btw I had to trigger it manually with step 4,
thanks for guide, also having issue with this device FW ver. 77 and turning on and off, will see if new FW would fix it

[deechtewber (Wouter)]

Thank you for the great write-up of these instructions!

I’m trying to OTA update 3 Aqara TRV’s, 4 Aqara plugs and a Popp TRV, but I can’t succeed.
All the Aqara devices always deliver the following message in homeassistant.log:

DEBUG (MainThread) [zigpy.zcl] [0xDEA4:1:0x0019] No OTA image is available

For the Popp TRV, which is the same hardware as the Danfoss Ally, I can’t find an OTA file on Koenkk’s github repo.

I’ve read this whole thread, and the whole documentation on OTA Device Firmware Updates · zigpy/zigpy Wiki · GitHub.
I think I have it all correctly set up. Here’s the relevant content of my configuration.yaml

The OTA files are in the folder too:

But no matter if I wait for HA to update them, or when I trigger it manually, they never update. What can be the issue here? How can I troubleshoot any further?

[MasterDevwi (William Devereux)]

I love that ZHA can now handle firmware updates via the UI!

One thing that’s constantly bothered me about ZHA firmware updates in general though is that new entities in the firmware don’t seem to be discovered unless you remove and re-pair the device. This can be a real pain in the neck when you have a bunch of devices (such as two-dozen Inovelli switches). ZHA remembers the previous settings for most of the entities when the device is re-added, but not the entity names or icons so there’s a risk of breaking quite a bit of my logic.

Is there any way to discover new entities without removing and re-pairing? Or is this the only option?

[aelsharawi (a)]

HI…any one have gledopto lights, and does it has any auto update with HA?

I got this

[mikhan (mike)]

It seems they’ve broken ota in zha. It worked before but after 2024.2 update HA doesn’t see updates in otau folder

[cjano]

same here, after 2024.2 this is no longer working, ALMOST updated all plugs and for some reason TZ3000_gvn91tmx TS011F says no up-to-date and FW version unknown

[deechtewber (Wouter)]

Are you guys sure it worked right before 2024.2? It didn’t work for me 5 days ago (trying to set it all up the first time) and my backups say I installed 2024.2 only 3 days ago. Wondering if my problem is the same as yours…

[erkr (Eric)]

Yes the otau_directory is disabled in 2024.2: [BUG] quirk (that removes level control) not loaded for all Tradfi plugs · Issue #2973 · zigpy/zha-device-handlers · GitHub
There is an undocumented configuration flag mentioned in that thread to enable it at your own risk.

[erkr (Eric)]

Did you try the re configure option?

[MasterDevwi (William Devereux)]

If I try to reconfigure the device, after a few seconds it says it completed successfully but the new entities never appear.

I’ve also tried putting the switch in pairing mode first (triple pressing the config button). In that case, the reconfiguration fails after 5-10 seconds and this error appears in the logs: “attempted pair verify without being paired first.”

[erkr (Eric)]

That is kind of disappointing news.
Similarly I noticed that reconfigure doesn’t load quirks that became available after adding a device. Only Re-adding the devices fixes that, so very similar to what you report for entities.

As a user, I wonder what reconfigure actually does?! At least NOT what the name suggests.
I would expect that it there to complete missing entities and reconsider available quirks…BUT…apparently not…

Thanks for trying!

[MasterDevwi (William Devereux)]

I appreciate you trying to help!

I hope this is something that can be fixed in ZHA. Removing and adding the device also messes up which entities are exposed to voice assistants (and how they’re configured within Alexa/Google Home/HomeKit).

[HerrTim (Tim)]

Hello all,

I’m pretty new to this topic.
I run HA and for Zigbee I use Skyconnect. I’m wondering if the OTA updates are also possible with Skyconnect? Any experience?
I don’t have to enable the “ota_provider” anymore, or?

Thank you!

[erkr (Eric)]

In core-2024.2 the directory for OTA files was disabled.
I noticed this related pull request that seems to become part of core-2024.3:

Use new zigpy OTA providers for ZHA

[deechtewber (Wouter)]

What does, this mean exactly? That it will work again after an update?