ZiGate users help wanted to test fork of zigpy-zigate with ZHA before developers submit pull requests:
Please see discussion and plea for help → https://github.com/zigpy/zigpy-zigate/issues/104
Help from testers with ZiGate adapters is wanted to “regression test” other Python packages of check if patches applied to a fork of zigpy-zigate look to have introduced any new bugs seen in ZHA integration.
The backstory:
The lead developer of zigpy-zigate (zigpy radio library for ZiGate based Zigbee Coordinator adapters used by the ZHA integration) does not have time to maintain or improve the zigpy-zigate library.
The good news is that some developers of a Zigbee implementation for Domoticz which will also use the same zigpy-zigate library have offered to submit bug-fixes and new features/functions.
The problem with that is that since those developers do not use ZHA at all they can not perform regression testing on ZHA to test if they introduce any other bugs or issues with their patches that can be seen in ZHA but not in their (non-ZHA) Zigbee implementation for Domoticz.
Since those developers of a Zigbee implementation for Domoticz do not have write access to the upstream zigpy-zigate repository on GitHub they have forked (copied) it to another repository and applied the patches there for now. That is why it is the library in that repository that will now need tested.
https://github.com/zigbeefordomoticz/zigpy-zigate
Volunteering testers that actually use a ZiGate adapter with ZHA is needed to help with testing the fork.
Once patches in the fork have been tested then developers can see to submitting patches upstream.
PS: I am posting this plea on behalf of others interested in maintaining zigpy-zigate, (I do not have a ZiGate Zigbee adapter myself and I have no personal interest in owning one as lack the time to test).