-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
non-connected devices give error #21
Comments
If I knew what each error code exactly means I could improve the message. The doc from Logitech (see section 2.10) is not very explicit. I'm going to reference #16 which also mention an obscure error message from an unifying receiver. |
It looks as if hidpp is doing an HID++ 2.0 protocol version / ping request of the device connected to the receiver. HID++ 1.0 devices give a particular error (0x01) for this request. It appears that if there is no device connected the error is 0x09 "Unsupported", which as you say is rather generic. Solaar assumes that this error from this request is because the device is not connected. Solaar also uses information stored in receiver registers for non-connected devices, as in
|
Same here under Linux. For my case, both the keyboard and mouse are connected to the USB receiver. But technically the USB receiver will be list as three hidraw devices.
|
It seems to me the error is not consistent. Most of the time it is okay for me. But the bluetooth mouse will appear sometimes once and sometimes twice.
|
Debug log:
|
I just go the following output from a Logitech Unifying Receiver paired with a Craft Keyboard and an MX Master 3. The Craft Keyboard was not connected at the time.
idefix build> ./src/tools/hidpp-list-devices
/dev/hidraw14: Logitech USB Receiver (046d:c52b) HID++ 1.0
[error] Error while querying /dev/hidraw14 wireless device 1: Resource error
/dev/hidraw14 (device 2): MX Master 3 (046d:4082) HID++ 4.5
It looks as if non-connected devices give this resource error. Wouldn't it be better to provide a better response?
The text was updated successfully, but these errors were encountered: