zigpy-blz
zigpy-blz is a Python library that adds support for Bouffalo Lab Zigbee (BLZ) radios to zigpy, a Python Zigbee stack project.
It is designed to interface with Bouffalo Lab Zigbee (BLZ) radios, enabling users to communicate with Zigbee devices using zigpy and compatible home automation platforms, such as Home Assistant's ZHA (Zigbee Home Automation) integration component.
Installation
Via the BLZ Custom ZHA Component (Recommended)
The easiest way to use zigpy-blz with Home Assistant is to install the BLZ Custom ZHA Component, which automatically pulls in zigpy-blz as a dependency. See that repository for HACS and manual install instructions.
Python Module
Install the Python module in your virtual environment:
$ python3 -m venv venv # if you don't already have one
$ source venv/bin/activate
(venv) $ pip install git+https://github.com/bouffalolab/zigpy-blz.git@main # latest commit from Git
(venv) $ pip install zigpy-blz # or, latest stable from PyPI
Home Assistant Core (manual)
Upgrade the package within your virtual environment (requires git):
(venv) $ pip install git+https://github.com/bouffalolab/zigpy-blz.git@main
Hardware Support
zigpy-blz is compatible with Bouffalo Lab's BLZ radios, which use the Bouffalo Zigbee Serial Protocol (BZSP). Ensure your firmware version matches the protocol version supported by this library.
Supported hardware includes:
Developer References
For more details on the protocol used by Bouffalo Lab radios, see:
- UG100 Bouffalo Lab Zigbee (BLZ) Protocol (included in this repo)
How to Contribute
We welcome contributions! If you'd like to contribute to this project, please follow the steps in the following guides:
Testing
Unit tests are available to verify the implementation. To run the tests, use:
pytest tests/
Releases via PyPI
Tagged versions of zigpy-blz are released via PyPI.
Push a v* tag to trigger the release workflow.
Related Projects
- zigpy: The core Python Zigbee stack project that integrates with ZHA in Home Assistant.
- BLZ Custom ZHA: Custom ZHA component with BLZ radio support for Home Assistant.
- Home Assistant ZHA: Zigbee Home Automation integration component in Home Assistant.
Metadata
Release files for zigpy-blz 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| zigpy_blz-0.1.0.tar.gz | 551.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| zigpy_blz-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.1 MB
Release files / zigpy_blz-0.1.0.tar.gz
| Download URL | zigpy_blz-0.1.0.tar.gz |
|---|---|
| Size | 551.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9c5601159ccb08a76dccb0deac30d4aba1d51447c6fb14311fa12b78ae83c081
|
|
BLAKE2b-256 checksum How to use checksums |
72948b30f67e1645224b31892d22c8b451f57e172999a7aee1b8f52494566ea9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 20, 2026.
Transparency logRelease files / zigpy_blz-0.1.0-py3-none-any.whl
| Download URL | zigpy_blz-0.1.0-py3-none-any.whl |
|---|---|
| Size | 547.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c0b12e0094a8c5cbe7f7ed1d851ae4df348c11e4ebc53c7eee65d1d86f5a6319
|
|
BLAKE2b-256 checksum How to use checksums |
97abc0807aac4d3a32696d8bc35bb76c72512f34dc2d60da99804b4cdf5ab8a3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 20, 2026.
Transparency log