Luca Weiss

I think that's just a Razer BlackWidow V3 Pro quirk then compared to other keyboards with the same "matrix dimensions" - which is the only metric currently used in RazerGenie...

Currently the driver has handling for these keys for Ornata V3 TKL: ```c { KEY_F9, RAZER_MACRO_KEY }, { KEY_F10, RAZER_GAME_KEY }, { KEY_F11, RAZER_BRIGHTNESS_DOWN }, { KEY_F12, RAZER_BRIGHTNESS_UP }, {...

If the device doesn't show up in `lsusb` then OpenRazer also can't communicate with the device. Then it's general USB problems or something.

The information you posted doesn't contain anything from Razer Core X. Does that thing not show up over USB? What of it can you control in Razer Synapse on Windows?

If you can achieve this using Razer Synapse then we can probably also build this functionality into OpenRazer. If not, then not. For the HyperPolling Wireless Dongle there's the sysfs...

@KohlerVG Something like `echo $pid_of_new_mouse > /sys/bus/hid/drivers/razermouse/0*/hyperpolling_wireless_dongle_pair` so e.g. if you want to pair DeathAdder V2 Pro it would be `echo 007D > [...]` I think, or 0x007D, not sure...

If that `hyperpolling_wireless_dongle_pair` file exists then you could also use that. If not, then either it's not implemented in OpenRazer for that device, or the device just doesn't support this...

If you can take USB packet captures of Synapse doing this, we can try and implement it in OpenRazer also. https://github.com/openrazer/openrazer/wiki/Reverse-Engineering-USB-Protocol

What's your `pacman -Q openrazer-daemon` showing? Either you've installed -git version and not rebuilt it after the last Python 3.12 -> 3.13 update or you messed something else up in...

Seems this is resolved, closing.