Replies: 1 comment
-
On-topic is however that zigpy based implementations allow both end-users and manufacturers to provide Zigbee OTA update images: https://github.com/zigpy/zigpy/wiki/OTA-Device-Firmware-Updates https://github.com/zigpy/zigpy/wiki/OTA-Information-for-Manufacturers https://github.com/zigpy/zigpy/blob/dev/README.md#zigbee-device-ota-updates https://www.home-assistant.io/integrations/zha#ota-firmware-updates https://github.com/zigpy/zigpy/tree/dev/zigpy/ota https://github.com/zigpy/zigpy/issues?q=is%3Aissue+is%3Aopen+ota PS: There is by the way a new open pull request for zigpy that will significantly improve the Zigbee OTAU update process for end-users: |
Beta Was this translation helpful? Give feedback.
-
Off-topic here but FYI as thought it is interesting for those with nRF52840 dongles or dev kits to know about the zigpy-zboss project as well:
https://github.com/kardia-as/zigpy-zboss
zigpy-zboss is a ZBOSS NCP serial interface abstraction library for the zigpy project which in turn is a radio hardware independent Zigbee framework that was primarily use case is to allow users to utilise Zigbee radios from different manufacturers as a Zigbee Coordinator adapter in open-source Zigbee gateway integrations like ZHA integration component for Home Assistant, the Zigbee Plugin for Domoticz, and the Zigbee Plugin for Jeedom (competing open-source home automation software).
https://github.com/zigpy/zigpy
zigpy contains common code implementing ZCL (Zigbee Cluster Library) and ZDO (Zigbee Device Object) application state management which is being used by various radio libraries implementing the actual interface with the radio modules from different manufacturers. The separate radio libraries interface with radio hardware adapters/modules over USB and GPIO using different native UART serial protocols.
Beta Was this translation helpful? Give feedback.
All reactions