No Longer Works on SteamOS 3.5

[MrMcAyyy]

I know just about nothing about code. All I know is that when I'm on SteamOS 3.4 this works perfectly and on 3.5 it doesn't work at all. I know there are a lot of background changes taking place for 3.5 so I assume it has something to do with that. This is one of the most useful things I've found for the Steam Deck and would love to see it continue forward to the next update of SteamOS.

[jefferai]

Can confirm, does not work with recent SteamOS.

[ds22x]

Unless I'm missing something important, if I run ls -l /sys/bus/usb/drivers/usbhid/ in konsole, the Steam Deck controllers "3-3:1.X" USB3 HID ID entries are missing entirely, only listing three "1-3:1.X" USB1 HIDs.
Maybe that has something to do with why it doesn't work anymore?

[Alexhrywkiw]

Just chiming in that also not working for me as of 3.5 sad as this made some games playable and I haven't found another work around. Hopefully this can be fixed.

[ds22x]

Can confirm changing the "3-3:1.X" entries in disable_steam_input.sh to "1-3:1.X" fixes the issue on 3.5.

[MrMcAyyy]

That fixed it for me. Thanks for your help!

[jefferai]

@MrMcAyyy Can you reopen this please? It would be nice for this to be fixed in the official repo and if the issue is closed the maintainer might not see that there is a problem.

[Mazebird]

Unless I'm missing something important, if I run ls -l /sys/bus/usb/drivers/usbhid/ in konsole, the Steam Deck controllers "3-3:1.X" USB3 HID ID entries are missing entirely, only listing three "1-3:1.X" USB1 HIDs. Maybe that has something to do with why it doesn't work anymore?

I have tried your solution and it work, so I have created Pull Request.

[Slvrtnge]

Hi, silly question, but when I'm editing the disable_steam_input.sh file, do I do it in a text edit program like KWrite then just save?

[Mazebird]

Hi, silly question, but when I'm editing the disable_steam_input.sh file, do I do it in a text edit program like KWrite then just save?

Yeah, it should work

[ds22x]

Can confirm changing the "3-3:1.X" entries in disable_steam_input.sh to "1-3:1.X" fixes the issue on 3.5.

Having reinstalled 3.5.7. after upgrading my SSD, running the command now results in the previous "3-3:1.X" being returned instead.
Can anyone else running 3.5.7. confirm if this is the case for them as well?

[Slvrtnge]

Can confirm changing the "3-3:1.X" entries in disable_steam_input.sh to "1-3:1.X" fixes the issue on 3.5.

Having reinstalled 3.5.7. after upgrading my SSD, running the command now results in the previous "3-3:1.X" being returned instead. Can anyone else running 3.5.7. confirm if this is the case for them as well?

Hi yes rerunning does return the “3-3:1.X” entries (all 6 of them) and with the latest steam OS update, this version of the script works fine! Changing those entries to the “1-3:1.X” actually doesn’t fix the problem anymore. Leave the script as is now! All better. Yay!

[maxexcloo]

How's this working now for everyone?

3.5.7

(deck@steam-deck ~)$ ls -l /sys/bus/usb/drivers/usbhid/
lrwxrwxrwx 1 root root    0 Dec 27 14:08 1-3:1.0 -> ../../../../devices/pci0000:00/0000:00:08.1/0000:04:00.4/usb1/1-3/1-3:1.0
lrwxrwxrwx 1 root root    0 Dec 27 14:08 1-3:1.1 -> ../../../../devices/pci0000:00/0000:00:08.1/0000:04:00.4/usb1/1-3/1-3:1.1
lrwxrwxrwx 1 root root    0 Dec 27 14:08 1-3:1.2 -> ../../../../devices/pci0000:00/0000:00:08.1/0000:04:00.4/usb1/1-3/1-3:1.2```

[Slvrtnge]

Works great for me overall as is right from the install code! No need to edit a file anymore however I noticed that when I’ve connected a controller and turned it off again for some reason, the steam deck built in controller often retains its own turned off status and doesn’t let me manipulate the built in controller till several restarts later. The built in always comes back it just takes those several restarts. 

[Lol260pro]

hi i'm having the same issue since the 3.5 but have not been able to make it work i already tried running the script as it is and changing it with the little about coding I know but nothing seems to work, would really appreciated some help.

[Sixoul]

I can't seem to be able to get this to work. I've tried changing the "3-3:1.X" entries and that didn't work. I'm on 3.5.7 and the original version and the edited entries do not work.

[Slvrtnge]

Oooh, try seeing if it’s a conflict with a Decky loader plug-in? Also make sure you’re on the stable version of Decky not the beta. The plug-in that caused issues for me was cheat deck I believe but yours might be another! Might be a trial and error of uninstalling one after another to see the conflict. Keep us posted if ya find the issue! My controller disable version is working fine! Maybe check the devices list doc and make sure your desired controller is correctly listed. Roland DuBoisiCloudOn Jan 23, 2024, at 11:52 PM, Louis Wagner ***@***.***> wrote: I can't seem to be able to get this to work. I've tried changing the "3-3:1.X" entries and that didn't work. I'm on 3.5.7 and the original version and the edited entries do not work. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[ThisByzantineConduit]

Hey, I see in the comments that earlier versions of SteamOS 3.5 required changing some lines of code, but now others commenting say it works fine as is with the latest release.

However, I can't get this to work at all. Followed install instructions carefully and pulled the name of my Bluetooth controller using the Konsole command and it was already on the default list ("Pro Controller"). Any idea how to get this working?

I also see someone mentioned Decky Plugins interfering - do we know which ones cause issues? The only controls related one I have is EmuDecky Controls.

Thanks!