[REQUEST] ThirdReality (3reality) OTA provider for Third Reality branded Zigbee devices

ThirdReality (3reality) Zigbee OTA firmware images are made publicly available by Third Reality, Inc. (first-party) at the following URL:

https://tr-zha.s3.amazonaws.com/firmware.json

Official website and Facebook group for reference:

https://www.3reality.com/

https://www.facebook.com/ThirdReality.offical/

Z2M devs might want to contact @hwzolin from Third Reality, Inc. for sample hardware if they are interested in Zigbee2MQTT support.

FYI; code for Third Reality (3reality) OTA provider support and custom image format parser were recently added to zigpy library:

https://github.com/zigpy/zigpy/pull/1096

https://github.com/zigpy/zigpy/pull/1090

https://github.com/zigpy/zigpy/pull/1089

BTW, also read that Third Reality (3reality) joined “Works with Home Assistant”/“Works via Zigbee with Home Assistant” partner program.

https://www.home-assistant.io/blog/2022/10/13/third-reality-partner/

https://www.home-assistant.io/blog/2022/07/12/partner-program/

@hwzolin please see the backstory below for reference:

As Third Reality, Inc. as a company probably do not know yet, zigbee-herdsman is the Zigbee framework used by Zigbee2MQTT and IoBroker as a dependency in their open source Zigbee gateway/hub implementations.

Providing a “3reality Zigbee OTA provider” and matching downloader code support for Zigbee devices from ThirdReality (3reality) in this zigbee-herdsman-converters library could potentially enable much easier OTA firmware upgrades for end-users of those in the future, and currently Zigbee2MQTT is probably the worlds most popular open source Zigbee gateway/hub implementation among DIY home automation enthusiasts.

https://github.com/Koenkk/zigbee-herdsman-converters/tree/master/lib/ota

That way it will be a single trusted and official primary source of official Zigbee OTA files released by Third Reality, and that OTA provider source repository with your Zigbee OTA files could not only be used by zigbee-herdsman / Zigbee2MQTT / IoBroker as it could also be reused by other Zigbee implementations independently (both other open-source implementations as well as closed source and proprietary implementations).

Maybe also consider copying concept of index.json with metadata on all files like Koenkk repository has to make scripting easier:

https://github.com/Koenkk/zigbee-OTA/blob/master/index.json

PS: Zigbee2MQTT allows users to use it locally as described here:

https://github.com/Koenkk/zigbee2mqtt.io/blob/develop/docs/guide/usage/ota_updates.md#local-ota-index-and-firmware-files

And of course README.md file which among other things could contain some basic information on how to update those:

https://github.com/Koenkk/zigbee-OTA/blob/master/README.md

Perhaps also as keeping some kind of CHANGELOG.md with changelog release history for each device firmware version:

https://github.com/Koenkk/Z-Stack-firmware/blob/master/coordinator/Z-Stack_3.x.0/CHANGELOG.md

[ahahamyan]

Hello, I noticed that some of the devices (such as water leak sensor) have DEV in OTA file name in the json descriptor file - such as TRTL_WaterLeak_DEV_V31_v1.00.31.ota while others have PROD as part of name. Are these DEV versions safe/proper to use when updating firmware on devices?

[Hedda]

In support, thanks.

@hwzolin Any updates on your ThirdReality (3reality) OTA provider for zigbee-herdsman (for use in Zigbee2MQTT and IoBroker)?