That’s what I saw in your logs. It should really be tidied up with --purge but then you would have to run sudo apt-get install --reinstall armv7-bluezalsa-osmc to make sure you have the latest conf files. This won’t affect your .asoundrc.
I you switch to Bluetooth Audio once it should always switch to your BT as soon as it connects and back to HDMI when it disconnect no need to change here.
The device should auto connect if you paired it. Only issue I have seen if the device is paired with multiple devices the auto connect sometimes fails.
I have OSMC setup on a Pi3 with IQaudio DAC HAT - using the Nov 21 version. It all works fine as a music player for material in my library.
Now, I’d like to set it up to operate as a Bluetooth speaker for my Smart TV so I figure I should follow the second section - Streaming to your OSMC device. However as the Pi is now operating headless I can only access the web interface or command line. Is it possible to pair/trust the TV Bluetooth from the command line?
Thank you so much, the guide is very clear and excellent.
I had given up a year ago with pulse, but today I just paired and activated both my BT headset and speaker, and all is nice and working !
Streaming from the smartphone is working fine as well.
I’m having some difficulty in bluetoothctl. I get the errors below when trying to power on or make the controller discoverable although I can change the pairable status. Have I missed some other required steps?
[bluetooth]# show
Controller B8:27:EB:5F:32:CF
Name: osmc
Alias: osmc
Class: 0x000000
Powered: no
Discoverable: no
Pairable: yes
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d052B
Discovering: no
[bluetooth]# power on
Failed to set power on: org.bluez.Error.Blocked
[bluetooth]# discoverable on
Failed to set discoverable on: org.bluez.Error.Failed
[bluetooth]# pairable off
Changing pairable off succeeded
[CHG] Controller B8:27:EB:5F:32:CF Pairable: no
[bluetooth]# pairable on
Changing pairable on succeeded
[CHG] Controller B8:27:EB:5F:32:CF Pairable: yes
[bluetooth]#
For audio devices, you would normally set that device in discoverable mode and initiate pairing from your OSMC device. Follow the steps above. Do not mess with power (as long as bluetooth is enabled in MyOSMC) or discoverable.
tried tree different android smartphones to pair, but fails always.
build 2022.03 and current build 2022.06 for rpi3 with onboard bluetooth.
same fail with or without pin.
btw: connecting wifi fails too on current build 2022.06.