I found this threat quite helpful, it allowed me to finally connect RPi3 to EDIFIER R1700BT speakers (although no sound from them still). I have tried a couple of times to use OSMC menu to connect with and witout PIN - always failed with red BT icon next to speakers name.
DBMandrake intructions helped with block command (why block?..) in addition, see:
[bluetooth]# devices
Device 00:26:83:11:E1:9F REKSIO
Device 40:EF:4C:B6:39:5C EDIFIER R1700BT
Device F8:3F:51:2E:FC:66 F8-3F-51-2E-FC-66
[bluetooth]# pair 40:EF:4C:B6:39:5C
Attempting to pair with 40:EF:4C:B6:39:5C
Failed to pair: org.bluez.Error.AlreadyExists
[bluetooth]# trust 40:EF:4C:B6:39:5C
Changing 40:EF:4C:B6:39:5C trust succeeded
[bluetooth]# connect 40:EF:4C:B6:39:5C
Attempting to connect to 40:EF:4C:B6:39:5C
Failed to connect: org.bluez.Error.Failed
[bluetooth]# info 40:EF:4C:B6:39:5C
Device 40:EF:4C:B6:39:5C
Name: EDIFIER R1700BT
Alias: EDIFIER R1700BT
Class: 0x240428
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
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)
[bluetooth]# block 40:EF:4C:B6:39:5C
[CHG] Device 40:EF:4C:B6:39:5C Blocked: yes
Changing 40:EF:4C:B6:39:5C block succeeded
[bluetooth]# info 40:EF:4C:B6:39:5C
Device 40:EF:4C:B6:39:5C
Name: EDIFIER R1700BT
Alias: EDIFIER R1700BT
Class: 0x240428
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: yes
Connected: no
LegacyPairing: no
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)
[bluetooth]# connect 40:EF:4C:B6:39:5C
Attempting to connect to 40:EF:4C:B6:39:5C
[CHG] Device 40:EF:4C:B6:39:5C Connected: yes
Failed to connect: org.bluez.Error.Failed
[CHG] Device 40:EF:4C:B6:39:5C Connected: no
[bluetooth]# connect 40:EF:4C:B6:39:5C
Attempting to connect to 40:EF:4C:B6:39:5C
[CHG] Device 40:EF:4C:B6:39:5C Connected: yes
Niceā¦ I have reconnected manually many times, after some tens of seconds it disconnects by itself.
[CHG] Device 40:EF:4C:B6:39:5C Connected: no
[bluetooth]# connect 40:EF:4C:B6:39:5C
Attempting to connect to 40:EF:4C:B6:39:5C
[CHG] Device 40:EF:4C:B6:39:5C Connected: yes
Failed to connect: org.bluez.Error.Failed
[CHG] Device 40:EF:4C:B6:39:5C Connected: no
[bluetooth]# connect 40:EF:4C:B6:39:5C
Attempting to connect to 40:EF:4C:B6:39:5C
[CHG] Device 40:EF:4C:B6:39:5C Connected: yes
Failed to connect: org.bluez.Error.Failed
[CHG] Device 40:EF:4C:B6:39:5C Connected: no
If I go to Kodi settings during OSMC is connected to Edifiers I still do not see anything like Bluetooth audio device (standard outputs plus Digiberry). I have no problem with these speakers over bluutooth when connected to Samsung Galaxy S7 or old S4 mini - the connection simply works.
This block command really made me wonder
[bluetooth]# unblock 40:EF:4C:B6:39:5C
[CHG] Device 40:EF:4C:B6:39:5C Blocked: no
Changing 40:EF:4C:B6:39:5C unblock succeeded
[bluetooth]# connect 40:EF:4C:B6:39:5C
Attempting to connect to 40:EF:4C:B6:39:5C
Failed to connect: org.bluez.Error.Failed
[bluetooth]# connect 40:EF:4C:B6:39:5C
Attempting to connect to 40:EF:4C:B6:39:5C
Failed to connect: org.bluez.Error.Failed
[bluetooth]# block 40:EF:4C:B6:39:5C
[CHG] Device 40:EF:4C:B6:39:5C Blocked: yes
Changing 40:EF:4C:B6:39:5C block succeeded
[bluetooth]# connect 40:EF:4C:B6:39:5C
Attempting to connect to 40:EF:4C:B6:39:5C
[CHG] Device 40:EF:4C:B6:39:5C Connected: yes
[EDIFIER R1700BT]#
I have unistallled the package and the new ones it had in dependencies. I was going to use BT speakers (with great Audio Profiles script for easy output switching) for audiobooks listening, since they donāt not require the quality of a big stereo set. Since the RPi buildt-in BT module has some issues in a2dp implementation Iāll wait for released fix
The note is quite misleading, pls. see below. I could have saved some time on trying to connect via BT using built-in RPi3 module.
Note: The Bluetooth tab will only appear if you are using a compatible Bluetooth dongle. OSMC manufactures and sells a compatible dongle, available for purchase here.
And, I do agree with @tiroy . A note regarding RPi3 onboard bluetooth and OSMC would have saved me quite some time as well. Time I could have invested in improving some other features of my OSMC setup.
The reason I thougth it is still relevant, is because I can reproduce the exact behaviour @tiroy described above using bluetoothctl.
I now learned that a2dp (which I couldnāt install before) was replaced by bluez.
I have armv7-bluez-osmc installed, but I am afraid my system needs some major updates, which I will focus on first.
Yeah I assume you found the current how to already?
And yes the internal Bluetooth is still not the best especially if you use WiFi in parallel but it should work.
Indeed, I found this very helpful thread and got my Bluetooth speaker working like a charm on the upgraded OSMC / Kodi 19 Matrix. The OSMC bluetooth processes worked smoothly, no need to play with the CLI.
(Just hope that there will be a working Amazon VOD (used Sandmann79s repo before) and Netflix add-on, soon.)