Is connecting remote and headphones via Bluetooth possible?

Could someone please advise if Vero4K (1st edition, without +) supports two-way Bluetooth connection? I am using Harmony Elite remote connected via Bluetooth from the beginning. Happy so far. Recently, I tried to hook up Bluetooth headphones, but unfortunately had no luck.

I must admit, that my ‘MY OSMC’ app has almost always been unresponsive on my Vero4K. It is currently upgraded to the latest version OSMC June 2020 2020.06-1. Sometimes pressing ‘Start/Stop Discovery’ under Bluetooth shows available devices, but most of the times the list is just empty. A couple of times I saw my headphones in the list (Beoplay H9 or Sennheiser TW2), but attempting to connect to either of them, with or without PIN, always returned ‘failed to connect’ message.

I wonder if it is actually possible to use two Bluetooth devices (i.e. remote and headphones) this way? If no, are there any other alternatives to connect headphones wirelessly?

Thank you.

Yes

You would need to install the ad2p package and also if your “headphones” register as “headset” you would need to change the audio sink.

To install a2dp execute this command:

sudo apt-get install a2dp-app-osmc

Thank you @fzinken! I have always been amazed with how quickly you provide assistance with users’ issues.

It’s good to know that two-way Bluetooth connection is possible on Vero4K!

With regards to my issue, perhaps I should have been more detailed in describing it. I went through all the relevant topics on this forum prior to posting my question. Of course, I was aware of a2dp package and it was already installed. I have thought that a2dp is required for Bluetooth streaming and has nothing to do with pairing a Bluetooth device. My issue is that I simply don’t see any of the two headphones in the list of available Bluetooth devices. Occasionally the headphones are listed but connection fails (as described in my original post).

Anyway, for the sake of experiment I have executed your command and got this:

osmc@Vero4K:~$ sudo apt-get install a2dp-app-osmc
Reading package lists… Done
Building dependency tree
Reading state information… Done
a2dp-app-osmc is already the newest version (1.1.3).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Could you please advice what else I should do?

Ok would try to pair via command line instead of GUI.
Start bluetoothctl

execute these commands

scan on
agent on
devices
pair <mac address for device>
trust <mac address for device>
connect <mac address for device>
exit

If you have problems share the output of those commands.

Note bluetoothctl supports tab completion so type the first two characters of the MAC and tab.

(Otherwise I would go mad.)

Great reminder

You don’t want us to comment on that :wink:

Haha, thank you guys! I have started bluetoothctl and discovered this:

osmc@Vero4K:~$ bluetoothctl
[NEW] Controller 44:2C:05:9D:2C:B1 Vero4K [default]
[NEW] Device 00:04:20:FE:AF:C9 Harmony Keyboard
[NEW] Device 00:09:A7:46:D8:52 Beoplay H9
[NEW] Device 00:1B:66:BA:EA:E0 MOMENTUM TW 2

Harmony Keyboard is my remote. It’s up and running, no issues.
Beoplay H9 is my old headphones, never worked with Vero4K and RIP for a couple of years now.
MOMENTUM TW 2 is my new headphones, which I tried to connect a couple of days ago and failed.

Command ‘scan on’ returns too many rows, but I guess the relevant ones are these two:

[CHG] Device 00:09:A7:46:D8:52 Name: LE-Beoplay H9
[CHG] Device 00:09:A7:46:D8:52 Alias: LE-Beoplay H9

LE-Beoplay H9 is my new headphones (which I would like to use together with MOMENTUM TW2 above).

My questions are:

  • How do I remove an old Beoplay H9 from the list? (Actually, should I worry?)
  • I wonder why Momentum TW 2 is listed as paired device given I got an ‘failed to connect’ message?
  • How do I pair LE-Beoplay H9? Is this its MAC - 00:09:A7:46:D8:52?

Thank you!

Read this

Just because it’s listed, doesn’t mean it’s paired. type info 00:1B:66:BA:EA:E0 to get its status.

1 Like

