Hello,
I just noticed that Volumio is in my list of Bluetooth devices (on phone, tablet and on laptop). I don’t need (and don’t even want) any wireless signal so I have switched it off in sources. Despite that it seems that Bluetooth is always on.
Is it a bug? And how to switch bluetooth off completely?
Thanks in advance!
Volumio 3.179
RPI 3b+ based streamer
@Vennesch Is it active in Settings/Sources?
Edit: ah, you already stated that it isn’t.
I just tested on mine after turning it off in Sources. I can also still see it as a bluetooth device and can even pair with it. It doesn’t actually connect and play though. Looks like a bug.
V3.179
Pi4
I see the same behaviour.
Running V3.182, rPi4 V1.4
If I turn BT off in Sources, it does disappear from my BT list (iOS).
Turning it back on, it appears again.
I will update to the latest test version and check it out. Thanks 
Confirmed. The bug has been fixed at latest test version. So it seems to be a known small bug
I’ve updated my Pi4 to 3.182 and with BT turned off on sources settings, it does not appear on iPhone, but it appears on Windows and it connects…
It does not turn up in my android devices. Have to check Windows and Mac
For me after performing an update it was just briefly visible on a Windows laptop (I guess it was still in cache memory, or something like that)
I did notice yesterday that this issue still seems to be there in some form, after updating to 3.378 I noticed when checking some other things on the network that I had an Volumio Bluetooth instance active.
Bluetooth is deactivated in Volumio, but can be seen both on Android and in Windows 11 - it can be paired, but at least it seems like the connection is refused.
… And here we are in Aug. 26’. I have it turned off and can see/pair from Android? WHATS THE DANG DEAL DEVs??
You do understand that this is not Google’s Android development forum - right? Perhaps you should discuss this with your smartphone manufacturer, why it caches discovered devices for a duration not to your liking.
Unless I have missed your point entirely in Aug 2026.
Kind Regards,
Yes, the snarkey little phuc that you are, missed the point.
Pound sand
Noted. Moving on to the actual question.
Let me give you the actual state of things.
The Bluetooth toggle in Volumio governs the Bluetooth audio plugin, not the radio itself. Think of it as closing the app rather than switching on flight mode. The controller can remain powered, and if the host stack is still up, a phone can still see it and can still complete a pairing exchange. Nothing is registered to accept the audio connection afterwards, which is why the connection then refuses. That matches what what you described in 2022.
If you want genuine flight mode, block the radio:
sudo rfkill block bluetooth
Check the result:
rfkill list bluetooth
To reverse it:
sudo rfkill unblock bluetooth
Note that systemctl stop bluetooth is not equivalent. That stops bluetoothd only and leaves the controller powered.
I have a plugin in the works for Volumio 4 that would put this under proper control, but I am not going to commit to a timeline on it.
If you want the underlying behaviour looked at rather than worked around, post your board model, your exact Volumio version, and a log link from http://<your_volumio_ip>/dev, taken with the toggle set to off. Without that there is nothing to investigate.
Kind Regards,
@nerd My post is from 2022, so this is an old issue from 4 years ago - so nothing I see that we need to spend any time on.