HORI Steam Controller bluetooth

[rasj1987]

The wired is still working fine, but the bluetooth is still acting the same way as in the original post. Do I need to do a similar thing for bluetooth devices? I have an 8bitdo SN30 Pro controller that I can connect to without any issues.

---

Mod edit: continued from earlier solved topic with different problem:

The hori steam controller is not working properly on linux

I verified that the controller works by booting my windows drive so I know it is linux. When connected with a wire the quick access button does not work in big picture mode, I am not getting an option to activate gyro by touching the joystick or getting the option to even calibrate the gyro. It is essentially treating it like it’s a standard xinput controller (it IS in steam mode). When I try to connect via bluetooth my computer says that it is connected and the controllers bluetooth led stays …

[Mirdarthos]

For bluetooth, edit the file again:

sudo nano /etc/udev/rules.d/50-horipad-steam.rules

And add these lines at the bottom:

# Wireless HORIPAD STEAM; Bluetooth
KERNEL=="hidraw*", KERNELS=="*0F0D:0196*", MODE="0660", TAG+="uaccess"
KERNEL=="hidraw*", ATTRS{idVendor}=="0f0d", ATTRS{idProduct}=="0196", MODE="0660", TAG+="uaccess"

Again, save and exit, the same as previously:

Ctrl+O → Ctrl + X

Followed again by rebooting.

[rasj1987]

The only message that I saw from you was “Do you know if this hardware is compatible with Linux?” I even ctrl+f the thread and your name is only showing up once. If it was a direct message then I must have missed it. My apologies.

As for the commands, they did not work. I tried doing it like this

# Wired HORIPAD STEAM; USB
KERNEL=="hidraw*", KERNELS=="*0F0D:01AB*", MODE="0660", TAG+="uaccess"
KERNEL=="hidraw*", ATTRS{idVendor}=="0f0d", ATTRS{idProduct}=="01ab", MODE="0660", TAG+="uaccess"
# Wireless HORIPAD STEAM; Bluetooth
KERNEL=="hidraw*", KERNELS=="*0F0D:0196*", MODE="0660", TAG+="uaccess"
KERNEL=="hidraw*", ATTRS{idVendor}=="0f0d", ATTRS{idProduct}=="0196", MODE="0660", TAG+="uaccess"

and like this

# Wired HORIPAD STEAM; USB
KERNEL=="hidraw*", KERNELS=="*0F0D:01AB*", MODE="0660", TAG+="uaccess"
KERNEL=="hidraw*", ATTRS{idVendor}=="0f0d", ATTRS{idProduct}=="01ab", MODE="0660", TAG+="uaccess"

# Wireless HORIPAD STEAM; Bluetooth
KERNEL=="hidraw*", KERNELS=="*0F0D:0196*", MODE="0660", TAG+="uaccess"
KERNEL=="hidraw*", ATTRS{idVendor}=="0f0d", ATTRS{idProduct}=="0196", MODE="0660", TAG+="uaccess"

Both ended with the same result.

I’ve tried both commands from here and from reddit.

su
udevadm control --reload-rules && udevadm trigger
seems to do nothing. Same result. I even tried doing a hard shut down of my PC.

Mine is the recent US release if that makes any difference. I did not import it.

When I initially pair the controller, everything looks like the first post (pc says it is connected, bluetooth icon is solid on the controller). If I power off the controller (or turn off bluetooth) and then turn it back on my computer says it is connected, but the bluetooth icon on the controller continues to flash. My PC then disconnects from the controller. Blueman says
Connection Failed: Input/output error

[omano]

I didn’t say I posted a link, I said you didn’t click the link in the thread.

[soundofthunder]

@omano

I said you didn’t click the link in the thread.

Note that if a Member right-clicks a link, perhaps to open in a new window, there is no tell tale indicator of a Member having clicked a link.

Can you please try to be generally less confrontational; (or, as @Fabby once asked) “Would you please be so kind to be a bit kinder”?

Regards.

[Kobold]

@rasj1987

The wired is still working fine, but the bluetooth is still acting the same way as in the original post. Do I need to do a similar thing for bluetooth devices?

The key is to trust the device first, otherwise the Device connection will be refused.

Trust>Pair>connect

[rasj1987]

Thank you, kobold. That is what I needed to do. I’ll remember that for the future. And thank you Mirdarthos as well