Supported devices

The tables below say what each family exposes. The authority on your own unit is openlogi diag features, which prints the feature table OpenLogi read from it.

Mice and trackballs

SmartShift is the enhanced 0x2111 variant on MX Master 3 / 3S / 4 and current MX-line mice; the MX Master 2S answers the older 0x2110, and its horizontal wheel is a 0x6501 gesture descriptor rather than the 0x2150 thumb wheel feature. Both paths are driven.

Keyboards

F-row remapping goes through the OS input hook, so it works on any keyboard, including ones absent from the table below. What differs is the on-device settings a board exposes:

RGB is written as one static colour through 0x8070 rather than per-key effects; the MX Keys white backlight is 0x1982 and is driven from the CLI. See Lighting.

Lights and webcams

A Litra is matched on its complete raw-HID route — vendor id, product id, usage page 0xff43, usage 0x0202 — not the product id alone, so a vendor report never lands on an unrelated HID collection. Other Litra models are not driven yet. Cameras are the opposite: they are standard UVC devices, so detection keys off the vendor id and no model table is involved. See Lights & webcams.

Devices OpenLogi recognises

These are the products OpenLogi knows by name: it has each one's model ids, the controls it carries, and a render of it. Search for yours — the model ids are the ones openlogi list prints beside a paired device.

Being on the list is not what makes a device work, and being off it doesn't stop one. Panels follow the features your unit reports, so a device here can still lack one the family usually has, and a device that isn't here is driven exactly the same — it just falls back to a drawn generic mouse whose hotspots follow the capabilities measured on your unit. "Not listed" in the controls column means Logitech publishes no control layout for that product, which is common on G-series hardware, where button layouts live in onboard memory.

Receivers

C537 is the Nano receiver bundled with the G602; C539 ships with the G502 LIGHTSPEED and the G Pro Wireless, C53F is the G305's nano receiver, and C547 ships with newer G-series hardware such as the G915 and the G502 X LIGHTSPEED. Lightspeed dongles answer the same HID++ 1.0 registers as Unifying, so they are enumerated, routed, and paired through the Unifying path; only the displayed name differs. Details in the receiver reference.

A dongle outside those ids is not recognised as a receiver, so the devices paired to it are invisible. The device itself is still supported over Bluetooth or a cable — Bluetooth-direct and wired devices are addressed on their own HID++ channel at device index 0xFF, with no pairing-slot indirection. On macOS, a Bluetooth-direct mouse such as the Lift or a Signature needs Input Monitoring before it appears; see Connect a device.

Not supported yet

• Audio devices. A headset paired to a receiver is listed in the inventory, but there are no panels for it — no sidetone, no equalizer.
• Onboard-memory profiles. OpenLogi never writes a G-series onboard profile (0x8100). Its own per-app profiles are host-side and follow the frontmost application.
• Non-Logitech hardware. Both HID++ enumeration and camera enumeration filter on the Logitech vendor id (0x046d).

Check your own device

openlogi list            # what is connected, per receiver, with battery
openlogi diag features   # every HID++ feature the active device reports
openlogi diag controls   # reprogrammable controls and their capability flags

If openlogi list finds nothing, the usual cause is Logi Options+ still holding the receiver, or missing permissions — see Connect a device.

Feature panels

OpenLogi reads a device's feature table (0x0001 FeatureSet) once and gates panels on the feature ids present, never on the device's marketing type — a mouse that misreports itself keeps every panel its firmware backs.

Look any id up in the HID++ reference.