Troubleshooting guidance with UHK80

General
1

Hi team,

Please let me know which steps I have to follow to gather some logs for some issues I’ve been having, and where to report them (gh or here)?

I was planning of following the steps on Windows 11 doesn't receive input occasionally · Issue #1572 · UltimateHackingKeyboard/firmware · GitHub , but let me know if there is a preferred method.

Setup: Split, key cluster on left half, touchpad on right half. This KC is new, the touchpad is the same one I was using on my old uhk60v2

KB FW: 17.0.0
Dongle FW: 17.0.0
Key cluster: 16.3.0 (can’t seem to update it?)

Using the dongle I’m experiencing this:

Random KB freezes, sometimes a few times per hour, sometimes longer. Sometimes no message at all, other times it displays different messages:

”usb remote wakeup request failed: -128”

”Messenger message pool space ran out!”

But most of the time it just freezes. In of the hard crashes I did manage to get some logs form the Advanced Settings > Zephyr logging section:

```• 2026-06-23 10:19:16 | UHK Dongle | bt_att: ATT channel not connected
bt_att: ATT channel not connected
NusClient: Client failed to send data over BLE connection (err -12)

• 2026-06-23 10:19:19 | UHK Dongle | bt_att: ATT channel not connected
bt_att: ATT channel not connected
NusClient: Client failed to send data over BLE connection (err -12)

• 2026-06-23 10:19:28 | UHK Dongle | bt_att: ATT channel not connected
bt_att: ATT channel not connected
NusClient: Client failed to send data over BLE connection (err -12)

• 2026-06-23 10:19:31 | UHK Dongle | bt_att: ATT channel not connected
bt_att: ATT channel not connected
NusClient: Client failed to send data over BLE connection (err -12)```

And the other issue is that the right half is discharging fast, and charging extremely slow to point it feels like a defect or something else is going on: last night it only charged about 10% despite leaving it connected to a charger for about 8h.

Unfortunately these are all making the device pretty much unusable, especially when it crashes more than once an hour. the only way to recover it is by pressing the reset button in the right half. Any guidance is appreciated. This is a new UHK80, received it maybe 2 or 3 weeks ago.

2

I think your battery and freezing issues should be resolved by upgrading the firmware of both the UHK80 and dongle to at least v17.1.3 (I’ve been on Pre-release v17.2.0 since yesterday, and it seems stable as well). UHK80 has yet to implement the ability to upgrade module FW yet, but probably not necessary anyway, since the modules haven’t had any updates in a very long time.

:smiling_face_with_sunglasses:

2 Likes
3

Got it, just did, we’ll see how it goes!!

4

Hi there!

Please grab Agent 10.1.0 from Release 10.1.0 · UltimateHackingKeyboard/agent · GitHub and flash its bundled firmware - 17.2.0.

If there still are issues:

  • in Agent, enable Advanced Settings:
    • Go to About page.
    • Click the Agent icon 7 times.
    • Optionally, go to Settings and check ‘Always enable advanced settings’.
    • Scroll the left pane up; click Advanced Settings.
  • in Advanced settings, enable logging for Right half.
  • monitor the log and share your findings

In case of bluetooth issues these commands may be useful:

  • uhk connections in the zephyr shell (the logging thing in Advanced settings)
  • set bluetooth.minAdvertisingDelay 2000 in a macro named $onInit, in case you are unable to use the shell due to too fast reconnection loops.

And the other issue is that the right half is discharging fast, and charging extremely slow to point it feels like a defect or something else is going on: last night it only charged about 10% despite leaving it connected to a charger for about 8h.

Is your backlight on? If so, most of the 500mA usb limit may be getting consumed by the backlight.

5

Hey @kareltucek. I actually go a crash last night with the pre-release fw, didn’t test for long enough though. I’ve just updated the agent to 10.1.0 and updated the fw to 17.2.0, will monitor during the day and let you know.

1 Like
6

24h in and 17.2.0 looks like a success!! Only remaining issue is the left half still has trouble charging past 50% or so, but the drain doesn’t seem as bad. I’ve disabled the “extend battery life” option for now, and reduced the LED brightness to 20 on battery. Will test charging later today, and will also test charging in sleep mode to see if it makes any difference.

Thanks!!!

2 Likes
7

Only left half? Are you charging it directly via a usb cable, or indirectly via the bridge cable?

8

Yeah only the left half, but it does look as if the update + a reset did the trick on it. Lowering the LED brightness is probably also doing a lot of work. Anyways 17.2.0 seems to fix all of my issues, no crashes in almost 2 days now, looking great!

Thanks!

1 Like
9

Happy to hear that! :blush:

10

I don’t remember all the details, but there were some discussions about this a long time ago. Basically I think this is normal when using Agent’s “Extend battery life: limit maximum battery charge level” option, or the equivalent macro set battery.chargeLimit optimizeHealth. IIrc, the UHK80 tries to balance the charging limit for each battery to somewhere around ~3800mV (optimum long-term storage levels). Since the left half’s battery is much smaller than the right, their values will be a little different.

You can see the percentage/voltage correlations when monitoring logs in Agent. My UHK80’s OLED stays around L=55-60% and R=80-83% when I enable the charging cap.

Here’s a recent reading of my UHK80’s battery levels:
StateSync: Batteries: 60% 83% (3856 / 4066 mV; 3807 / 4000 mV)

So, left battery says ~3856mV at 60%, and ~4066mV max.
And right battery says ~3807mV at 83%, and ~4000mV full.

The percentages may look a little off at times and they’ll fluctuate a bit, but the actual voltage is what’s important.

And this is what my values look like after fully charging for the first time in months:
StateSync: Batteries: 100% 100% (4142 / 4138 mV; 4166 / 4160 mV)

2 Likes
11

Yeah that makes sense. I disabled the option and charged both to 100%. Will monitor it and then re-enable the option at some point. Thanks for the help everyone!!

1 Like