Failed to pair org bluez error alreadyexists

Воспроизведение звука на Intel Edison через Bluetooth с использованием Advanced Audio Distribution Profile (A2DP)

В ходе реализации проектов на плате Intel Edison иногда возникает необходимость воспроизвести звук. В последних версиях образа Yocto добавлена поддержка Alsa, и можно воспользоваться USB аудиокартой. Но большую мобильность даст использование встроенного Bluetooth модуля. Например, устройство на базе Intel Edison, которое получает аудиофайлы по сети, может находиться стационарно в одном месте в комнате. Слушать же музыку можно в любой точке помещения, используя обычные беспроводные наушники. Итак, начнём.

Вам понадобятся

Настройка

Включите ваше Bluetooth устройство и сделайте его видимым. Введите следующие команды в терминале:

Просканируйте доступные Bluetooth устройства:

Найдите ваше устройство и присоединитесь к нему (подставив его MAC адрес):

Установите соединение, если необходимо:

Закройте программу bluetoothctl:

Проверьте, что ваше A2DP устройство (в нашем случае наушники LG) распознались в pulseaudio как sink-устройство и его имя начинается с bluez_sink

Сконфигурируйте дефолтный sink для использования в pulseaudio следующими командами, подставив параметры вашего устройства:

Скопируйте аудио файл в формате wav на плату Intel Edison, используя scp (Linux) или pscp.exe (Windows) и проиграйте его через mplayer:

Используйте wav файлы, так как могут быть некоторые сложности при проигрывании mp3 файлов.

Устранение проблем

Если вы получили:

Проверьте, какое устройство у вас подключено:

Удалите устройство, к которому вы подключены (подставьте MAC-адрес вашего устройства):

Другие полезные команды bluetoothctl можно получить так:

Дополнительная информация

От переводчика

При проверке этой статьи у меня возникли некоторые проблемы. Устройство не получалось подсоединить командой connect, не было команды pactl. Плата Edison была прямо из коробки, поэтому всё это решилось перепрошивкой новой версией образа Yocto.

Чтобы перепрошить плату, можно воспользоваться следующей рекомендацией. Я сделал немного по-другому в Windows.

В папке с распакованным архивом Yocto на Windows компьютере запускаем flashall.bat. Возможно, еще понадобится программа dfu-util.exe, которую надо поместить в эту же распакованную папку. Сама программа доступна по ссылке.

Обсуждение dfu-util под Windows и перепрошивку Edison можно найти тут и тут.

Источник

Error when trying to connect to bluetooth speaker: `org.bluez.Error.Failed`

I’m running Debian Jessie 8.2. I have a bluetooth USB dongle connected to my machine.

I run sudo bluetoothctl -a then do the following:

But I can connect to my iPhone this way. Why can’t I connect to my Bose Mini II SoundLink speaker?

7 Answers 7

This may be due to the pulseaudio-module-bluetooth package not being installed. Install it if it missing, then restart pulseaudio.

If the issue is not due to the missing package, the problem in this case is that PulseAudio is not catching up. A common solution to this problem is to restart PulseAudio. Note that it is perfectly fine to run bluetoothctl as root while PulseAudio runs as user. After restarting PulseAudio, retry to connect. It is not necessary to repeat the pairing.

Continue trying second part only if above does not work for you:

If restarting PulseAudio does not work, you need to load module-bluetooth-discover.

The same load-module command can be added to /etc/pulse/default.pa . If that still does not work, or you are using PulseAudio’s system-wide mode, also load the following PulseAudio modules (again these can be loaded via your default.pa or system.pa):

Try trusting the device first before paring the device.
I got the same error while attempt to pair my AirPods to Ubuntu 16.04.
In bluetoothctl with sudo I got

Now this is what I’ve tried (full progress)

Now the AirPods works beautifully between my iPhone and Ubuntu.

this procedure works for me, thx.

I was trying to add a bluetooth speaker, this was the error message that I had,

