Some keys of your UHK may start to produce repeated keystrokes or don't produce keystrokes at all.

If your UHK is affected, please check points 1 to 12 and let us know your findings point by point. Please don't skip any points. Only this way can we narrow down the cause.

  1. Disconnect the bridge cable and merge the keyboard halves. The bridge cable may be faulty.
  2. Disconnect the modules. The connection of your modules may not be reliable, triggering various issues with your UHK. If you've already used your UHK for a while, clean its contacts where the modules mate with isopropyl alcohol or contact cleaner spray. If the issue persists, please fasten these screws.
  3. Use the stock bridge cable. A third-party bridge cable may be the culprit, especially if it's long or contains thin wires.
  4. Use the stock USB cable. If you're using a third-party USB cable, it may cause issues.
  5. Put your wireless devices farther. Phones, tablets, and other wireless devices can interfere with your UHK, especially during a phone call or heavy data transfer.
  6. Connect your UHK directly to your computer. USB hubs, KVM switches, and docking stations may provide insufficient power.
  7. Connect your UHK to other computers. Some power supplies and chargers provide insufficient or noisy power.
  8. Connect your UHK via a powered USB hub. A powered USB hub should provide enough power to your UHK.
  9. Connect your UHK to a battery-powered laptop that isn't connected to mains power. If noisy mains power is the cause, your UHK should work this way.
  10. Try your UHK at another location; the farther, the better. Your environment may be affected by EMI (electromagnetic interference). Some appliances, such as treadmills, can generate electrostatic discharge, even your chair!
  11. Disable the LEDs in Agent. The power consumption of your UHK will be dramatically reduced this way, potentially fixing the issue. If so, you can increase LED brightness and experiment with how much power your computer can provide without affecting your UHK.
  12. Use contact cleaner spray. If only certain keys are affected, the misbehaving key switches are probably contaminated. Please remove the keycaps of the affected key switches (possibly with a DIY keycap puller), and spray contact cleaner spray into them while pressing them several times. Although compressed air spray may work, we suggest using contact cleaner spray, as it's far more effective.
  13. Replace key switches. If only certain keys are affected, and the above doesn't help, the misbehaving key switches must be replaced.
    • A) If you have a UHK 60 v1 and want to fix this yourself, you'll need basic soldering equipment; you can disassemble your UHK, then desolder the affected switches and solder new ones. If you choose this route and your two-year warranty is still valid, we'll gladly reimburse your expenses, such as key switches. Alternatively, if fixing things is not your cup of tea, and our two-year warranty covers you, shoot us an email, include your order id, and we'll recall and fix your UHK. We even provide post-warranty repairs, so feel free to reach out to us.
    • B) If you have a UHK 60 v2, you can easily replace the problematic switch with the keycap puller we provided. The switch may be perfect; you just have to remove it, bend its pins slightly to make contact with its sockets, and put it back.
  14. If the LED display flickers, it may be worth sticking a self-adhesive aluminum foil to the bottom of your left UHK half to shield the electronics from electromagnetic interference.

If you're affected by this issue, please let us know which of these points worked.

Advanced troubleshooting

If the above hasn't helped, install the latest Agent, go to the About page, click seven times on the Agent icon at the top, go to the newly shown Advanced settings page, and enable the "I2cRecovery debugging" option. The output should look like this:

2022-03-19 08:18:39 I2cRecovery: 0

The I2cRecovery value increments when communication errors occur within the UHK. You can trigger such errors by reconnecting the left half or the modules, and then the value will increase:

2022-03-19 08:24:32 I2cRecovery: 1
2022-03-19 08:24:36 I2cRecovery: 2

Under normal circumstances, the I2cRecovery value should be low and not increase. But when the UHK is subjected to electric noise or electromagnetic interference (EMI), it keeps increasing, potentially resulting in repeated keystrokes (also known as chatter), missing keystrokes, or phantom keystrokes.

If the I2cRecovery value keeps incrementing, start with the simplest setup you can create. Merge your UHK halves, connect your UHK directly to your computer, disconnect other USB devices, disconnect other power appliances from power sockets, and disable the backlighting in Agent. Then watch how the I2cRecovery value is affected as you split your UHK halves, add more USB devices, connect power appliances and generally restore your environment. Please also try the suggested points at the top of this page while watching the I2cRecovery value to find the cause of the issue.

If the I2cRecovery value keeps increasing, no matter what, then you can reduce the communication speed of the internal I2C bus of the UHK, making it more stable. The default value is 100000. You can half the communication speed by running the following smart macro commands, preferably in the $onInit macro:

set macroEngine.extendedCommands 1
set i2cBaudRate 500000

which should make communication more stable, but the smaller the value, the less responsive your UHK will get, which you will notice below a certain value.

Feel free to contact us with your findings!