Trying to connect UE Boom 2 via Bluetooth to OSMC on RPi 3

[themeadows94]

Here’s what happens with bluetoothctl:

osmc@osmc:~$ bluetoothctl
[NEW] Controller B8:27:EB:91:23:AC osmc [default]
[NEW] Device 88:C6:26:9C:F6:D4 UE BOOM 2
[bluetooth]# agent on
Agent registered
[bluetooth]# trust 88:C6:26:9C:F6:D4
[CHG] Device 88:C6:26:9C:F6:D4 Trusted: yes
Changing 88:C6:26:9C:F6:D4 trust succeeded
[bluetooth]# pair 88:C6:26:9C:F6:D4
Attempting to pair with 88:C6:26:9C:F6:D4
[CHG] Device 88:C6:26:9C:F6:D4 Connected: yes
[CHG] Device 88:C6:26:9C:F6:D4 Paired: yes
Pairing successful
[CHG] Device 88:C6:26:9C:F6:D4 Connected: no
[bluetooth]# connect 88:C6:26:9C:F6:D4
Attempting to connect to 88:C6:26:9C:F6:D4
Failed to connect: org.bluez.Error.Failed
[bluetooth]# 

Could anyone suggest what might be the next step to getting this thing connected via bluetooth? Thanks!

[fzinken]

@themeadows94

Could anyone suggest what might be the next step to getting this thing connected via bluetooth?

[Deprecated] [TESTING] Bluetooth audio streaming (A2DP)

Hi, We’d like to add Bluetooth audio streaming to the App Store shortly, but first we’d like to get some feedback and testing done. Make sure your system is fully up to date, and then run the following commands: sudo apt-get update sudo apt-get install a2dp-app-osmc Note: Pairing is sometimes problematic. This is being worked on. If you experience stutters or dropouts, it may be your dongle. I personally experienced this with a couple of Bluetooth dongles and had better luck with other one…

[themeadows94]

Thanks for this! I’m using the built-in Bluetooth on the Pi 3. But anyway - we’re getting somewhere! I ran apt-get update and apt-get dist-upgrade and the command above. Retried connecting with the following results:

[bluetooth]# agent on
Agent registered
[bluetooth]# scan on
Discovery started
[CHG] Controller 60:57:18:C3:4C:C1 Discovering: yes
[NEW] Device 88:C6:26:9C:F6:D4 UE BOOM 2
[bluetooth]# trust 88:C6:26:9C:F6:D4
[CHG] Device 88:C6:26:9C:F6:D4 Trusted: yes
Changing 88:C6:26:9C:F6:D4 trust succeeded
[bluetooth]# pair 88:C6:26:9C:F6:D4
Attempting to pair with 88:C6:26:9C:F6:D4
[CHG] Device 88:C6:26:9C:F6:D4 Connected: yes
[CHG] Device 88:C6:26:9C:F6:D4 UUIDs: 00000000-deca-fade-deca-deafdecacaff
[CHG] Device 88:C6:26:9C:F6:D4 UUIDs: 00001101-0000-1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:9C:F6:D4 UUIDs: 0000110a-0000-1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:9C:F6:D4 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:9C:F6:D4 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:9C:F6:D4 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:9C:F6:D4 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:9C:F6:D4 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:9C:F6:D4 Paired: yes
Pairing successful
[CHG] Device 88:C6:26:9C:F6:D4 Connected: no
[bluetooth]# connect 88:C6:26:9C:F6:D4
Attempting to connect to 88:C6:26:9C:F6:D4
[CHG] Device 88:C6:26:9C:F6:D4 Connected: yes    [bluetooth]# agent on
Agent registered
[bluetooth]# scan on
Discovery started
[CHG] Controller 60:57:18:C3:4C:C1 Discovering: yes
[NEW] Device 88:C6:26:9C:F6:D4 UE BOOM 2
[bluetooth]# trust 88:C6:26:9C:F6:D4
[CHG] Device 88:C6:26:9C:F6:D4 Trusted: yes
Changing 88:C6:26:9C:F6:D4 trust succeeded
[bluetooth]# pair 88:C6:26:9C:F6:D4
Attempting to pair with 88:C6:26:9C:F6:D4
[CHG] Device 88:C6:26:9C:F6:D4 Connected: yes
[CHG] Device 88:C6:26:9C:F6:D4 UUIDs: 00000000-deca-fade-deca-deafdecacaff
[CHG] Device 88:C6:26:9C:F6:D4 UUIDs: 00001101-0000-1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:9C:F6:D4 UUIDs: 0000110a-0000-1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:9C:F6:D4 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:9C:F6:D4 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:9C:F6:D4 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:9C:F6:D4 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:9C:F6:D4 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:9C:F6:D4 Paired: yes
Pairing successful
[CHG] Device 88:C6:26:9C:F6:D4 Connected: no
[bluetooth]# connect 88:C6:26:9C:F6:D4
Attempting to connect to 88:C6:26:9C:F6:D4
[CHG] Device 88:C6:26:9C:F6:D4 Connected: yes
Connection successful
[NEW] Device BC:B1:F3:72:56:AB C3350
Connection successful
[NEW] Device BC:B1:F3:72:56:AB C3350    [bluetooth]# agent on
Agent registered
[bluetooth]# scan on
Discovery started
[CHG] Controller 60:57:18:C3:4C:C1 Discovering: yes
[NEW] Device 88:C6:26:9C:F6:D4 UE BOOM 2
[bluetooth]# trust 88:C6:26:9C:F6:D4
[CHG] Device 88:C6:26:9C:F6:D4 Trusted: yes
Changing 88:C6:26:9C:F6:D4 trust succeeded
[bluetooth]# pair 88:C6:26:9C:F6:D4
Attempting to pair with 88:C6:26:9C:F6:D4
[CHG] Device 88:C6:26:9C:F6:D4 Connected: yes
[CHG] Device 88:C6:26:9C:F6:D4 UUIDs: 00000000-deca-fade-deca-deafdecacaff
[CHG] Device 88:C6:26:9C:F6:D4 UUIDs: 00001101-0000-1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:9C:F6:D4 UUIDs: 0000110a-0000-1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:9C:F6:D4 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:9C:F6:D4 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:9C:F6:D4 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:9C:F6:D4 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:9C:F6:D4 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:9C:F6:D4 Paired: yes
Pairing successful
[CHG] Device 88:C6:26:9C:F6:D4 Connected: no
[bluetooth]# connect 88:C6:26:9C:F6:D4
Attempting to connect to 88:C6:26:9C:F6:D4
[CHG] Device 88:C6:26:9C:F6:D4 Connected: yes
Connection successful
[NEW] Device BC:B1:F3:72:56:AB C3350