I removed the device and then repeat all the steeps that David Jung share.

this is how it looks now:

In my case, a related error message ( Failed to pair: org.bluez.Error.AuthenticationFailed ) was happening just because the device was already paired to another source.

Lesson learned : When debugging bluetooth pairing issues, step zero should be checking the device is fully available to new connections, disconnected from any other source, and rebooting the source and the bluetooth device.

To long for a comment and hence writing an answer to benefit others from the observation :

In my case, Ubuntu 17.04, just installing the bluez ( sudo apt-get install bluez ) worked. I did not need any of the pulseaudio packages. I just followed David Jungs answer to do the first ever connection with the JBL bluetooth headset. Make sure that the headset has just been powered on — basically it is set in the discoverable mode.

Also, for reconnecting ( for example after a restart ), simply calling bluetoothctl -a and then connect works. If you have a applet in your window manager, then of course one can connect from there, otherwise the command line interface is bluetoothctl -a . Don’t forget to issue devices command in the sudo bluetoothctl -a menu to be sure that your device is available. If the device list is empty, follow first the answer from @David Jung.

Be sure to have the services running. Check for sudo systemctl status bluetooth.service and sudo systemctl status bluetooth.target . Both should be active and loaded! Sometimes, restarting both the services, before bluetoothctl -a works. I did all the commands under sudo rights, just to avoid any loopholes.

An useful utility is btmon to monitor, what exactly is going on, when you connect, or pair, or anything related to the bluetooth commands.

Источник

Arch Linux

You are not logged in.

#1 2013-07-14 11:02:32

Bluetooth audio paired but not connect?

Hi, guys. I’ve got a SONY BTN-40 handsfree set. It works very well under Windows XP and Windows 7. Now I’ve tried several times to make it working under Archlinux. Here is my step:

Now I get into bluetooth control interface:

Now I set the controller:

I scan my handfree set and paring:

See last info: «Connected no»? I am wondering why my device has connected but a short time after, it disconnected automatically.
If I manually connect my device:

Again failed here.

I think use only this «bluetoothctl» can solve this problem. Any guys know how to solve this ?

Last edited by jameschyn (2013-07-15 00:25:19)

#2 2013-07-14 17:34:51

Re: Bluetooth audio paired but not connect?

Moderator: Please use BBCode Tags code tags when posting program output.
Thanks

Nothing is too wonderful to be true, if it be consistent with the laws of nature — Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. — Alan Turing
—
How to Ask Questions the Smart Way

#3 2013-07-16 17:12:05

Re: Bluetooth audio paired but not connect?

I ran into the exact same issue today with a HomeSpot NFC-enabled Bluetooth Audio Receiver. I’m able to pair and connect, but then it disconnects immediately. Here’s my bluetoothctl session:

And here’s the relevant hcidump:

#4 2013-07-20 04:09:01

Re: Bluetooth audio paired but not connect?

No one use bluetooth handfree set under linux ?
Or every one use wired or 2.4G?

#5 2013-07-20 10:32:40

Re: Bluetooth audio paired but not connect?

The stable pulseaudio (v4.0) does not support the new bluez 5 API. The git version should support it since june.
PS: heftig has a precompiled pulseaudio-git in his private repository, it is listed here: https://wiki.archlinux.org/index.php/Un … positories

Last edited by progandy (2013-07-20 10:42:07)

#6 2013-10-08 11:51:45

Re: Bluetooth audio paired but not connect?

Using pulseaudio-git also fixed my Bluetooth Headphone issue with Gnome3.10 requiring bluez5.

#7 2013-10-08 23:00:19

Re: Bluetooth audio paired but not connect?

Why would having pulseaudio installed or not interfere with the ability to connect or to pair with one’s device?

When using bluez4 I used to connect through ALSA and didn’t even have pulseaudio installed. Did bluez5 introduce pulseaudio as a dependency or an optional dependency, but forgot to list it as such? Also, I want to note that I just tried installing pulseaudio-git from AUR and I still cannot connect to my headset using bluez5.

