01-04-2025, 04:32 PM
Hi Kent - thanks for the swift reply.
The adapter is the TP-LINK Long Range Bluetooth 5.3 USB Adapter UB500 PLUS
lsusb shows 2357:0604 TP-Link TP-Link Bluetooth USB Adapter
'''
[bluetooth]# show
Controller F0:09:0D:E9:93:43 (public)
Name: Moode Bluetooth
Alias: RTL
Class: 0x000c041c
Powered: yes
Discoverable: yes
DiscoverableTimeout: 0x00000000
Pairable: yes
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-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)
Modalias: usb:v1D6Bp0246d0542
Discovering: no
Roles: central
Roles: peripheral
Advertising Features:
ActiveInstances: 0x00 (0)
SupportedInstances: 0x04 (4)
SupportedIncludes: tx-power
SupportedIncludes: appearance
SupportedIncludes: local-name
SupportedSecondaryChannels: 1M
SupportedSecondaryChannels: 2M
SupportedSecondaryChannels: Coded
'''
The connection script worked - thanks
'''
pi@moode:~ $ sudo /var/www/util/blu-control.sh -C A8:99
C:52:19:C4
** Connecting to device A8:99
C:52:19:C4
** Device A8:99
C:52:19:C4 connected
'''
But on reverting to the GUI and pressing play, I get the error message "Failed to open "ALSA Bluetooth" (alsa); Failed to open ALSA device "_audioout": No such device"
So perhaps the failure is not in the connection itself, but somewhere between connection and BT player.
As per the OP, connecting via bluetoothctl works.
Best
R
The adapter is the TP-LINK Long Range Bluetooth 5.3 USB Adapter UB500 PLUS
lsusb shows 2357:0604 TP-Link TP-Link Bluetooth USB Adapter
'''
[bluetooth]# show
Controller F0:09:0D:E9:93:43 (public)
Name: Moode Bluetooth
Alias: RTL
Class: 0x000c041c
Powered: yes
Discoverable: yes
DiscoverableTimeout: 0x00000000
Pairable: yes
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-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)
Modalias: usb:v1D6Bp0246d0542
Discovering: no
Roles: central
Roles: peripheral
Advertising Features:
ActiveInstances: 0x00 (0)
SupportedInstances: 0x04 (4)
SupportedIncludes: tx-power
SupportedIncludes: appearance
SupportedIncludes: local-name
SupportedSecondaryChannels: 1M
SupportedSecondaryChannels: 2M
SupportedSecondaryChannels: Coded
'''
The connection script worked - thanks
'''
pi@moode:~ $ sudo /var/www/util/blu-control.sh -C A8:99

** Connecting to device A8:99

** Device A8:99

'''
But on reverting to the GUI and pressing play, I get the error message "Failed to open "ALSA Bluetooth" (alsa); Failed to open ALSA device "_audioout": No such device"
So perhaps the failure is not in the connection itself, but somewhere between connection and BT player.
As per the OP, connecting via bluetoothctl works.
Best
R