#Wooting 80HE spamming keys on Windows boot, only fixed by re-plugging
1 messages · Page 1 of 1 (latest)
Thanks for posting your support request!
Note: #community_support is only for answering general questions and for troubleshooting.
All order-specific and shipment-specific support must be handled via the Wooting Support Wizard*
(You need to create an account on the Wooting Hub, using the same email address as your purchase. The account is not created for you automatically!)
Troubleshooting your Wooting Keyboard? Try these steps first!
Basic Troubleshooting
Questions about shipping, or what to do if your shipment has a problem?
Possible Problems During Shipping (with Solutions)
Looking for information about your specific order?
You can find that on the Wooting Hub! There you can also add upgrades, update your shipping address, and much more.
Is your order about to ship and you need to pause it for any reason?
Place it on hold via the Wooting Hub!
Do you need to...
- Cancel an order?
- Return/Refund an order?
- Get assistance with placing an order?
- Change the items in your order?
- Change your shipping address to a different country?
- Return a recent purchase?
- Get warranty support?
All of these types of requests need to be made via the Wooting Support Wizard!
Are you using the stock cable? Tachyon mode enabled? What is your RGB brightness?
If it happens only during login, right after you start up your PC, it might be bad calibration as well - you press the key on your keyboard during the initial quick calibration phase
Stock cable, tachyon mode on, brightness at 70%
Granted it hasn't happened to me today so I can't really tell if something was touching the keyboard during startup but if it happens again we'll see 
That should be okay, also is your keyboard plugged at the back of your computer? (Into the motherboard)
yep
I am experiencing the same thing, it only stopped when I turned off tachyon mode
Can you make your own thread please? Thank you
So it happened again, this time it was spamming right shift :
Didn't go away until I pressed right shift. This time I'm sure I wasn't holding that key down on startup 🤷
Also worth mentioning that this only started when I updated the firmware to latest
same thing happening to me also
Best would be to make an official ticket if you haven't already. You can use the Wooting Support Wizard linked by the bot above
Same for you as well @wary tapir
could you attempt to use the "AOE" effect to see how the sensors are reacting on power up and record a video of this
The aoe effect will glow depending on how far the switch is pressed (similar to the https://analog-monitor.wootility.io/ tool)
To enable the RGB effect “AOE” you can use one of the Two Methods
Method one:
Importing the already created "(Test Profile) AOE " into wootility
- Select "My Profile"
- Press "Import Profile"
- (Copy/Paste) the Code for your device:
60HE/Two HE -91a99fc23c5ad0d1e9273265108f8ea47520
80HE -6e61f5876c064029b051d4476e72d1feefe6 - Press "Import"
- Select the newly imported Profile "(Test profile) AOE"
Method Two:
To manually create or enable the effect, you can do the following:
- Select the "RGB Effect" Tab
- Under "Effect layers", add or change the current effect to "AOE"
- Set the "Base Brightness to 0%"
Tried this and nothing lit up during boot. Unfortunately in the process I broke it more :(. I made it break every time I would switch back to a tachyon mode profile. Gonna upload a video in a second
From the looks of it its two random keys that start getting held down every time I switch to a tachyon mode profile
For the profile you switch to can you provid the profile code
- wish to check if tachyon is enable/disabled
54bb8a654fe2e2fcb75fc1381ce136d50861
Thankls
The keyboard default profile (that loads on start up)
is that The profile code you provided?
also could you set the AOE profile as "Default" profile and restart the system
wish to check if this relates to having tachyon mode enabled on start up
I set the aoe profile to default when I was testing
Thanks hmm
Same question here, seems it does not depend on switch itself:
also today it is "2", yesterday I've seen L-CTRL doing same thing
And this is what I see after reconnect / power cycle and this noise is fixed with pressing "2" one time:
@radiant junco best to make a new post
also to check is this issue for you limited to start up or this happens all the time?
I would say it is kind of random, but definitely happens with tachyon mode. And usually fixed with reconnecting keyboard couple of times.
another reconnect, I can see noise without tachyon mode:
But no noise in tachyon mode.
Because this problem is so inconsistent, I don't personally think it's a hardware problem, but probably firmware issue?
Incase this relates to a profile issue can you remake the profile from scratch and mimic the current settings
Best to make a new #1019755933959733258 post otherwise this can get confusing when mutiple people are troubleshooting on the same same page
new profile, didn't even copy the settings to see the same issue 
on newest firmware btw
We have a test build for this issue.
Can you give this a try and see if this resolves the problem?
- Use this link https://beta.wootility.io/?test-builds=true (this URL has Test builds enabled)
- Click on "Settings"
- Select "Updates"
- Select "Your keyboard"
- Press "Get Test Firmware"
- Press "Select Test Build"
7. Select "v.2.12.5+pcboot.0" - Select ""V2.11.0+rollback"
sorry been busy ill lyk when i get to it. though strangely my keyboard hasnt had the issue again in the past week or so. will try to replicate it later today
No rush on this and if anything thanks taking the time to try the test build
if you do have issue you can also rollback the firmware "V2.11.0+rollback" as well
having this very same issue here
Could you try the test firmware linked by Andrew above?
An update from those that have tested this test build seems to not help
for now i recommend to rollback the firmware to 2.11. while we work on a new test build
(note this may be tied to tachyon mode if enabled on default profile so may also help disabling this for default profile)
i have this installed and still have been presenting the same issue
i feel like it is now worse
it even gets me to my bios menu when booting up, i am currently having to fully unplug the cable in onder for it to have a chance to boot normally
Have you tried rolling back to firmware v2.11? Use the guide by Andrew above
- Use this link https://wootility.io/?test-builds=true (this URL has Test builds enabled)
- Click on "Settings"
- Select "Updates"
- Select "Your keyboard"
- Press "Get Test Firmware"
- Press "Select Test Build"
7. Select "v.2.12.5+pcboot.0" - Select ""V2.11.0+rollback"
revised the guide as the test build has issues
Ill try that, for how long to keep it on the look out
I have been trying it as for today and issue seems to persist
As for today issue still continues
i think i installed the wrong one i was double checking and that one is not in the list
had to double check since the issue is persistent still
looks like the "rollback" is only on stable
https://wootility.io/?test-builds=true
can you try this link instead and look for the rollback firmware
adding my message that i placed in chat recently:
Can anyone tell me if just recently a new bug is according that your number 1 key will literally spam the button a shitload when your keyboard turns on with your PC? I dont think this is water related because I can just unplug it replug it in and it stops. It does even stop without unplugging it but it take like a min or two. I noticed this started happening after updating my 80he from a super old firmware to the latest.
Wooting 80HE
Layout: ANSI
Firmware: v2.12.5
Serial number: *
Chip: ARM
State: Connected
I just did a keyboard reset. Will see if that will work. No idea. It only seems to happen when I am starting up my computer for the first time of the day.
edit: I see there is a test build, I rather not test anything just let me know when its fixed lol. Just letting ya'll know its happening to me as well.
for now to get this resolved for now i recommend rolling back the firmware to an older one by the guide above as this issue is limited to the latest firmware's
(working on a fix)
still having this issue so far
issue persist
best to send a ticket as you likely have a different issue