When I type while my UHK 80 is connected over Bluetooth, key strokes are missing.
Just now when I’m writing this post, there are missing letters (in this sentence alone: “h” in “when”, “o” in “post”, “e” in “letters”, …).
Previously I used a UHK 60 with the same key switches and this never happened, so I think this is a keyboard/firmware issue.
Feels like you are going through what I did yesterday. Might be helpful to review all the posts from yesterday. And looking at the issues for agent and firmware in GitHub
I thought I did. Where did you write about missing key presses? I only read about other Bluetooth issues, e.g. switching between USB-C and BLE (which I’m also seeing).
I found that the left and right sides got out of sync and as if the left side was delayed at times.
I see. I have not noticed this.
I’m now typing this with both halves individually connected via USB-C (two cables) and no bridge cable. I’m not seeing the missing keys anymore, so I’m pretty sure it’s the BLE connection.
I can’t rule out BLE being borked for you, but there have been some ongoing issues with garbled/missing output recently.
Someone correct me if I’m wrong, but I don’t think the left half’s keystroke output is sent through its (left half’s) USB cable; I’m pretty sure it’s sent via bridge cable or wireless communication to the right half, and then to the host through the right half’s USB/BLE/Dongle. I believe the left half’s USB is mostly just for charging and flashing firmware, etc…
So IMO, it seems the most likely culprit would be problems with communication over the bridge cable, and when you disconnected it, that’s what solved it…
Could you please test to see if it happens over BLE with no USB or bridge cable?
Also, if it happens with the bridge cable connected again, see if it stops by temporarily disconnecting the bridge cable while it’s happening?
It doesn’t necessarily occur consistently, so maybe just make a note of things if you see it again.
Anyway, it might be helpful for you to head over to GitHub and let them know you might be experiencing something similar over BLE. Like @Tunney said, it’s probably a good idea to go skim through the GitHub issues, because there’s a lot going on right now.
I suspect this is the issue likely related to what you’re experiencing:
Hmm.
I currently have the bridge cable disconnected and the right half connected via USB-C, not BLE and I’m again seeing missing key presses.
So I’m not sure what’s going on…
Thanks for the GitHub link!
I’m honestly quite frustrated now.
With the bridge cable connected and LEDs on, I have terrible high-pitched noise.
Without the bridge cable, I have missing key presses.
(And I paid more than €500 for this - including the Riser 80, OS keycap and shipping.)
I’m not sure if these are fundamental hardware flaws or things that can be fixed with software.
I’m sure the missing key presses issue is probably solvable in firmware. Please create an issue on GitHub so they can look into it.
As for the noise, Idk how much can be done about that, but here’s a GitHub link about it:
What version of firmware and Agent are you using, BTW?
Agent 5.0.2 and Firmware 12.2.0.
And just now I had lags, missing key presses and out of order key presses even with the bridge cable connected.
I also just reflashed the firmware, but that (unsurprisingly) didn’t help.
Try downgrading to FW v12.0.1, and see if that’s better. Also might be a good idea to flash it with the bridge cable disconnected, just in case.
Pretty sure it is software.
There is a lot of new code, and old code has been drastically restructured in order to improve battery life, and we have not yet figured out how to debug these efficiently. At the moment it is very challenging to figure out where these problems originate, especially given that we can’t reproduce them.
And yes, right half is uhk’s brain. All keystrokes are processed there and then sent via right half usb or ble.
The firmware is maturing rapidly; I’m sure we’ll fix such issues. We’ll devise a way to make these issues as easily reproducible as possible.
As for the noise, I’m still working on reducing it, and I’ll keep you updated.
Thank you! I’ve been a loyal user since 2017 and hope the UHK 80 will be as great as the original UHK and the UHK 60v2.
When I have the keyboard in front of me completely wireless with no bridge cable and connected to the computer with BLE, it feels almost magical. So I’m looking forward to the firmware updates.
I can see the same behaviour today. If the left side is connected to any source of power (bridge or USB) the high pitched sound is there. Doesn’t matter what the LEDs are set to. So would suspect LEDs a red herring.
Very high pitched and loud. Given the return period is 14 days does not bode well for a resolution in this period.
Yeah, that is my thinking as well. An extended return period would be great…
Some more testing results.
Connect the two halves together with the spiral cable disconnected. Connect the right side to the computer.
Observe that there is no noise.
Leave the two halves connected and connect the spiral cable.
Observe that the noise is back.
I think that’s similar to what I tried to describe here: High-pitched noise when connecting left half of UHK 80 to USB-C for charging - #7 by Lextar
Except that you are connecting it with two USB-C cables and without the bridge cable at first if I understand correctly?