feat(Razer): Adding Support for 100 mouses

[viix0dev]

Adds support for 100 Razer mouses.
Tested only with Razer Deathadder Essential (Needs more testing).
Primary implementation references:

Current supported-device list:
https://openrazer.github.io/

OpenRazer repository / current master device table:
https://github.com/openrazer/openrazer

Mouse driver:
https://github.com/openrazer/openrazer/blob/master/driver/razermouse_driver.c

Common report definitions:
https://github.com/openrazer/openrazer/blob/master/driver/razercommon.h

Chroma/common command constructors:
https://github.com/openrazer/openrazer/blob/master/driver/razerchromacommon.c

Mouse driver header / PID constants:
https://github.com/openrazer/openrazer/blob/master/driver/razermouse_driver.h

OpenRazer mouse-driver usage notes:
https://github.com/openrazer/openrazer/wiki/Using-the-mouse-driver

Implementation work was assisted with Claude Code & Codex (For Research)

Supported Mouses:
List: https://github.com/viix0dev/openmouse/blob/dev/src/devices/razer/devices.ts

Tests Results (211/211):

ℹ tests 211
ℹ suites 0
ℹ pass 211
ℹ fail 0
ℹ cancelled 0
ℹ skipped 0
ℹ todo 0
ℹ duration_ms 3647.1993

[KuririmFestozo]

Tested this on a real Razer Viper V3 HyperSpeed (VID 1532 / PID 00B8) using the stock HyperSpeed receiver.

Most things seem to be working fine (battery, DPI read/write, lift-off distance, sleep timeout, etc).

I did find one issue with polling rate though. The current 0x00B8 profile inherits highRatePolling: true, which makes it use the extended polling command (0x40). The Viper V3 HyperSpeed rejects that command as unsupported.

I locally changed the entry to:

ts
[0x00b8, {
model: "Viper V3 HyperSpeed",
...VIPER_RECEIVER_WIRELESS,
highRatePolling: false,
maxDpi: DPI_FOCUS_PRO
}],

After that I tested:

• 1000 → 500 Hz
• 500 → 125 Hz
• 125 → 1000 Hz

All three changes were accepted and correctly read back from the mouse afterward.

So highRatePolling: false looks like the correct setting for the Viper V3 HyperSpeed / PID 0x00B8.

Happy to send the full diagnostics JSON if useful.

[matthewgriffinSS]

viper-receiver transaction id looks wrong for the Viper Ultimate generation (hardware-confirmed)

Testing src/devices/razer/devices.ts against a real Razer Viper Ultimate (0x007b)
I hit a transaction-id mismatch.

The Viper Ultimate routes through viper-receiver → MODERN_WIRED/MODERN_RECEIVER,
which assign transactionId: RAZER_TRANSACTION_ID (0x1f). But it only answers on
0x3f (your RAZER_TRANSACTION_ID_LEGACY):

• Reading over native HID (node-hid) with 0x1f → no reply. With 0x3f →
  firmware/DPI/polling/battery read back correctly (v1.05 / 5000 DPI / 1000 Hz / 93%).
• Matches OpenRazer, which uses 0x3f for the whole 2019–2020 HyperSpeed-receiver
  generation (Viper Ultimate, DeathAdder V2 Pro, Naga Pro, Basilisk Ultimate,
  Lancehead/Mamba Wireless, …).

Since those PIDs are all verified: false, it's latent, nothing has exercised them.
The newer 0x1f models (Viper V2/V3 Pro) are correct, which is why they pass.

Suggested fix: give the older receiver generation 0x3f (i.e. _LEGACY) instead
of inheriting 0x1f from the shared base, and audit each receiver-family PID against
OpenRazer's transaction_id. (Minor: _LEGACY = 0x3f is a misleading name — 0x3f
is the middle generation; 0xff is the oldest.)

Note for the WebHID path / #47: on the Viper Ultimate dongle, Chrome exposes no
feature report on any interface (every collection is feat[none]; the Generic-Desktop-
Mouse interface's reports are stripped as "protected"), so sendFeatureReport fails
regardless of transaction id. I could only drive it via the native OS HID API, so this
model realistically needs the native/HAL transport, not WebHID. Happy to share the repro.

[viix0dev]

@KuririmFestozo Yes, please send the diagnostics JSON.
I pushed a fixed version. you can test it

[viix0dev]

@matthewgriffinSS I'm working on fixing it. it will be pushed soon.

[viix0dev]

@matthewgriffinSS I’ve pushed a fix. could you retry it here and let me know if you’re still seeing the issue?
https://openmouse-sable.vercel.app/
This is a deployed version of my repo.

[viix0dev]

Tests I ran with people (5/5):
Razer DeathAdder V3 Pro - works (tested with hardware)
Razer DeathAdder V2 X HyperSpeed - works (tested with hardware)
Razer Basilisk X HyperSpeed - works (tested with hardware)
Razer DeathAdder Essential - works (tested with hardware)
Razer DeathAdder V2 (wired) - works (tested with hardware)

[natic0309]

Selected device is not a supported control interface (DeathAdder V4 Pro (VID 0x1532 PID 0xbf; usage 0x1:0 feat[none] | usage 0x1:0 feat[none] | usage 0xc:1 feat[none]) · unknown (VID 0x1532 PID 0xbf; usage 0xc:1 feat[none])). Pick a vendor control interface (not a plain boot mouse). If this keeps failing, note the VID/PID from this message.

[viix0dev]

@natic0309
it doesnt support WebHID only works via Native HAL( razer designed it this way ) so for now our web app wont support it