PeriHub 0.7.0

PeriHub 0.7.0 recognizes 129 mice of three more brands: 21 ASUS ROG and TUF, 33 SteelSeries and 75 Razer. They are supported from the published documentation of their protocols, not from a test on a real device: nobody has tried them with PeriHub yet. If you have one, a test report makes it tested for everyone who has it.

The new mice

Brand	Models	What PeriHub reads	What it can change, at your own risk
ASUS ROG and TUF	21: Chakram, Gladius II, Keris, Spatha X, Strix Impact, TUF Gaming M3… on their cable and their own receiver	firmware, active profile, DPI levels, polling rate, button response, angle snapping, lighting, buttons	the active profile's DPI levels, polling rate, button response, angle snapping and lighting: Apply without saving, or Save to memory
SteelSeries	33: Rival, Sensei, Aerox, Prime, Kana, Kinzu, on their cable and their own receiver	firmware, battery of wireless ones	DPI presets, polling rate, colours, effects, brightness, timers, one at a time with Send, never saved
Razer	75: DeathAdder, Viper, Basilisk, Naga, Orochi… on their USB cable	firmware, DPI, polling rate	DPI and polling rate, with Save to memory only, since these mice store every change

The full list, with USB IDs, is in docs/devices.md.

What PeriHub does to protect them

• It sends only the commands in its list for each mouse, and refuses anything else before it leaves: nothing that touches firmware, switches profiles or rebinds buttons.
• It sends only values the mouse accepts, saves a backup of the settings first, reads them back after, and puts them back after 15 seconds unless you keep the change, also the next time the mouse is connected if PeriHub was closed.
• Save to memory asks for the No warranty box the first time for each mouse.
• SteelSeries mice cannot report their settings, so nothing can back them up: PeriHub never saves to their memory, and unplugging the mouse brings back what it has saved.
• An answer that does not look as documented leaves the mouse read-only, and the test report shows exactly what it answered.
• Receivers and docks that can be shared with a keyboard (the ROG Omni receiver, Razer receivers and docks) are left out.

Sources and licenses

ASUS mice come from libratbag (MIT), SteelSeries mice from rivalcfg (WTFPL), Razer mice from facts found in OpenRazer, with no code copied. Every package now carries THIRD-PARTY-NOTICES.md next to LICENSE.

Help test your mouse

On the mouse's page, Copy test report or Open test form: the device test form asks what worked. Sending a report only reads the mouse.

Updating

• Windows, installed from this page: PeriHub offers the update in the tray menu and in Settings → Updates.
• Windows with Scoop: scoop update perihub, once the bucket has the new version.
• Linux: download the new file and install it as before. The .deb, .rpm and perihub-bin packages install the new udev rule by themselves. With the AppImage or the Flatpak, install the udev rule again: the new one opens the new mice.

Which file to download

System	File
Windows 10/11	PeriHub_0.7.0_x64-setup.exe (recommended) or PeriHub_0.7.0_x64_en-US.msi
Debian/Ubuntu	PeriHub_0.7.0_amd64.deb (smaller, recommended)
Fedora/openSUSE	PeriHub-0.7.0-1.x86_64.rpm (smaller, recommended)
Linux, any distribution with Flatpak	PeriHub_0.7.0_x86_64.flatpak
Linux, any distribution (including Arch/CachyOS)	PeriHub_0.7.0_amd64.AppImage

• Windows: the installer is not code-signed yet (PeriHub has applied to SignPath Foundation). If SmartScreen blocks it, click More info → Run anyway. Quit SteelSeries GG, Logitech G HUB, Logitech Gaming Software, Corsair iCUE, ASUS Armoury Crate and Razer Synapse before using PeriHub with their devices: two programs talking to the same device get in each other's way.
• Linux with the AppImage or the Flatpak: if you see "permission denied", install the udev rule.
• The .sig files and latest.json are used by the Windows updater.

Full details are in the CHANGELOG.