PeriHub 0.8.3

PeriHub 0.8.3 fixes what happened with a LIGHTSPEED receiver whose mouse does not answer, such as a POWERPLAY mat's: PeriHub showed "No device found" and the receiver could not be found anywhere, not even to send a report (#4).

Fixed

• A receiver nothing answers through is shown: the sidebar lists the mouse, and its page says that nothing paired with the receiver has answered, with Open test form to send what the receiver answered. The same goes for a Logi Bolt or Unifying receiver with nothing paired answering. The log also says once what the receiver's slots answered.

Also new

• The mouse test report lists the mouse's HID++ features (#22): it shows what a mouse has that PeriHub does not read yet, such as lighting through another feature.
• First mouse read through a LIGHTSPEED receiver: a G903 HERO, on Linux (#22). It stays read-only: its memory uses profile format 4, which PeriHub does not write, and PeriHub never saves through a receiver. Windows and the POWERPLAY mat are not confirmed yet.

Help test your device

On the mouse's page, Copy test report or Open test form: the mouse 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. From 0.8.2 on, the update installs without the installer's window.
• Windows with Scoop: scoop update perihub, once the bucket has the new version.
• Linux: download the new file and install it as before. The udev rule has not changed.

Which file to download

System	File
Windows 10/11	PeriHub_0.8.3_x64-setup.exe (recommended) or PeriHub_0.8.3_x64_en-US.msi
Debian/Ubuntu	PeriHub_0.8.3_amd64.deb (smaller, recommended)
Fedora/openSUSE	PeriHub-0.8.3-1.x86_64.rpm (smaller, recommended)
Linux, any distribution with Flatpak	PeriHub_0.8.3_x86_64.flatpak
Linux, any distribution (including Arch/CachyOS)	PeriHub_0.8.3_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 (Razer Synapse, Logitech G HUB, 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 .sig files and latest.json are used by the Windows updater.

Full details are in the CHANGELOG.

PeriHub 0.8.2

PeriHub 0.8.2 adds lighting for Razer mice. It comes from facts found in OpenRazer (no code copied), not from a test on a real mouse: nobody has tried it with PeriHub yet. If you have a Razer mouse, a test report makes it tested for everyone who has it.

Razer lighting

All with the mouse's USB cable.

	Mice	How
Brightness of each light (logo, scroll wheel, sides, backlight)	47 of the 75 Razer mice	Save to memory, at your own risk: the No warranty box the first time, a backup, a read-back, and the old value put back after 15 seconds unless you keep the change
One colour, not saved	27 of them	Send: sent the way OpenRazer draws its custom colour, without saving it to the mouse

• These mice cannot report the lighting effect they are using, so PeriHub cannot show it, check the colour or put the effect from before back. The page says so next to the colour. Nobody has checked yet how long the colour lasts, or which lights it covers on each mouse.
• PeriHub never stores a lighting effect on them: a stored effect is refused before it leaves PeriHub.
• Which mice have what is in docs/devices.md, and the protocol in docs/protocols/razer-mice.md.

Also new

• Windows updates without the installer's window: PeriHub closes, installs the update silently and opens again by itself, then says which version it was updated to. This starts with the update after this one, since the version being replaced runs the installer: updating to 0.8.2 still shows the small installer window.

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 udev rule has not changed.

Which file to download

System	File
Windows 10/11	PeriHub_0.8.2_x64-setup.exe (recommended) or PeriHub_0.8.2_x64_en-US.msi
Debian/Ubuntu	PeriHub_0.8.2_amd64.deb (smaller, recommended)
Fedora/openSUSE	PeriHub-0.8.2-1.x86_64.rpm (smaller, recommended)
Linux, any distribution with Flatpak	PeriHub_0.8.2_x86_64.flatpak
Linux, any distribution (including Arch/CachyOS)	PeriHub_0.8.2_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 (Razer Synapse, Logitech G HUB, 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 .sig files and latest.json are used by the Windows updater.

Full details are in the CHANGELOG.

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, .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 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 .sig files and latest.json are used by the Windows updater.

Full details are in the CHANGELOG.

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, .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. 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 .sig files and latest.json are used by the Windows updater.

Full details are in the CHANGELOG.

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.

PeriHub 0.6.8

PeriHub 0.6.8 comes as a Flatpak too, for any Linux distribution with Flatpak. Nothing else changes from 0.6.7.

The Flatpak

PeriHub_0.6.8_x86_64.flatpak is built from source by the release workflow, like the other packages. Install it for your user:

flatpak install --user PeriHub_0.6.8_x86_64.flatpak

• It runs on the GNOME 51 runtime, which Flatpak downloads from Flathub, offering to set Flathub up if it is not.
• PeriHub is not on Flathub, so the Flatpak does not update by itself: install the next release's file the same way.
• Like the AppImage, it needs the udev rule installed by hand. The optional rules (reactive lighting, software macros, Unifying receivers) cannot be installed from inside the sandbox either: PeriHub shows the commands to run instead.
• Start at sign-in goes through the desktop's Background portal. On desktops without it, such as Hyprland, PeriHub says to add flatpak run io.github.hex_dump.perihub --hidden to the desktop's own autostart (an exec-once line on Hyprland).
• The sandbox cannot see the other programs running, so the Corsair lighting and Logitech DPI pages ask to quit OpenRGB, ckb-next, OpenLinkHub, Solaar and logiops instead of noticing them.
• Settings and backups live in ~/.var/app/io.github.hex_dump.perihub/config/perihub.

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. Nothing changes for the .deb, .rpm and AppImage in this version.

Which file to download

System	File
Windows 10/11	PeriHub_0.6.8_x64-setup.exe (recommended) or PeriHub_0.6.8_x64_en-US.msi
Debian/Ubuntu	PeriHub_0.6.8_amd64.deb (smaller, recommended)
Fedora/openSUSE	PeriHub-0.6.8-1.x86_64.rpm (smaller, recommended)
Linux, any distribution with Flatpak	PeriHub_0.6.8_x86_64.flatpak
Linux, any distribution (including Arch/CachyOS)	PeriHub_0.6.8_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 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.

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 .sig files and latest.json are used by the Windows updater.

Full details are in the CHANGELOG.

PeriHub 0.6.6

PeriHub 0.6.6 recognizes the Logi Bolt receiver, a first step towards the MX Master 3S.

Supported devices

• The Logi Bolt receiver (046d:c548) is recognized (issue #17). No mouse paired with it is supported yet. PeriHub reads what the paired device is (its name, firmware and the HID++ features it has), with read commands only, and the Mouse page offers a test report with it. Nothing is written to the mouse or to the receiver, and the receiver's own commands, which pair and unpair devices, are never sent.
• When PeriHub cannot reach a receiver, the test report lists the receiver's HID collections and what each of its slots answered, to find out why.
• The part of the device information that identifies a single unit is left out of the report, since reports are posted publicly.

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 udev rule has one new line, for the Bolt receiver.

Which file to download

System	File
Windows 10/11	PeriHub_0.6.6_x64-setup.exe (recommended) or PeriHub_0.6.6_x64_en-US.msi
Debian/Ubuntu	PeriHub_0.6.6_amd64.deb (smaller, recommended)
Fedora/openSUSE	PeriHub-0.6.6-1.x86_64.rpm (smaller, recommended)
Linux, any distribution (including Arch/CachyOS)	PeriHub_0.6.6_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 .sig files and latest.json are used by the Windows updater.

Full details are in the CHANGELOG.

PeriHub 0.6.5

PeriHub 0.6.5 brings full support for the Logitech G502 X Wireless.

Supported devices

• The Logitech G502 X Wireless is supported (issue #15). Its profiles, DPI levels, buttons and macros can be edited straight away with Edit, without turning on experimental editing or accepting a warning. A user confirmed it on a real G502 X Wireless (profile format 3, 255-byte sectors) on Windows: the changes took effect, they remained after unplugging and over wireless, the 15-second undo restored the backup when not kept, macros worked, and backups restored cleanly. Thanks to Fomius.
• Labels for the 11 buttons of the G502 family on the buttons page (Left/Right/Wheel click, Back, Forward, Sniper / DPI Shift, DPI –/+, Profile switch, Wheel tilt left/right) now apply to the G502 X Wireless as well.

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.5_x64-setup.exe (recommended) or PeriHub_0.6.5_x64_en-US.msi
Debian/Ubuntu	PeriHub_0.6.5_amd64.deb (smaller, recommended)
Fedora/openSUSE	PeriHub-0.6.5-1.x86_64.rpm (smaller, recommended)
Linux, any distribution (including Arch/CachyOS)	PeriHub_0.6.5_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 .sig files and latest.json are used by the Windows updater.

Full details are in the CHANGELOG.

PeriHub 0.6.4

PeriHub 0.6.4 brings full support for the Logitech G300, warns when Logitech Gaming Software is running, and fixes losing unsaved mouse changes when unrelated devices change.

Supported devices

• The Logitech G300 is supported (issue #21). Its three onboard profiles can be edited straight away with Edit, without turning on experimental editing or accepting a warning. A user confirmed it on a real G300 on Windows: the changes took effect, they were still there after the mouse was unplugged and plugged back in, and a save that was not kept was undone. The safety net stays: a backup of the three profiles before every save, the save read back, and Keep? after each one (undone after 15 seconds without an answer). No G300 has been tried on Linux yet. Thanks to omeggga.

Changed

• PeriHub warns when Logitech Gaming Software (LCore.exe) is running, as it does for G HUB: it keeps its own copy of a mouse's profiles and may write it back or take control of the mouse.

Fixed

• Unsaved changes on the mouse page were lost when something else changed. Plugging in the keyboard or another device, or a program such as G HUB starting or quitting, made the mouse page read the mouse again and drop the changes you had not saved yet. It now reads the mouse again only when the mouse itself was opened again or taken by another program.
• A Logitech G300 or a Corsair device that cannot be opened for lack of the udev rule was reported every two seconds, to the window and in the log file, where it pushed everything else out within hours. It is now reported once.

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.4_x64-setup.exe (recommended) or PeriHub_0.6.4_x64_en-US.msi
Debian/Ubuntu	PeriHub_0.6.4_amd64.deb (smaller, recommended)
Fedora/openSUSE	PeriHub-0.6.4-1.x86_64.rpm (smaller, recommended)
Linux, any distribution (including Arch/CachyOS)	PeriHub_0.6.4_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 .sig files and latest.json are used by the Windows updater.

Full details are in the CHANGELOG.