FYI, zigpy now have their own central firmware Zigbee OTA image repository (beta and dev) and a new zigpy-ota OTA provider

[Hedda]

FYI, zigpy now have their own central firmware Zigbee OTA image repository (beta and dev) and a new zigpy-ota OTA provider. See:

• https://github.com/zigpy/zigpy-ota

  • Add zigpy-ota OTA provider zigpy/zigpy#1731

    • https://github.com/zigpy/zigpy/wiki/OTA-Information-for-Manufacturers

      • https://github.com/zigpy/zigpy/blob/dev/zigpy/ota/providers.py

Launch announcement for the new repo here:

• Launch of the zigpy-ota repo zigpy/zigpy-ota#2

Quote: "Please check if this meets your needs and fill out the issue form there to submit your firmware."

Only beta and dev "channels" so far for collection of Zigbee OTA files. Example proof-of-concept implementation here in the zha library:

• Expose zigpy OTA release_url metadata in update entity zigpy/zha#602

  • Add config option to use zigpy-ota beta channel zigpy/zha#617

Quote: "Please reach out if you have any questions or open a discussion on the zigpy repository directly":

• https://github.com/zigpy/zigpy/discussions/

Update: Note that by default, only stable firmware is available, (which is highly recommended for most users that are not zigbee developers). So the zigpy-ota stable channel is active by default with Home Assistant Core 2026.1.0 and later with no configurations required by the end-user. To opt into pre-release firmware, add this to your Home Assistant configuration:

zha:
  zigpy_config:
    ota:
      extra_providers:
        - type: zigpy_ota
          channel: beta # or 'dev' for bleeding edge (unstable, not recommended)
          override_previous: true

PS: Here is a more extensive introductory comment that TheJulianJES wrote for ThirdReality:

• May I ask, when performing ZHA OTA (Over-the-Air Software Update), how does the program determine which devices to update? zigpy/zigpy#1724 (comment)

Originally posted by TheJulianJES in zigpy/zigpy#1724 (comment)

Just some info: We have an early version of our central firmware repo set up now: zigpy-ota. The underlying OTA provider in zigpy for the repo is included in Home Assistant Core 2026.1.0.

We're trying to move towards a central approach, as it's easier for most manufacturers, allows us to get feedback on the installed OTAs, do a quick sanity check for new updates, and have a "beta" zigpy-ota release channel to which we can (temporarily) limit new updates to.

The repo doesn't require any PRs nor JSON metadata to add images. You can submit an issue (per image) with your existing OTA image URL and a PR will be auto-created and merged by us.

Providing release notes is also simple and we've found that to be really helpful for users who are unsure about installing updates, so it's very much encouraged to just add a bit of the text about the particular update in that section of the issue form.

If you want to limit the update to certain device models (e.g. like here), or to users who configured the zigpy-ota beta channel, or if you want to require a minimum installed existing version on the device, you can also add a bit of optional metadata. See the placeholder and examples in the issue form and README for that. We're also here to answer any questions.

If any update later needs to be removed, you can submit a PR to edit the YAML text file per image and just add disabled: true. Alternatively, you can also just submit a PR that removes the image and YAML metadata file, e.g. for updates with bad regressions.

Also note that the ThirdReality firmware.json index is still used by zigpy as well, though we generally prefer using the zigpy-ota repo in the future.