[Edit] It seems indeed that pulseaudio-git is needed to get headsets working with bluez5. As for getting my headset paired and connected everything seems to work fine as of today through bluetoothctl as long as I don’t forget to turn the power to the controller on and enable the agent before pairing.

Last edited by vlsd (2013-11-18 20:31:47)

#8 2013-12-02 01:03:44

Re: Bluetooth audio paired but not connect?

I have pulseaudio-git and bluez5 installed, and I have similar problem. I can pair my headset but I can not connect.

#9 2013-12-05 23:34:57

Re: Bluetooth audio paired but not connect?

I have the exact same problem — it connects shortly, never having asked for a password, and then disconnects after two seconds. Also updated to pulseaudio-git.. any further hints or troubleshooting questions anyone? Thanks..

#10 2013-12-07 20:20:48

Re: Bluetooth audio paired but not connect?

I had these same problems. It would pair, but not connect. I updated the archwiki page on my setup. here

#11 2013-12-27 12:50:58

Re: Bluetooth audio paired but not connect?

pulseaudio from [extra] pulls from a git snapshot to support bluez5 — see this and this commit. Can somebody test if it works with the package from [extra]? Otherwise it might be worth filing a bug report.

#12 2014-01-18 20:18:21

Re: Bluetooth audio paired but not connect?

Chiming in with the paired but can’t connect problem. I’ve uninstalled everything alsa and pulseaudio 4 or 5 times during the past month or so trying to get this thing to work but it never does. The wiki, which I have «followed to a t», suggests using pulseaudio-git from AUR but that package has been broken for over a month, failing with:

Is there anyone out there who has a bluetooth headset set up working on a 64 bit machine in the current sad state of affairs in the bluetooth4 not quite bluetooth5 world?

I’m on a Dell Latitude D630.

Edit: For some reason libtool wasn’t installed on my system and was causing install of pulseaudio-git to fail. Past that hurdle now but still can’t connect my bluetooth headset. Sigh.

Last edited by whatshisname (2014-01-19 17:43:25)

#13 2014-01-21 12:27:17

Re: Bluetooth audio paired but not connect?

pulseaudio-git makes no difference to me.

Please let me know if anyone finds the answer — most frustrating!

#14 2014-01-21 16:36:39

Re: Bluetooth audio paired but not connect?

OK, this seems to be a bluez5 problem. Downgrading to bluez-fedora, bluez-tools and bluez-utils (bluez4), all still in AUR, and then connecting the headset with ‘bt-audio -c’ works.

‘course, this will probably break other things, especially bluedevil which only works with bluez5

#15 2014-01-21 16:47:18

Re: Bluetooth audio paired but not connect?

Glad you got it working. After my post, I too tried downgrading — again — but it still didn’t work.

Did you use pulseaudio-git with your bluez4 installation or do you fall back to pulseaudio from the main repositories? I think I stayed with pulseaudio-git.

#16 2014-01-21 16:56:17

Re: Bluetooth audio paired but not connect?

No I did not use pulseaudio-git

I used bluez-fedora, which includes bluez-utils, and bluez-tools (change the dependency in PKGBUILD to bluez-fedora) all from AUR

bluez-tools includes bt-audio, among others, which connects the headset.

#17 2014-01-21 18:21:14

Re: Bluetooth audio paired but not connect?

There’s currently no bluez5 media api compatible alsa implementation. So either use pulseaudio and bluez5 or some outdated bluez4 AUR stuff.

#18 2014-01-21 19:03:00

Re: Bluetooth audio paired but not connect?

Are you saying that if you use pulseaudio and bluez5, then you should remove all things alsa from your system?

#19 2014-01-21 19:09:11

Re: Bluetooth audio paired but not connect?

no. I once could confirm my BT headphones working in Gnome with PA and kept alsa stuff installed but removed all BT v4 packages.

