Logitech MX Master 3
Fully drivable by open code over the stock firmware.
Configurable on Linux with libratbag (hidpp20 driver) and the Piper or ratbagctl front ends: resolutions, buttons, LEDs and profiles where the device exposes them. Also matched over Bluetooth (046d:b023). Supported features vary by model and firmware; this is not an OpenDeviceDB hardware test.
Get started
One known way to put open firmware or software on this device, easiest first. Each one links to the project's own instructions.
- Back up your data and settings (and the stock firmware, when the guide says how).
- Check the exact model, hardware revision and firmware version against the guide: a close model may not work.
- Charge the battery or use a stable power supply; do not unplug during the install.
Use libratbag (nothing is flashed)
Install: easy
Use libratbag (nothing is flashed)No tools, the device stays closed · libratbag
- Device opened
- No
Install libratbag (ratbagd) and Piper from your Linux distribution, or build from source if your distribution's version predates this device file.
No install report yet. · Report how it went
OpenDeviceDB links to each project's own instructions and tools; nothing is flashed from this site. Flashing is at your own risk and may void the warranty.
Use this device
Discover the available functions and their setup requirements.
USB technical examples
These examples and utilities demonstrate components or read an existing driver. Check each tool’s requirements.
- ID
- logitech/mx-master-3
- Category
- peripheral
- Vendor support
- Unknown
- usb
- 046d:4082
- Updated
- 2026-11-10
Being worked on
No live claim. If you start working on this device, claim it so nobody duplicates your work.
Interfaces
No interface documented yet.
Projects
| Project | Kind | Origin | License | Freedom |
|---|---|---|---|---|
| libratbag | driver | community | MIT | Still non-free: stock firmware · Cloud: nonelibratbag configures the device's existing firmware over USB or Bluetooth; it does not replace it. |
| Piper | tool | community | GPL-2.0-or-later | not stated |
What "still non-free" and "cloud" mean
What "still non-free" and "cloud" meanWhat stays proprietary or depends on the vendor's cloud once the project is in use, from the project's own documentation.
- vendor blobs
- proprietary files extracted from the stock firmware
- stock firmware
- the stock firmware stays on the device; the project only talks to it
- modem
- cellular modem firmware
- GPU
- graphics driver or firmware
- Wi-Fi
- Wi-Fi driver or firmware
- Bluetooth
- Bluetooth firmware
- camera
- camera driver or image processing
- sensors
- sensor hub or sensor drivers
- bootloader
- boot firmware
- other
- another proprietary part
- Cloud: none
- works fully locally
- Cloud: only at setup
- a vendor account is needed once, e.g. to obtain a local key
- Cloud: optional
- cloud features exist but are not needed
- Cloud: required
- does not work without the vendor's cloud
- Cloud: unknown
- not known
Verification
Not verified. A "verified on hardware" badge requires a replayable test (hardware-replay) run on a real device with a stated firmware version.
Provenance
- libratbag mice and peripherals (MIT, fetched 2026-11-10) · about this source
AI assistance not stated.
Status and claims as of the build date (2026-11-13). Data licensed CC BY-SA 4.0; imported data keeps its upstream license.