have to toggle the lock off then on to get it to light up. also artemis rgb breaks with this keyboard after wake and only thing that solves it is unplugging and replugging keyboard. this happened seemingly for no reason; updating firmware did not help; artemis discord could not help me. any idea what could be going on here and/or how to fix it?
#lock indicators don't light up after waking from sleep
runic ether
mild solarBOT
Thanks for posting your support request!
Please note, the support center is only for community-based support with technical troubleshooting and general questions.
For official Wooting Customer Support, please use the Contact Us button on the Wooting Hub or email your request to social@wooting.io
note: use the email address associated with your order for fastest resolution
Looking for information about your specific order?
You can find that on the Wooting Hub! There you can also add upgrades, change/confirm 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!
https://hub.wooting.io/login
runic ether
we will see if a different usb port causes the issue, then maybe reset/restore board if not
drifting haven
few questions
- are you talking about the
LED indicator to tell if it is on/off for the following keys
Caps lock , Scroll lock , Num lock
if you are
Running "Artemis RGB" that will override any RGB/Led effects handled by the keyboard
- are you running wootility And "Artemis RGB" at the same time as it can cause the keyboard to crash or become unresponsive if both are running and would need to unplug/replug keyboard or restart pc
a fix for this would be to shutdown "Artemis RGB" while "Wootility" is running
(i may take awhile to respond 6am i should be asleep)
runic ether
- Yes
- No. I never run them simultaneously, but the behavior in the title is with neither running
drifting haven
regarding the lock state indicator
if you lunch windows "on screen keyboard" and press the caps,scrolll,num lock
dose it change the state on the on screen keyboard even though it doesn't change it on the keyboard light indicator ?
runic ether
so i switched usb ports and now it half works waking from sleep (some indicators are wrong and the animation is very choppy but it's something)
should i factory reset my board?
also yeah state changes but not reflected in lighting in this most recent conundrum
drifting haven
can't hurt to do a factory reset if that helps
(make sure to back up your profiles as it will wipe them)
Video Guide
https://youtu.be/f9f8PAI3XJI?t=41
if that doesn't help i am unsure on how to proceed further i can ping some one that has a better understanding and might be able to help
runic ether
who should i ping in that case?
drifting haven
it would be rocky but
best to try the Reset guide first
--
just to confirm what lock keys are not in tune with what it says in windows is it just one or more
- Capslock
- numlock
- Scroll lock
?
rereading the posts there is something i missed that we can try
can you do the following and Go to
Wootility
Colour Tab
brightness
lower the brightness to half
save to keyboard
Test if keyboard function as it is indented
this is to test if there may be a lack of power going to the keyboard causing problems by lowering the power
drifting haven
@marsh dragon sorry mate i would normally ping when i had more info but 6:00 am and i included some info below and looking in "Suppor_center" history can't find similar reports
Model: Wooting Two HE
**Timeline: **Unsure if this just started to happen or new keyboard
Problem:
- the Current state of (caps ,scroll ,Num) is not reflected by the Keyboard RGB Colour
- Wooting RGB effect are "choppy"
**attempted: **
Firmware update
unplug/plugging it back in
switch USB port (shown some results)
Requested:
to attempt a Factory Reset
(results unknown)
to test lowering LED brightness to (half) to test if lack of power is cause for issue
(results or attempted unknown)
marsh dragon
@runic ether I'm aware that the Wootings can't handle it well on some systems when the host sends to much device request.
Do you may also use the L-Conenct 3 software from Lian Li? This is known to cause issues. While I know what's this causing on USB I don't know yet what the root cause within the device is.
About the lock indication issue after sleep, the Wooting should internally still save the last lock state when sleeping and so have that shown when resuming from sleep. Are you sure the device still get power? I'm not 100% sure if the host sends the lock state by its own to the device after waking that up.
runic ether
--
just to confirm what lock keys are not in tune with what it says in windows i...
all
runic ether
<@254081295158607873> I'm aware that the Wootings can't handle it well on some s...
do not use that software
runic ether
<@254081295158607873> I'm aware that the Wootings can't handle it well on some s...
should i undo "allow to turn off to save power" in device manager?
marsh dragon
should i undo "allow to turn off to save power" in device manager?
You can try...
runic ether
i will
i turned down brightness (was already turned down some) and disabled animation in wootility
hopefully reduces device requests
marsh dragon
So when the caps lock is set and the rebort gets re-plugged. The keyboard will start with the default lock state and then change to the correct one after the host automatically sends the state to the keybaord.
So I assuming this isn't the case when the keyboard was on sleep, while I'm not sure.
runic ether
i use hybrid sleep state. dunno if that has anything to do with this issue
marsh dragon
I confused, are you using Artemis RGB to control the RGB of the Wooting or not?
marsh dragon
In that case you should indeed disable all internal RGB effects otherwise these will fight with Artemis over the control.
runic ether
didn't have an issue before but i will try that in addition to turn off power management
marsh dragon
If there is an issue only depens when the keyboard will update the LED compared to when Artemis also sends a package to change the RGB.
Either way it's not good if two different and independent programs want to change the same thing.
runic ether
how do i turn off lock lights
marsh dragon
Would be nice if you can cross check the lock state issue on another PC.
runic ether
issue only present with artemis control
other usb port does not have lock state issue
marsh dragon
how do i turn off lock lights
You basically can't. The only thing you can do is set the same color to both state in the Wootility so that the shown color don't changes.
runic ether
ok so hopefully that's not what's messing me up
marsh dragon
Oh, the host sends the lock state via a special package to the keyboard and the Wooting will react to that.
runic ether
ok
marsh dragon
In the case Artemis takes over the lock state the Wooting will react to both.
runic ether
that's not good. any way to prevent conflict?
marsh dragon
I'm surprised that Artemis does this. The lock state is typically a dedicated LED on the most keyboards and so has nothing to do with the RRB color for the caps lock.
runic ether
if i do not put a conditional layer in artemis the key does not light up
marsh dragon
It should be fine if that can be turned off in Artemis but I'm not falimiar with that app.
runic ether
it can, but then no indicator
marsh dragon
The indicator of the Wooting should still work.
runic ether
it does not it is overridden by my rgb in artemis
marsh dragon
Oh, yeah...
runic ether
apparently i am the only user of the software who has ever had this issue
marsh dragon
So I assume Artemis will always send the RGB colors to the device even if there is no change. So the Wootility will react to the lock state by its own but then there is an update from Artemis and that gets overwritten.
runic ether
i suppose that's where the conflict lies
marsh dragon
Meaning yes, you would need to let Artemis take the control of the lock state. But in the case there are issue with that it would be better addressed by the Artemis support. So not sure why they weren't able to help you.
So the problem is likely that Artemis can't communicate to the Wooting anymore after that was woke up from sleep.
runic ether
they just said "that has never happened before"
runic ether
So the problem is likely that Artemis can't communicate to the Wooting anymore a...
agree
marsh dragon
But after a re-plugging Artemis should update the correct color because that controls it.
So I would think it's a bug within Artemis if that then don't send the lock state color to the Wooting.
runic ether
might try disabling those before the computer sleeps; see if that is indeed the issue
drifting haven
Reading the post I believe I miss read the situation I assumed it was a hardware issue
Did not consider software
runic ether
maybe both
marsh dragon
The confection issue, especially after resuming from sleep, is likely a firmware related problem.
marsh dragon
I'm currently investigating different USB related issues and found some. So it would be really nice if you can try to reproduce the issue on another system.
In the case that can be reproduced and so is system independet I would check that out later when I have some time.
marsh dragon
Right now, it would distract me to much if I want to try to set it up and test it.
marsh dragon
In the case you can reproduce it I would need to know how to set it up. I don't really want to learn how to use that app.
runic ether
i can give screenshots
marsh dragon
I get annoyed by it every time and only want to uninstall it as fas as possible 😄
runic ether
also of note: i have analog sdk installed on my system (uninstalling it did not fix the issue)
marsh dragon
The RGB SDK is split from the analog SDK. Artemis should come with RGB SDK. So without tinkering in their files you can't remove it.
drifting haven
I can also try to replicate it I use Artemis for room / keyboard
Lighting
Can wipe up some profiles that mimic the effects he is using it for
marsh dragon
Looks like he is a she. 😄
drifting haven
Oh sorry
marsh dragon
So you can't replicate the issue on the other machine?
runic ether
not had the opportunity to test yet; probably not until tonight
marsh dragon
Feel free to tag me when you have new data about the issue.
runic ether
i will thank you
drifting haven
test method / results
model: Wooting two he (ARM)
system os: Windows 11 pro
Artemins Profile: effect background constant changing + static LED indicator for caps/num
test one. only artemis running
- lunch artemis rgb
- press capslock / numlock statis to show indicator
- click windows sleep
- keyboard Leds turn off - (room) leds turn static (no movement)
- move mouse _ comes out of sleep
- keyboard no longer respond
- artemis no longer static and animations begin to start up
- keyboard state in notes
(note)
behavior is not consistent of the 6 times
attempt 1-6 became **unresponsive **
attempt 2-3-4-5 attempts works as intended
Unresponsive as in
keyboard unresponsive key press
LED state is static and not changing
and only fix was to unplug replug
autumn crescent
I haven't read everything about artemis in this chat but what i did read was wrong. if you need information about it feel free to tag me.
drifting haven
test two: (no software running except on screen keyboard)
- press capslock / numlock statis to show indicator
- click windows sleep
3.keyboard Leds turn off
4.move mouse comes out of sleep - keyboard still maintains Caps,numluck Current state by led state
- End state result in notes
(notes)
behavior is not consistent of the 5 times
attempt 1 became unresponsive
attempt 2-3-4-5 worked as intended
unresponsiveas in
keyboard did not respond to key presses
Numlock/capslock **did **change state from Windows on screen keyboard
unplug / replug fixed it
marsh dragon
@drifting haven What happens when Artemis is used, the caps lock is locked and the Wooting is then (re-)plugged in?
In the case that there is then an issue I would expect it to be Artemis. Either way, if Artemis can't communicate with the Wooting when this resumed after sleep it would be likely due to a firmware related problem.
marsh dragon
I haven't read everything about artemis in this chat but what i did read was wro...
Can you please be more precise.
autumn crescent
So I assume Artemis will always send the RGB colors to the device even if there ...
this for example is false. the colors are only sent if artemis computes a difference. When the internal artemis state is unchanged, no update is sent.
marsh dragon
Ok, good to know.
autumn crescent
So the problem is likely that Artemis can't communicate to the Wooting anymore a...
this is also not true, i use artemis with both a wooting 60he and a Two HE, i sleep my computer everyday, and it works correctly
the lock color state not being sent is not up to us. the firmware on the keyboard does not update the lock color when it is in SDK-control mode.
You can replicate this behavioud within artemis, but it's optional. The user might not want this, especially on other keyboards that have dedicated LEDs
drifting haven
OK when artemis is running
1.unplug keyboard
2.plug it back in
3. for the sec when the keyboard is starting up it will flash back and forth around 4-5 times
between the Blue/pink
(note)
Pink is the state of capslock "on" in artemis
marsh dragon
this is also not true, i use artemis with both a wooting 60he and a Two HE, i sl...
For you this seems to be not true. I'm aware that the Wooting can't handle some edge cases very well that depends on the specific USB setup and system. Like for me the Wooting is sometimes still lit even the host is off.
I'm also aware that under some rare cases the Wooting can have problems to wake from sleep (like lit but slow respond). So it can be that this is the case for the user.
autumn crescent
right, some weird behaviour is not unheard of. but do you suggest we try to fix this on the artemis side? I don't think this is a bug with our program
marsh dragon
right, some weird behaviour is not unheard of. but do you suggest we try to fix ...
The Wooting firmware bugs should be addressed by Wooting. I'm not really a fan of adding some workarounds in the code just to handle issues from a third party. This would likely add issues when the bug is fixed.
As mentioned I'm currently investigating into multiple USB issues and found the cause of some of them. So I'm in touch with the Wooting devs about them. Some are more complex and sadly they are very busy due to the new upcoming product launch, so it will likely take a while until these get into a (stable) firmware.
@runic ether I assume the Wooting isn't directly connected to the host. Possible that a used USB hub may causing the issue for you. So please connect the Wooting directly into a USB port of the I/O panel on the back of the PC.
runic ether
It is connected to the io panel directly
Should I try a usb 3.0 port instead of a 2.0 port?
marsh dragon
This is recommended when you are using a high brightness settings because USB 3.X handle handle power better but this should not change the outcome of your issue.
runic ether
My brightness is 51%
marsh dragon
Yeah, that's fine. Starting at 70% it's better to use USB 3.X.
runic ether
So this is a wooting-side issue Artemis?
marsh dragon
If you have issue when the Wooting is resumed from sleep it's likely a Wooting firmware issue.
A video of how it behaves would be nice. That likely helps to identify the problem.
I need to know what is going on in order to think through the possible issue which can cause this. So to have points I can check for to find the issue.
Possible that I'm already aware of the cause which is making the trouble for you.
runic ether
Ok I will be home from work around 5 pm gmt-5
I will take video and if the issue presents itself I will send
This is somewhat unfortunate as this is like the only keyboard that works with this software without a manufacturer utility running alongside it
autumn crescent
Could this be a bios setting?
runic ether
Not sure which bios setting would cause this
This started happening despite me not even touching this before it broke
runic ether
Pls excuse the mess
hope this helps
after restoring i no longer have a power management tab in device manager
runic ether
@marsh dragon
runic ether
Any ideas?
marsh dragon
hope this helps
Sadly not, not sure what I should see there. I can't spot an issue.
Would be nice if you can explain what you expect and how it differs.
runic ether
I expect a scrolling right animation for the rainbow
marsh dragon
But this isn't shown on the screen either.
runic ether
Timeline is unresponsive for a while after waking
Eventually it shows the animation but it's not reflected by the keyboard
Hope that gives context
marsh dragon
The complete timeline would be interesting. Like to see that it's working before putting it to sleep, then to put it to sleep and showing that it don't work and then to re-plug the device to show that it starts to work again.
runic ether
What would seeing it do?
marsh dragon
You mentioned you are using an effect. So the Wooting should show the effect. So I would like to see that the Wooting does this.
runic ether
You mean you want to see when it works as expected?
marsh dragon
Sort off, I need to compare the non-working and the working state. I need to know how it differes.
Best to use an animation which changes fast. On the video I can't see that there is even a changing aninimation.
To me it looks like solid colors which the Wooting correctly shows.
runic ether
You wish to see when there is a discrepancy between the software and the keyboard?
marsh dragon
Again, I'm not familiar with this software so I don't know how that works or that the settings are. So on the video it looks fine to me and I can't really see an issue.
runic ether
Ok
I will show discrepancy
Know that timeline is not responding after wake for a while (click play and it does not resume, shown in video)
marsh dragon
I can only see that the Wooting was black, likely because it was sleeping. Then you pressed a key while the Wooting likely showed its own color which is quickly changed by Artemis. So to me everything seems to be fine as expected.
runic ether
I set all wooting lights to black for this
marsh dragon
Know that timeline is not responding after wake for a while (click play and it d...
I'm not familiar with that tool so I don't know what this means.
marsh dragon
What's why it would be good to show that it's not working and then to re-plug the Wooting. I expect after a re-plug it would work as expected and so I can see the difference.
runic ether
I will show you discrepancy state and working state
marsh dragon
Would be really nice if you can also mention what you are doing in the video.
So I know where to look at.
runic ether
When you see in the video of me with my cursor on the play button in the video, I am trying to resume the animation
It does not respond to my input
marsh dragon
For me you were just hovering over the area there. I can't see when you are clicking. 🙂 I also don't heard a click.
runic ether
I removed sound to make file size smaller and people were talking
I was clicking, unless you think I'm lying about that
marsh dragon
I was clicking, unless you think I'm lying about that
You mistaken me... I wasn't aware of it. How should I?
runic ether
I just told you. I'm trying to explain.
marsh dragon
But I didn't know that before.
runic ether
Now you do. Does it provide any insight?
marsh dragon
I don't that know that Artemis only starts an starting when the start button is clicked on. I would assume this works automatically.
runic ether
It is supposed to.
marsh dragon
Now you do. Does it provide any insight?
Not much... I still don't know how it's supposed to work.
runic ether
The timeline is suspended when not focused on the window, but the animation still occurs on the device.
I am trying to preview the animation in the software (it is paused while editing)
I am unable to preview the animation in the video I shared (not intended behavior of software)
marsh dragon
I would appreciate if you can make another video showing the non-working state and the transition to the working state by re-plugging the device.
runic ether
Ok
I will show the working state when I get home, then probably tomorrow I can show the broken and "fixing"
Just know the software is not properly responding when I wake the computer until some time after
Not sure if @autumn crescent is able to weigh in on this
autumn crescent
i also do not understand
the effect seems stopped in the artemis window, which makes sense
runic ether
Even when I try to play it in the window, it does not. Does that make sense? I hit the button and nothing happens.
autumn crescent
if what's show in the window is the same as the keyboard, this is expected behaviour
runic ether
Even if there is an animation and I am focused on the window and trying to play it in the window?
Is Artemis thinking there is no animation to be played?
Perhaps I should show another video with the timeline playing but the keyboard not animating
Would that help?
autumn crescent
Possible yes
runic ether
ok so i woke my machine just now and the issue is somehow gone. i guess factory reset did it?
marsh dragon
I assume this is unlikely...
runic ether
consistent issue suddenly gone after doing so
drifting haven
how many tests did you preform that it was consistent ?
marsh dragon
The internal settings of the Wooting should not influence the wake up behavior. In the case a restoring helped it can indicate that the previous flashed firmware wasn't good (but that should be unlikely too).
I guess sooner or later the issue will come back.
runic ether
There was a difference in that I have rgb sleep on in wooting settings