#20 2014-01-21 19:16:07

Re: Bluetooth audio paired but not connect?

pulseaudio-git makes no difference to me.

It didn’t use to work for me either, I think something changed in a semi-recent version to support my hardware ( I have a D-Link DBT-120 adapter and a Sony DR-BT50 headset).

Are you saying that if you use pulseaudio and bluez5, then you should remove all things alsa from your system?

You don’t need to remove alsa, just reroute its output through pulseaudio in asound.conf. This is what my /etc/asound.conf looks like, for reference:

#21 2014-01-21 19:22:10

Re: Bluetooth audio paired but not connect?

Also just did a bluez upgrade today (from the official repos) and while my headset still works, it took about five tries to connect to it, with messages like this:

So something is here is certainly fucky.

#22 2014-01-21 23:21:53

Re: Bluetooth audio paired but not connect?

Often with simple ‘failed’ messages like that there can be clues as to what really went wrong in the system journal.
To see the last 20 lines of the journal:

I have audio through pulseaudio to bluetooth headset working on my x86_64 desktop Arch box, but not yet
on my headless Arch ARM box. The problem is not ARM, but that there are quite a few things that just
«come along» with the desktop environment (I use xfce4) that have to be done manually on a headless system.
Starting the per-session dbus daemon and the pulseaudio server (which runs as the user,
not as root) are a couple; there may be more.

As was noted above, ALSA wlll not work with the latest bluez. The story I heard is that nobody stepped forward
to update ALSA, so this might change in the future. But for now, pulseaudio is it. The wiki has several
obsolete bluez4 references so beware of any Google searches on these problems that date from more than
a year ago.

bluez 5.13-1
pulseaudio 4.0-6

#23 2014-01-22 08:12:48

Re: Bluetooth audio paired but not connect?

For me, there is nothing reported in the journal, and my headset does not work with bluez5. I also have x86_64 arch, bluez 5-14-1 and pulseaudio 4.0.6

I confirm that it works with bluez4, so I guess it must depend on the type of hardware.

Requesting information .
BD Address: 00:0C:55:1C:CD:DA
OUI Company: Microlink Communications Inc. (00-0C-55)
Device Name: Motorola H500
LMP Version: 1.2 (0x2) LMP Subversion: 0x886
Manufacturer: Cambridge Silicon Radio (10)
Features: 0xfc 0xfe 0x0f 0x00 0x08 0x08 0x00 0x00

#24 2014-01-28 01:33:54

Re: Bluetooth audio paired but not connect?

I’m chiming in in agreement with fdservices. It’s all in the hardware!

I have spent *days* trying to get the 2 or 3 headsets around my house (the latest being a Plantronics 330) working with my laptop, trying both Bluez4 and Bluez5 to no avail.

The wiki for Bluetooth Headsets, https://wiki.archlinux.org/index.php/Bl … dio_method, mentioned success with the SoundBot SB220. So I broke down and bought a pair. They arrived today. (Nice headsets, BTW!)

My last attempt at this madness had me trying bluez4 so I started there this evening.

I began with the wiki: https://wiki.archlinux.org/index.php/Bluez4 paying particular attention to https://wiki.archlinux.org/index.php/Bl … SA_devices and editing the /etc/asound.conf file per the wiki.

The command sequence was:

systemctl start bluetooth
hcitool scan # To get the Mac address of my new headset
bluez-simple-agent # Ctrl-C to exit after the agent is registered. Ignore the error messages.
bluez-simple-agent hci0 FC:58:FA:C6:49:B3 # pairing the SoundBot
(Enter 0000 passkey)
bt-audio -c FC:58:FA:C6:49:B3 # as normal user to connect

Then a quick trip to alsamixer to make sure there weren’t any muted outputs. (This is a big gotcha. For some reason, probably due to all the tinkering around, some of the outputs continually get muted even though I have unmuted them numerous times before. Also, beware of outputs that have their volume set to max or 80%, etc. but are nonetheless muted as evidenced by the «MM» in the box below the volume scale. Click «m» to unmute them.)

