Mopidy-Raspberry-GPIO

Mopidy extension for GPIO input on a Raspberry Pi

DEV

install ext (once to link): sudo python3 -m pip3 install -e .

restart (to load code): systemctl restart mopidy.service

see logs: journalctl -u mopidy -f

Allow shutdown: sudo visudo

add line: mopidy ALL=NOPASSWD: /usr/sbin/shutdown

Installation

Ensure Mopidy has access to GPIO:

sudo usermod -a -G gpio mopidy

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 = volume_down,active_low,250
bcm16 = next,active_low,250
bcm20 = volume_up,active_low,250

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

• Source code
• Issue tracker
• Changelog

Credits

• Original author: Phil Howard
• Current maintainer: Phil Howard
• Contributors