No luck unfortunately! The “speaker connected” sound is played and no “speaker discconected” sound follows. I select as audio output “ALSA: OSMC streaming to Bluetooth speaker / headphones” but no audio is coming out of the (apparently connected) Bluetooth speaker, just out of the projector I have connected to the Pi 3 via HDMI.

[fzinken]

Have you tried to connect from within MyOSMC instead of manually via bluetoothctl?

[themeadows94]

Initially I checked within MyOSMC to see whether it was connected. I just connected again via MyOSMC, seemingly with success, but audio is still only coming out of the projector via HDMI.

[fzinken]

@themeadows94

but audio is still only coming out of the projector via HDMI.

Try to reboot, generally if you choose “ALSA: OSMC streaming to Bluetooth speaker / headphones” and your speakers are connected then it should automatically only play to bluetooth and not HDMI

[themeadows94]

Rebooted, audio still outputting via HDMI only, despite speaker appearing to be connected:

[UE BOOM 2]# info 88:C6:26:9C:F6:D4
Device 88:C6:26:9C:F6:D4
	Name: UE BOOM 2
	Alias: UE BOOM 2
	Class: 0x240404
	Icon: audio-card
	Paired: yes
	Trusted: yes
	Blocked: no
	Connected: yes
	LegacyPairing: no
	UUID: Vendor specific           (00000000-deca-fade-deca-deafdecacaff)
	UUID: Serial Port               (00001101-0000-1000-8000-00805f9b34fb)
	UUID: Audio Source              (0000110a-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

Device is a benq w1110.

[themeadows94]

Also tried rebooting without HDMI connected, and reconnecting to the speaker via bluetoothctl and using Yatse on android as a controller.

Could it be significant that I’m not seeing pulseaudio/a2dp as output options?

[themeadows94]

I finally got this working faultlessly. I have to follow a very specific order:

• If bluetooth speaker is currently connected but audio is only coming out via HDMI, then disconnect the speaker via shh/bluetoothctl
• In OSMC, go to Settings>System>Audio and choose analogue as sound output device.
• Restart OSMC
• Make bluetooth speaker discoverable
• ssh into OSMC
• at the OSMC command line, type ‘bluetoothctl’
• type ‘agent on’ and hit enter
• type ‘scan on’ and hit enter
• wait for the mac address of the speaker to appear
• type ‘trust [mac address]’
• type ‘pair [mac address]’
• bluetoothctl will at this stage say the speaker is paired and connected. then, a few seconds later, will say the speaker is not connected. ignore this.
• type ‘connect [mac address]’
• and the speaker connects! In OSMC, go to Settings>System>Audio and choose bluetooth as the output device.

This is using a UE Boom 2 and this → Bluetooth 4.0-Adapter, USB-A | Bluetooth | Notebook & Computer | 2direct which I got from German ebay. for 8 euros.