-
Notifications
You must be signed in to change notification settings - Fork 0
fix: allow to delete host connection when dongle is not connected #135
fix: allow to delete host connection when dongle is not connected #135
Conversation
980cb37
to
a422025
Compare
Should I try this branch build to see if I can get my Dongle connected/paired again? At the moment, when I connect the Dongle to USB, and unplug the UHK from USB, the UHK will say "Dongle" but will not send any keystrokes or mouse movements. I guess I have to repair it to the Dongle, but the Dongle doesn't even show up in Agent. |
That's strange. What does dmesg say when you plug it in? |
What is the output of the Agent when you start with |
and `lsusb' shows it as:
So it's certainly connected, and the kernel knows about it. I'll check Agent later, I have to go somewhere now. |
Actually, here's Agent's output:
|
The dongle communication interface in the list. Agent should communicate with it.
This PR fixes some bug. |
@kareltucek Robi told me that upon removing host connections, Agent deletes the dongle's connection info whenever the dongle is present. If the dongle is not present, the connection info stored on it is preserved. I think connection info shouldn't be deleted on the dongle for the sake of consistency, only in the right half. Agreed? |
Alright. |
@ert78gb Then please don't delete the connection info on the dongle upon deleting its host connection, even if it's connected. |
@kareltucek I am experiencing the following issues, which may be (partially) firmware-related. Please comment on them.
|
How would Agent know that this Dongle is the Dongle that used to be paired to the UHK that Agent is currently talking to, and not a Dongle paired to a different UHK which is currently not connected? Imagine I had two UHK80s, and two Dongles (one for each keyboard). If I leave Dongle A (paired to UHK A) plugged in, and connect UHK B via USB, how would Agent know not to delete the pairing to UHK A from Dongle A? |
@mondalaci will look into it. Have experienced it before, but was unclear on how to reproduce it. @mhantsch we provide ble addresses via usb commands.
Well, I guess Agent should again unpair the dongle whenever deleting a host connection when the dongle is connected. Furthermore, whenever Agent notices a new dongle, it should ask to whom it is paired, and if it is the currently connected keyboard, then check whether the uhk is paired to it, and if no, then delete the connection on the dongle. |
@ert78gb Let's do as Karel suggested. @kareltucek Should I create a firmware issue for this? |
Feel free to. |
Am I understanding well, technically I have to revert my last commit. Because it was the earlier behaviour.
Should we overcomplicated it? I mean when Agent detects the dongle is not paired with the keyboard then it offer to pair it. If the user deletes a host connection when Dongle is not connected then Agent can't delete the bonds from the Dongle. " ask to whom it is paired" @kareltucek do you mean Agent should use the |
Yes, please revert your commit. Based on our chat, please don't delete the bonds on dongles that weren't deleted because they were disconnected when deleting their host connection. It's a rare situation, and if someone is bothered by the LED color, they can pair the dongle and delete the pairing while the dongle is connected. |
I meant the new
|
This reverts commit 686efc3.
0d6a586
to
d28cba0
Compare
reverted the last commit and rebased the branch |
My dongle is connected, and after deleting its connection, its LED doesn't go red, not even when reconnected via USB. @kareltucek Please confirm this issue and provide instructions to Robi. |
Agent works as expected. Opening a firmware issue about the dongle LED update. |
No description provided.