can not configure keyboard and mouse separately

[Vladymir]

I have Logitech wireless keyboard and wireless mouse, coonnected to the same Unifying receiver.
battery level of these devices is reported correctly, but both are listed in power settings as a keyboard, making me a bit confusing, which device is ran out of power, when I get 'low keyboard battery' message.

trying to set correct device type via modaliases for mouse changes nothing, but when I change my keyboard to 'a mouse', I get two mice in power settings! (and no keyboard)
thus, I can not configure these devices separately, to get 1 keyboard and 1 mouse, but only can see 2 keyboards or 2 mice.

ubuntu unity 23.04
UPower client version 0.99.20
UPower daemon version 0.99.20

output of 'upower -d':

Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_0
  native-path: hidpp_battery_0
  model: K800
  serial: b2-69-6e-91
  power supply: no
  updated: Wed 05 Jul 2023 10:57:43 (2 seconds ago)
  has history: yes
  has statistics: yes
  keyboard
    present: yes
    rechargeable: yes
    state: discharging
    warning-level: low
    battery-level: low
    percentage: 10% (should be ignored)
    icon-name: 'battery-caution-symbolic'

Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_1
  native-path: hidpp_battery_1
  model: Performance MX
  serial: 04-81-33-3a
  power supply: no
  updated: Wed 05 Jul 2023 10:57:37 (8 seconds ago)
  has history: yes
  has statistics: yes
  keyboard
    present: yes
    rechargeable: yes
    state: discharging
    warning-level: none
    battery-level: high
    percentage: 70% (should be ignored)
    icon-name: 'battery-good-symbolic'

Device: /org/freedesktop/UPower/devices/DisplayDevice
  power supply: no
  updated: Wed 05 Jul 2023 10:48:37 (548 seconds ago)
  has history: no
  has statistics: no
  unknown
    warning-level: none
    percentage: 0%
    icon-name: 'battery-missing-symbolic'

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

modaliases in 61-input-id-local.hwdb:

id-input:modalias:input:b0003v046Dp101Ae0111*
 ID_INPUT_MOUSE=1
 ID_INPUT=1

id-input:modalias:input:b0003v046Dp2010e0111*
 ID_INPUT_KEYBOARD=1
 ID_INPUT=1

[Sebastien Bacher (seb128)]

Thank you for your bug report. Which mouse model do you have? It looks similar to https://gitlab.freedesktop.org/upower/upower/-/issues/215

[Vladymir (vladymir0)]

device models are listed in the log above:
model: K800 (this is keyboard)
model: Performance MX (mouse)

their product codes are 046D:2010 and 046D:101A

it really seems similar to the issue #215, but that fix didn't help me.
I cloned git version of upower, compiled and installed.
now I see:

UPower client version 1.90.1
UPower daemon version 1.90.1

unfortunalely, the problem still persists.

[Vladymir (vladymir0)]

probably it's due to the single path (ID_PATH) for both devices?..
also suspective that MODEL_ID for both events is equal to c52b (wireless receiver), but not 101a (mouse)

udevadm info /dev/input/event3

