[WARN] Error adding device /dev/hidraw2: Device timed out - MX Keys for Business #406
Comments
|
I run the commando "sudo logid -v" and get this informations "[DEBUG] Unsupported device /dev/hidraw0 ignored |
|
Anyone? |
|
I'm having this issue too, with a M720 Triathlon connected over Bluetooth.
|
|
I've the same issue as @IgorAntunes66 with a new MX Keys for Business (YR0073), the hidraw is also not in use by the process afterwords. I also tried to set the timeout to 5000ms, so i can see that /dev/hidraw6 is opend by logid until the timeout is reached. Has anyone some idears how to debug this issue? |
|
i believe i have a similar issue: |
|
An analogous situation with MX Keys Mini. I observed the following behaviour: As you can see, beginning with button 103 (higher number buttons do the same, I checked it), the keyboard unexpectedly responds to the HID++ 2 FAP with the second byte According to the hid++ 2.0 specification by Logitech:
So at first, this was my understanding: But then I found more: And dug deeper, taking a look at Linux hid++ driver: If you look here once again: So I looked into the code and saw that Another thing is that this library never correctly understands an error response, if such arrives (feature index = |
|
I've issued a pull request that resolves the problem. |
|
@wprzytula I built your code but the problem persists, in this case with a MX Mechanical Mini. Here the output: [INFO] Config file does not exist, using empty config. Some system details:
|
Please post your output when run with |
|
My M720 Triathlon is also still timing out with your code. When it's connected over Bluetooth, logid crashes with the same timeout. When the mouse is connected via the Unifying receiver, logid (your branch, at least) works fine and I can remap the gesture thumb button. |
Could you please provide your |
That's the output: |
|
If you look closely, you'll see that the last two lines are identical to what I had experienced before I introduced my changes. Are you sure that you are building the code with my changes? It would be strange if an exactly identical message were sent from another place in code than the one I fixed. |
You mentioned Bluetooth connection and I can see a timeout; and I asked about the Unifying receiver instead and a successful connection log, for comparison with the erroneous connection using Bluetooth. |
|
I am a moron, it has been fixed. Sorry about that 😃 I also am definitely running your code, |
|
@wprzytula, my bad, I built using your fork but using main instead the improved branch. This works well. Thanks for the support! |
|
I have a POP Keys and POP Mouse, and encountered the same timeout error (logiops 0.3.3 on gentoo). Applying the patch from @wprzytula to my build resolved this, as well. Thank you. |
Description:
When running the command "sudo logid", it gives an error identifying the MX Keys for Business keyboard model "YR0073".
Steps to Reproduce:
Run the command "sudo logid"
Evidence: Terminal Output
"[INFO] Device found: MX Master 3 for Business on /dev/hidraw1:255
[INFO] Device found: MX Keys for Business on /dev/hidraw2:255
[WARN] Error adding device /dev/hidraw2: Device timed out"
The mouse is detected normally, but the keyboard encounters this problem.
The text was updated successfully, but these errors were encountered: