What problem it solves

Users need a local way to configure Logitech mice, keyboards, and webcams without an account or telemetry. OpenLogi addresses configuration needs such as button remapping, DPI, SmartShift, gestures, keyboard lighting, and camera controls through HID++, UVC, and a CLI automation API.

Key features

• Local-first device configuration — Configure supported Logitech devices locally, with settings stored in a plain TOML file that can be synchronized between machines. The application provides a native interface and a CLI with a JSON automation API.

  Source: README

• Button, gesture, and profile remapping — Remap mouse buttons and keyboard keys to built-in actions, shortcuts, typed text, or multi-step workflows. Per-application profiles can switch with the focused app and follow an application across platforms through an alias.

  Source: README

• Pointer and scrolling controls — Adjust DPI presets, pointer speed, report rate, SmartShift behavior, scroll direction, wheel resolution, and smooth scrolling. Supported controls include a permanent-ratchet switch and sideways scrolling using the Back or Forward buttons.

  Source: README

• Keyboard and lighting management — Manage Fn Lock, keyboard backlight behavior, and static RGB on supported keyboards. Litra lights expose power, brightness, and color-temperature controls.

  Source: README

• UVC webcam controls and profiles — Control supported Logitech UVC webcams, including zoom, pan, tilt, focus, exposure, and white balance. The application provides live preview and Default, Streaming, and Video call profiles that are kept per camera.

  Source: README

Quick start

Copied verbatim from the project's README.

brew install --cask openlogi

curl -fsSL https://github.com/AprilNEA/OpenLogi/releases/latest/download/install.sh | sh

yay -S openlogi

Who it may suit

Inference: may suit Linux, macOS, and Windows users who want local, scriptable control of supported Logitech mice, keyboards, webcams, and lighting.

Topics to discuss

• Which Logitech devices and individual controls should receive priority for compatibility testing?

• How should community members organize and share portable TOML configurations across machines?

• What workflows should be prioritized for the CLI automation API beyond DPI, SmartShift, Fn-lock, and report rate?

Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.

Read the original README https://github.com/AprilNEA/OpenLogi#readme

ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.