storm matrix
Hello, I recently ordered a Wooting Two HE.
I installed the wootility app and updated the hardware.
The keyboard is preventing my PC from hibernating. I select hibernate, my PC turns off, and almost immediately it turns back on.
I am able to hibernate my PC after I unplug the keyboard, and the issue comes back whenever it’s connected. None of the keys are lighted up (signaling that they’ve been pressed).
I have rapid trigger on and jelly lighting effect.
torn current
hibernation shouldnt be able to wake from hibernating with mouse/keyboard as the motherboard power should be off completely
eager socket
hibernation shouldnt be able to wake from hibernating with mouse/keyboard as the...
Not necessarily... You can still wake the system depending how it's configured. On my old now dead system it was the same.
carmine mist
Yeah the BIOS can let you wake on keyboard and mouse if that's enabled AND USB power on power-off.
eager socket
Hello, I recently ordered a Wooting Two HE.
I installed the wootility app and ...
This is most likely caused by a too sensitive Rapid Trigger setting. Best to use less sensitive values.
When the device is put to sleep the RGB is off to comply with the power requirements while the key detection still works. The keyboard supports the wake on function.
On sensitive settings nearly everything can cause issues, like EMI or even a slight bump.
If you don't want to wake the system with the keyboard you need to disallow that in the power settings of the Wooting in the device manager for all its nodes. For that you should change the view to container to find which nodes belong to the Wooting.
@winged bane Can you disable Rapid Trigger when the device is on sleep to prevent that the keyboard may wakes up the system unintentional? And in the case someone uses a low actuation value (high point) to set that to a greater min value. Like if the user set it to just 0,1 mm to ignore that and use 1,2 mm instead and only use the configured value if that is greater.
winged bane
When the keyboard is idle it wouldn't really be anything to do with rapid trigger, more with the actuation point. Rapid trigger only comes into play when the key is pressed, if they're hibernating the machine without pressing any keys then if a key somehow gets triggered causing it to wake again, it would be an actuation point/signal issue not rapid trigger I think
@storm matrix What is your actuation point and does the behaviour remain the same if you have a basic profile selected that has tachyon mode off + ~2mm actuation?
Also, do you have tachyon mode enabled? As when the keyboard goes into sleep mode it disables tachyon mode, so it's possible that it gets triggered by the keyboard turning off tachyon mode and having a signal spike. If that is what happens, then I think the current alpha build could resolve it as I spent a decent bit of time ensuring that signals don't spike when changing tachyon mode setting