OpenLogi

0x8090 · modeStatus

Read and selectively update a device’s performance-mode status and its hardware or software switching capabilities.

The modeStatus feature reads two mode-status bytes and selectively updates their bits. In v1, bit 0 of status0 selects performance mode; an unset bit selects endurance mode. OpenLogi v0.8.15 provides a typed protocol wrapper, but no device-layer path uses it.

Spec: Logitech HID++ 2.0 — modeStatus (v1). Cross-checked: G HUB (static analysis). Used by: Not used by OpenLogi.

Function reference

ModeStatusFeature is available when feature enumeration finds 0x8090 at version 1 or later.

Methods

FunctionHID++ fnSignatureReturns
get_mode_status0()ModeStatus
set_mode_status1(change: ModeStatusChange)()
set_performance_mode1(enabled: bool)()
get_device_config2()ModeStatusCapabilities

All methods are async and return Result<…, Hidpp20Error>.

Types

ModeStatus

FieldTypeDescription
status0ModeStatus0Primary status bits. Unknown bits are retained.
status1u8Secondary status byte. v1 reserves this byte, and OpenLogi preserves it on reads.

ModeStatusChange

FieldTypeDescription
status0ModeStatus0Requested primary status bits.
status1u8Requested secondary status byte.
changed_mask0ModeStatus0Primary bits to update.
changed_mask1u8Secondary bits to update.

ModeStatus0

VariantValueDescription
PERFORMANCEbit 0Performance mode. An unset bit selects endurance mode.

ModeStatusCapabilities

VariantValueDescription
HARDWARE_SWITCHbit 0A hardware switch can change the mode bit.
SOFTWARE_SWITCHbit 1Software can change the mode bit.

Events

ModeStatusFeature has no event listener or event decoder in OpenLogi v0.8.15.

Wire format

Short requests contain 3 zero bytes. OpenLogi expands short responses to its 16-byte payload buffer before decoding them.

get_mode_status (fn 0)

Request: [0x00, 0x00, 0x00].

ByteFieldNotes
0status0ModeStatus0; bit 0 is PERFORMANCE. Unknown bits are retained.
1status1Secondary status byte.
2–15—OpenLogi does not read these bytes.

set_mode_status (fn 1)

OpenLogi sends a 16-byte long request and checks only the result status.

ByteFieldNotes
0status0Requested primary status bits.
1status1Requested secondary status byte.
2changed_mask0Primary bits to update.
3changed_mask1Secondary bits to update.
4–15—OpenLogi writes zero.

set_performance_mode (fn 1)

This convenience method uses the fn 1 layout. It writes PERFORMANCE or an empty status0, sets changed_mask0 to PERFORMANCE, and writes zero to both secondary fields.

get_device_config (fn 2)

Request: [0x00, 0x00, 0x00].

ByteFieldNotes
0–1capabilitiesu16 BE. Bits 0 and 1 map to HARDWARE_SWITCH and SOFTWARE_SWITCH. Unknown bits are retained.
2–15—OpenLogi does not read these bytes.

Status event (event 0)

ByteFieldNotes
0–3Status payloadG HUB passes four bytes to its upper layer without byte-order conversion. The field mapping is not recovered. G HUB

OpenLogi v0.8.15 does not subscribe to or decode this event.

How OpenLogi uses it

OpenLogi creates ModeStatusFeature during feature enumeration when a device reports 0x8090 version 1 or later. No device-layer writer, session, inventory path, CLI command, or user-facing page calls the wrapper in v0.8.15. OpenLogi therefore performs no read-modify-write sequence, read-back check, state restoration, or capability gate beyond the wrapper’s version gate.

Open questions

G HUB static analysis identifies a four-byte status event, but it does not recover the meanings of its bytes. The event payload and device behavior need hardware verification before OpenLogi adds an event decoder or a device-layer policy.

Usage (Rust)

use hidpp::{
    device::Device,
    feature::mode_status::{
        ModeStatus0, ModeStatusCapabilities, ModeStatusFeature,
    },
    protocol::v20::Hidpp20Error,
};

async fn enable_performance_mode(device: &mut Device) -> Result<(), Hidpp20Error> {
    device.enumerate_features().await?;

    let Some(feature) = device.get_feature::<ModeStatusFeature>() else {
        return Ok(());
    };

    let status = feature.get_mode_status().await?;
    println!("performance mode: {}", status.status0.contains(ModeStatus0::PERFORMANCE));

    let capabilities = feature.get_device_config().await?;
    if capabilities.contains(ModeStatusCapabilities::SOFTWARE_SWITCH) {
        feature.set_performance_mode(true).await?;
    }

    Ok(())
}

On this page