Beta firmware (2HE AVR) produces random non-adjacent key actuations while typing

[mikey-dg]

Describe the bug
Starting immediately after applying the v2.10 beta firmware update, specific untouched keys are randomly registering presses when multiple other keys are pressed together or in rapid succession. I've never encountered any variation of this behavior in the previous two years I've had the keyboard, but I do recall seeing some bug reports of similar behavior in older firmware versions that were subsequently fixed.

On this particular keyboard, the keys being inappropriately registered are 'r' and '5', and this can happen at random during both rapid typing or 2-3 key modifier combinations on a completely different part of the keyboard. Either one or both of those two keys can be registered randomly, sometimes at the same time, sometimes several other keystrokes apart (e.g. 'Somethinrg like thi5s'). Both keys appear to have normal actuation sensitivity, and are no more prone to double presses nor to accidental actuation when bumped.

Despite the clear association of the issue with the firmware update, I did consider that I've suddenly begun accidentally bumping those two keys, and so I increased actuation distance from 1.5mm to 2.0mm, reined in my typing speed a bit, and have tried to maintain an awareness of whether or not I'm touching those keys when this happens - and I'm definitely not, because this behavior can occur with completely non-adjacent key combinations where my hands are nowhere near the part of the keyboard containing the offending keys.

For example, a particular key combination that I've had trigger this bug multiple times is End to jump to the end of the line rapidly followed by Ctrl+Left Arrow to backtrack a few words, and of course these keys are nowhere near 'r' or '5' and I typically retract my left hand back to the edge of the keyboard when holding Ctrl in this case, so the chance of an accidental press of either affected key is absolutely zero.

To Reproduce
Reproducibility is very poor. In a few weeks of using the new firmware, I've had random 'r's or '5's appear about once every 20-60 minutes of typing. I've never had it happen during gaming (at least in any game where those two keys are bound to something I'd recognize happening without my intervention), where I'm typically only rapidly pressing and holding keys on the left side of the keyboard, suggesting that pressing keys on both sides of the keyboard is required to trigger the issue.

I do most of my typing in the digital profile, with 1.5mm-2.0mm actuation depending on the keys, Rapid Trigger set to half of actuation, Tachyon and Focus Mode off with an AOE RGB effect, with no advanced keys on the main layer. Increasing all keys to 2.0mm actuation and deactivating RT and RGB had no effect on the frequency of occurrence. I sometimes play less reaction-sensitive games in the digital profile as well, and have never observed the spurious key presses, so I'm not sure it's affected by any settings.

I'll make an effort to reproduce it in an analog profile with Tachyon Mode on, just to confirm that's the case.

Keyboard
Wooting Two HE (AVR)
Firmware v2.10.1-beta.5

• Keyboard is plugged directly into a motherboard USB2.0 port with the stock cable (the same port it's been in for months)
• Switching to a USB3 port does not affect the issue

Desktop
Windows 11 24H2
AMD 7000 series CPU
Gigabyte X870 motherboard

• No significant or related hardware or software configuration changes in weeks prior or since the onset of the issue

[mat1jaczyyy]

@mikey-dg It would be really helpful if you could try capture the ghost input phenomenon happening on our Analog Monitor.

Assuming the phantom inputs are a result of incorrect sensor readings, there's a good chance you'll be able to immediately note something wonky with the sensor readings there if they can get egregious enough to cause unwanted actuations.

[mikey-dg]

I can try. So far, R and 5 keys are working as normal, if maybe slightly more sensitive than most others.

I'm noticing though that some of my keys don't register on the monitor until they reach at least 0.4-0.5mm, while some keys can easily be nudged to 0.1mm on the graph. There's definitely a wider range of key sensor calibrations than I'd prefer or expect.

Since all of the differences are within the 0.5mm threshold of my shortest-actuation profile, I can't be certain whether that's caused by the firmware update or if it was an existing issue. I guess I've noticed some initial reticence in some of the affected keys when assigned to analog axes, so it's probably been there the whole time.

I've been using analog profiles for typing for the past day, and so far I haven't had any spurious keypress events, so I'm beginning to suspect it's only the digital profile that's causing that issue.