This proved to be sufficient to get the new headset working with Google Talk, the primary reason for my messing with bluetooth in the first place. Happily, the SB220 was one of the options in both the «Microphone» and «Speakers» drop down boxes in «Chat» settings. Selected the SB220 in both boxes, successfully tested the mike and and headset and I’m finally back to making long distance phone calls with my laptop. Yay!

Back to my laptop only to discover that music played with mplayer wasn’t streaming to the headset

I installed bluez-tools which changed the /etc/asound.conf file but happily got my headset listed in pavucontrol. In the «Output devices» tab I had to click the green check mark to activate the headset whereupon «mplayer some.mp3» streamed music to my headset!!

I *might* get around to testing this with bluez5 but having gotten this far, I’m not inclined to fix something that isn’t broken.

The moral of this story is the choice of bluetooth headset/hardware makes all the difference. At least it did for me.

Perhaps we should start a list of compatible bluetooth headsets in the wiki? There is clearly a big interest in this topic considering the well over 4,400 views of this thread alone.

Источник

В ходе реализации проектов на плате Intel Edison иногда возникает необходимость воспроизвести звук. В последних версиях образа Yocto добавлена поддержка Alsa, и можно воспользоваться USB аудиокартой. Но большую мобильность даст использование встроенного Bluetooth модуля. Например, устройство на базе Intel Edison, которое получает аудиофайлы по сети, может находиться стационарно в одном месте в комнате. Слушать же музыку можно в любой точке помещения, используя обычные беспроводные наушники. Итак, начнём.

Вам понадобятся

• Звуковое Bluetooth устройство, например, наушники или колонки.
• Подключенная к WiFi сети плата Intel Edison. (Смотрите Step 3: Get your Board Online).
• Компьютер с музыкальными wav файлами, расположенный в нашей сетке.
• Установленное терминальное соединение с платой через последовательный порт (Смотрите Set Up WiFi – Intel Edison) или SSH.

Настройка

Включите ваше Bluetooth устройство и сделайте его видимым. Введите следующие команды в терминале:

rfkill unblock bluetooth
bluetoothctl

Просканируйте доступные Bluetooth устройства:

scan on

Найдите ваше устройство и присоединитесь к нему (подставив его MAC адрес):

pair 00:25:DB:05:72:F2

Установите соединение, если необходимо:

connect 00:25:DB:05:72:F2

Закройте программу bluetoothctl:

quit

Проверьте, что ваше A2DP устройство (в нашем случае наушники LG) распознались в pulseaudio как sink-устройство и его имя начинается с bluez_sink

pactl list sinks

Сконфигурируйте дефолтный sink для использования в pulseaudio следующими командами, подставив параметры вашего устройства:

pactl set-default-sink bluez_sink.00_25_DB_05_72_F2

Скопируйте аудио файл в формате wav на плату Intel Edison, используя scp (Linux) или pscp.exe (Windows) и проиграйте его через mplayer:

mplayer Intel_bong.wav2

Используйте wav файлы, так как могут быть некоторые сложности при проигрывании mp3 файлов.

Устранение проблем

Если вы получили:

Failed to pair: org.bluez.Error.AlreadyExists

Проверьте, какое устройство у вас подключено:

paired-devices

Удалите устройство, к которому вы подключены (подставьте MAC-адрес вашего устройства):

remove 78:24:AF:13:58:B9

Другие полезные команды bluetoothctl можно получить так:

help

Дополнительная информация

• Потоковое вещание по сети или через конвейер

От переводчика

При проверке этой статьи у меня возникли некоторые проблемы. Устройство не получалось подсоединить командой connect, не было команды pactl. Плата Edison была прямо из коробки, поэтому всё это решилось перепрошивкой новой версией образа Yocto.

