Dear @nerd,
today I was able to connect the BT remote to the 4.010 beta release of volumio.
Have done exactly same as yesterday, but today it worked.
Unfortunately despite successful pairing, keystrokes are not recognized.
- Device model Bluetooth Media Button
- Hardware platform Raspberry Pi 5
- Bluetooth dongle or internal chip model
Internal Chip :
volumio@korellmusik:~$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 1997:2433 Shenzhen Riitek Technology Co., Ltd wireless mini keyboard with touchpad
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
volumio@korellmusik:~$ hciconfig -a
hci0: Type: Primary Bus: UART
BD Address: 2C:CF:67:60:4C:23 ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN
RX bytes:9620 acl:373 sco:0 events:434 errors:0
TX bytes:68483 acl:10 sco:0 commands:408 errors:0
Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH SNIFF
Link mode: PERIPHERAL ACCEPT
Name: 'korellmusik'
Class: 0x0c041c
Service Classes: Rendering, Capturing
Device Class: Audio/Video, Portable Audio
HCI Version: 5.0 (0x9) Revision: 0x17e
LMP Version: 5.0 (0x9) Subversion: 0x6119
Manufacturer: Cypress Semiconductor (305)
- Hardware class of the remote HID, I believe .
For your records - what I have done :
volumio@korellmusik:~$ bluetoothctl
Agent registeredct to bluetoothd...
AdvertisementMonitor path registered
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# pairable on
Changing pairable on succeeded
[bluetooth]# scan on
SetDiscoveryFilter success
Discovery started
[CHG] Controller 2C:CF:67:60:4C:23 Discovering: yes
[NEW] Device 30:4A:3F:23:57:0B 30-4A-3F-23-57-0B
[NEW] Device 3D:28:DA:58:D5:E6 3D-28-DA-58-D5-E6
[NEW] Device 01:41:D1:7F:8A:0E 01-41-D1-7F-8A-0E
[NEW] Device 2F:EF:09:E0:60:9E 2F-EF-09-E0-60-9E
[NEW] Device 2D:6A:12:4C:EE:11 2D-6A-12-4C-EE-11
[DEL] Device 30:4A:3F:23:57:0B 30-4A-3F-23-57-0B
[DEL] Device 3D:28:DA:58:D5:E6 3D-28-DA-58-D5-E6
[DEL] Device 01:41:D1:7F:8A:0E 01-41-D1-7F-8A-0E
[NEW] Device 0C:FC:83:8B:91:C5 BT005 <--THIS is the BT remote
[bluetooth]# pair 0C:FC:83:8B:91:C5
Attempting to pair with 0C:FC:83:8B:91:C5
[CHG] Device 0C:FC:83:8B:91:C5 Connected: yes
[CHG] Device 0C:FC:83:8B:91:C5 Bonded: yes
[CHG] Device 0C:FC:83:8B:91:C5 WakeAllowed: yes
[CHG] Device 0C:FC:83:8B:91:C5 Modalias: usb:v0000p0000d0000
[CHG] Device 0C:FC:83:8B:91:C5 UUIDs: 00001124-0000-1000-8000-00805f9b34fb
[CHG] Device 0C:FC:83:8B:91:C5 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device 0C:FC:83:8B:91:C5 ServicesResolved: yes
[CHG] Device 0C:FC:83:8B:91:C5 Paired: yes
Pairing successful
[CHG] Device 0C:FC:83:8B:91:C5 ServicesResolved: no
[CHG] Device 0C:FC:83:8B:91:C5 Connected: no
[bluetooth]# trust 0C:FC:83:8B:91:C5
[CHG] Device 0C:FC:83:8B:91:C5 Trusted: yes
Changing 0C:FC:83:8B:91:C5 trust succeeded
[bluetooth]# connect 0C:FC:83:8B:91:C5
Attempting to connect to 0C:FC:83:8B:91:C5
[CHG] Device 0C:FC:83:8B:91:C5 Connected: yes
Connection successful
[CHG] Device 0C:FC:83:8B:91:C5 ServicesResolved: yes
[BT005]# exit
What the volumio system “thinks” about this is logged in:
In all other earlier installationt the BT device broadcasts on channel 0 so I have modified triggerhappy config file:
sudo nano /etc/triggerhappy/triggers.d/audio.conf
(i commented out default config and added below)
KEY_PLAYPAUSE 0 /usr/local/bin/volumio toggle
KEY_NEXTSONG 0 /usr/local/bin/volumio next
KEY_PREVIOUSSONG 0 /usr/local/bin/volumio previous
sudo /etc/init.d/triggerhappy reload
rm /lib/systemd/system/triggerhappy.socket
sudo reboot
As stated above unfortunately keystrokes are not recognized 
For this reason I’ve tried to catch keystrokes with thd :
volumio@korellmusik:~$ sudo thd --dump /dev/input/event0
^Z
[1]+ Stopped sudo thd --dump /dev/input/event0
volumio@korellmusik:~$ sudo thd --dump /dev/input/event1
^Z
[2]+ Stopped sudo thd --dump /dev/input/event1
volumio@korellmusik:~$ sudo thd --dump /dev/input/event2
^Z
[3]+ Stopped sudo thd --dump /dev/input/event2
So no success there.
To double-check BT connection tried bluetoothctl again:
volumio@korellmusik:~$ bluetoothctl
Agent registered
AdvertisementMonitor path registered
[BT005]# exit
volumio@korellmusik:~$
BT005 is written as prompt which I interpret as connected.
So far my findings.
regards,
Ralf