P: /devices/pci0000:00/0000:00:14.0/usb3/3-6/3-6:1.2/0003:046D:C52B.0004/0003:046D:2010.0007/input/input18/event3
M: event3
R: 3
U: input
D: c 13:67
N: input/event3
L: 0
S: input/by-id/usb-Logitech_USB_Receiver-if02-event-kbd
S: input/by-path/pci-0000:00:14.0-usb-0:6:1.2-event-kbd
E: DEVPATH=/devices/pci0000:00/0000:00:14.0/usb3/3-6/3-6:1.2/0003:046D:C52B.0004/0003:046D:2010.0007/input/input18/event3
E: DEVNAME=/dev/input/event3
E: MAJOR=13
E: MINOR=67
E: SUBSYSTEM=input
E: USEC_INITIALIZED=4130304
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_INPUT_KEYBOARD=1
E: ID_BUS=usb
E: ID_MODEL=USB_Receiver
E: ID_MODEL_ENC=USB\x20Receiver
E: ID_MODEL_ID=c52b
E: ID_SERIAL=Logitech_USB_Receiver
E: ID_VENDOR=Logitech
E: ID_VENDOR_ENC=Logitech
E: ID_VENDOR_ID=046d
E: ID_REVISION=1210
E: ID_TYPE=hid
E: ID_USB_MODEL=USB_Receiver
E: ID_USB_MODEL_ENC=USB\x20Receiver
E: ID_USB_MODEL_ID=c52b
E: ID_USB_SERIAL=Logitech_USB_Receiver
E: ID_USB_VENDOR=Logitech
E: ID_USB_VENDOR_ENC=Logitech
E: ID_USB_VENDOR_ID=046d
E: ID_USB_REVISION=1210
E: ID_USB_TYPE=hid
E: ID_USB_INTERFACES=:030101:030102:030000:
E: ID_USB_INTERFACE_NUM=02
E: ID_USB_DRIVER=usbhid
E: ID_PATH=pci-0000:00:14.0-usb-0:6:1.2
E: ID_PATH_TAG=pci-0000_00_14_0-usb-0_6_1_2
E: XKBMODEL=pc105
E: XKBLAYOUT=us,rud
E: XKBVARIANT=dvorak,
E: XKBOPTIONS=grp:shift_caps_toggle
E: KMAP=/etc/console/boottime.kmap.gz
E: BACKSPACE=guess
E: LIBINPUT_DEVICE_GROUP=3/46d/2010:usb-0000:00:14.0-6
E: DEVLINKS=/dev/input/by-id/usb-Logitech_USB_Receiver-if02-event-kbd /dev/input/by-path/pci-0000:00:14.0-usb-0:6:1.2-event-kbd
E: TAGS=:power-switch:
E: CURRENT_TAGS=:power-switch:

udevadm info /dev/input/event4

P: /devices/pci0000:00/0000:00:14.0/usb3/3-6/3-6:1.2/0003:046D:C52B.0004/0003:046D:101A.0008/input/input19/event4
M: event4
R: 4
U: input
D: c 13:68
N: input/event4
L: 0
S: input/by-path/pci-0000:00:14.0-usb-0:6:1.2-event-mouse
S: input/by-id/usb-Logitech_USB_Receiver-if02-event-mouse
E: DEVPATH=/devices/pci0000:00/0000:00:14.0/usb3/3-6/3-6:1.2/0003:046D:C52B.0004/0003:046D:101A.0008/input/input19/event4
E: DEVNAME=/dev/input/event4
E: MAJOR=13
E: MINOR=68
E: SUBSYSTEM=input
E: USEC_INITIALIZED=4122172
E: ID_INPUT=1
E: ID_INPUT_MOUSE=1
E: ID_BUS=usb
E: ID_MODEL=USB_Receiver
E: ID_MODEL_ENC=USB\x20Receiver
E: ID_MODEL_ID=c52b
E: ID_SERIAL=Logitech_USB_Receiver
E: ID_VENDOR=Logitech
E: ID_VENDOR_ENC=Logitech
E: ID_VENDOR_ID=046d
E: ID_REVISION=1210
E: ID_TYPE=hid
E: ID_USB_MODEL=USB_Receiver
E: ID_USB_MODEL_ENC=USB\x20Receiver
E: ID_USB_MODEL_ID=c52b
E: ID_USB_SERIAL=Logitech_USB_Receiver
E: ID_USB_VENDOR=Logitech
E: ID_USB_VENDOR_ENC=Logitech
E: ID_USB_VENDOR_ID=046d
E: ID_USB_REVISION=1210
E: ID_USB_TYPE=hid
E: ID_USB_INTERFACES=:030101:030102:030000:
E: ID_USB_INTERFACE_NUM=02
E: ID_USB_DRIVER=usbhid
E: ID_PATH=pci-0000:00:14.0-usb-0:6:1.2
E: ID_PATH_TAG=pci-0000_00_14_0-usb-0_6_1_2
E: MOUSE_DPI=1000@166
E: LIBINPUT_DEVICE_GROUP=3/46d/101a:usb-0000:00:14.0-6
E: DEVLINKS=/dev/input/by-path/pci-0000:00:14.0-usb-0:6:1.2-event-mous...

[Vladymir (vladymir0)]

also FYI: solaar detects my mouse properly