A simple, light weight audio receiver with Bluetooth (A2DP), AirPlay 2, and Spotify Connect.
Devices like phones, tablets and computers can play audio via this receiver.
- A USB Bluetooth dongle (the internal Raspberry Pi Bluetooth chipset turned out as not suited for audio playback and causes all kinds of strange connectivity problems)
- Raspberry Pi OS 11 Lite
- Internal audio, HDMI, USB or I2S Audio adapter (tested with Adafruit USB Audio Adapter, pHAT DAC, and HifiBerry DAC+)
Again: do not try to use the internal Bluetooth chip, this will only bring you many hours of frustration.
The current version of Raspberry Pi OS (2022-01-28) is based on Debian 11 (Bullseye). This version does not contain the BlueALSA package (bluealsa) anymore. This repository now uses PulseAudio instead of ALSA. This may or may not work on slower devices like Raspberry Pi 1 and Raspberry Pi Zero.
For these devices, you might want to try HiFiBerryOS for similar functionality or stick with the debian-10 branch, which works with the "Raspberry Pi OS (Legacy)".
The installation script asks whether to install each component.
wget -q https://github.com/manuel5cc/rpi-audio-receiver/archive/main.zip
unzip main.zip
rm main.zip
cd rpi-audio-receiver-main
sudo ./initiator.sh
reboot
Lets you choose the hostname and the visible device name ("pretty hostname") which is displayed as Bluetooth name, in AirPlay clients and in Spotify.
Sets up Bluetooth, adds a simple agent that accepts every connection, and enables audio playback through PulseAudio. A udev script is installed that disables discoverability while connected.
sudo bluetoothctl
power on
agent on
# Now search for available bluetooth devices from your device
# Once paired note down the MAC address of your device
trust 00:00:00:00:00:00 # Put device MAC address here so after reboot it can automatically re-connect again
Installs Shairport Sync AirPlay 2 Audio Receiver.
Installs Raspotify, an open source Spotify client for Raspberry Pi.
To avoid SD card corruption when powering off, you can boot Raspberry Pi OS in read-only mode. This can be achieved using the raspi-config script.
- Only one Bluetooth device can be connected at a time, otherwise interruptions may occur.
- The device is always open, new clients can connect at any time without authentication.
- To permanently save paired devices when using read-only mode, the Raspberry has to be switched to read-write mode until all devices have been paired once.
- You might want to use a Bluetooth USB dongle or have the script disable Wi-Fi while connected (see
bluetooth-udev), as the BCM43438 (Raspberry Pi 3, Zero W) has severe problems with both switched on, see raspberrypi/linux/#1402. - The Pi Zero may not be powerful enough to play 192 kHz audio, you may want to change the values in
/etc/asound.confaccordingly.
There are some further examples, tweaks and how-tos in the GitHub Wiki.
These scripts are tested and work on a current Raspberry Pi OS setup on Raspberry Pi. Depending on your setup (board, configuration, sound module, Bluetooth adapter) and your preferences, you might need to adjust the scripts. They are held as simple as possible and can be used as a starting point for additional adjustments.
This project does not really support upgrading to newer versions of this script. It is meant to be adjusted to your needs and run on a clean Raspberry Pi OS install. When something goes wrong, the easiest way is to just wipe the SD card and start over. Since apart from Bluetooth pairing information all parts are stateless, this should be ok.
Updating the system using apt-get upgrade should work however.
This project does not support uninstall at all. As stated above, it is meant to run on a dedicated device on a clean Raspberry Pi OS. If you choose to use this script along with other services on the same device, or install it on an already configured device, this can lead to unpredictable behaviour and can damage the existing installation permanently.
Package and configuration choices are quite opinionated but as close to the Debian defaults as possible. Customizations can be made by modifying the scripts, but the installer should stay as simple as possible, with as few choices as possible. That said, pull requests and suggestions are of course always welcome. However I might decide not to merge changes that add too much complexity.