Repository navigation
PeriHub 0.6.7
PeriHub 0.6.7 supports Logitech mice by the format of their memory instead of by model, and brings a first experimental setting for the devices on a Logi Bolt or Unifying receiver, such as the MX Master.
Logitech mice: supported by memory format
What decides how PeriHub saves a mouse's profiles is the format of its onboard memory, which many models share and a firmware update can change. PeriHub reads it every time the mouse connects:
- A format already tested on a real mouse (format 2 in 256-byte sectors, the G502 HERO's; format 3 in 255-byte sectors, the G502 X Wireless's) makes the mouse supported, whatever the model.
- A format PeriHub can write but nobody has tried yet can be edited straight away with the USB cable, as an experimental feature. The mouse page asks for a test report, a No warranty box comes before the first save to that mouse, and every save is still backed up and undone after 15 seconds unless you keep it.
- Any other format stays read-only.
Edit anyway… and Turn off experimental editing are gone: there is nothing to turn on any more.
Nothing is saved through a LIGHTSPEED receiver any more, on any mouse: a write over the radio has never been tried. Since 0.6.5 the G502 X Wireless could be saved to through its receiver too; now it needs its USB cable, like every other mouse. Profiles and DPI levels can still be switched through the receiver.
Devices on a Logi Bolt or Unifying receiver (experimental)
- Unifying receivers are recognized, like the Logi Bolt one.
- Every device paired with them gets a page of its own in the sidebar, mouse or keyboard, built from the features it reports: what it is, what it can do, its battery and DPI as they are now, and a test report.
- The DPI can be changed on the devices without onboard memory, such as the MX Master, after the No warranty box the first time. PeriHub sets it in the device's RAM, never in its memory, and only to values the device itself accepts. The device forgets it when it is turned off or falls asleep, so PeriHub sets it again when the device connects or wakes up, while PeriHub is running. Nobody has tried it on a real device yet: reports are welcome in issue #17.
- PeriHub warns when Solaar or logiops runs: they set their own DPI and may undo PeriHub's.
- Linux: the Unifying receivers carry what is typed on their keyboards through the same channel PeriHub needs, so PeriHub's udev rule leaves them closed. When PeriHub finds one, the mouse page explains this and offers an optional rule, after a warning; with Solaar installed it is not needed.
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.
Which file to download
| System | File |
|---|---|
| Windows 10/11 | PeriHub_0.6.7_x64-setup.exe (recommended) or PeriHub_0.6.7_x64_en-US.msi |
| Debian/Ubuntu | PeriHub_0.6.7_amd64.deb (smaller, recommended) |
| Fedora/openSUSE | PeriHub-0.6.7-1.x86_64.rpm (smaller, recommended) |
| Linux, any distribution (including Arch/CachyOS) | PeriHub_0.6.7_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 and Corsair iCUE before using PeriHub.
- Linux with the AppImage: if you see "permission denied", install the udev rule.
- The
.sigfiles andlatest.jsonare used by the Windows updater.
Full details are in the CHANGELOG.