Sorry to reply under my son’s login but I can’t be bothered to make my own account .
I actually am a Linux Guru and I’ve made some headway on this ‘project’ of his.
Following instructions here: blog.fraggod.net/2015/03/28/blue … ez-5x.html
I’ve managed to get my Nexus 5x to create a network-over-bluetooth connection to the Pi. It’s not automatic yet and a lot can be improved but it’s another step.
However, I’m not a developer and although I know all the technologies that have been applied in Volumio by name (nice technical overview, btw!)
The raspbian image seems to be missing quite a bit of the bluetooth tools that are even in Debian Jessie proper.
So steps still to take:
- upgrade both the kernel and the bluetooth toolchain to later versions to fully support Bluetooth LE.
- automate the network detection with further systemd changes, including setting up DHCP on the bridged bnep interface.
- make the volumio web interface listen on the bnep bridge address.
- set up and automate routing if the wifi of the pi is connected to an access point? (Seems pointless, though, but cool.)
- Redirect the volumio app/interface to the bluetooth provided IP address instead (weighted? forced? Might be a fixed address one can change by hand in a config file if needed.)
- package into a plugin
I’m starting to think, though that this is best served with waiting for a raspbian (and therefore Volumio, I hope) upgrade to Debian stretch so that Raspbian isn’t really needed anymore.
Big question: is there a way to deploy the Volumio components ‘clean’ onto Debian stretch? That would simplify further development massively. There’s now a way to run Debian Stretch proper on Raspberry Pi so that would help.