Repository navigation
PeriHub 0.8.1
PeriHub 0.8.1 adds the older Logitech G mice whose software is gone: Logitech removed Logitech Gaming Software from its site on 31 October 2026. They are supported from the published documentation of their HID++ 1.0 protocol in libratbag, not from a test on a real mouse: nobody has tried them with PeriHub yet. If you have one, a test report makes it tested for everyone who has it.
The mice
All with their USB cable.
| Mouse | What PeriHub reads | What it can change, at your own risk |
|---|---|---|
| G500s, G700s | DPI in use, polling rate, and the profile in use as the mouse stores it: name, DPI levels, polling rate, buttons | the DPI in use, from 50 to 8200, with Apply: it is not saved to the mouse |
| G9, G9x, G500, G700 | the same (and the stored colour on the G9 and G9x) | nothing: read-only, since the sources disagree on how their DPI is coded |
- PeriHub never writes their memory: the profiles, buttons and macros stored by Logitech Gaming Software stay as they are. It never switches profile either.
- A DPI change is read back, and put back after 15 seconds unless you keep it. According to libratbag the mouse forgets it when unplugged or when its own DPI buttons pick another level; nobody has confirmed that yet.
- The G700 and G700s through their wireless receiver are not supported, only with the cable.
- The G400s is not supported: the only known way to configure it is a raw USB request that PeriHub cannot send, and nothing can be read back from it.
The full list, with USB IDs, is in docs/devices.md, and the protocol in docs/protocols/logitech-hidpp10.md.
Also new
- The page of a device of another brand can show what the device stores as it is, such as a stored profile, and the test report includes it.
Help test your device
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,.rpmandperihub-binpackages install the new udev rule by themselves. With the AppImage or the Flatpak, install the udev rule again: the new one opens these mice.
Which file to download
| System | File |
|---|---|
| Windows 10/11 | PeriHub_0.8.1_x64-setup.exe (recommended) or PeriHub_0.8.1_x64_en-US.msi |
| Debian/Ubuntu | PeriHub_0.8.1_amd64.deb (smaller, recommended) |
| Fedora/openSUSE | PeriHub-0.8.1-1.x86_64.rpm (smaller, recommended) |
| Linux, any distribution with Flatpak | PeriHub_0.8.1_x86_64.flatpak |
| Linux, any distribution (including Arch/CachyOS) | PeriHub_0.8.1_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 (Logitech G HUB, Logitech Gaming Software, SteelSeries GG 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.