0x8080 · perKeyLighting
Legacy per-key RGB lighting control that streams HID usage and colour entries in very-long reports, then commits the staged frame.
0x8080 is the earlier per-key RGB feature for keyboards with addressable LEDs.
OpenLogi drives it as a raw HID++ fallback when newer lighting paths are unavailable.
Spec: No public Logitech specification. Layout reverse-engineered from Logi Options+ 2.8 (static analysis). Used by: Keyboard lighting.
Function reference
OpenLogi has no typed PerKeyLightingFeature wrapper for 0x8080.
Its device writer resolves the runtime feature index and sends the two raw commands below.
Methods
| Function | HID++ fn | Signature | Returns |
|---|---|---|---|
setKeyColors | 3 | one 64-byte 0x12 report with at most 14 (key_id, red, green, blue) entries | Raw write length; feature errors are collected before commit. |
flushLeds | 5 | one normal long request with a 16-byte zero payload | Result<(), WriteError> after the HID++ response. |
Types
The raw writer has no public 0x8080 type, enum, or per-key state model.
It accepts one u8 value for each RGB channel.
Events
0x8080 has no feature-specific OpenLogi event type.
The raw writer listens only for HID++ feature errors that match its streamed frames.
Wire format
setKeyColors uses the 64-byte HID++ very-long report (0x12).
flushLeds uses a normal HID++ long request and waits for its response.
setKeyColors (fn 3)
OpenLogi sends 17 frames for its 0x00..=0xe8 HID usage range.
Sixteen frames contain 14 entries, and the final frame contains nine entries.
| Byte(s) | Field | Value or encoding | Notes |
|---|---|---|---|
| 0 | report ID | 0x12 | HID++ very-long report. |
| 1 | device index | runtime value | The device route supplies this value. |
| 2 | feature index | runtime value | OpenLogi resolves the index for 0x8080. |
| 3 | function and software ID | high nibble 3; low nibble 0xa | Function 3 with OpenLogi software ID 0xa. |
| 4–5 | key_type | BE 0x0001 | OpenLogi writes this fixed value. Options+ 2.8 |
| 6–7 | entry_count | BE u16, 1..=14 | The count equals entries in this frame. Options+ 2.8 |
| 8–63 | entries | up to 14 × (key_id, red, green, blue) | key_id is one byte, followed by three 8-bit RGB channels. Options+ 2.8 |
Unused entry bytes remain zero. They are outside entry_count and must not be treated as entries.
Since v0.8.14, OpenLogi writes the final count as BE 0x0009, not 0x000e.
flushLeds (fn 5)
This command commits the colours staged by prior function-3 reports. OpenLogi sends it only after the streamed reports pass its error check.
| Byte(s) | Field | Value | Notes |
|---|---|---|---|
| 0–15 | payload | all 0x00 | OpenLogi sends a normal long request with function 5 and software ID 0xa. |
OpenLogi waits for the normal HID++ reply to this request. It does not assign semantics to the reply payload.
How OpenLogi uses it
LightingMethod::Auto tries 0x8070, then 0x8071, then 0x8081, and finally 0x8080.
LightingMethod::PerKey selects this raw path for diagnostics.
The writer resolves 0x8080 through the Root feature at run time.
It has no typed feature wrapper or feature-version gate.
The writer streams every HID usage from 0x00 through 0xe8 with one requested RGB colour.
It checks that every raw report wrote all 64 bytes.
The protocol response report ID for a very-long function-3 request is not established. OpenLogi therefore records matching feature errors while streaming each frame.
A Root ping follows the last frame and acts as an ordered response fence.
If the device rejected any frame, OpenLogi returns that error and does not send flushLeds.
The final function-5 request uses the normal HID++ request path and waits for its reply. This check shipped in v0.8.14 through PR #1764.
OpenLogi applies a solid colour only. It does not store or expose a map of independent key colours through the keyboard-lighting product surface.
Open questions
Options+ 2.8 calls function 3 synchronously, but static analysis does not establish its response report ID. OpenLogi cannot wait for a per-frame success reply until a hardware capture identifies that response.
The current error listener and Root-ping fence prevent a known rejected frame from being committed.
A hardware capture must verify this behavior on 0x8080 keyboards.
Usage (Rust)
use openlogi_hid::{
set_keyboard_color_with, DeviceRoute, LightingMethod, WriteError,
};
async fn paint_with_legacy_per_key(
route: &DeviceRoute,
) -> Result<(), WriteError> {
set_keyboard_color_with(
route,
LightingMethod::PerKey,
0x20,
0x80,
0xff,
)
.await
}