Чтобы перепрошить плату, можно воспользоваться следующей рекомендацией. Я сделал немного по-другому в Windows.

В папке с распакованным архивом Yocto на Windows компьютере запускаем flashall.bat. Возможно, еще понадобится программа dfu-util.exe, которую надо поместить в эту же распакованную папку. Сама программа доступна по ссылке.

Обсуждение dfu-util под Windows и перепрошивку Edison можно найти тут и тут.

Читайте также:

» Практикум «Intel IoT». Edison — могучая «кроха»

i@pi400:~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
pi@pi400:~ $ uname -a
Linux pi400 5.10.17-v7l+ #1403 SMP Mon Feb 22 11:33:35 GMT 2021 armv7l GNU/Linux

pi@pi400:~ $ sudo apt update
Hit:1 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:2 http://archive.raspberrypi.org/debian buster InRelease
Reading package lists... Done
Building dependency tree       
Reading state information... Done
All packages are up to date.
pi@pi400:~ $ sudo apt upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
pi@pi400:~ $ 

pi@pi400:~ $ bluetoothctl
Agent registered
[bluetooth]# devices
Device 30:C0:1B:2E:2F:AB JBL Flip 4
Device 00:F6:20:8A:2F:12 Kitchen speaker
[bluetooth]# connect 30:C0:1B:2E:2F:AB
Attempting to connect to 30:C0:1B:2E:2F:AB
Failed to connect: org.bluez.Error.Failed
[bluetooth]# connect 00:F6:20:8A:2F:12
Attempting to connect to 00:F6:20:8A:2F:12
Failed to connect: org.bluez.Error.Failed
[bluetooth]# info 00:F6:20:8A:2F:12
Device 00:F6:20:8A:2F:12 (public)
	Name: Kitchen speaker
	Alias: Kitchen speaker
	Class: 0x00240400
	Icon: audio-card
	Paired: yes
	Trusted: yes
	Blocked: no
	Connected: no
	LegacyPairing: no
bluetooth]# info 30:C0:1B:2E:2F:AB
Device 30:C0:1B:2E:2F:AB (public)
	Name: JBL Flip 4
	Alias: JBL Flip 4
	Class: 0x00240414
	Icon: audio-card
	Paired: yes
	Trusted: yes
	Blocked: no
	Connected: no
	LegacyPairing: no
	Modalias: bluetooth:v000ApFFFFdFFFF

johann@arthur:~$ uname -a
Linux arthur 5.4.0-66-generic #74~18.04.2-Ubuntu SMP Fri Feb 5 11:17:31 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
johann@arthur:~$ bluetoothctl
[NEW] Controller FC:44:82:3B:B0:6D arthur [default]
[NEW] Device 30:C0:1B:2E:2F:AB JBL Flip 4
Agent registered
[bluetooth]# info 30:C0:1B:2E:2F:AB
Device 30:C0:1B:2E:2F:AB (public)
	Name: JBL Flip 4
	Alias: JBL Flip 4
	Class: 0x00240414
	Icon: audio-card
	Paired: yes
	Trusted: yes
	Blocked: no
	Connected: no
	LegacyPairing: no
	UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
	UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
	UUID: Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)
	UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
	Modalias: bluetooth:v000ApFFFFdFFFF
[CHG] Device 30:C0:1B:2E:2F:AB Connected: yes
[JBL Flip 4]# 

pi@pi400:~ $ groups
pi adm lp dialout cdrom sudo audio video plugdev games users input netdev lpadmin gpio i2c spi

pi@pi400:~ $ ps aux | grep pulse
pi         682  0.0  0.2 358540  8616 ?        S<sl 21:17   0:00 /usr/bin/pulseaudio --daemonize=no
pi        1520  0.0  0.0   7348   580 pts/0    S+   21:24   0:00 grep --color=auto pulse

