OpenLogi

Product Introduction

1. Definition: OpenLogi is a native, local-first device configuration and management application for Logitech peripherals, written in the Rust programming language. It is a direct, open-source alternative to proprietary software like Logitech Options+.
2. Core Value Proposition: OpenLogi exists to provide full control over Logitech mice, keyboards, and webcams without mandatory cloud services, user accounts, or telemetry. Its primary value is privacy-first, local device management over the HID++ protocol, enabling button remapping, DPI control, and SmartShift configuration directly from the user's machine.

Main Features

1. Local-First Button Remapping: OpenLogi provides granular control over every button on supported Logitech devices. It works by directly communicating with the device firmware via the HID++ protocol (versions 1.0 and 2.0) to assign one of 44 built-in actions, custom shortcuts, or scripts. All configurations are stored in a plain-text config.toml file in the user's home directory.
2. Direct Hardware Control (DPI & SmartShift): Unlike cloud-dependent software, OpenLogi writes DPI settings and SmartShift parameters directly to the device's sensor and wheel mechanism over HID++. This includes setting precise DPI levels, creating and cycling DPI presets, and configuring the automatic disengage threshold for the MagSpeed electromagnetic scroll wheel (feature 0x2201).
3. Multi-Transport Support & Live Device View: The software supports all standard Logitech connection methods: Bolt, Unifying, and Lightspeed receivers; direct Bluetooth pairing; and USB wired connections. It features a live device carousel that displays real-time battery percentage and charge state for all connected peripherals by querying HID++ feature 0x1004.

Problems Solved

1. Pain Point: It eliminates dependency on bloated, telemetry-collecting commercial driver software that requires internet accounts and phoning home. It solves the problem of losing device configurations when switching computers or if cloud services are unavailable.
2. Target Audience: Privacy-conscious professionals (developers, writers, designers), Linux users seeking native Logitech support, power users who want portable configurations, and individuals who avoid proprietary software on principle.
3. Use Cases: Essential for users who need consistent mouse/keyboard settings across multiple offline or air-gapped machines; for Linux desktop users replacing Solaar with a more feature-complete GUI; for developers who wish to audit or script their peripheral configuration via TOML files.

Unique Advantages

1. Differentiation: Compared to Logitech Options+, OpenLogi is open-source (MIT/Apache-2.0), has zero telemetry, and requires no account. Versus community tools like Solaar, it offers a more polished native GUI, direct Bolt receiver support, and a structured roadmap for features like per-app profiles.
2. Key Innovation: Its architecture treats the user's config.toml file as the single source of truth. This file is portable, human-editable, and version-controllable. All GUI interactions are mere editors for this file, and the HID++ communication layer applies changes directly to hardware, bypassing any cloud intermediary.

Frequently Asked Questions (FAQ)

1. Is OpenLogi compatible with Logitech Flow? Not fully. OpenLogi currently implements the host-switching half of Flow by driving Easy-Switch over HID++ features 0x1814/0x1815, allowing paired mice to follow a keyboard's host switch. A full local-network pointer and clipboard bridge is a distant roadmap item and would be strictly opt-in.

2. Can I import my settings from Logitech Options+ into OpenLogi? Not automatically at this time. An importer is under development. However, OpenLogi's bindings are stored in a simple, portable TOML file, allowing users to manually recreate their setup in a transparent and future-proof format.

3. Why does OpenLogi need Accessibility permissions on macOS? On macOS, remapping standard system buttons (Back, Forward, Middle Click) requires a CGEventTap, which is gated by the Accessibility permission for security. Crucially, HID++-based features like the gesture button, thumb wheel, DPI, and SmartShift do not require this permission.

4. How do OpenLogi updates work? Updates are user-initiated and opt-in. The in-app update checker is disabled by default. Users update via their system's package manager (e.g., brew upgrade --cask openlogi on macOS) or by manually downloading and installing new signed builds (.dmg, .deb, .msi) from the official releases.

5. How can I transfer my OpenLogi bindings to another computer? Simply copy the ~/.config/openlogi/config.toml file to the new machine. Because devices are keyed by their physical identity (receiver serial number and slot, or device serial), the bindings will automatically apply to the same hardware on any system where OpenLogi is installed with that config file.