Hi! I’m new to the forum and have been using Volumio on a Pi 0 W with PhatDAC. I’m a Dutch music lover and love the sound but:
I want to control the player with bluetooth instead of Wifi so I can use the wifi to play spotify etc.
This is perhaps ‘easiest’ with TCP/IP over bluetooth but I’m no Linux Guru and can’t make this:
stackoverflow.com/questions/283 … an-systems
Can this be added to a next release, please?
Use of wifi to control the RPi and play spotify are not mutually exclusive.
Hey chsim1, thanks for answering.
I understand that it is not one or the other but consider these scenarios:
- Using my phone as hotspot for my Pi to stream (I haven’t found a way to access the volumio interface that way)
- Using a public hot-spot. Most of the time, two clients can’t contact each other on the same hotspot for security.
I’ve found most of the solution, I just don’t know how to put it all together, make it start automatically and (hopefully) package it as a plugin.
To automatically allow bluetooth clients to pair: raspberrypi.org/forums/view … 8&p=752712
To set up a PAN: udoo.org/docs-neo/Wireless_ … 20NAP.html
My goal is to have the bluetooth interface act as it’s own dhcp server so that phones can use the default volumio interface without extra hassle.
What are your thoughts?
Ah, with further explanation it makes sense , and not something that I have tried. I do have a portable Volumio device that I take in the car, but in that case I use the Volumio hotspot (and the sd card).
It would make a good guide when you get it all working. Good luck.
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.
This apparently simple suggestion actually turns into something far more complex than I was expecting. Updating the kernel is very much in the pipeline, and is hoped to be sooner than later. However, wholesale movement to Debian Stretch is not on the radar (at least as far as I am aware) for RPi.