Launch of the zigpy-ota repo

[TheJulianJES]

Welcome to zigpy-ota

Welcome to the zigpy-ota repository — the central hub for Zigbee OTA firmware images used by zigpy, Home Assistant's ZHA integration, and other zigpy-based applications.

Before You Start

Please read the README to understand how this repository works.

Quick Rundown

You can browse all available firmware images in the index via the links in the "Browse available firmware" section of the README.

For ZHA users: No configuration is required to use zigpy-ota with Home Assistant 2026.1.0 or later. Firmware updates are available automatically through the ZHA integration.

For Zigbee2MQTT users: An experimental index is also generated for use with Zigbee2MQTT. You can configure it in your Z2M configuration.yaml:

ota:
  zigbee_ota_override_index_location: https://raw.githubusercontent.com/zigpy/zigpy-ota/release/files/stable/z2m_v1_ota.json

Current Status

This project is in its early stages:

• Manufacturers are welcome to submit their firmware images. If you are a device manufacturer, feel free to submit your OTA firmware by creating an issue.
• Otherwise, please only submit OTA firmware images if you have been asked to do so by a maintainer, or if you have reached out to a maintainer and received permission first (feel free to ask in this thread).
• We plan to open contributions to the full community soon.

Note: Please do not submit Philips Hue firmware images at this time.

Goal: Stable firmware

The goal of zigpy-ota is to provide fully stable, verified firmware to end users. Quality and reliability are critical since firmware updates pushed through this repository reach Home Assistant users worldwide.

A beta channel is also available for firmware that may be less stable or is still being validated. This allows users who opt in to test newer firmware before it reaches the stable channel. For more information, expand the "Using pre-release channels" section in the README.

Warning: Firmware on the beta or dev channels may be unstable and can potentially brick your devices. Use these channels at your own risk.

How to Use GitHub Issues vs. Discussions

• GitHub Issues — Reserved for:
  • OTA firmware submissions (via the issue forms)
  • Bug reports related to tooling or firmware
• GitHub Discussions — Use for:
  • Questions about the project
  • Feedback and suggestions
  • General conversation

Questions?

If you have any questions about the project, feel free to ask them right here in this thread.

[Hedda]

It is awesome work that you have done with this!

I assume that the existing/old OTA providers that was previous supported in zigpy will still be used by zha for now, but understand that in the future zigpy/zha devs would prefer if all those manufactuers also move to using this new zigpy-ota repo and the new zigpy-ota provider, or?

Also assume that sooner or later zigpy/zha devs will probably want to deprecate all of the older OTA providers available directly in the zigpy library today, meaning that then Zigbee OTA images will need to be provided via the new zigpy-ota repo or else they will no longer be be available via zigpy/zha, or?

Previous OTA providers for manufacturers that zigpy provide today that will need to be moved or risk being removing from zigpy/zha:

• IKEA
• Inovelli
• Ledvance/OSRAM
• Sonoff/iTead
• Third Reality (a.k.a. ThirdReality, a.k.a. 3reality)

Is there a plan/roadmap (not under an non-disclosure agreement or trust-me-bro secret) to export and import OTA images from some or all OTA providers for manufacturers that do not currently have a partnership with the Open Home Foundation? I.e. IKEA, Inovelli, Ledvance/OSRAM, and Sonoff/iTead?

• https://works-with.home-assistant.io/

By the way, zigpy readme has not yet been updated:

• https://github.com/zigpy/zigpy/blob/dev/README.md#zigbee-device-ota-updates

Niether has the ZHA integration end-user documentation:

• https://www.home-assistant.io/integrations/zha#ota-updates-of-zigbee-device-firmware

Anyway, great job with all this so far!