FYI, the new external zha library is a high-level Zigbee Gateway library written in Python and depends on the zigpy project + all of its libraries.
This new external zha library is meant to be used by application-level implementions such as the Zigbee Home Automation integration) in Home Assistant.
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 the library (and thus the rewritten integration) mirrors that of Core. This is intentional and will diverge as we see fit.
Update README.md to mention the new external zha library that has been split out of ZHA integration in Home Assistant's core.
References;
FYI, the new external zha library is a high-level Zigbee Gateway library written in Python and depends on the zigpy project + all of its libraries.
This new external zha library is meant to be used by application-level implementions such as the Zigbee Home Automation integration) in Home Assistant.
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 inetgration 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 the library (and thus the rewritten integration) mirrors that of Core. This is intentional and will diverge as we see fit.