Aerox 5 wired not listed about rivalcfg HOT 5 OPEN

I'll mess around with wireshark for this soon and let you know what I gather!

from rivalcfg.

The Aerox 5 is not supported by Rivalcfg yet. We will need some reverse engineering to support it. :)

NOTE: Aerox 5 Wireless and Aerox 5 are two different devices (we already found differences in the protocols of the Aerox 3 / Aerox 3 Wireless)

from rivalcfg.

is there anything that can be done to help with the wired Aerox 5?

from rivalcfg.

@mxiaa yes. I need someone to capture packet sent by the GG Engine to the mouse when changing each options. This will allow me to reverse engineer its protocol and to implement it in Rivalcfg.

Here is an example of what has been done for the Aerox 3 Wireless: https://github.com/gort818/aerox3-wireless/blob/aa1020d493bfcb451438a5cd5e00aed249d9bc29/aerox3-wireless.txt

from rivalcfg.

I too have a Wired Aerox 5, and would be happy to run whatever tests that you need. To start with, here's the output requested on the Contributing page.

$ lsusb -d 1038:
Bus 001 Device 008: ID 1038:1850 SteelSeries ApS SteelSeries Aerox 5

$ rivalcfg --print-debug

RIVALCFG
========
Version: 4.8.0
udev rules installed: True
udev rules up to date: True
Installation path: /home/leon/.virtualenvs/rivalcfg/lib/python3.10/site-packages/rivalcfg

OPERATING SYSTEM
================
OS: Linux
Platform: Linux-5.19.0-38-generic-x86_64-with-glibc2.36
Version: #39-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 17:33:16 UTC 2023
Distribution issue: Ubuntu 22.10 \n \l

PYTHON
======
Python version: 3.10.7
HIDAPI version: 0.13.1

PLUGGED STEELSERIES DEVICES ENDPOINTS
=====================================
1038:1850 | 00 |  (firmware v0)
1038:1850 | 01 |  (firmware v0)
1038:1850 | 02 |  (firmware v0)
1038:1850 | 03 |  (firmware v0)

from rivalcfg.