#Keyboard keeps disconnecting

1 messages · Page 1 of 1 (latest)

spare coral
#

Got my keyboard in November. Have been experiencing this for the past 3 weeks.

Using stock cable, directly connected to motherboard 3.0 port. Changed ports and still happening. Keyboard disconnects and remains unresponsive.

First time it happened, replugging in and out the cable on the keyboard worked. Happened a few more times until keyboard remains unresponsive after replugging in. So I opened up the keyboard to re-seat the JST module. Keyboard came back online, but issue persisted.

I have tried updating to latest firmware, uninstalling on devicemanagement & deleting regedit. Issue still persists.

This is happening even more often now. Keyboard just disconnects out of nowhere, sometimes while I'm playing game, though most times its after my computer sleeps (it does not reconnect back). Have unchecked the textbox that says "allow computer to turn off this device".

Please help. Can i get a replacement?

queen doveBOT
# spare coral Got my keyboard in November. Have been experiencing this for the past 3 weeks. ...

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...

All of these types of requests need to be made via the Wooting Support Wizard!

spare coral
#

Was hoping to capture the part where replugging in cable gets the keyboard back on but this time i needed to reseat the JST cable (not even sure if this is the problem but doing this has been able to turn my keyboard back on)

spare coral
#

Help? Is there anything I can do on my end to fix / diagnose where exactly is the problem?

tepid grotto
#

Please keep in mind that Discord is not customer support. You may be able to get assistance from a fellow Discord user here, but for warranty support with Wooting, you will have to use the links provided by the bot above. 🙂

dreamy garden
oblique nacelle
#

never had a fix, just dealt with the issue for a year. turning off rgb sleep also seemed to make it happen much less often

#

ping me here in a few days if updating to v5 and/or turning off rgb sleep works, im curious if the problem/solution are universal

#

my theory as to why it was happening in case ur curious: i think an instance of the wootility backend somewhere crashed, specifically the part reading the raw data from the usb host controller and giving it to the rest of wootility to handle. since it's accessing something hardware level, i think something in windows prevents access/causes a crash unless the instance was initiated during startup, which would explain why it only works again after restart. it would also possibly explain why v5 fixed it, since it seems they essentially did a complete rewrite of how it all works.

this is mostly speculation, i had a log i posted when this first happened to me that included something along the lines of "wootility-xxx process could not start, retrying" multiple times (dont remember it exactly, its been over a year), that and the behavior is all i have to go off of

spare coral
#

right now this is what im on

i believe i updated to use latest wootility + latest firmware at the same time around last week. before that, i barely used wootility after i was done with the initial setup

spare coral
#

i'll try the RGB sleep off option. thanks for the suggestion!

dreamy garden
#

also it is recommended to disable fast boot option in windows power options, its known to cause problems

oblique nacelle
#

not sure how it works in v5 yet but at least in v4, even if you werent actively using an analog function, if you wanted the ability to switch to a profile that did make use of it you needed the controller emulation function to be turned on. that function obviously comes with continuously running software of some kind to take the raw data from the keyboard for analog input detection, so if that software breaks and can't restart without a pc restart for some reason, it would explain everything. i also bet that means the problem would be solved if you turned it off comletely and just used it as a regular keyboard but at that point... why have a wooting?

spare coral