OpenLogi

0x4522 · disableKeysByUsage

Disable or re-enable keyboard keys by 8-bit HID usage, using cumulative long-report requests.

DisableKeysByUsage controls arbitrary 8-bit keyboard HID usages. Unlike 0x4521, each disable or enable request adds to or removes from the existing disabled set.

Spec: Logitech HID++ 2.0 — disableKeysByUsage. Used by: Not used by OpenLogi outside the openlogi-hidpp wrapper.

Function reference

DisableKeysByUsageFeature is creatable for feature version 0.

Methods

FunctionHID++ fnSignatureReturns
get_capabilities0()u8
disable_keys1(usages: &[u8])()
enable_keys2(usages: &[u8])()
enable_all_keys3()()

Every method is async and returns Result<…, Hidpp20Error>.

Types

This feature has no public feature-specific type. Each usages element is an 8-bit keyboard HID usage.

Events

OpenLogi v0.8.15 exposes no event type or listen() method for this feature.

Wire format

get_capabilities and enable_all_keys use 3-byte short requests. disable_keys and enable_keys use 16-byte long requests.

OpenLogi rejects 0x00 in usages with Hidpp20Error::Feature(ErrorType::InvalidArgument). The value is the wire list terminator and cannot represent a disabled key.

get_capabilities (fn 0)

Request: 0x00, 0x00, 0x00.

ByteFieldNotes
0max_usagesMaximum number of usages the device can hold disabled.
1–15—OpenLogi ignores these bytes.

disable_keys (fn 1)

OpenLogi splits the input into sequential packets of 16 usages. The device accumulates every packet into its disabled set.

ByteFieldNotes
0–15usagesUp to 16 usage bytes. A partial packet is zero-padded, which supplies the 0x00 terminator.

A full 16-byte packet has no terminator. OpenLogi waits for each reply but ignores all reply bytes.

enable_keys (fn 2)

This function uses the same 16-byte packet layout as disable_keys. Each usage removes that key from the disabled set; enabling an already enabled key is a device no-op.

ByteFieldNotes
0–15usagesUp to 16 usage bytes. Partial packets are padded with 0x00.

OpenLogi waits for each reply but ignores all reply bytes.

enable_all_keys (fn 3)

Request: 0x00, 0x00, 0x00.

The function clears the complete disabled-usage set. OpenLogi waits for the reply and ignores its bytes.

How OpenLogi uses it

OpenLogi v0.8.15 exposes only the typed wrapper. No device-layer, agent, CLI, or user-interface path calls this feature.

An empty usage slice is valid and sends no requests. The wrapper does not cache the disabled set, so it has no state to restore at exit.

Usage (Rust)

use hidpp::{
    device::Device,
    feature::disable_keys_by_usage::DisableKeysByUsageFeature,
};

// `device` is a discovered HID++ device.
device.enumerate_features().await?;
if let Some(feature) = device.get_feature::<DisableKeysByUsageFeature>() {
    let capacity = feature.get_capabilities().await?;
    println!("maximum disabled usages: {capacity}");

    feature.disable_keys(&[0x3a, 0x3b, 0x3c]).await?;
    feature.enable_keys(&[0x3b]).await?;
    feature.enable_all_keys().await?;
}

On this page