Skip to main content

Architecture and Device Support

This is not a firmware SDK

The current Logitech developer model is an application-level plugin ecosystem. You extend Logi Options+ and Logi Plugin Service, not the underlying keyboard or mouse firmware directly.

1. The layers​

Your plugin or automation
        |
        +-- Smart Actions
        +-- App-specific profiles
        +-- Logi Actions SDK plugin
                |
                +-- Logi Plugin Service
                +-- Logi Options+
                +-- Actions Ring / MX Creative Console / supported devices

2. Official supported plugin surface​

The current public SDK docs define two device categories:

CategoryWhat it means
Action-executing devicesDevices or overlays that can run plugin actions
Haptics devicesDevices that can receive haptic feedback events

Officially documented action-executing surfaces include:

  • MX Creative Console
  • Actions Ring
  • Loupedeck devices

The docs describe Actions Ring as available via any MX device, and note that a Logitech MX device is required to activate it.

3. What this means for MX Keys and MX Master 3​

For MX Keys and MX Master 3, the supported customization story is:

  • app-specific customization,
  • Smart Actions,
  • Actions Ring,
  • Marketplace plugins through the current Logi ecosystem.

That is a real developer surface, but it is not the same as directly writing a raw hardware driver for the keyboard or mouse.

4. What this means for MK850​

MK850 Performance is the tricky one.

It is not an MX device, and I could not verify it in Logitech's current public Actions SDK supported-device material. That strongly suggests:

  • it is outside the main Actions Ring / Marketplace plugin path,
  • it likely belongs to older Logitech Options style customization,
  • it should not be treated as a primary target for a new Logi Actions SDK plugin.

So if your project specifically depends on MK850, plan conservatively.

5. Haptics note​

The current public SDK says haptics support is only available on MX Master 4.

That means:

  • MX Master 3 can participate in the action ecosystem,
  • but it is not the public haptics target.

6. Practical recommendation​

If you want something that works now:

  1. Build for the MX path first.
  2. Treat Actions Ring as the main plugin surface for MX Keys and MX Master 3.
  3. Treat MK850 as a customization-only device unless Logitech publishes broader support.