input-remapper
input-remapper copied to clipboard
sezanzeb
Xbox Elite Series 2 Via bluetooth paddles is "unknown"
03:15:04.421110 729267 GUI DEBUG reader.py:162: down ·························· <InputEvent KEY_UNKNOWN (240) down>
03:15:04.454501 729267 GUI DEBUG reader.py:147: release ······················· <InputEvent KEY_UNKNOWN (240) up>
03:15:04.487954 729267 GUI DEBUG reader.py:162: down ·························· <InputEvent KEY_UNKNOWN (240) down>
03:15:04.521335 729267 GUI DEBUG reader.py:147: release ······················· <InputEvent KEY_UNKNOWN (240) up>
03:15:05.185641 729267 GUI DEBUG reader.py:162: down ·························· <InputEvent KEY_UNKNOWN (240) down>
03:15:05.318563 729267 GUI DEBUG reader.py:147: release ······················· <InputEvent KEY_UNKNOWN (240) up>
I use Xbox Elite Series 2 via bluetooth, and the remapper recognizes 3 out of 4 paddles as "unknown" (it does not see p-2), and when I try to reassign them all, it says "unknown already mapped" In the log, all paddles have the same identifier
can you run $ sudo evtest and select your controller?
If you now press a paddle you should see something like this:
Event: time 1653212403.050407, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70009
Event: time 1653212403.050407, type 1 (EV_KEY), code 33 (KEY_F), value 1
Event: time 1653212403.050407, -------------- SYN_REPORT ------------
Can you post the output here and mark which Events come from which paddle.
Event: time 1653263354.777211, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0081
Event: time 1653263354.777211, type 1 (EV_KEY), code 240 (KEY_UNKNOWN), value 1 #Paddle 1 press
Event: time 1653263354.777211, -------------- SYN_REPORT ------------
Event: time 1653263354.945799, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0081
Event: time 1653263354.945799, type 1 (EV_KEY), code 240 (KEY_UNKNOWN), value 0 #Paddle 1 release
Event: time 1653263354.945799, -------------- SYN_REPORT ------------
Event: time 1653263355.375797, type 1 (EV_KEY), code 240 (KEY_UNKNOWN), value 2 #Paddle 2 detected as click
Event: time 1653263355.375797, -------------- SYN_REPORT ------------
Event: time 1653263356.045770, type 1 (EV_KEY), code 240 (KEY_UNKNOWN), value 4 #Paddle 3 press
Event: time 1653263356.045770, -------------- SYN_REPORT ------------
Event: time 1653263356.187182, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0081
Event: time 1653263356.187182, type 1 (EV_KEY), code 240 (KEY_UNKNOWN), value 0 #Paddle 3 release
Event: time 1653263356.187182, -------------- SYN_REPORT ------------
Event: time 1653263356.756176, type 1 (EV_KEY), code 240 (KEY_UNKNOWN), value 8 #Paddle 4 press
Event: time 1653263356.756176, -------------- SYN_REPORT ------------
Event: time 1653263356.876174, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0081
Event: time 1653263356.876174, type 1 (EV_KEY), code 240 (KEY_UNKNOWN), value 0 #Paddle 4 release
Event: time 1653263356.876174, -------------- SYN_REPORT ------------
These are all 4 paddles pressed in turn. Strange, but paddle n-2 is determined only by pressing, there is no information when releasing
Event: time 1653263530.238947, type 1 (EV_KEY), code 240 (KEY_UNKNOWN), value 2
Event: time 1653263530.238947, -------------- SYN_REPORT ------------
Event: time 1653263530.467337, type 1 (EV_KEY), code 240 (KEY_UNKNOWN), value 2
Event: time 1653263530.467337, -------------- SYN_REPORT ------------
Event: time 1653263530.697327, type 1 (EV_KEY), code 240 (KEY_UNKNOWN), value 2
Event: time 1653263530.697327, -------------- SYN_REPORT ------------
Event: time 1653263530.887328, type 1 (EV_KEY), code 240 (KEY_UNKNOWN), value 2
Event: time 1653263530.887328, -------------- SYN_REPORT ------------
Event: time 1653263531.067321, type 1 (EV_KEY), code 240 (KEY_UNKNOWN), value 2
Event: time 1653263531.067321, -------------- SYN_REPORT ------------
Event: time 1653263531.408907, type 1 (EV_KEY), code 240 (KEY_UNKNOWN), value 2
Event: time 1653263531.408907, -------------- SYN_REPORT ------------
This makes me curious is there any program which can differentiate between the different paddles?
All the paddles report the same event type (1) and code (240) so inputremapper cannot know which paddle was pressed.
This is a bug with your controller or maybe a device driver. We can not do anything about this.
I used reWASD on Windows before switching to linux and it was great. But most likely Windows detected the gamepad more correctly than Linux. What else could I try to solve the problem?
it looks like it behaves similar to D-Pads, which send -1 for left and 1 for right, but also the same type and code. The release event also has a value of 0
maybe you have more luck when configuring it via the config file, see https://github.com/sezanzeb/input-remapper/blob/main/readme/usage.md#configuration-files
If you look at the logs of input-remapper-gtk -d you'll see a more detailed error message, like
11:04:57.634507 179345 GUI INFO editor.py:612: <EventCombination (1, 276, 1)> "Button EXTRA" already mapped to "foo"
The value there would be interesting. Since each paddle has a different value I would have expected to not show this error.