qbee-gpio
A docker image to control an LCD and amplifier relay for use in an AirPlay and/or Spotify Connect Raspberry Pi server.
- Detect sound output and turn on the amplifier power supply.
- Get the track information and display it on an LCD.
- Auto turn off amplifier power supply after set period of inactivity.
Additional documentation:
Running
docker run -d \
--name qbee \
--restart always \
--network host \
-e LG_WD=/tmp \
--device=/dev/gpiochip0 \
-v ~/qbee:/app/config:ro \
--user $(stat -c '%u:%g' ~) \
--group-add $(stat -c '%g' /dev/gpiochip0) \
gpajot/qbee-gpio:latest
This expects a config file located at ~/qbee/conf.yaml. See all config options
A typical config would look like:
power:
pin_on: 27
pin_standby: 22
display:
lcd:
pins:
data_4: 9
data_5: 25
data_6: 17
data_7: 10
enable: 24
register_select: 23
Metadata display
To enable reception of metadata:
udp:
host: "0.0.0.0"
to enable UDB metadata (librespot and/or shairport)
mqtt:
hostname: ...
to enable MQTT metadata (shairport)
1 maintainer
Metadata
1 maintainer
Release files for qbee-gpio 4.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| qbee_gpio-4.3.1.tar.gz | 12.6 kB | With provenance | Details for qbee_gpio-4.3.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| qbee_gpio-4.3.1-py3-none-any.whl | Python 3 | none | any | Details for qbee_gpio-4.3.1-py3-none-any.whl |
Total release size: 31.2 kB
Release files / qbee_gpio-4.3.1.tar.gz
| Download URL | qbee_gpio-4.3.1.tar.gz |
|---|---|
| Size | 12.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e0ccdab54e76f339acbc737e755ed6d9f3b0880fd461223b83304fdb582a30cf
|
|
BLAKE2b-256 checksum How to use checksums |
6ab51d3c85210a163a8e570478d6412ad6977dc1a6ac6a2f1e69ac3d4ce903ee
|
| 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 22, 2026.
Transparency logRelease files / qbee_gpio-4.3.1-py3-none-any.whl
| Download URL | qbee_gpio-4.3.1-py3-none-any.whl |
|---|---|
| Size | 18.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
427d40588f4e4e110267f79b7d163af736d38c50e715c8175749669a2810ae95
|
|
BLAKE2b-256 checksum How to use checksums |
0efc6c4fb3b3b1dc831fc707d066fa6c852c9b25a12ffe5472011d5e07c7e852
|
| 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 22, 2026.
Transparency logSecurity for qbee-gpio 4.3.1
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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for qbee_gpio-4.3.1.tar.gz
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 22, 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.
