[TheMechanist]

I switched from Ubuntu 14.04 to 16.04 .. unfortunately I don't get it to pair my PS3 BD Remote Control .. it worked flawlessly with bluez/blueman (v. 1.23) from the ubuntu 14.04 repository, but it seems, that newer version of bluez/blueman (v. 2.0.4) no longer support legacy pairing without pin. (tried it over cmdline with bluetoothctl, same result).

Tested pairing with Win7 - runs fine, since windows still supports pairing without pin - other ways using a pin (0000, 1234) are reported as "not supported by device" ..

Did anybody manage to pair the PS3 remote ?

Greetz

TheMechanist

[BytEvil]

Hi. Try pairing with bluetoothctl command from console.

Code:

[root@KODI /]# bluetoothctl
[NEW] Controller 00:02:72:BF:77:0F KODI [default]
[NEW] Device 00:24:33:95:EE:1F BD Remote Control
[bluetooth]#

I have bluez v5.44 on my Arch Linux system.

[TheMechanist]

Hi. Try pairing with bluetoothctl command from console.

Code:

[root@KODI /]# bluetoothctl
[NEW] Controller 00:02:72:BF:77:0F KODI [default]
[NEW] Device 00:24:33:95:EE:1F BD Remote Control
[bluetooth]#

I have bluez v5.44 on my Arch Linux system.

I did - as mentioned ;-) - and it asks for pin when "pair" command is used (bluez 5.37 ubuntu 16.04 package) .. does it ask for pin on your system ?

[BytEvil]

I use these commands for pairing

Code:

# bluetoothctl
[bluetooth]# list
[bluetooth]# select <BT dongle mac>
[bluetooth]# power on
[bluetooth]# scan on
[bluetooth]# agent on
[bluetooth]# devices
Device <bd remote mac> BD Remote Control
[bluetooth]# pair <bd remote mac>
[bluetooth]# trust <bd remote mac>
[bluetooth]# connect <bd remote mac>

BD remote paired without pin.

[TheMechanist]

.. yeah, did the same steps, when I run command pair, "agent" asks for PIN ..

Code:

[bluetooth]# pair <BD>
Attempting to pair with <BD>
[CHG] Device <BD> Connected: yes
Request PIN code
[agent] Enter PIN code: 0000
Failed to pair: org.bluez.Error.AuthenticationRejected

Which keys do you press on the remote to start pairing ? I use Start & Enter (OK) ..

Obviously it's the different version of bluez - arch is bleeding edge with v. 5.44 from feb '17, ubuntu 16.04 contains 5.37 .. seems I should upgrade manually

I'll tell if this helps ..

[TheMechanist]

.. I finally got it

seems to be a bug in dbus bluetooth.conf , described here:

https://www.raspberrypi.org/forums/viewt...28&t=21045

Changed the config and performed the steps again - but don't command "pair", but just "connect". Then BD was successfully registered in /proc/bus/input/devices !

Btw. I've coded a ps3-to-kodi script to use the remote without configuration ..

https://github.com/TheMechanist2/ps3rd/b...r/ps3rd.sh

Seems, that something changed, script is no longer working as with Ubuntu 14.04, keys are not correctly recognized .. scan code offset has changed: line 222

Code:

last_command=$(hexdump -s 18 -n 2 -e '1/2 "%04x"' "$ps3_interface" 2> /dev/null)

Change "-s 18" to "-s 42" and it's working again ..

[BytEvil]

It's great! I need to try your script while i'm using bdremoteng...

[TheMechanist]

It's great! I need to try your script while i'm using bdremoteng...

Yeah, the script is a much simpler solution (just bash, no dependencies) since it uses kodi http control, it simply reads remote keys and sends via json rpc commands to kodi .. keys can be mapped to every function that kodi supports without hassle, just change the commands in the script ..

[BytEvil]

Yes. This is very nice! Thanks!!! I'll try it!

[Soli]

But it won't sleep the remote, right? I still have to use patched bluez 4 or my batteries won't last more than a few days (if I remember correctly)

[TheMechanist]

But it won't sleep the remote, right? I still have to use patched bluez 4 or my batteries won't last more than a few days (if I remember correctly)

the script just reads the keys and is not associated to the bluetooth stack .. I don't know, how bluez, now version 5.44, this handles .. version 4 is really old ..

I use rechargeable batteries, so it's not that mess with the power consumption ..