pi@pi400:~ $ sudo bluetoothctl
Agent registered
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# devices
[bluetooth]# scan on
Discovery started
[CHG] Controller E4:5F:01:05:93:E5 Discovering: yes
[NEW] Device 4D:3D:8B:67:43:00 4D-3D-8B-67-43-00
[NEW] Device 02:37:E2:AD:4E:EB 02-37-E2-AD-4E-EB
[NEW] Device F0:99:19:3B:D4:BB F0-99-19-3B-D4-BB
[NEW] Device 08:66:98:BA:B5:D1 08-66-98-BA-B5-D1
[NEW] Device 69:97:46:D3:C4:12 69-97-46-D3-C4-12
[NEW] Device 4B:BE:43:E4:12:28 4B-BE-43-E4-12-28
[NEW] Device 30:C0:1B:2E:2F:AB JBL Flip 4
[bluetooth]# trust 30:C0:1B:2E:2F:AB
[CHG] Device 30:C0:1B:2E:2F:AB Trusted: yes
Changing 30:C0:1B:2E:2F:AB trust succeeded
[bluetooth]# pair 30:C0:1B:2E:2F:AB
Attempting to pair with 30:C0:1B:2E:2F:AB
[CHG] Device 30:C0:1B:2E:2F:AB Connected: yes
[CHG] Device 30:C0:1B:2E:2F:AB Connected: no
[bluetooth]# connect 30:C0:1B:2E:2F:AB
Attempting to connect to 30:C0:1B:2E:2F:AB
Failed to connect: org.bluez.Error.Failed
[NEW] Device 57:99:82:BA:81:84 57-99-82-BA-81-84
[CHG] Device 57:99:82:BA:81:84 ManufacturerData Key: 0x004c
[CHG] Device 57:99:82:BA:81:84 ManufacturerData Value:
  10 06 10 1a 32 62 4c a8                          ....2bL.        
[CHG] Device F0:99:19:3B:D4:BB RSSI: -89
[CHG] Device F0:99:19:3B:D4:BB RSSI: -77
[NEW] Device 4D:5E:75:01:A8:2E 4D-5E-75-01-A8-2E
[bluetooth]# connect 30:C0:1B:2E:2F:AB
Attempting to connect to 30:C0:1B:2E:2F:AB
Failed to connect: org.bluez.Error.Failed

pi@pi400:~ $ pulseaudio --verbose --start
N: [pulseaudio] main.c: User-configured server at {b9e11b12b49248988c54de6784db6e5c}unix:/run/user/1000/pulse/native, which appears to be local. Probing deeper.
I: [pulseaudio] main.c: Daemon startup successful.
pi@pi400:~ $ sudo bluetoothctl
Agent registered
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# scan on
Discovery started
[CHG] Controller E4:5F:01:05:93:E5 Discovering: yes
[NEW] Device 60:F6:06:74:4F:82 60-F6-06-74-4F-82
[NEW] Device 57:99:82:BA:81:84 57-99-82-BA-81-84
[NEW] Device F0:99:19:3B:D4:BB F0-99-19-3B-D4-BB
[NEW] Device 02:37:E2:AD:4E:EB 02-37-E2-AD-4E-EB
[NEW] Device 08:66:98:BA:B5:D1 08-66-98-BA-B5-D1
[NEW] Device 66:BD:00:1D:24:15 66-BD-00-1D-24-15
[NEW] Device 30:C0:1B:2E:2F:AB JBL Flip 4
[bluetooth]# trust 30:C0:1B:2E:2F:AB
[CHG] Device 30:C0:1B:2E:2F:AB Trusted: yes
Changing 30:C0:1B:2E:2F:AB trust succeeded
[NEW] Device 69:D1:B1:D4:20:8E 69-D1-B1-D4-20-8E
[bluetooth]# pair 30:C0:1B:2E:2F:AB
Attempting to pair with 30:C0:1B:2E:2F:AB
[CHG] Device 30:C0:1B:2E:2F:AB Connected: yes
[CHG] Device 30:C0:1B:2E:2F:AB Connected: no

