Well sadly i guess the developer of this plugin has no time for it, but is still alive, that is good in general. 
I was able to install this one as many others on older release of volumio, but wasnāt satisfied with the performance over all as the firmware and everything wasnāt that smooth experience for me on a raspberry pi zero w as it is with the newest volumio version available. So whats the deal? You still donāt neet this plugin at all to get your bluetooth speaker working the āmanualā way works still fine!
An ssh session to volumio and creating the following shell script helps a lot Make it executeable after all and run it.
[code]#!/bin/bash
echo āInstalling Bluetooth Dependenciesā
sudo apt-get update
sudo apt-get install -y libasound2-dev dh-autoreconf libortp-dev bluez pi-bluetooth bluez-tools libbluetooth-dev libusb-dev libglib2.0-dev libudev-dev libical-dev libreadline-dev libsbc1 libsbc-dev
echo āCloning Bluez-Alsa repoā
cd /tmp
git clone -b v1.2.0 --single-branch https://github.com/Arkq/bluez-alsa.git
echo āBuilding Bluez-Alsaā
cd bluez-alsa
autoreconf --install
mkdir build && cd build
ā¦/configure --disable-hcitop --with-alsaplugindir=/usr/lib/arm-linux-gnueabihf/alsa-lib
make
echo āInstalling Bluez-Alsaā
sudo make install
cat > /lib/systemd/system/bluezalsa.service <<EOC
[Unit]
Description=BluezAlsa proxy
Requires=bluetooth.service
After=bluetooth.service
[Service]
Type=simple
User=root
Group=audio
ExecStart=/usr/bin/bluealsa --disable-hfp
[Install]
WantedBy=multi-user.target
EOC
sudo systemctl daemon-reload
sudo systemctl enable bluezalsa.service
#requred to end the plugin install
echo āplugininstallendā[/code]
After the process is done it can take a while, as some things need to be compiled.
Reboot the system and checkout if the service is running:
systemctl status bluezalsaIf yes then go for pairing your raspy with your speaker, make it a trustable and connect at least.
bluetoothctl
[bluetooth]# power on
[bluetooth]# agent on
[bluetooth]# default-agent
[bluetooth]# scan on
[NEW] Device xx:xx
[bluetooth]# pair xx:xx
[bluetooth]# trust xx:xx
[bluetooth]# connect xx:xx
[bluetooth]# exit
Well thatās almost it!
Two more steps and you are there:
First of all you could patch the mpd.conf in /etc which is not a good idea at all! Just do a search for a mpd.conf volumio config template as root:
sudo -scd /
find -name mpd.conf.*
Well you will see a result with two pretty long path and mpd.conf.tmpl so here you go edit this file and put after last output device following:
After that create a new hidden file in your /home/volumio directory with the name: .asoundrc with following content:
Specify the parameters of the Bluetooth connection
defaults.bluealsa {
interface "hci0" # host Bluetooth adapter
device "xx:xx:x:x:xx:x" # Bluetooth headset MAC address
profile "a2dp"
}
change the mac address to the one you had seen during pairing process, donāt forget of course to put you speaker into pairing process before trying and thatās it!
If you start now playing something from webinterface a webradio or local files it should work like a charm, if not and you have a choppy sound as i discovered for the first time then you have probably enabled the wlan and bluetooth module at same time. This is the root of the issue. To solve it i used an old wlan usb stick and disabled the internal one. Same should work if you use an external bluetooth module and disable the internal. This can be done via config.txt in /etc.
In general if you donāt change you bluetooth speakers like some people their socks, everyday, it is a way to have nice small internet radio for a bluetooth speaker.
However the scapcast plugin donāt work with bluetooth devices as it need to be implemented somehow, the only way it should wirk would be to use a direct soundcard connection to the speaker.
Regards,
Fossy
