Mopidy-Raspberry-GPIO
Mopidy extension for GPIO input on a Raspberry Pi
Installation
Ensure Mopidy has access to GPIO:
sudo usermod -a -G gpio mopidy
Make sure you have the RPi.GPIO library installed:
sudo apt install python3-rpi.gpio
Install by running:
python3 -m pip install Mopidy-Raspberry-GPIO
Or, if available, install the Debian/Ubuntu package from apt.mopidy.com.
Configuration
Before starting Mopidy, you must add configuration for Mopidy-Raspberry-GPIO to your Mopidy configuration file:
[raspberry-gpio] enabled = true bcm5 = play_pause,active_low,250 bcm6 = prev,active_low,250 bcm16 = next,active_low,250 bcm21 = volume_down,active_low,10,rotenc_id=vol,step=1 bcm20 = volume_up,active_low,10,rotenc_id=vol,step=1
Each bcmN entry corresponds to the BCM pin of that number.
You must assign an event, mode and bouncetime (ms) to your desired pins.
Supported events:
play_pause
volume_up
volume_down
next
prev
Supported modes:
active_low - configures the pin with a pull-up and triggers when it reads 0/low (RECOMMENDED)
active_high - configures the pin as a pull-down and triggers when it reads 1/high
Events volume_up and volume_down both support an (optional) “step” option, which controls the amount (in percent) that the volume is adjusted with each button press.
Eg:
[raspberry-gpio] enabled = true bcm5 = play_pause,active_low,250 bcm6 = volume_down,active_low,250,step=1 bcm16 = next,active_low,250 bcm20 = volume_up,active_low,250,step=1
Project resources
Credits
Original author: Phil Howard
Current maintainer: Phil Howard
Metadata
Release files for mopidy-raspberry-gpio 1.0.4
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 |
|---|---|---|---|---|
| mopidy-raspberry-gpio-1.0.4.tar.gz | 15.0 kB | Without provenance | Details for mopidy-raspberry-gpio-1.0.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mopidy_raspberry_gpio-1.0.4-py3-none-any.whl | Python 3 | none | any | Details for mopidy_raspberry_gpio-1.0.4-py3-none-any.whl |
Total release size: 25.7 kB
Release files / mopidy-raspberry-gpio-1.0.4.tar.gz
| Download URL | mopidy-raspberry-gpio-1.0.4.tar.gz |
|---|---|
| Size | 15.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
313b4e2b037d5101f618615e1cc7bb3ae9a7e8aa17d906bfb015876de2d0c6fd
|
|
BLAKE2b-256 checksum How to use checksums |
163e4a703ff641124c6287e1114fba2b9b98f41278d6b54f448d8f2e2dcd25cf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.22.0 setuptools/45.2.0 requests-toolbelt/0.9.1 tqdm/4.54.1 CPython/3.8.10
|
Release files / mopidy_raspberry_gpio-1.0.4-py3-none-any.whl
| Download URL | mopidy_raspberry_gpio-1.0.4-py3-none-any.whl |
|---|---|
| Size | 10.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0966eecc5c9e63ccfd073781cc25451ca89da501f7d79435588f400a575e9739
|
|
BLAKE2b-256 checksum How to use checksums |
3cf9da4bf7b62532a5ce43ad7831971e2dc6f2a399ab35d623ef0c5137c34828
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.22.0 setuptools/45.2.0 requests-toolbelt/0.9.1 tqdm/4.54.1 CPython/3.8.10
|
Security for mopidy-raspberry-gpio 1.0.4
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.