zigbang-relay
Prebuilt, statically linked relay binary from zigbang_relay,
packaged as platform wheels (Linux x86_64/aarch64, musl and glibc) so the
zigbang_doorlock Home Assistant integration can run it
as a subprocess. This package only ships the binary and default rules:
import zigbang_relay
zigbang_relay.bin_path() # Path to the relay executable
zigbang_relay.RULES_DIR # Path to the bundled rules/*.rhai
Metadata
Release files for zigbang-relay 0.1.9
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| zigbang_relay-0.1.9-py3-none-manylinux_2_17_x86_64.musllinux_1_2_x86_64.whl | Python 3 | none | Linux musl 1.2+ x86-64, Linux glibc 2.17+ x86-64 | Details for zigbang_relay-0.1.9-py3-none-manylinux_2_17_x86_64.musllinux_1_2_x86_64.whl |
| zigbang_relay-0.1.9-py3-none-manylinux_2_17_aarch64.musllinux_1_2_aarch64.whl | Python 3 | none | Linux glibc 2.17+ ARM64, Linux musl 1.2+ ARM64 | Details for zigbang_relay-0.1.9-py3-none-manylinux_2_17_aarch64.musllinux_1_2_aarch64.whl |
Total release size: 7.1 MB
Release files / zigbang_relay-0.1.9-py3-none-manylinux_2_17_x86_64.musllinux_1_2_x86_64.whl
| Download URL | zigbang_relay-0.1.9-py3-none-manylinux_2_17_x86_64.musllinux_1_2_x86_64.whl |
|---|---|
| Size | 3.6 MB |
| Tags | Linux glibc 2.17+ x86-64 Linux musl 1.2+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
266a389e98a0ec279bf440a07663a28718fe5444c21a23a809ed817f52c831dc
|
|
BLAKE2b-256 checksum How to use checksums |
1edd35bc495a3832b637d5c6bc14bff01a60ec74a6e648119e8af9980e6236e6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 31, 2026.
Transparency logRelease files / zigbang_relay-0.1.9-py3-none-manylinux_2_17_aarch64.musllinux_1_2_aarch64.whl
| Download URL | zigbang_relay-0.1.9-py3-none-manylinux_2_17_aarch64.musllinux_1_2_aarch64.whl |
|---|---|
| Size | 3.5 MB |
| Tags | Linux glibc 2.17+ ARM64 Linux musl 1.2+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
65e3cd2b7d059e618d4154fd7c69a4980fa9119ab43b7416235d17fbd0658966
|
|
BLAKE2b-256 checksum How to use checksums |
fb5274fba02c510780ca6717b335ecf836ae359fbfb6fbc4e3d3d8683e70f47e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 31, 2026.
Transparency logSecurity for zigbang-relay 0.1.9
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for zigbang_relay-0.1.9-py3-none-manylinux_2_17_x86_64.musllinux_1_2_x86_64.whl
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 Oct 31, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.