SteelSeries Rival 3 mapped-value (button6) not working

[Aditya-Tolikar]

Problem description

SteelSeries Rival 3 button6 seems to be not working.

Command Used:

rivalcfg --buttons "buttons(button6=button6)"

Alternative Command Used for diagnosis:

rivalcfg --buttons "buttons(button5=button6)"

Checked using screenkey

All other buttons M1 to M5 seem to be working as expected.
M6 from the Rival 110 mouse works fine (to be sure problem is not somewhere else)

Checked using libinput

libinput debug-events /dev/input/event#
Results:

libinput debug-events

    Rival 110
        event14  POINTER_BUTTON          +64.432s      BTN_LEFT (272) pressed, seat count: 1
        event14  POINTER_BUTTON          +64.533s      BTN_LEFT (272) released, seat count: 0
        event14  POINTER_BUTTON          +65.016s      BTN_RIGHT (273) pressed, seat count: 1
        event14  POINTER_BUTTON          +65.147s      BTN_RIGHT (273) released, seat count: 0
        event14  POINTER_BUTTON          +16.191s      BTN_MIDDLE (274) pressed, seat count: 1
        event14  POINTER_BUTTON          +16.582s      BTN_MIDDLE (274) released, seat count: 0
        event14  POINTER_BUTTON          +32.934s      BTN_SIDE (275) pressed, seat count: 1
        event14  POINTER_BUTTON          +33.114s      BTN_SIDE (275) released, seat count: 0
        event14  POINTER_BUTTON          +103.141s     BTN_FORWARD (277) pressed, seat count: 1
        event14  POINTER_BUTTON          +103.354s     BTN_FORWARD (277) released, seat count: 0

    Rival 3
        event7   POINTER_BUTTON          +62.450s      BTN_LEFT (272) pressed, seat count: 1
        event7   POINTER_BUTTON          +62.588s      BTN_LEFT (272) released, seat count: 0
        event7   POINTER_BUTTON          +63.128s      BTN_RIGHT (273) pressed, seat count: 1
        event7   POINTER_BUTTON          +63.296s      BTN_RIGHT (273) released, seat count: 0
        event7   POINTER_BUTTON          +67.415s      BTN_MIDDLE (274) pressed, seat count: 1
        event7   POINTER_BUTTON          +67.673s      BTN_MIDDLE (274) released, seat count: 0
        event7   POINTER_BUTTON          +76.117s      BTN_SIDE (275) pressed, seat count: 1
        event7   POINTER_BUTTON          +76.301s      BTN_SIDE (275) released, seat count: 0
        event7   POINTER_BUTTON          +77.318s      BTN_EXTRA (276) pressed, seat count: 1
        event7   POINTER_BUTTON          +77.629s      BTN_EXTRA (276) released, seat count: 0

The Rival 110 gives BTN_FORWARD (277) event (--btn6_mode=os in that case), which the Rival 3 does not give.
I also tried checking the Rival 3 keyboard events and there was nothing for button6.

Further Diagnosis Required

Could it perhaps be a firmware issue?
Can someone confirm if they have a working button6 action?

Installation information

yay rivalcfg
1 aur/rivalcfg 4.10.0-2 (+15 0.01) (Installed)
    CLI tool and Python library to configure SteelSeries gaming mice

→ rivalcfg seems to be working fine since I have started using it. I have used it with Rival 110 for a few years.
→ SteelSeries Rival 3 was bought just recently.

System information

RIVALCFG
========
Version: 4.10.0
udev rules installed: True
udev rules up to date: True
Installation path: /usr/lib/python3.11/site-packages/rivalcfg

OPERATING SYSTEM
================
OS: Linux
Platform: Linux-6.5.4-zen2-1-zen-x86_64-with-glibc2.38
Version: #1 ZEN SMP PREEMPT_DYNAMIC Thu, 21 Sep 2023 12:54:31 +0000
Distribution issue: EndeavourOS Linux \r (\l)

PYTHON
======
Python version: 3.11.5
HIDAPI version: 0.14.0

PLUGGED STEELSERIES DEVICES ENDPOINTS
=====================================
1038:1824 | 00 | SteelSeries Rival 3 (firmware v36.0)
1038:1824 | 00 | SteelSeries Rival 3 (firmware v36.0)
1038:1824 | 01 | SteelSeries Rival 3 (firmware v36.0)
1038:1824 | 01 | SteelSeries Rival 3 (firmware v36.0)
1038:1824 | 02 | SteelSeries Rival 3 (firmware v36.0)
1038:1824 | 03 | SteelSeries Rival 3 (firmware v36.0)

I also tried the same from source. same result.

[flozz]

Hello,

Thank you for your report. I you are not able to make it work, I think it is a bug.

Can someone confirm if they have a working button6 action?

It may worked on my Rival 3 in the past (or maybe I not tested enough? It was years ago ^^'). Maybe it depends on the firmware revision...

Anyway, I have a bunch of Rival 3 at work, I will make some tests on them [when I will be able to come back to work...] to try to figure out what happens :)

[Aditya-Tolikar]

It would also be helpful to be able to compare my mouse's firmware version to that of any other user, as I currently don't have a Windows installation with which to update firmware (and I'd prefer that way unless I have to).

So I updated the firmware and button6=button6 mapping seems to work.
At the same time, I tried setting buttons 1 through 5, to button6 and none of them worked properly.
Not that they were not written to the device, but after the setting, clicking the corresponding buttons were giving no input.

This seems to me like not a bug of rivalcfg, but some kind of firmware limitation.
Still, since I now have the option, I'll try using Steelseries Engine to check the above mentioned variations to confirm what it is.