Dualshock 3 doesn't pair in 3.6.20

[kindkains]

Your system information

• Steam client version: 1730853027
• SteamOS version: 3.6.20
• Opted into Steam client beta?: [Yes/No] No
• Opted into SteamOS beta?: [Yes/No] No
• Have you checked for updates in Settings > System?: [Yes/No] Yes

Please describe your issue in as much detail as possible:

Describe what you expected should happen and what did happen.

I always was able to connect my original PS3 Controller to the Steam Deck.

1. Plug in via usb
2. Unplug
3. Press PS Button
4. Ready

But since the last Update it seems Impossible

1. Plug in via usb
2. Plugin via usb
3. Unplug
4. Press PS Button
5. Lights are flashing, but nothing happens

I tried to go to desktop mode, opened a terminal and wrote

bluetoothctl devices

But the PS3 Controllers are not listet.

bluetoothctl list

I see only the steamdeck default Controller.

How can I fix this?

[Sunspark-007]

I confirm this. I have a Dualshock 3 and it pairs fine with 3.4 but not with 3.6.20.

Add new Bluetooth device in desktop mode doesn't do anything anymore.

Looks like it is some sort of issue that also affects other controllers.

https://github.com/bluez/bluez/issues/673#issuecomment-1858431729 https://github.com/bluez/bluez/issues/771 https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931

bluez needs to be updated and the controller needs to be paired in wired mode somehow.. it can't be paired in bt mode.

[kindkains]

I found maybe a solution, but I can not reproduce it, because I was able to connect one of my two Dualshock Controllers, but not both. Maybe they differ in their firmware or it was just luck. But I will tell my steps, so maybe it may help someone else.

• in Desktop mode open the bluetooth settings and a terminal
• in bluetooth settings go to Setup
• 
• make sure, that bluetooth is activated, will be activated due startup and (guess this is the important one) bluetooth will accept recieving data anytime
• 
• then go back, choose "Add new device", start the pairing of your dualshock, and when you are happy like me, you will see it in the device list and it can be paired
• maybe you must do this serveral times (like me) while you look into the terminal and enter "bluetoothctl devices"
• when you see the MAC address of the controller, then enter "bluetoothctl pair THE-MAC-ADDRESS" and "bluetoothctl trust THE-MAC-ADDRESS"

I am not sure what worked first, the pairing in the gui or the pairing in the terminal, I did both simular and I needed some tries. But then suddenly my first PS3 Dualshock was paired and is working now.

As I already told, I have still trouble to repeat this with my second controller. It is a little bit weird, because I could see the first (working) controller in the GUI devices list as a controller (the icon is clearly a controller icon) but the second one always appears only with the standard bluetooth icon.

So I guess they have differnt firmwares installed, I do not know what else could it be. But maybe some of you may be lucky and can pair your controller in the way I did. Let me know, when it worked for you.

[Sunspark-007]

I saw this comment on Reddit, haven't tested, but makes sense since the issues I linked talk about bluez:

"After putting the input.conf in place (/etc/bluetooth) just like you did, try this:

You'll need to install bluez-plugins (sudo pacman -S bluez-plugins). In case pacman whines about pgp signature or something you disable that to install anyways. Remember to re-enable the signature check afterwards. Next, run the command "bluetoothctl devices Trusted" to list all deviced and "bluetoothctl remove xx:xx:xx:xx:xx:xx" and remove the ps3 controller manually in case it is in there.

Restart your deck. Now you can plug the ps3 controller via usb and wait for the little pop-up asking to trust the device."

/etc/bluetooth/input.conf file should contain these 3 lines:

[General]
ClassicBondedOnly=false
UserspaceHID=false

Valve really needs to address this.. users should not be expected to create an input.conf file and install a bluez plugin from the terminal.. it should "just work" ideally from the gaming mode without having to drop down to desktop mode like we are discussing here.

[gytdoo]

Dropping in to say I’m also experiencing this issue exactly as described in the first post with two different model authentic Sony DualShock 3s. They were previously working fine wirelessly before the 3.6 update. I also noticed in the steam input menu there’s no gyro option when plugged in via usb. Not sure if that’s how it’s always been, but motion controls still function in rpcs3.

Slight side tangent, but it would be very cool if in the process of fixing this, someone found a way to get pressure sensitive buttons to officially be supported in steam input. It’s a very handy feature and these controllers still have many years left in them thanks to their high quality analog sticks.

[Hahasamian]

Valve really needs to address this.. users should not be expected to create an input.conf file and install a bluez plugin from the terminal.. it should "just work" ideally from the gaming mode without having to drop down to desktop mode like we are discussing here.

Dude I've been looking all over for some fix to this issue and then I see this

This is it. This is all I needed to do, create an input.conf file and things are back to how they used to be. Thank you <3

This right here is the root of the issue: input.conf is missing from /etc/bluetooth ! Please fix it soon 🙏

[qmgsqyf]

Same issues here, Valve team please fix it soon. DS3 is my favorite controller.