OpenLogi

0x8060 · adjustableReportRate

Enumerate 1 ms to 8 ms report intervals, then read or write the active legacy report interval.

adjustableReportRate controls how often a device sends HID reports to its host. The feature expresses the active interval in milliseconds. Devices that expose 0x8060 advertise each supported interval in a one-byte bitmap.

Spec: Logitech HID++ 2.0 — adjustableReportRate. Cross-checked: Logi Options+ 2.8 (static analysis), Solaar. Used by: Report rate.

Function reference

The ReportRateFeature wrapper (0x8060, version 0+) exposes the legacy interval interface.

Methods

FunctionHID++ fnSignatureReturns
get_report_rate_list0()ReportRateList
get_report_rate1()u8
set_report_rate2(report_rate_ms: u8)()

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

Types

ReportRateList is a u8 bitflag set. Bit n names the interval n + 1 ms.

FlagBit or valueDescription
MS_11 << 01 ms interval.
MS_21 << 12 ms interval.
MS_31 << 23 ms interval.
MS_41 << 34 ms interval.
MS_51 << 45 ms interval.
MS_61 << 56 ms interval.
MS_71 << 67 ms interval.
MS_81 << 78 ms interval.

Events

ReportRateFeature exposes no event type. OpenLogi has no 0x8060 report-rate broadcast path.

Wire format

All functions send 3-byte short requests. OpenLogi reads functions 0 and 1 as 16-byte extended replies. The setter checks only the HID++ acknowledgement.

get_report_rate_list (fn 0)

Request: [0x00, 0x00, 0x00]. All three bytes are padding.

Byte or bitsFieldNotes
0, bits 0–7ReportRateListBit 0 is 1 ms through bit 7 for 8 ms.
1–15ReservedOpenLogi ignores these bytes.

get_report_rate (fn 1)

Request: [0x00, 0x00, 0x00]. All three bytes are padding.

ByteFieldNotes
0report_rate_msActive interval in milliseconds. OpenLogi accepts only 1..=8; another value returns Hidpp20Error::UnsupportedResponse.
1–15ReservedOpenLogi ignores these bytes.

set_report_rate (fn 2)

Request bytesFieldNotes
0report_rate_msRequested interval in milliseconds. OpenLogi accepts only 1..=8; another value returns Hidpp20Error::Feature(ErrorType::InvalidArgument) before I/O.
1–2PaddingOpenLogi writes 0x00.

Response: HID++ acknowledgement. OpenLogi ignores all response payload bytes. An in-range interval that the device does not support can return InvalidArgument.

How OpenLogi uses it

Since v0.8.14, PR #1779 rejects invalid legacy reply and request intervals in the typed wrapper. Since v0.8.14, PR #1808 connects report rate to the device layer, agent IPC, desktop Pointer tab, and openlogi api report-rate.

The device layer prefers 0x8061 when a device exposes it. It falls back to 0x8060 only when 0x8061 is unsupported. For this feature, it converts the advertised intervals to whole hertz, reads the list and active rate, and refuses a value not in that list before it writes.

The device layer skips a write when the rate is already active. Otherwise it reads back the active rate after the acknowledgement. A different read-back returns WriteError::ReportRateNotApplied; a post-write read failure retains the acknowledged requested rate as a provisional result.

The agent saves report_rate only when the user requests persistence. On reconnect, it re-applies a saved rate only to a device with report-rate capability and only when the current connection advertises that rate. OpenLogi does not reset the device's report rate on exit. See Report rate for the GUI, configuration, and CLI behavior.

Usage (Rust)

use hidpp::{
    device::Device,
    feature::report_rate::{ReportRateFeature, ReportRateList},
    protocol::v20::Hidpp20Error,
};

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

    if let Some(feature) = device.get_feature::<ReportRateFeature>() {
        let supported = feature.get_report_rate_list().await?;
        if supported.contains(ReportRateList::MS_1) {
            feature.set_report_rate(1).await?;
        }
    }

    Ok(())
}

On this page