[bluetooth]# paired-devices
[bluetooth]# info 30:C0:1B:2E:2F:AB
Device 30:C0:1B:2E:2F:AB (public)
	Name: JBL Flip 4
	Alias: JBL Flip 4
	Class: 0x00240414
	Icon: audio-card
	Paired: no
	Trusted: yes
	Blocked: no
	Connected: no
	LegacyPairing: no
	UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
	UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control Cont.. (0000110f-0000-1000-8000-00805f9b34fb)
	UUID: Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)
	UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
	UUID: Headset HS                (00001131-0000-1000-8000-00805f9b34fb)
	Modalias: bluetooth:v000ApFFFFdFFFF
	RSSI: -26
	TxPower: 8

[bluetooth]# pair 30:C0:1B:2E:2F:AB
Attempting to pair with 30:C0:1B:2E:2F:AB
Failed to pair: org.bluez.Error.AlreadyExists
[bluetooth]# 

pi@pi400:~ $ bluetoothctl
Agent registered
[bluetooth]# paired-devices
Device 30:C0:1B:2E:2F:AB JBL Flip 4
[bluetooth]# 

pi@retropie:~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

Return to “Raspberry Pi 400”

I’m chiming in in agreement with fdservices.  It’s all in the hardware!

I have spent *days* trying to get the 2 or 3 headsets around my house (the latest being a Plantronics 330) working with my laptop, trying both Bluez4 and Bluez5 to no avail.

The wiki for Bluetooth Headsets, https://wiki.archlinux.org/index.php/Bl … dio_method,  mentioned success with the SoundBot SB220.  So I broke down and bought a pair.  They arrived today.  (Nice headsets, BTW!)

My last attempt at this madness had me trying bluez4 so I started there this evening.

I began with the wiki: https://wiki.archlinux.org/index.php/Bluez4 paying particular attention to https://wiki.archlinux.org/index.php/Bl … SA_devices and editing the /etc/asound.conf file per the wiki. 

The command sequence was:

systemctl start bluetooth
hcitool scan  # To get the Mac address of my new headset
bluez-simple-agent # Ctrl-C to exit after the agent is registered.  Ignore the error messages.
bluez-simple-agent hci0 FC:58:FA:C6:49:B3 # pairing the SoundBot
(Enter 0000 passkey)
bt-audio -c FC:58:FA:C6:49:B3 # as normal user to connect

It connected!!!

Then a quick trip to alsamixer to make sure there weren’t any muted outputs.  (This is a big gotcha.  For some reason, probably due to all the tinkering around, some of the outputs continually get muted even though I have unmuted them numerous times before.  Also, beware of outputs that have their volume set to max or 80%, etc. but are nonetheless muted as evidenced by the «MM» in the box below the volume scale. Click «m» to unmute them.) 

This proved to be sufficient to get the new headset working with Google Talk, the primary reason for my messing with bluetooth in the first place.  Happily, the SB220 was one of the options in both the «Microphone» and «Speakers» drop down boxes in «Chat» settings.  Selected the SB220 in both boxes, successfully tested the mike and and headset and I’m finally back to making long distance phone calls with my laptop.  Yay!

Back to my laptop only to discover that music played with mplayer wasn’t streaming to the headset

So another trip to the wiki and this section: https://wiki.archlinux.org/index.php/Bl … om_the_AUR

I installed bluez-tools which changed the /etc/asound.conf file but happily got my headset listed in pavucontrol.  In the «Output devices» tab I had to click the green check mark to activate the headset whereupon «mplayer some.mp3» streamed music to my headset!!

I *might* get around to testing this with bluez5 but having gotten this far, I’m not inclined to fix something that isn’t broken.

The moral of this story is the choice of bluetooth headset/hardware makes all the difference.  At least it did for me.

Perhaps we should start a list of compatible bluetooth headsets in the wiki?  There is clearly a big interest in this topic considering the well over 4,400 views of this thread alone.

Hope this helps someone.