[Device] Attack Shark RS3 Ultra

[Rodtree]

Device type

Mouse

Device model

Attack Shark RS3 Ultra

vendorId:productId

3554:f515

Connection type

Multiple (tell us below)

What happens today?

Partially works (some settings missing — tell us which below)

Diagnostics

Windows (no lsusb available):
- Wired:    USB\VID_3554&PID_F515  -> 3554:f515
- Receiver: USB\VID_3554&PID_F517  -> 3554:f517

OpenMouse BETA v2.0.7a3
Driver family: "lamzu-atlantis" (brand Scyrox), displayed as "Scyrox V8S"
WebHID product name: "RS3 Ultra" (wired) / "ATTACK SHARK Mouse" (receiver)
Firmware: Mouse v5.06

Full diagnostics for both connections will be attached as .json files in a comment below.

Can you help test?

Yes, and I can capture USB traffic (Wireshark / usbpcap)

Anything else?

What is missing: only the correct device identity (it shows as "Scyrox V8S" with a generic placeholder image instead of "Attack Shark RS3 Ultra"). Changing DPI and polling rate works.

Both connections share the same USB serial number, so they appear to be the same device exposing a different PID per connection mode.

OpenMouse detects the mouse over both wired and 2.4 GHz receiver using the existing Scyrox profile. Connection state, battery level, polling rate (up to 8,000 Hz) and DPI stages are read correctly, and settings changed in OpenMouse are applied to the device on both connections. It may only need a proper device entry (name and artwork).

Possibly related to #1246 (ARYE RCC-1): the receiver uses the same ID (3554:f517), while the wired ID differs (f515 here, f516 there).

Yes, and I can capture USB traffic (Wireshark / usbpcap)

Anything else?

What is missing: only the correct device identity (it shows as "Scyrox V8S" with a generic placeholder image instead of "Attack Shark RS3 Ultra"). Changing DPI and polling rate works.

Both connections share the same USB serial number, so they appear to be the same device exposing a different PID per connection mode.

OpenMouse detects the mouse over both wired and 2.4 GHz receiver using the existing Scyrox profile. Connection state, battery level, polling rate (up to 8,000 Hz) and DPI stages are read correctly, and settings changed in OpenMouse are applied to the device on both connections. It may only need a proper device entry (name and artwork).

Possibly related to #1246 (ARYE RCC-1): the receiver uses the same ID (3554:f517), while the wired ID differs (f515 here, f516 there).

[Rodtree]

Full diagnostics exported from the device's Advanced panel (OpenMouse BETA v2.0.7a3):

• openmouse-3554-f515-2026-11-05-23-11-16.json: wired (3554:f515)
• openmouse-3554-f517-2026-11-05-23-08-56.json: 2.4 GHz receiver (3554:f517)
  openmouse-3554-f515-2026-11-05-23-11-16.json
  openmouse-3554-f517-2026-11-05-23-08-56.json