12.0-nightly can't connect Sony PS3 bluetooth remote

buuuuugs · December 22, 2023 at 11:31 AM

Yesterday i've tried LibreELEC-RPi5.aarch64-12.0-nightly-20231219-865d980.img.gz on my RaspberryPi 5 and i had to find out that i can't connect my Sony PS3 bluetooth remote. I got always asked for a pin at the first buttonpress after establishing a connection, no matter how i connect it (trust and connect/connect). I removed and disconnected it multiple times and added/connected it again with the same results.

I'm now back on 11.0 (LibreELEC-RPi5.arm-11.0-nightly-20231218-f33f513.img.gz) and the remote works as expected (with trust and connect).

**chewitt** · December 23, 2023 at 7:42 AM

Does it make any difference to perform the pairing/truest using bluetoothctl over SSH?

buuuuugs · December 23, 2023 at 10:35 AM

Will flash another Sd-Card later and check it out.

buuuuugs · December 23, 2023 at 11:51 AM

I've flashed LibreELEC-RPi5.aarch64-12.0-nightly-20231222-581a2fe

Code

Attempting to pair with XX:XX:XX:XX:XX:XX
[bluetooth]# hci0 device_flags_changed: XX:XX:XX:XX:XX:XX (BR/EDR)
[bluetooth]#      supp: 0x00000001  curr: 0x00000000
[bluetooth]# hci0 type 7 discovering off
[bluetooth]# hci0 XX:XX:XX:XX:XX:XX type BR/EDR connect failed (status 0x04, Connect Failed)
[bluetooth]# Failed to pair: org.bluez.Error.ConnectionAttemptFailed
[bluetooth]# [DEL] Device XX:XX:XX:XX:XX:XX BD Remote Control

trust XX:XX:XX:XX:XX:XX
[bluetooth]# [NEW] Device XX:XX:XX:XX:XX:XX BD Remote Control
[bluetooth]# trust XX:XX:XX:XX:XX:XX
[bluetooth]# [CHG] Device XX:XX:XX:XX:XX:XX Trusted: yes
[bluetooth]# Changing XX:XX:XX:XX:XX:XX trust succeeded

connect XX:XX:XX:XX:XX:XX
Attempting to connect to XX:XX:XX:XX:XX:XX
[bluetooth]# hci0 device_flags_changed: XX:XX:XX:XX:XX:XX (BR/EDR)
[bluetooth]#      supp: 0x00000001  curr: 0x00000000
[bluetooth]# hci0 XX:XX:XX:XX:XX:XX type BR/EDR connected eir_len 24
[CHG] Device XX:XX:XX:XX:XX:XX Connected: yes

Display More

noggin · January 13, 2024 at 2:49 PM

I'm having the same issue trying to pair a PS3 BD Remote on a Pi 5 running LE 12 nightly from 20240106. The PS3 BD remote is a second gen one (with TV and AVR IR remote functionality) that used to work fine with older versions of LE (not sure when I last used it) and I can't pair it either via bluetoothctl or the Add On.

(I get prompts for a PIN when the remote tries to connect with the Pi5 - but 0000 and 1234 don't do anything - and I used not to have a PIN prompt I'm sure - it just paired?)

Code

Attempting to pair with 64:D4:BD:6A:C2:62
[bluetooth]# hci0 device_flags_changed: 64:D4:BD:6A:C2:62 (BR/EDR)
[bluetooth]#      supp: 0x00000001  curr: 0x00000000
[bluetooth]# hci0 type 7 discovering off
[bluetooth]# hci0 64:D4:BD:6A:C2:62 type BR/EDR connected eir_len 24
[CHG] Device 64:D4:BD:6A:C2:62 Connected: yes
[BD Remote Control]# hci0 64:D4:BD:6A:C2:62 auth failed with status 0x0b (Rejected)
[BD Remote Control]# Failed to pair: org.bluez.Error.AuthenticationRejected
hci0 64:D4:BD:6A:C2:62 type BR/EDR disconnected with reason 2
[CHG] Device 64:D4:BD:6A:C2:62 Connected: no

I found this reference to an issue https://forums.raspberrypi.com/viewtopic.php?f=28&t=21045

Could it be relevant?

**chewitt** · January 13, 2024 at 8:10 PM Best Answer

Diff

diff --git a/packages/network/bluez/package.mk b/packages/network/bluez/package.mk
index 9170f27418..0dd5ebef4d 100644
--- a/packages/network/bluez/package.mk
+++ b/packages/network/bluez/package.mk
@@ -62,6 +62,8 @@ post_makeinstall_target() {
         -e "s|^#\[Policy\]|\[Policy\]|g" \
         -e "s|^#AutoEnable.*|AutoEnable=true|g" \
         -e "s|^#JustWorksRepairing.*|JustWorksRepairing=always|g"
+    echo "[General]" > ${INSTALL}/etc/bluetooth/input.conf
+    echo "ClassicBondedOnly=false" >> ${INSTALL}/etc/bluetooth/input.conf
 
   mkdir -p ${INSTALL}/usr/share/services
     cp -P ${PKG_DIR}/default.d/*.conf ${INSTALL}/usr/share/services

Display More

noggin https://chewitt.libreelec.tv/testing/LibreE…h64-11.80.0.tar contains ^ this patch based on information from https://github.com/bluez/bluez/issues/696 and https://github.com/bluez/bluez/is…ment-1854599254 which reads like the same issue.

noggin · January 14, 2024 at 9:30 AM

Quote from chewitt

Diff

diff --git a/packages/network/bluez/package.mk b/packages/network/bluez/package.mk
index 9170f27418..0dd5ebef4d 100644
--- a/packages/network/bluez/package.mk
+++ b/packages/network/bluez/package.mk
@@ -62,6 +62,8 @@ post_makeinstall_target() {
         -e "s|^#\[Policy\]|\[Policy\]|g" \
         -e "s|^#AutoEnable.*|AutoEnable=true|g" \
         -e "s|^#JustWorksRepairing.*|JustWorksRepairing=always|g"
+    echo "[General]" > ${INSTALL}/etc/bluetooth/input.conf
+    echo "ClassicBondedOnly=false" >> ${INSTALL}/etc/bluetooth/input.conf
 
   mkdir -p ${INSTALL}/usr/share/services
     cp -P ${PKG_DIR}/default.d/*.conf ${INSTALL}/usr/share/services

Display More

noggin https://chewitt.libreelec.tv/testing/LibreE…h64-11.80.0.tar contains ^ this patch based on information from https://github.com/bluez/bluez/issues/696 and https://github.com/bluez/bluez/is…ment-1854599254 which reads like the same issue.

Thanks for this chewitt - using the above patched tar I can trust and connect using the LE add-on (though I initially used bluetoothctl to connect to test) - and so far it seems to work - no constant nags for a PIN. (No need to pair in the add-on or bluetoothctl but the controller does need to be in pairing mode - SELECT+ENTER held down gets it into pairing mode.)

**chewitt** · January 14, 2024 at 10:32 AM

noggin thanks for confirming. I've sent the change to the LE repo for merging.