Repository navigation
PeriHub 0.8.0
PeriHub 0.8.0 recognizes 23 more mice, six of them from new brands (Glorious, Roccat, Pulsar, Lamzu, Cooler Master and EVGA) plus the Logitech G600, and keyboards with QMK or Vial firmware. They are supported from the published documentation of their protocols and from USB captures, 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.
It also brings a sidebar with only the devices that are there, a page to ask for a device PeriHub does not know, and mouse lighting zones that can each keep their own effect. These three were tried on Windows 11 with an Apex 3 TKL and a G502 HERO.
The new devices
| Brand | Models | What PeriHub reads | What it can change, at your own risk |
|---|---|---|---|
| Glorious | Model O/O-, Model D, Model O Eternal, with a cable | firmware, DPI of each slot, slot in use, polling rate | DPI and polling rate, with Save to memory. On Windows read-only for now |
| Logitech G600 | 1 | the profile in use: DPI, polling rate, lighting, buttons | DPI, polling rate and lighting of the profile in use, with Save to memory |
| Roccat | Kone Pure, Kone XTD, Kone EMP | profile in use, DPI levels, polling rate | nothing: read-only |
| Pulsar | Xlite, X2, X2H, X2A, Xlite v4, X3, X3 LHD, X2 CrazyLight, X3 LHD CrazyLight, with a cable | firmware, profile, DPI stages, polling rate, debounce, angle snapping, ripple control, motion sync (lift-off on the CrazyLight) | the same, with Save to memory |
| Lamzu | Atlantis, with a cable | DPI, polling rate and its other settings | nothing: read-only |
| Cooler Master | MM530, MM711, MM720, MM730 | lighting | colour, brightness and mode, with Save to memory |
| EVGA | X12 and X20, with a cable | lighting | on the X12, each zone off or steady with its colour and brightness, with Save to memory. The X20 is read-only |
| Keyboards with QMK firmware | every Vial keyboard, and VIA keyboards you turn on in the new QMK keyboards page | protocol versions, layers, macros, lighting | lighting, where the protocol says exactly how (VialRGB, VIA firmware from 2023). Keymaps are left to VIA and Vial |
The full list, with USB IDs, is in docs/devices.md. The website now has one table of every supported device, and says clearly which Logitech G mice are supported.
What PeriHub does to protect them
- It sends only the commands in its list for each device, and refuses anything else before it leaves: nothing that touches firmware, resets a profile or rebinds buttons.
- Every save is backed up first, read back after, and undone after 15 seconds unless you keep it, also the next time the device is connected if PeriHub was closed. Save to memory asks for the No warranty box the first time for each device.
- An undo is never written onto another profile: if the device switched profile since the change, PeriHub says which profile to go back to, and makes no other change on that device until then.
- An answer that does not look as documented leaves the device read-only, and the test report shows exactly what it answered.
- On QMK keyboards PeriHub opens only the raw HID channel that VIA and Vial use, never the interface that carries what you type.
Also new
- The sidebar lists only the devices that are there. With none connected, it offers Send a report: it lists the USB and Bluetooth devices PeriHub does not know and opens a device request on GitHub already filled in (no serial numbers). It is also in Settings → Devices.
- Mouse lighting: "Same effect on all zones". On, one card sets every zone, so breathing and color cycle pulse together. Off, each zone keeps its own effect.
- Faster updates on Windows, from the next update on: PeriHub downloads the installer as soon as it finds a new version, shows the download on the button, and comes back with its window, also with Always start hidden on. This update is still installed the old way: with Always start hidden on, PeriHub comes back in the tray this time.
- Starting PeriHub again while it is open no longer writes a false start line to the log.
Sources and licenses
Glorious mice, the G600 and the Roccat Kone mice come from libratbag (MIT), Pulsar mice from pulsar-mouse-linux (MIT), the Lamzu Atlantis from lamzu-cfg (MIT/Apache-2.0). Cooler Master and EVGA lighting comes from facts in OpenRGB and the USB captures attached to its device requests, and QMK keyboards from facts in the QMK and Vial sources, with no code copied. THIRD-PARTY-NOTICES.md names every source.
Help test your device
On the device's page, Copy test report or Open test form: the device test form asks what worked. Sending a report only reads the device.
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,.rpmandperihub-binpackages 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. QMK keyboards get their own optional rule from the QMK keyboards page.
Which file to download
| System | File |
|---|---|
| Windows 10/11 | PeriHub_0.8.0_x64-setup.exe (recommended) or PeriHub_0.8.0_x64_en-US.msi |
| Debian/Ubuntu | PeriHub_0.8.0_amd64.deb (smaller, recommended) |
| Fedora/openSUSE | PeriHub-0.8.0-1.x86_64.rpm (smaller, recommended) |
| Linux, any distribution with Flatpak | PeriHub_0.8.0_x86_64.flatpak |
| Linux, any distribution (including Arch/CachyOS) | PeriHub_0.8.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 the maker's app (SteelSeries GG, Logitech G HUB, Corsair iCUE, ASUS Armoury Crate, Razer Synapse and the others) before using PeriHub with its 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
.sigfiles andlatest.jsonare used by the Windows updater.
Full details are in the CHANGELOG.