Launch of the zigpy-ota repo #2
Replies: 6 comments 4 replies
-
|
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:
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? By the way, zigpy readme has not yet been updated: Niether has the ZHA integration end-user documentation: Anyway, great job with all this so far! |
Beta Was this translation helpful? Give feedback.
-
|
Existing OTA providers that pull updates directly from manufacturers without any verification (and with no release notes) are still available. We do plan to eventually deprecate them because of all advantages that zigpy-ota has.
Some manufacturers, like Sonoff, have started providing new updates to zigpy-ota now. Ideally, all existing updates are ported over with release notes, though it may be difficult to get changelogs for older updates. And thanks for the note on documentation. We'll update it soon but it may be difficult to explain for which manufacturers we provide updates now. 😅 |
Beta Was this translation helpful? Give feedback.
-
In addition to allowing ZHA users to choose geting OTA-updates from stable, beta or dev channel, have you considered in the future enabling some kind of filter (also available in the UI) to allow ZHA users to select if they only want to get firmware images submitted by verified manufacturers or if they want to select getting community-submitted contributions as well? Directly related to what is Originally posted by @TheJulianJES in #1 here:
That is, when you start allowing community contributions then you have settings for it in zha so that end-user explicitly needs to enable getting OTA community contributions by default, however that it should still be relativly easy to enable it via ZHA's control panel UI in Home Assistant, but with a pop-up warning with a disclaimer that the user understands the risk with community contributions OTA updates. The point with this would be make it simpler to get a larger collection of Zigbee OTA for a wider range of devices similar to koenkk's zigbee-ota collection (which is used by default in Zigbee2MQTT) while still not getting all those by default in ZHA if user do not explicitly enable it: PS: Off-topic but FYI, the section about Zigbee OTA updates in ZHA integration end-user documentation has not yet been updated: |
Beta Was this translation helpful? Give feedback.
-
|
Somewhat, yes. We do plan to expose a UI option in the ZHA options to easily switch between The beta channel could include more of the community contributions. Already, we show a link in the release notes for every update in Home Assistant, where you can quickly open the corresponding zigpy-ota PR. There, users can report issues with the update (or post success stories). Depending on the feedback, updates could be removed/disabled entirely, or pushed to the stable channel. Initial PR (though this will need some changes + other PRs as well): |
Beta Was this translation helpful? Give feedback.
-
|
FYI, it looks as if Bosch has now published official Zigbee OTAU files for Bosch Smart Home devices on GitHub in this repository: |
Beta Was this translation helpful? Give feedback.
-
@sebastianharder @samuelfleischle as the maintainers of that Git repo on GitHub could you maybe check with your empoyeer (Bosch Smart Home) if it you could also get explicit approval to submit those Zigbee OTA firmware update images to this zigpy-ota repo as well so that they can be included with Home Assistant's ZHA integration (built-in Zigbee gateway) by default? Also, while not a requirment for manufacturers to submit Zigbee OTA firmware files, perhaps you could even consider bringing up the idea of joining the Works With Home Assistant partnership program (note that the WWHA annual fee/cost is very low) and maybe even try to get some devices certified too? That would not only prove out-of-the-box compatibily but also be good publicity as well as allow you to use their badge on those products for marketing? Home Assistant might not be a household name yet, like Bosch, but it is quickly growing in popularly within the niche smart home market (especially among DIY:ers), and more importantly to companies Home Assistant can be a great testing ground as its userbase/community has many early adopters and entusiast that can often also acts as brand evengalists to help spread the news about product they like (sometimes even through reviews, blogs/vlogs, podcasts, and YouTube). PS: Oh, and if your boss(es)/empoyeer did not know, Home Assistant is one of the main software applications that is now owned and govered by the newly formed Open Home Foundation non-profit organization, so if Bosch Smart Home would like to in some way sponsor or donate to them (with no strings attatched) via others means then I am sure such donations would be welcomed as well: |
Beta Was this translation helpful? Give feedback.
-
|
For reference, noticed that ThirdReality and Inovelli was sent a public heads-up now that their legacy OTA providers per-company feed in zigpy is now on a plan for removal from zigpy with a message that they should resubmit all updates to this central zigpy-ota repository: PS: @TheJulianJES With the launch of the zigpy-ota repo soon coming up on 6-months, wondering if information about this has already been sent out by the Partnership Manager at Home Assistant / The Open Home Foundation to all Works with Home Assistant (WWHA) partners and if there now perhaps a follow-up plan to maybe before the end of the year publicly have this new central repository for Zigbee OTA firmware images more formally announced so this news reaches more Zigbee device manufacturers? Example via the Open Home Assistant newsletter and the Home Assistant blog (or via the developers blog). Thinking that such public announcement could be really good publicity for not only the zigpy-ota but should also good publicity the zha and zigpy Zigbee stack Python libraries to possible help attract both more manufacturers and interest from more independent developers in helping out with these projects. |
Beta Was this translation helpful? Give feedback.
-
|
Oh, and you probably want to "pin" the zigpy-ota repo as well under the zigpy originazation so that it listed as "pinned" at the top: 
|
Beta Was this translation helpful? Give feedback.
-
|
For reference, I asked @manup from Dresden Elektronik in an open-letter on their deconz-ota-plugin repository about the possibility of them as a company also activly working towards providing Zigbee OTA update firmware files for their dresden elektronik and Phoscon branded devices to this zigpy-ota repository for automatic inclusion to Home Assistant's built-in ZHA integration by default out-of-the-box (and other zha and zigpy-based Zigbee gateway applicationsm which today includes the Zigbee plugin for Domoticz as well): In summery he replied threre that anyone and everyone in the zha/zigpy cummunity should feel free to submit the Zigbee OTAU files that Dresden Elektronik publish publicly, but personally he did not realy see the point with the zigpy-ota repository at this time as he does not understand the benefit it brings and added that we should consider that some or most of those firmware files have also already been uploaded to Koenkk's zigbee-OTA repository by the Zigbee2MQTT community, so anyone could optionally just use that repo in ZHA instead if they want to get the firmware that are provided there today. FYI, dresden elektronik themselves of course publish Zigbee OTA firmware images for all their own devices direcly from their official website:
Product catalog on dresden-elektronik.com website: PS: Might be worth mentioning that Dresden Elektronik actually goes something kind of similar as they provide Zigbee OTA firmware from third-parties inside their own deCONZ Zigbee gateway applications via their custom deCONZ STD OTAU plugin for Zigbee OTA Updates, which by default retrieve its OTA files from the Koenkk/zigbee-OTA repository as an unofficial GitHub-based mirror via its JSON index file: |
Beta Was this translation helpful? Give feedback.
-
|
Tip! Dresden Elektronik's deCONZ wiki actually has quite nice documentation and direct links to original Zigbee OTA files from third-parties: OTA Image Types Firmware versionsPhilips Hue (Signify)Manufacturer code: 0x100B Signify doesn't provide their firmware for use with other ZigBee gateways than the Hue bridge. The communication between the bridge and the server hosting the firmware files is encrypted, so we cannot get an overview of the files available automatically. To find the firmware files, you need to sniff the traffic from the Hue bridge to the Internet, as it downloads the files. Unfortunately, the bridge will only download firmware files for connected devices with outdated firmware. For details, see issue #10 in the OTAU plugin repository. Note that for powered Philips/Signify devices that support both ZigBee and Bluetooth (such as the filament bulb LWA004), it is possible to update the firmware of these devices using a mobile phone and the Philips Hue Bluetooth app. This can be done while the device is already configured/seen in DeConz. In order to refresh the firmware information shown in DeConz/Phoscon, one needs to re-read the cluster information in DeConz. That way, these devices can be updated without knowlegde of the actual download link for the latest firmware.
Osram LightifyManufacturer code: 0x110C Download-URL: https://update.ledvance.com/firmware-overview
IKEAManufacturer code: 0x117C Download-URL: http://fw.ota.homesmart.ikea.net/feed/version_info.json Download-URL (Test/Beta-Version): http://fw.test.ota.homesmart.ikea.net/feed/version_info.json
✅ = OTA updating is working in deCONZ. dresden elektronikManufacturer code: 0x1135
SengledManufacturer code: 0x1160
LutronManufacturer code: 0x1144
Busch-JaegerManufacturer code: 0x112E The ZLL switches from Busch-Jaeger have upgradable firmware. The firmware can be extracted from the Windows Upgrade Tool provided by Busch-Jaeger with the following steps:
UbisysManufacturer code: 0x10F2 https://www.ubisys.de/en/support/firmware/ DanfossManufacturer code: 0x1246
Eurotronichttps://github.com/EUROTRONIC-Technology/Spirit-ZigBee/releases Salus / Computimehttps://eu.salusconnect.io/demo/default/status/firmware?timestamp=0 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
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:Current Status
This project is in its early stages:
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
Questions?
If you have any questions about the project, feel free to ask them right here in this thread.
Beta Was this translation helpful? Give feedback.
All reactions