Wootility - Configuring device access for Wootility under Linux (udev rules)

Background

Because the Wootility communicates directly with the keyboard the user needs the permission for it, otherwise the keyboard can't be found. So either the Wootility must be started with higher privileges (like with sudo) or the user need the permission for accessing the device.

Granting access with udev

To granting the user for accessing the Wooting keyboard without the need to run it with higher privileges, the access rights must be set for the device. This can be done with dedicated udev rules.

Creating the rules

Create a new file called '70-wooting.rules' under the path '/etc/udev/rules.d/' with the following content. The name can be changed (but it should start with 70-), but the file extension must be 'rules' otherwise it wont work.

'/etc/udev/rules.d/70-wooting.rules'

# Wooting One Legacy
SUBSYSTEM=="hidraw", ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="ff01", TAG+="uaccess"
SUBSYSTEM=="usb", ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="ff01", TAG+="uaccess"
# Wooting One update mode 
SUBSYSTEM=="hidraw", ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="2402", TAG+="uaccess"

# Wooting Two Legacy
SUBSYSTEM=="hidraw", ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="ff02", TAG+="uaccess"
SUBSYSTEM=="usb", ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="ff02", TAG+="uaccess"
# Wooting Two update mode  
SUBSYSTEM=="hidraw", ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="2403", TAG+="uaccess"

# Generic Wootings
SUBSYSTEM=="hidraw", ATTRS{idVendor}=="31e3", TAG+="uaccess"
SUBSYSTEM=="usb", ATTRS{idVendor}=="31e3", TAG+="uaccess"

Applying the new rules

To activate the rules they must be loaded and applied by the following command:

sudo udevadm control --reload-rules && sudo udevadm trigger

Different distributions can use different commands and tools, you need to check if the mentioned system inputs are supported by your distribution.

Thanks to Rocky_4 (DEU) on Discord for the solution.

Updated on: 11/08/2023