Comments on: Fixed: Connect Bluetooth Headphones with your Raspberry PI

By: peppe8o

peppe8o — Tue, 10 May 2022 16:18:17 +0000

In reply to Ben.

Hi Ben,
what happens if you issue a new “connect xx:xx:xx:xx:xx” command in bluetoothctl after changing the output?

By: Ben

Ben — Sat, 07 May 2022 16:53:32 +0000

Awesome tutorial. I was able to get completely connected but for some reason when I try to change the output use my bluetooth headphones I get this error:

“Failed to connect to Bluetooth device – Device not found by PulseAudio”

If I look at the bluetooth.service I get this error:

May 07 11:48:23 raspberrypi bluetoothd[829]: Unable to get connect data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)

Any advice on this problem? I found a guide where someone was having the same issues and someone was putting together a walkthrough on how to fix it but it was never updated. Any help would be greatly appreciated.

By: peppe8o

peppe8o — Fri, 25 Mar 2022 22:15:15 +0000

In reply to Noel. Happy it worked to you too! Thank you for your feedback, Noel

By: Noel

Noel — Tue, 22 Mar 2022 21:23:24 +0000

Finally a tutorial that actually worked for me! So glad to have my RPI 3B+ Buster connecting to my A2DP car radio by bluetooth. Thank you so much!

By: peppe8o

peppe8o — Thu, 16 Sep 2021 09:46:37 +0000

In reply to djs. Hi djs, sincerely, some users commented that without pulseaudio should be working. If it works without it, you can leave pulseaudio disabled. I assembled the procedure by a sum of internet posts and this could be not required.

By: djs

djs — Fri, 10 Sep 2021 11:41:23 +0000

Wow – thanks so much – endless fiddling with this on a fresh install until I read this.

I have a question – you instruct to do a manual start of pulse audio (pulseaudio –start).

It seems there is a disabled pulse.audio service at the user level and when I start it, it works. Should that be set to enable to always start?

Everything seems to work without enabling the service – so I’m not understanding it’s role in this post nor whether it would be good to enable.

Thanks!

By: Ray KT

Ray KT — Sun, 29 Aug 2021 03:07:55 +0000

In reply to peppe8o. downgrading the bluez will solve this MAC address problem.

By: peppe8o

peppe8o — Tue, 17 Aug 2021 09:40:43 +0000

In reply to Phil.

I just now realized that AA:AA:AA:AA:AA:AA wasn’t to hide your MAC but it is the real result you are getting…
Did you started from a fresh Raspberry PI OS installation or from an existing one? I read in some forums that old Raspbian versions had a similar issue with some Bluez releases.

By: Phil

Phil — Mon, 16 Aug 2021 20:57:49 +0000

The controller never ever has the MAC AA:AA:AA:AA:AA:AA. This is a kind of dummy.

By: peppe8o

peppe8o — Mon, 16 Aug 2021 14:07:45 +0000

In reply to Phil. You are seeing only 1 MAC address, which is the controller one (this is the RPI bluetooth module). If you see in my post, there is a point where is show mine ones:

[CHG] Controller B8:27:EB:23:73:DF Discovering: yes
[NEW] Device 00:25:DB:78:86:98 BTC7

First row was my RPI, second row was my bluetooth device (a headphone). You should make your external device discoverable and scan it from Raspberry PI. If you can't find it, also check supported bluetooth versions for your 2 bluetooth devices. From Raspberry PI side, you can use my Raspberry PI models comparing post