Hello @Chalking, https://github.com/ValveSoftware/steam-devices/pull/69 looks relevant. I'd try adding something like SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="057e", ATTRS{idProduct}=="2069", MODE="0660", TAG+="uaccess" to 60-steam-input.rules (based on slouken's link https://github.com/libsdl-org/SDL/blob/d94cd1efad89953a360bcd8835a066104da00003/src/joystick/usb_ids.h#L111-L114).
@kisak-valve I edited the file (for others, it's located in /lib/udev/rules.d/60-steam-input.rules)
After that, restarted Steam (in Beta client, don't know if that matters right now) + reconnected the controller.
It works :D
(Linux Mint 22.2)
Thank you.
Is there any chance to use the Pro 2 Controller wireless?
Hi, I used the workaround from @kisak-valve successfully for a couple of weeks, however sometime between today and last week my Switch 2 Pro Controller stopped working, the /lib/udev/rules.d/60-steam-input.rules file was reset. After modifying it again it resumed to work but if the file keeps changing this is very annoying.
Is there a plan to add the line permanently? I don't see a difference between it and the other devices.
Thanks in advance
this workaround seems to have stopped working on the newest steam beta release. the controller now just gets recognized as a regular switch pro controller and none of the inputs are registered. the manually added line is still in the file, so it's not an issue of the file resetting
It worked perfectly for me without any tweaks from when I got the controller up until a few days ago, and now it detects the controller I can see it in controller settings, But pressing any buttons makes it try to connect to my switch 2
It worked perfectly for me without any tweaks from when I got the controller up until a few days ago, and now it detects the controller I can see it in controller settings, But pressing any buttons makes it try to connect to my switch 2
I'm having the same issue
It worked perfectly for me without any tweaks from when I got the controller up until a few days ago, and now it detects the controller I can see it in controller settings, But pressing any buttons makes it try to connect to my switch 2
I'm having the same issue
i don't really use github so i don't know if this is the right place to share this but this reddit thread worked for me!
https://www.reddit.com/r/linux_gaming/comments/1px4ko6/any_switch_2_pro_controller_support_on_linux_yet/
My Pro 2 Controller is / was working fine - Preview Channel SteamOS / Stable SteamClient - but as soon as i join the SteamClient BETA, it stopps working. The controller is getting detected - but no button presses work.
if i revert to steam stable, it works again (wired of course)
I have been using a switch 2 pro controller wired for months without issue, but after the June 26th steam client update, steam only recognizes the controller, without getting any input from it.
It worked perfectly for me without any tweaks from when I got the controller up until a few days ago, and now it detects the controller I can see it in controller settings, But pressing any buttons makes it try to connect to my switch 2
I'm having the same issue
Me too
i've found a (for me) working solution. as soon as you opt in the Steam RT3 - Client BETA (slider in settings) it starts working again.
i've found a (for me) working solution. as soon as you opt in the Steam RT3 - Client BETA (slider in settings) it starts working again.
works for me also. thanks!
I have been using a switch 2 pro controller wired for months without issue, but after the June 26th steam client update, steam only recognizes the controller, without getting any input from it.
Same here. I'd rather stick to the stable SteamOS rather than switch to beta though.
EDIT: SteamOS Beta + Experimental RT3 client works as of today. I'm turning off wifi and holding this build until this is fixed long term as I'm currently travelling for 6 weeks.
Same here. Wired Switch 2 was working fine until a few days ago. It doesn't matter if I use SteamOS Stable, Beta or Preview.
I can't get it to work at all. No inputs registering.
Tested on:
SteamOS 3.8.1.4 Stable
Latest SteamOS Beta (same behaviour)
Direct USB-C connection to the Steam Deck (no hub)
Symptoms:
Controller is detected and appears in Steam's controller list.
Steam's "Test Device Inputs" page receives no button or stick input.
If the Deck is booted with the controller already connected, the controller test shows the same phantom analog values every boot. Unplugging and reconnecting clears the phantom values, but inputs remain completely dead.
Diagnostics:
lsusb correctly identifies the controller as 057e:2069 (Nintendo Pro Controller).
dmesg shows successful USB/HID enumeration with no errors:
hid-generic 0003:057E:2069.0001: input,hidraw0: USB HID v1.11 Gamepad
evtest lists the controller (/dev/input/event4), but pressing buttons and moving sticks generates no events at all.
The controller worked previously on this same Steam Deck over USB, so this appears to be a regression?
CachyOS
both Stable and Beta Steam
What worked for me is waking the controller using procon2tool on Chromium Browsers
or the python version
But it registers the controller as Switch 1 Pro Controller (just with the Switch 2 name).
So no paddle and C-button support like on Windows..
Edit: Nvm on Steam Beta if you go to Settings > Interface > Use experimental SteamRT3 Steam Client (on the very bottom) worked!!
Does anyonw know if this is still working on the latest Steam Beta RT3 client?
I've been holding off updating, but there's big issues with HDR and external screen support lol.
Does anyonw know if this is still working on the latest Steam Beta RT3 client? I've been holding off updating, but there's big issues with HDR and external screen support lol.
Yes I still have to switch back and forth between RT3 (Switch 2 Pro Controller support) and stable (for other stuff).
Nothing extracted yet.
Your system information
tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs]Please describe your issue in as much detail as possible:
It seems as though Nintendo Switch 2 Pro Controller support has been temporarily disabled on all versions of SteamOS and the Steam Client as of today, December 24th, 2025.
I just received one as a Christmas present, as was looking forward to using it, and now have found that it's useless until an update comes out. Not even the beta branches allow use of this feature. I understand that it was causing crashes with other controllers, but I'd like to accept the risks to be able to use my new controller. It seems that the Stable branch was updated to disable this on December 19th, and the Beta branch was updated on December 24th to disable this feature.
I am unable to switch to the Preview branch on Steam Deck to check if that would change anything, due to another issue that's already been listed on this GitHub.
I would very much like an option to reenable this feature until a proper solution is found and rolled out, so that I may at least attempt to use my new controller.
Maybe somewhere the the developer menu, and/or in the Beta branches. I understand that resolving crashes is important, but it's incredibly poor timing and frustrating to have received this very expensive controller and not be able to use it in any way whatsoever, when it was announced that Steam added support for it it weeks ago, even if I'm prepared to accept the risks.Thank you very much.