I’m using a Wooting One on v2.10.1-beta.4+kvm.2 (Desktop Wootility App) with the lvl1 KM (HID port).
The following seems to work fine:
NKRO (up to 14 keys, but I can’t fathom a scenario where you would need more than that)
Tachyon mode and rapid trigger
Making keyboard setting changes while connected to HID ports.
Using Ctrl + KVM keyboard shortcuts through HID ports to change selected PC
Things I haven’t tested
Gamepad mode (I just never use it)
Updating keyboard firmware over HID ports. (It seems too risky even if it worked so I stick to using usb 3.0 ports for this)
The Keyboard seems to disconnect from wootility frequently when in HID ports but I can’t figure out the cause. (this isn’t a huge deal as I can use a usb 3 port to configure it then switch it back for normal use)
Is there anything else I could test for you? Should we expect the KVM version of firmware to be merged with the main branch, or will have have to stay a separate beta firmware?
I want to give a HUGE thank you to @WootingKB.Markus and @wendell as well as everyone on your respective teams for working on this. You both have amazing products and support and I’ll continue to keep purchasing and recommending your products.
How long does it take until you can’t use the Wootility anymore?
There are some hard limitations when a HID port is used on the K(V)Ms. In order to make the Wootility somewhat compatible it needs some changes how the device functions are structured. Modern gaming keyboards are more complex than the classic ones and KVMs are typically not designed for these.
If the emulated controller is used the Wooting uses an additional endpoint which exceeds the number the KVM can handle on the HID ports. We may merge the changes to the official branch but there is no time estimate for this. In the case these test builds aren’t available anymore there is a good chance that it got merged.
@WootingKB.Markus Hi! Sorry I didn’t get a notification here, but I have seen it disconnect after 5 minutes and after 15, so it does not seem consistent. I’ve been doing the same and moving to a usb3 port if I need to use the configuration app.
Replugging into the hid port makes it work for a while again, as well.
@blackal As mentioned there are still problems, especially for all current models which use an ARM chip. Only the older models with an AVR chip like the W1, W2, W2 HE (ARV) & W60HE (AVR) may can be configured just fine.
@WootingKB.Markus Hi! Just wanted to check for an update here! I see that we have new firmware for devices, and that v5.wootility.io doesn’t let you stay on that site, it redirects to wootility.io which apparently doesn’t allow the test builds. It looks lioke neither does beta.wootility.io if you go there.
I just got an 80HE and I would love to flash it with the downgraded firmware that supports the HID port, even if its limited at the moment. Is there a URL that I can go to that will allow me to do so still?
@blackal To use the dev build a specific flag needs to be enabled. Because Wootility v5 is released now its sub domain got removed. Due to the redirect the flag isn’t carried over.
I’ve noticed now that I’m unable to make changes to keyboard settings now in Wootility v5 (both the website and the desktop client). using v2.10.1-beta.4+kvm.2
I’ve connected directly into my pc avoiding the KVM and restarted windows. Every time I attempt save any change in wootility, I receive the error that the keyboard has lost connection and my keyboard becomes unresponsive until I disconnect the cable and reconnect it.
