Logitech illuminated keyboard (wired HID++ 1.0 device) causes error at startup

Created by: JohnyPeaN

Information

• Solaar version: 1.1.8
• Distribution: Garuda Linux
• Kernel version: Linux 6.1.4-1-cachyos-tt-lto x86_64 GNU/Linux
• Output of solaar show:

solaar version 1.1.8

USB and Bluetooth Devices

solaar: error: Traceback (most recent call last):
File "/usr/lib/python3.10/site-packages/solaar/cli/__init__.py", line 209, in run
m.run(c, args, _find_receiver, _find_device)
File "/usr/lib/python3.10/site-packages/solaar/cli/show.py", line 305, in run
_print_device(d, num=dev_num)
File "/usr/lib/python3.10/site-packages/solaar/cli/show.py", line 85, in _print_device
dev.ping()
File "/usr/lib/python3.10/site-packages/logitech_receiver/device.py", line 455, in ping
protocol = _base.ping(self.handle or self.receiver.handle, self.number, long_message=long)
File "/usr/lib/python3.10/site-packages/logitech_receiver/base.py", line 556, in ping
raise NoSuchDevice(number=devnumber, request=request_id)
logitech_receiver.base.NoSuchDevice: {'number': 255, 'request': 31}

• Contents of ~/.config/solaar/config.yaml (or ~/.config/solaar/config.json if ~/.config/solaar/config.yaml not present):

- 1.1.8
- _NAME: ERGO M575 Trackball
_absent: [hi-res-scroll, lowres-scroll-mode, hires-smooth-invert, hires-smooth-resolution, hires-scroll-mode, smart-shift, thumb-scroll-mode, thumb-scroll-invert,
onboard_profiles, report_rate, pointer_speed, speed-change, backlight, backlight-timed, fn-swap, persistent-remappable-keys, disable-keyboard-keys,
divert-crown, crown-smooth, divert-gkeys, m-key-leds, mr-key-led, multiplatform, change-host, gesture2-gestures, gesture2-divert, gesture2-params, sidetone,
equalizer, scroll-ratchet]
_battery: 4100
_modelId: B02740960000
_sensitive: {dpi: true}
_serial: 650148AA
_unitId: 650148AA
_wpid: '4096'
divert-keys: {82: 0, 83: 0, 86: 0}
dpi: 700
reprogrammable-keys: {80: 80, 81: 81, 82: 82, 83: 83, 86: 86}
- _NAME: Wireless Mouse M185 new
_absent: [hi-res-scroll, hires-smooth-invert, hires-smooth-resolution, hires-scroll-mode, smart-shift, thumb-scroll-invert, thumb-scroll-mode, onboard_profiles,
report_rate, dpi, dpi-sliding, speed-change, backlight, backlight-timed, fn-swap, persistent-remappable-keys, disable-keyboard-keys, crown-smooth, divert-crown,
divert-gkeys, m-key-leds, mr-key-led, multiplatform, change-host, gesture2-gestures, gesture2-divert, gesture2-params, sidetone, equalizer]
_battery: 0
_modelId: '000000000000'
_serial: '00000000'
_unitId: '00000000'
_wpid: '4054'
divert-keys: {82: 0}
lowres-scroll-mode: false
pointer_speed: 256
reprogrammable-keys: {80: 80, 81: 81, 82: 82}

• Errors or warrnings from Solaar: logitech_receiver.base.NoSuchDevice: {'number': 255, 'request': 31}

Describe the bug My Logitech Illuminated keyboard (wired, USB) model: Y-UY95 started causing an exception on solaar startup and breaking detection of other devices. Solaar starts up with no devices detected. After unplugging and plugging back unifiing receiver it gets detected and works.

To Reproduce Steps to reproduce the behavior:

1. Start solaar with both Y-UY95 and Logitech receiver connected.
2. No devices show up.
3. Unplug and plug back Logitech receiver.
4. Receiver shows up and normal functionality resumes.
5. After new start (logout, reboot, exit/start solaar) situation repeats.

Additional context Solaar worked well in the past even while using this keyboard, but can't pinpoint when the behavior changed. Used to replug the receiver for a while.

According to the traceback output I tried to alter /usr/lib/python3.10/site-packages/logitech_receiver/base.py on line 556

-raise NoSuchDevice(number=devnumber, request=request_id) +return

and now it works, just shows greyed out unknown device "?? (C318)" It would be better to handle such error more gracefully and not interrupt the startup detection.