Comet - Can it wake via USB simulate mouse click

KVM
1

So I have a wifi windows laptop device that is sleeping. I assume I do not have any capacity to do WoL over wifi. I am not connected to ethernet.

Can I use it to trigger the machine to wake via the usb mouse input directly ?

I somehow seem to not able get it to work.
I even used the toolbox > shortcut feature to trigger some keyboard commands without success in waking up machine.

Is this use case working for any of you guys ?
For reference my target machine is a windows machine that is sleeping. It can normally wake via a mouse click action on USB mouse.

2

In our test, if you inserted the comet control cable before the computer went to sleep, it should be able to wake it up by clicking the mouse or tapping the keyboard on the web page

4

I don't get the wifi part.

Some computers can wake on keyboard as a separate bios choice.

On this target, try another USB input to see if it works. Might be that the USB port power sleeps?

5

I have done some comparison with 2 machines, I think it's an issue with my locked down bios unable to activate wake on usb port. I am not sure why sometimes it works.

I can wake immediately from sleep from the KVM, but after few hours I am unable.

I've checked my supported sleep states and it seems it will be an issue for me:
powercfg /a


The following sleep states are available on this system:
    Standby (S0 Low Power Idle) Network Connected
    Hibernate
    Fast Startup
 
The following sleep states are not available on this system:
    Standby (S1)
        The system firmware does not support this standby state.
        This standby state is disabled when S0 low power idle is supported.
 
    Standby (S2)
        The system firmware does not support this standby state.
        This standby state is disabled when S0 low power idle is supported.
 
    Standby (S3)
        The system firmware does not support this standby state.
        This standby state is disabled when S0 low power idle is supported.
 
    Hybrid Sleep
        Standby (S3) is not available.
        The hypervisor does not support this standby state.
6

So a second computer works as expected with the entire config exactly the same?

Why is bios locked? Is this a windows sleep issue? UEFI?