Power problem and Force KDB Boot Protocol option

[philippwallrafen]

Thanks a ton for this great device and software! :)

I have a few problems with my keyboard. (Wooting 60HE)
I think it might draw too much power, which forces me into "Force KDB Boot Protocol"-mode, which then introduces a couple of different bugs.
Also I can't access it's configuration web page. (https://wootility.io)

About the power:
Keystrokes are repeated, which got worse when I increased the brightness of the backlit keys.
However this keeps happening and makes typing unusable when I turn off the LEDs completely.
This also happened with a KVM switch I used previously of amazon (https://www.amazon.de/dp/B0CHY8L11W), until I attached a additional USB cable for power supply. I'm thinking about how I could achieve this for this project? Maybe with a USB splitter on either the input or output side?

About the "Force KDB Boot Protocol"-option:
Most of my FN keys completely stopped working (media keys, controlling volume and opening my calc).
Some others are extremely delayed and I have to spam them for the PC to pick up. (e.g. FN+P bound to F13)

Whatever the mode, I can't configure the keyboard on the config page for it, which makes it hard to test a few other features which I suspect might also stopped working. (Rapid trigger)

Kind of related to the power problem is, when I turn off my work pc, the USB-A hub on his side loses it's power and I can't use my mouse anymore. Just attaching a usb cable as a power cable from my monitor added a sporadic wild spinning of the mouse. So atm I just keep my work pc on all the time. :D

Would greatly appreciate your help!

[hrvach]

Ok, so - being unable to access the keyboard config page is by design. For security reasons, only information from the computer to the keyboard is allowed and no proxying to the keyboard is done. This is a bit inconvenient, but provides a much safer environment when connecting different systems/computers together (please check readme for a more detailed explanation).

In boot kdb mode, this is expected - only basic keyboard functionality works in that one. For the power issues, a larger capacitor would likely help, but the standard limits the amount of capacity you are supposed to put in there, so it's a compromise. Perhaps try an old powered usb 1.1/2.0 hub, but don't invest a lot of money in it because hub support is a bit flaky. My hub works for example, but a lot of folks complained theirs don't.

I'm fairly certain you picked this very keyboard because you really love it, so I'm not going to suggest you use another keyboard - everyone is attached to their own gear :) I'd advise to first try getting a shorter/different cables and see if that results in any improvement.