Hedda
commented
3 months ago @DamKast have you by the way tested/verified zigpy-zboss funtionality with Home Assistant 2024.8 release (or later HA releases)?
Asking since the latest ZHA integration component in Home Assistant core now depends on a new externalzha library (which is the Zigbee Gateway implementation broken out into its own library), you can find that new library under the zigpy originazation:
As such you now also need to patch that new zha library as well as add zboss radio configuration to the zha component inside Home Assistant core. See example:
and
UPDATE: If you have time please also check out this indirectly related discussion if possible:
DamKast
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.