Unable to use from Y***, any way to test if it is working without Y***? about evdevhook2 HOT 10 CLOSED

Looks like I had the wrong assumption that the Dualsense Edge was automatically supported. Testing with a normal Dualsense worked as expected.

from evdevhook2.

Please see if #21 fixes this. You can download test appimage here in artifacts section.

from evdevhook2.

Thanks for this mate.

Btw, do you know if it is possible to run this without sudo on a Steam Deck?

from evdevhook2.

It should be, but I don't know how exactly deck handles device permissions.

Please report your DualSense Edge testing results when you have time.

from evdevhook2.

Can confirm, that this adds support for the Dualsense Edge controller!

from evdevhook2.

Great to hear, I've released v1.0.2 with DualSense Edge support included.

from evdevhook2.

For anyone happening by trying to get their Dualsense Edge (or any other) controller gyro to work on the Steam Deck, here is what I did to be able to run evdevhook2 without sudo:

1. Run evdevhook2 and note the /dev/input/eventNN device it is trying to access but failing.
2. Run this command udevadm info -a -p $(udevadm info -q path -n /dev/input/eventNN)
3. From the output, note the ATTRS{id/product} and ATTRS{id/vendor} from the same block which also has ATTRS{name} matching the name of your controller.
4. From sudo, create a file called 70-name-of-controller.rules inside /etc/udev/rules.d with the content:

SUBSYSTEM=="input", ATTRS{id/product}=="your product id", ATTRS{id/vendor}=="your vendor id", TAG+="uaccess"

5. Run udevadm control --reload-rules && udevadm trigger
6. Now you should be able to run evdevhook2 without needing sudo.

from evdevhook2.

Furthermore, if you want to run evdevhook2 as a service, you can create a file:

~/.config/systemd/user/evdevhook2.service

[Unit]
Description=evdevhook2 server
After=sockets.target
StartLimitIntervalSec=0

[Service]
Type=simple
Restart=always
RestartSec=1
ExecStart=%h/evdevhook2/evdevhook2-v1.0.2-x86_64.AppImage %h/evdevhook2/evdevhook2.ini

[Install]
WantedBy=default.target

After that, systemctl --user -q enable --now evdevhook2.service should enable/start the service. You will probably need to restart the service when you plug in new controllers (@v1993 has to confirm this) using systemctl --user restart evdevhook2.service

PS: looks like restarting the service is not required. I tested disconnecting and reconnecting the controller. It was able to detect the change.

from evdevhook2.

That's a nice guide! I'd appreciate if you'd post it in discussions section of this repo under "show and tell" to make it easier to discover.

Notes:

1. Hotplug works just fine, no need to restart
2. Vendor/Product IDs can also be found in https://github.com/v1993/evdevhook2/blob/main/src/DeviceTypes.ini

from evdevhook2.

Will do.

Also, I think we can help auto generate this as an artifact given we have the .ini file:

70-evdevhook2.rules (to be placed at /etc/udev/rules.d)

SUBSYSTEM=="input", ATTRS{id/vendor}=="057e" , ATTRS{id/product}=="2006", TAG+="uaccess"
SUBSYSTEM=="input", ATTRS{id/vendor}=="057e" , ATTRS{id/product}=="2007", TAG+="uaccess"
SUBSYSTEM=="input", ATTRS{id/vendor}=="057e" , ATTRS{id/product}=="2009", TAG+="uaccess"
SUBSYSTEM=="input", ATTRS{id/vendor}=="054c" , ATTRS{id/product}=="0268", TAG+="uaccess"
SUBSYSTEM=="input", ATTRS{id/vendor}=="054c" , ATTRS{id/product}=="05c4", TAG+="uaccess"
SUBSYSTEM=="input", ATTRS{id/vendor}=="054c" , ATTRS{id/product}=="09cc", TAG+="uaccess"
SUBSYSTEM=="input", ATTRS{id/vendor}=="054c" , ATTRS{id/product}=="0ce6", TAG+="uaccess"
SUBSYSTEM=="input", ATTRS{id/vendor}=="054c" , ATTRS{id/product}=="0df2", TAG+="uaccess"

from evdevhook2.