Now you are confusing me. The LE-Beoplay H9 that is shown is the current one based on it’s MAC.

What is output of

info 00:1B:66:BA:EA:E0
and
info 00:09:A7:46:D8:52

Thank you @grahamh and @fzinken!

This is what I’m getting:

osmc@Vero4K:~$ bluetoothctl
[NEW] Controller 44:2C:05:9D:2C:B1 Vero4K [default]
[NEW] Device 00:04:20:FE:AF:C9 Harmony Keyboard
[NEW] Device 00:09:A7:46:D8:52 LE-Beoplay H9
[NEW] Device 00:1B:66:BA:EA:E0 MOMENTUM TW 2
[Harmony Keyboard]# info 00:1B:66:BA:EA:E0
Device 00:1B:66:BA:EA:E0
Name: MOMENTUM TW 2
Alias: MOMENTUM TW 2
Class: 0x240404
Icon: audio-card
Paired: yes
Trusted: no
Blocked: no
Connected: no
LegacyPairing: no
UUID: Serial Port (00001101-0000-1000-8000-00805f9b34fb)
UUID: Headset (00001108-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)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Battery Service (0000180f-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (0000eb03-d102-11e1-9b23-00025b00a5a5)
UUID: Unknown (0000fdce-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1377p7001d0480
[Harmony Keyboard]# info 00:09:A7:46:D8:52
Device 00:09:A7:46:D8:52
Name: LE-Beoplay H9
Alias: LE-Beoplay H9
Class: 0x240418
Icon: audio-card
Paired: no
Trusted: no
Blocked: no
Connected: no
LegacyPairing: no
UUID: Serial Port (00001101-0000-1000-8000-00805f9b34fb)
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)
UUID: Vendor specific (81c2e72a-0591-443e-a1ff-05f988593351)
UUID: Vendor specific (f8d1fbe4-7966-4334-8024-ff96c9330e15)
Modalias: bluetooth:v0103p1021d0500
ServiceData Key: 0000fe26-0000-1000-8000-00805f9b34fb
ServiceData Value: 0x01
ServiceData Value: 0xaa
ServiceData Value: 0x91
ServiceData Key: 0000fe2c-0000-1000-8000-00805f9b34fb
ServiceData Value: 0x01
ServiceData Value: 0xaa
ServiceData Value: 0x91

Ok, so put the Beoplay in pairing mode and do

pair 00:09:A7:46:D8:52
trust 00:09:A7:46:D8:52
connect 00:09:A7:46:D8:52

Okay, so I guess it is now paired, but failed to connect:

[Harmony Keyboard]# pair 00:09:A7:46:D8:52
Attempting to pair with 00:09:A7:46:D8:52
[CHG] Device 00:09:A7:46:D8:52 Connected: yes
[CHG] Device 00:09:A7:46:D8:52 UUIDs: 00001101-0000-1000-8000-00805f9b34fb
[CHG] Device 00:09:A7:46:D8:52 UUIDs: 00001108-0000-1000-8000-00805f9b34fb
[CHG] Device 00:09:A7:46:D8:52 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device 00:09:A7:46:D8:52 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device 00:09:A7:46:D8:52 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device 00:09:A7:46:D8:52 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 00:09:A7:46:D8:52 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device 00:09:A7:46:D8:52 UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device 00:09:A7:46:D8:52 UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device 00:09:A7:46:D8:52 UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Device 00:09:A7:46:D8:52 UUIDs: 0000180f-0000-1000-8000-00805f9b34fb
[CHG] Device 00:09:A7:46:D8:52 UUIDs: 0000fe89-0000-1000-8000-00805f9b34fb
[CHG] Device 00:09:A7:46:D8:52 UUIDs: 81c2e72a-0591-443e-a1ff-05f988593351
[CHG] Device 00:09:A7:46:D8:52 UUIDs: 91c10d9c-aaef-42bd-b6d6-8a648c19213d
[CHG] Device 00:09:A7:46:D8:52 UUIDs: f8d1fbe4-7966-4334-8024-ff96c9330e15
[CHG] Device 00:09:A7:46:D8:52 UUIDs: fe59bfa8-7fe3-4a05-9d94-99fadc69faff
[CHG] Device 00:09:A7:46:D8:52 ServicesResolved: yes
[CHG] Device 00:09:A7:46:D8:52 Paired: yes
[NEW] Primary Service
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0001
00001801-0000-1000-8000-00805f9b34fb
Generic Attribute Profile
[NEW] Characteristic
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0001/char0002
00002a05-0000-1000-8000-00805f9b34fb
Service Changed
[NEW] Descriptor
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0001/char0002/desc0004
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
[NEW] Primary Service
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service000a
0000180a-0000-1000-8000-00805f9b34fb
Device Information
[NEW] Characteristic
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service000a/char000b
00002a24-0000-1000-8000-00805f9b34fb
Model Number String
[NEW] Characteristic
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service000a/char000d
00002a25-0000-1000-8000-00805f9b34fb
Serial Number String
[NEW] Characteristic
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service000a/char000f
00002a27-0000-1000-8000-00805f9b34fb
Hardware Revision String
[NEW] Characteristic
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service000a/char0011
00002a26-0000-1000-8000-00805f9b34fb
Firmware Revision String
[NEW] Primary Service
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0013
0000180f-0000-1000-8000-00805f9b34fb
Battery Service
[NEW] Characteristic
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0013/char0014
00002a19-0000-1000-8000-00805f9b34fb
Battery Level
[NEW] Descriptor
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0013/char0014/desc0016
00002904-0000-1000-8000-00805f9b34fb
Characteristic Format
[NEW] Descriptor
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0013/char0014/desc0017
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
[NEW] Primary Service
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0018
fe59bfa8-7fe3-4a05-9d94-99fadc69faff
Vendor specific
[NEW] Characteristic
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0018/char0019
104c022e-48d6-4dd2-8737-f8ac5489c5d4
Vendor specific
[NEW] Characteristic
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0018/char001b
69745240-ec29-4899-a2a8-cf78fd214303
Vendor specific
[NEW] Descriptor
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0018/char001b/desc001d
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
[NEW] Characteristic
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0018/char001e
70efdf00-4375-4a9e-912d-63522566d947
Vendor specific
[NEW] Descriptor
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0018/char001e/desc0020
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
[NEW] Characteristic
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0018/char0021
eea2e8a0-89f0-4985-a1e2-d91dc4a52632
Vendor specific
[NEW] Characteristic
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0018/char0023
a79e2bd1-d6e4-4d1e-8b4f-141d69011cbb
Vendor specific
[NEW] Primary Service
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0025
91c10d9c-aaef-42bd-b6d6-8a648c19213d
Vendor specific
[NEW] Characteristic
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0025/char0026
99d1064e-4517-46aa-8fb4-6be64dd1a1f1
Vendor specific
[NEW] Descriptor
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0025/char0026/desc0028
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
[NEW] Characteristic
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0025/char0029
fbe87f6c-3f1a-44b6-b577-0bac731f6e85
Vendor specific
[NEW] Descriptor
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0025/char0029/desc002b
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
[NEW] Characteristic
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0025/char002c
420791c0-bff5-4bd1-b957-371614031136
Vendor specific
[NEW] Descriptor
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0025/char002c/desc002e
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
[NEW] Characteristic
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0025/char002f
e4ef5a46-30f9-4287-a3e7-643066acb768
Vendor specific
[NEW] Descriptor
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0025/char002f/desc0031
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
[NEW] Primary Service
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0032
0000fe89-0000-1000-8000-00805f9b34fb
B&O Play A/S
[NEW] Characteristic
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0032/char0033
773e4203-a0e7-456b-96fa-e1b4ad56eb63
Vendor specific
[NEW] Characteristic
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0032/char0035
7dd2f744-16c4-4c58-88a4-0fafecc78343
Vendor specific
[NEW] Descriptor
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0032/char0035/desc0037
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
[NEW] Characteristic
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0032/char0038
44fa50b2-d0a3-472e-a939-d80cf17638bb
Vendor specific
[NEW] Descriptor
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0032/char0038/desc003a
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
[NEW] Characteristic
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0032/char003b
4446cf5f-12f2-4c1e-afe1-b15797535ba8
Vendor specific
[NEW] Descriptor
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0032/char003b/desc003d
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
[NEW] Characteristic
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0032/char003e
95c09f26-95a4-4597-a798-b8e408f5ca66
Vendor specific
[NEW] Characteristic
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0032/char0040
4a75c20f-13bd-44a1-b39d-a70f86f607a2
Vendor specific
[NEW] Descriptor
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0032/char0040/desc0042
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
[NEW] Characteristic
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0032/char0043
fa302d24-d775-4343-b9ed-8cc68ace3284
Vendor specific
[NEW] Descriptor
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0032/char0043/desc0045
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
[NEW] Characteristic
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0032/char0046
3ba91c2e-8b08-4c27-9d4e-4936a793fcfb
Vendor specific
[NEW] Characteristic
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0032/char0048
eda1e25f-be65-4d3c-ae8a-23bbaa713773
Vendor specific
[NEW] Descriptor
/org/bluez/hci0/dev_00_09_A7_46_D8_52/service0032/char0048/desc004a
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
Pairing successful
[Harmony Keyboard]# trust 00:09:A7:46:D8:52
[CHG] Device 00:09:A7:46:D8:52 Trusted: yes
Changing 00:09:A7:46:D8:52 trust succeeded
[Harmony Keyboard]# connect 00:09:A7:46:D8:52
Attempting to connect to 00:09:A7:46:D8:52
Failed to connect: org.bluez.Error.Failed

I think the answer to the question posed in the title is no if the remote includes an audio speaker. You can’t connect two BT speakers at the same time.

Hmmm… It is a Logitech Harmony Elite remote. AFAIK it does not have a speaker.

Sorry, I may have mis-read the output. What does info say (with no MAC)?

Actually, I have some update. I think I somehow managed to connect LE-Beoplay H9! :slight_smile:

[LE-Beoplay H9]# info 00:09:A7:46:D8:52
Device 00:09:A7:46:D8:52
Name: LE-Beoplay H9
Alias: LE-Beoplay H9
Class: 0x240418
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Serial Port (00001101-0000-1000-8000-00805f9b34fb)
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)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Battery Service (0000180f-0000-1000-8000-00805f9b34fb)
UUID: B&O Play A/S (0000fe89-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (81c2e72a-0591-443e-a1ff-05f988593351)
UUID: Vendor specific (91c10d9c-aaef-42bd-b6d6-8a648c19213d)
UUID: Vendor specific (f8d1fbe4-7966-4334-8024-ff96c9330e15)
UUID: Vendor specific (fe59bfa8-7fe3-4a05-9d94-99fadc69faff)
Modalias: bluetooth:v0103p1021d0500
ServiceData Key: 0000fe26-0000-1000-8000-00805f9b34fb
ServiceData Value: 0x01
ServiceData Value: 0xaa
ServiceData Value: 0x91
ServiceData Key: 0000fe2c-0000-1000-8000-00805f9b34fb
ServiceData Value: 0x01
ServiceData Value: 0xaa
ServiceData Value: 0x91

That looks good. So you should be able to use it when you change the audio output to pulseaudio entry in settings - system - audio.

If you don’t get audio then you might need to change the audio sink

Now, my understanding is that I have to change Audio Output Device in settings. I only have these options:

  • Default (AML-M8AUDIO: HDMI, S/PDIR & analogue)
  • AML-M8AUDIO, HDMI
  • USB Audio 2.0, Analog
  • USB Audio 2.0, S/PDIF

Usually I am using the last option to send audio to DAC. To use Bluetooth headphones should not I have something else in this list?

pulseaudio is definitely missing. :frowning:

Yes you are missing the pulseaudio entry