@andrewjrpi123 said in Can't sucesfully pair PS4 Dualshock controller with retropie.:

@mitu Incidentally, running/closing retroarch doesn't seem to create a runcommand.log

It's created only when you start a game, not when you start RetroArch from the RetroPie system. Start a game first, with verbose logging as explained in the docs, get the 'unconfigured message', then exit the game (press Esc on the keyboard) and you can then find the /dev/shm/runcommand.log file.

@Thorr69 Yeah, DUH on me. I saw XBox and then put my bliinders on! MY bad!

@GoshGeeGolly said in Pi4, pairing random Bluetooth devices.:

Does installing vice, from source, maybe damage some core dependencies of retropie itself. Hence the weirdness?

No, that shouldn't affect Bluetooth connectivity. Also, why install from source when the binary is available ? Vice is also installed out of the box, so no installation should be necessary.

Would I have better luck with a USB dongle? I do have a pretty decent Asus BT400 I think somewhere, but I'd have thought by the year 2020 the Pi4 might have a reasonable enough chip??

If you have a metal case or an USB3 hdd connected, that may interfere with the wireless chip on the Pi and an external USB dongle may work better. You haven't provided the full details asked in https://retropie.org.uk/forum/topic/3/read-this-first, that would have helped diagnose this faster.

Try removing all Bluetooth connected devices from the RetroPie-Setup configuration, then re-pair the controller (I assume 'dual sense' is the new PS5 controller) and see if it works better.

@pscotto1234 Yes.

ok, i solved it myself. and here's the solution for all future "truth seekers" ;)

i updated some packages:
apt update #refresh catalog
apt install bluetooth/oldstable bluez-firmware/oldstable bluez/oldstable pi-bluetooth
reboot

afterwards, the pairing worked as easy as it should.

@mitu Sorry for the late response!

There were indeed no events when I tested with evtest.

I completely removed the keyboard again, rebooted and started Pixel. I again paired the keyboard, and made sure it worked in Pixel. Then I rebooted into ES again, again no keyboard..... some kind of weird inspiration made me go to the Retropie Config (you know, where the setup.sh is started) and, much to my surprise, I found that after a few button pushes the keyboard started working! I have no idea what went on and why it worked, because apart from opening setup I did nothing differently from the first time. After leaving the config I started evtest again (via the remote console) and actually this time around the events were showing up! The keyboard actually started to work!

Soooo happy now, as after adding the proper event source to the moonlight config I actually have full keyboard support there as well!!!

Thank you again for your help and patience @mitu !

@cyrusxvi Yes - just follow the docs and use the sixaxis helper for the P3 controllers.

@retroresolution

Hi RR, I had the exact same problem and it was driving me insane... thanks for figuring this out and sharing your solution!

@buzz You also seem to have an existing topic regarding this - please do not open multiple topics for the same issue.

@zacho95 Also another thing you can try is powering off the console, pulling the power cord/power supply, press the power button on the Xbone a couple of times to drain it, and then reboot and retry.
I used to get paid to do this shit for Microsoft :)

When you connect a controller to an XBONE via wired or wireless, it saves the ID of the console in the controller's memory, so if it is not connecting to it after all of these steps, it is probably the wireless functionality on the controller that is dead (in all my years of working we have not had the wireless adapter on the console side break). I have seen a lot of those original controllers break over the years :)

Also if you have a friend with an XBONE, try to pair it to that console

@odosayshi
Will do the same If I found a fix!

Hello and thanks for reply.
Yes, it's Bluetooth.

I've tried to pair it via Bluetooth pairing procedure.
It's recognized by Raspberry, but when I go to PAIR it, I got a Timeout error.

Same error I receive pairing controller with my Mac (I can pair ORIGINAL PS3 Wireless controller).

I think I'll trash out the controller and use an Xbox 360 wireless controller.

The PS3 controller can only be synced to one device at a time. It remembers the Mac address of the device it's synced to. Nice thing is once synced to a pi, all you have to do is plug it in via USB on the pi, press the ps button and then unplug. To go back to PS3, plug the USB into the PS3, press the ps button then unplug.