Hi,
I work for Wooting and would like to get in touch with someone from Level1Tech. Our partnership manager Max already tried to get in touch with Wendell but without any successes so far to my knowledge.
We are interested in getting our keyboards to work, if possible, with the Level1Tech products.
Gratings, Markus…
Epic 
Thanks @wendell & @WootingKB.Markus , lmk how I can help / guinea pig.
Both of you team’s products are amazing.
My python scripts and read outs are in: h ttps://github.com/WootingKb/wootility-issues/issues/293#issuecomment-2372608529
I’m also willing to do any testing with a wooting one and the newest 4 port KM. Let me know how I can help.
tbh it shouldn’t be that bad, especially since qmk works. A hid 1.1 compliant endpoint should be all thats needed here. There are mysterious problems with bit-banged usb implementations i.e. there is some atmel based solution out there that doesnt actually use a usb phy. I gave up on ever fixing that because of the timing/clock drift. I hope this is not some kind of bit-banged usb under the hood.
I wrote an e-mail…
And no, we rely on a PHY and not bit banging. 
So I have now a Wooting 80HE and it only works if I disable NKRO for the keyboard. And the wooting keyboard siwtches from uses the “old style 6 key max” enpoint to using ONLY the new NKRO rollover keyboard endpoint
My previous Steelseries Apex instead did trickery achieve the NKEY rollover but haivng both endpoints, sending the first 6 key strokes on the “old” endpoint and only using the new endpoint for any keystroke over 6. My feeling is that the KVM switch just is not able to the parse the messages from the new endpoint.
I confirmed this behaviour by looking at usbhid-dump -e all
Interesting! Thank you for sharing your data point!
WRT To disabling NKRO, you’re are you just doing that in wootility > settings > NKRO disable?
I’ve tried that for my 60HE and didn’t get any luck.
Or is there another approach you’d recommend to disable NKRO?
Do you have a W60HE with an AVR MCU? We had reports that these may don’t work.
@WootingKB.Markus how could I confirm if I have or don’t have an AVR MCU?
I’m not sure what that is.
The best way would be if you can name me the USB product ID of the device, for example 0x1301.
The models with the ARM chips should also have ARM in their name in the device manager (if the view is changed to container). AVR should not contain the chip name in there.
Looks like mine is
Device Name: Wooting 60HE (ARM)
Vendor ID: 0x31e3, Product ID: 0x1312
Yeah, this is the ARM model. Please update via the Wootility V5 (v5. wootility. io) to get the latest alpha firmware. This has some keyboard interface changes. Then it should work when NKRO is disabled. For now I can’t say what the issue is with the current stable firmware.
I’ll give it another try.
I believe I did this last week and it did not work.
Appreciate the help!
Another interesting/weird datapoint. With my 80HE in 6KRO everyting* works fine apart from the CAPS lock indicator. If I connect another keyboard to the kvm HID ports it works. When I connect another keyboard and the Wooting in parallel I can toggle caps lock led of the non-Wooting keyboard (a cheap DELL keyboard) with both the Wooting and the other keyboard. The wooting CAPS lock is always off. If I connect directly, caps lock indicator light works as expected.