Puesto al día el 19 de noviembre de 2026.
hardware del bluetooth
en primer lugar, cabe comprobar si el sistema operativo detecta el hardware:
sudo bluetoothctl[NEW] Controller B8:27:EB:03:01:15 RB3 [default]
lo que, en cualquier momento, equivale al comando list:
sudo bluetoothctl
[bluetooth] listController B8:27:EB:03:01:15 RB3 [default]
activar/desactivar el bluetooth de la raspberry pi 3
nano /boot/config.txt
dtoverlay=pi3-disable-bt
si se elimina o comenta esta línea, el bluetooth se activará normalmente.
servicio del bluetooth
sudo systemctl status bluetooth.service
bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled)
Active: inactive (dead)
si el servicio de bluetooth no está activo (esto es, inactive), se lo puede habilitar mediante systemctl:
sudo systemctl enable bluetooth.serviceSynchronizing state for bluetooth.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d bluetooth defaults
Executing /usr/sbin/update-rc.d bluetooth enable
una vez se ha dispuesto que el servicio bluetooth se activará cada vez que arranque el sistema operativo (esto es, enable), puede activarse el servicio mediante start:
sudo systemctl start bluetooth.servicesudo systemctl status bluetooth.service
bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled)
Active: active (running) since vie 2018-08-03 15:39:50 CEST; 13s ago
bluetoothctl
bluetoothctlAgent registered
[CHG] Controller B8:27:EB:03:01:15 Pairable: yes
[bluetooth] scan on[NEW] Device 68:52:10:77:E0:02 [AV] B-Series Soundbar
[bluetooth] devicesDevice 68:52:10:77:E0:02 [AV] B-Series Soundbar
[bluetooth] pair 68:52:10:77:E0:02Attempting to pair with 68:52:10:77:E0:02
[CHG] Device 68:52:10:77:E0:02 Connected: yes
[...]
[CHG] Device 68:52:10:77:E0:02 ServicesResolved: yes
[CHG] Device 68:52:10:77:E0:02 Paired: yes
Pairing successful
[bluetooth] trust 68:52:10:77:E0:02[CHG] Device 68:52:10:77:E0:02 Trusted: yes
Changing 68:52:10:77:E0:02 trust succeeded
[bluetooth] connect 68:52:10:77:E0:02Attempting to connect to 68:52:10:77:E0:02
Connection successful
[bluetooth] exit
bash
nano /home/ernesto/bin/rtb#!/bin/bash
bluetoothctl pair 68:52:10:77:E0:02
bluetoothctl trust 68:52:10:77:E0:02
bluetoothctl connect 68:52:10:77:E0:02
chmod +x /home/ernesto/bin/rtb
rc.local
nano /etc/rc.local/home/ernesto/bin/rtb
exit 0
sudo systemctl restart rc-local.service
si se llama al ejecutable /home/ernesto/bin/rtb desde /etc/rc-local, éste se ejecutará cada vez que arranque el sistema operativo y, de esta manera, se conectará la raspberry pi con el dispositivo 68:52:10:77:E0:02 vía bluetooth automáticamente.
ALSA + Bluez 5
You can use bluez-alsa to provide integration between Bluez and ALSA. This setup can be used either completely without Pulseaudio, or you can then use your headset as another ALSA device in Pulseaudio (in which case disable its bluetooth support, so the two don't collide).
«ALSA + Bluez 5» en Bluetooth headset de la Gentoo wiki.
sudo apt show bluez-alsa-utilsBluetooth Audio ALSA Backend allow bluetooth audio without PulseAudio [...] From now on, Bluez acts as a middleware between an audio application, which implements Bluetooth audio profile, and a Bluetooth audio device.
sudo apt install bluez-alsa-utils
MPD
nano audio/.mpd/mpd.confaudio_output {
type "alsa"
name "RB3 BLUETOOTH"
device "bluealsa"
mixer_type "software"
}
puede añadirse este audio_output además del que se emplee, por ejemplo, con la tarjeta de sonido.
fuentes
- «ALSA + Bluez 5» en Bluetooth headset de la Gentoo wiki.
- arkq, «Bluetooth Audio ALSA Backend» en Github, 2026.
- Maximilian Ballard, «Connect to a Bluetooth Device via the Terminal» en Baeldung linux, 2026.