Edit Human Interface Device Parameters

Support
1

On my device my Mouse is for some reason detected as a keyboard, see screenshot below.
Nothing major, but kinda annoying. Especially when I get the low battery warning, then it just says keyboard battery low and it is not clear which device is meant.

My hope is this can probably fixed in some configuration file, but where?

Screenshot_20240505_000742
Screenshot_20240505_0007421020×700 56.6 KB

lsusb -tv
Bus 005.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 001: Dev 004, If 0, Class=Hub, Driver=hub/2p, 480M
        ID 05e3:0610 Genesys Logic, Inc. Hub
        |__ Port 002: Dev 005, If 0, Class=Human Interface Device, Driver=usbhid, 12M
            ID 046d:c52b Logitech, Inc. Unifying Receiver
        |__ Port 002: Dev 005, If 1, Class=Human Interface Device, Driver=usbhid, 12M
            ID 046d:c52b Logitech, Inc. Unifying Receiver
        |__ Port 002: Dev 005, If 2, Class=Human Interface Device, Driver=usbhid, 12M
            ID 046d:c52b Logitech, Inc. Unifying Receiver
2

What is the output of upower -d ?

3 
upower -d
Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_14
  native-path:          hidpp_battery_14
  model:                Wireless Mouse MX Master
  serial:               43-17-4b-5d
  power supply:         no
  updated:              So 05 Mai 2024 19:45:05 CEST (29 seconds ago)
  has history:          yes
  has statistics:       yes
  keyboard
    present:             yes
    rechargeable:        yes
    state:               discharging
    warning-level:       none
    battery-level:       normal
    percentage:          55% (should be ignored)
    icon-name:          'battery-low-symbolic'
  History (charge):
    1714931105  55,000  discharging
    1714931105  0,000   unknown
    1714931075  55,000  discharging
    1714931075  0,000   unknown
    1714931075  55,000  discharging
    1714931075  0,000   unknown
  History (rate):
    1714931105  0,000   unknown
    1714931075  0,000   unknown
    1714931075  0,000   unknown

Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_15
  native-path:          hidpp_battery_15
  model:                Craft Advanced Keyboard
  serial:               26-15-db-3f
  power supply:         no
  updated:              So 05 Mai 2024 19:45:05 CEST (29 seconds ago)
  has history:          yes
  has statistics:       yes
  keyboard
    present:             yes
    rechargeable:        yes
    state:               discharging
    warning-level:       none
    battery-level:       normal
    percentage:          55% (should be ignored)
    icon-name:          'battery-low-symbolic'
  History (charge):
    1714931105  55,000  discharging
    1714931105  0,000   unknown
    1714931076  55,000  discharging
    1714931076  0,000   unknown
    1714931076  55,000  discharging
    1714931076  0,000   unknown
  History (rate):
    1714931105  0,000   unknown
    1714931076  0,000   unknown
    1714931076  0,000   unknown

Device: /org/freedesktop/UPower/devices/DisplayDevice
  power supply:         no
  updated:              Sa 04 Mai 2024 14:43:29 CEST (104525 seconds ago)
  has history:          no
  has statistics:       no
  unknown
    warning-level:       none
    percentage:          0%
    icon-name:          'battery-missing-symbolic'

Daemon:
  daemon-version:  1.90.2
  on-battery:      no
  lid-is-closed:   no
  lid-is-present:  no
  critical-action: HybridSleep
4

https://wiki.archlinux.org/title/Logitech_Unifying_receiver

5

And? …

6

It’s a bug in upower Logitech MX Master detected as keyboard.

1 Like
7

This may potentially be of use (related links can be found on the page):

sudo pacman -S solaar

Retated: Manjaro packages - Solaar

However, the bug report linked by @medmedin for your specific device (open, and not addressed in a year) tends to indicate that a new mouse might be easiest solution.

Cheers.

8

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.