Bluetooth controller - entering pairing PIN
-
Hey guys
Hoping for some help here. I've got a bluetooth controller I wish to use with Retropie. When I pair it, it asks for the PIN. Now, the PIN on this device isn't the stadnard 0000, it's 1234. So I tell Retropie this is what the PIN is - great - but then Retropie (quite rightly) tells me to enter 1234 on the device in order to pair.
Unfortunately, the device is an original 3 button Mega Drive controller that has had a HC-06 bluetooth module installed in it.
How can I effectively enter this PIN on the device? I've seen a video on YouTube on how to change the PIN on the HC-06, but this needs all sorts of hardware etc to do...
Help?
-
Anyone? By the way I’ve since successfully paired it with an Android device - it didn’t ask me to enter the PIN on the controller.
So, I think the issue is with Pi itself. Thoughts?
-
@Dinsdale said in Bluetooth controller - entering pairing PIN:
So, I think the issue is with Pi itself. Thoughts?
Try to pair it manually with
bluetoothctl
from the command line, something like https://github.com/recalbox/recalbox-os/wiki/Connect-bluetooth-controller-manually-(EN). -
Thanks. Tried that, still getting an error when trying to connect... which is "Failed to connect: org.bluez.Error.NotAvailable". Looking up this issue elsewhere I was able to get a solid light on the pad by using sudo rfcomm connect hci0 00:18:E4:34:FD:B5.
But in Retropie I still can't configure the controller when I hold a button down...
So it's sort of connected but sort of not.
-
This post is deleted! -
Here is some info on the info command... I'm totally lost.
Device 00:18:E4:34:FD:B5 Name: HC-06 Alias: HC-06 Class: 0x001f00 Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: yes UUID: Serial Port (00001101-0000-1000-8000-00805f9b34fb) RSSI: -50
-
@Dinsdale Can you to see if the device is detected as a gampad/joystick with
jstest
(https://retropie.org.uk/docs/RetroArch-Configuration/#determining-button-values) ?
You can also quickly runcat /proc/bus/input/devices
to see if it is detected as an input device.
-
Doesnt look like it as I only get this:
I: Bus=0003 Vendor=1c4f Product=0002 Version=0110 N: Name="SIGMACHIP USB Keyboard" P: Phys=usb-3f980000.usb-1.3/input0 S: Sysfs=/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:1C4F:0002.0001/input/input0 U: Uniq= H: Handlers=sysrq kbd leds event0 B: PROP=0 B: EV=120013 B: KEY=10000 7 ff800000 7ff febeffdf f3cfffff ffffffff fffffffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=1c4f Product=0002 Version=0110 N: Name="SIGMACHIP USB Keyboard" P: Phys=usb-3f980000.usb-1.3/input1 S: Sysfs=/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.1/0003:1C4F:0002.0002/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=1f B: KEY=3007f 0 0 0 0 483ffff 17aff32d bf544446 0 0 1 130c13 b17c000 267bfa d941dfed 9e1680 4400 0 10000002 B: REL=40 B: ABS=1 0 B: MSC=10
I have done some research and THIS page says I need to install bluez-rfcomm and bluez-hcitool. Now, that's because this module in this pad is an HC-06... but it says these tools have been depreciated also.
I checked the version of Bluez and I'm using 5.43... I know the latest seems to be 5.50. How can I upgrade it? (I'm not saying this will solve my problem, but may be worth a go).
-
@Dinsdale I don't know if upgrading the Bluetooth stack would make a difference. Maybe an udev rule (something like https://askubuntu.com/questions/1041679/generic-bluetooth-joystick-driver-udev-rules) tailored to your device might work.
-
Thanks. Hmmm, tried that using the GUI but no difference. Feel I’m missing something obvious here...
-
Anyone! I’m really desperate to fix this.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.