c/steamdeck · by UntouchedWagons@lemmy.ca · 3y

How do I use my xbox one wireless receiver on my deck?

This is the receiver I have: https://www.amazon.ca/gp/product/B00ZB7W4QU/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

And this is the controller I have: https://www.amazon.ca/gp/product/B08DF26MXW/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

If I try to connect the controller using bluetooth my deck can see the controller but can't establish a connection. Is there an addon I can install so that I can use the usb receiver I currently have?

20 points · 6 comments · view on lemmy.world

6 Comments

perivesta@feddit.de · 6 pts · 3y (1 reply)

Iirc, you need the xone-dkms and xone-dongle-firmware packages

SatyrSack@lemmy.one · 4 pts · 3y

Found this while searching how to do so. Copy/pasting here for future reference once that site goes up in flames.

I assembled a rerunnable bash script based on the original post and a few comments in this thread that can be used to install or update xone. I ran it after updating to SteamOS 3.4.2 earlier today and my controllers are working like a charm with the wireless dongle. Here it is in a public gist on GitHub (will try to update this in the future if changes are needed to keep it working!):

Install or update xone driver for Steam Deck desktop shortcut and bash script

Like others have mentioned, make sure you set a password via the passwd command and unplug the wireless dongle before running.

Save the .sh file anywhere on your Deck in Desktop mode. Make sure it has executable permissions (Right-click it -> Properties -> Permissions -> Check "Is Executable"). To run it: Right-click it, and select "Run In Konsole". The xone repo will be cloned to "/home/deck/repos/xone" by default, but you can change that near the top of the script to a different location if you prefer.

https://www.reddit.com/r/SteamDeck/comments/yr248o/comment/j1crgti/

azvasKvklenko@sh.itjust.works · 6 pts · 3y (1 reply)

You may need to upgrade your controller firmware using an Xbox console or Windows.

UntouchedWagons@lemmy.ca · 7 pts · 3y

Updating the firmware did the trick. Thanks for the suggestion!