Replies: 2 comments
-
|
@pipiche38 Have you followed the split of the ZHA integration component and creation/breakout to this new external zha gateway library? I have tried to summerized the updates here as understod by me: Perhaps you could now begin to look into this if you could use this new external zha gateway library in your Zigbee Plugin for Domoticz? FYI, it looks like zha component split and break changes in HA passed beta stage now and will be included in Home Assistant 2024.8 release: Home Assistant 2024.8 release is scheduled for release tomorrow and ZHA integration component is now using external zha library instead: "The Zigbee Home Automation (ZHA) integration has seen lot of improvements and love from @dmulcahey, @puddly, and @TheJulianJES this release. What this means for you? Well… basically nothing! And this sounds odd, but is is a good thing! The whole integration has been split into a separate codebases, making it easier to maintain and improve. This is a huge step forward for the integration that took months of work to get done. You will not notice anything different right now, but this change will make it easier to maintain and improve the integration in the future, including the ability for code contributors to contribute to the integration more easily." Again, this new external "zha" library is designed to be a higher-level Zigbee Gateway library (which in turn is depending on the lower-level zigpy libraries), and is as such meant to help streamline both zha and zigpy development and make easier for new developers to contribute higher level functions to the zha and zigpy projects without having to learn all the underlying code. This new external "zha" library is also not only meant to be used by application-level implementions such as the Zigbee Home Automation integration) in Home Assistant. It can potentially potentially also be used by other projects or could even be used in a stand-alone Zigbee Gateway application (similar in the architecture to that of Zigbee2MQTT) Back-story is that this new zha class library started as an initial migration of the core logic from ZHA integration to breakout and move the Zigbee Gateway part away from the zha intégration component inside Home Assistant's core repository into a self-contained external library. The end result of this split (and other further changes to come) should be a huge improvement in terms of code quality in both the Home Assistant half and the library half of zha. The ultimate goal of having zha as a separate library is to eventually make ZHA reusable outside of Home Assistant, easier to understand, and pave the path to a more streamlined model for contributing device support code to ZHA and Home Assistant (when necessary). Note that this is an initial pass where the aim was to modify as little as possible in this split. Future changes will hopefully enable zha to work with other stand-alone applications as well. You will notice that the terminology currently in use within this new external zha library (and thus also the rewritten ZHA integration) mirrors that of Home Assistant's Core. This is intentional and will diverge as we see fit. References;
PS: Off-topic, but FYI, recently also @elupus has also started actively contributing to the development of this new external "zha" library: |
Beta Was this translation helpful? Give feedback.
-
|
FYI, looks as if dmulcahey picked up ZHA WebSocket Server (ZHAWS) / ZHA WebSocket Server Gateway (websocketservergateway) project again, or? These two WIP draft pull requests seem to indicate that: |
Beta Was this translation helpful? Give feedback.
-
FYI, looks like zigpy developer is working on external ZHA gateway library for stand-alone implementations -> zigpy/zigpy#1207 (comment)
Beta Was this translation helpful? Give feedback.
All reactions