[FEATURE REQUEST] Add Mouse Jiggler

[lwbt]

If user has enabled Mouse jiggler feature, It will allow to monitor the remotely connected device, by preventing it from getting into sleep mode or locking itself (plus would not require installation of additional software or purchase of USB jiggler)

PiKVM has an implementation, and it would be a great addition to NanoKVM.
It will also allow me to buy more NanoKVMs thanks to not needing to buy a mouse jiggler too.

#158

I reopen this request as I have received my JetKVM an this is a feature that immediately jumps at me on the first screen after login. It's not a tucked away expert feature.

Jiggler
Simulate movement of a computer mouse. Prevents sleep mode, standby mode or the screensaver from activating

[Snazzie]

Why cant you just disable sleep and auto lock in the OS. feature seems pointless outside of faking activity on work computer.

[lwbt]

You always imply desktop operating systems with a writable partition and a clearly documented way to configure what you think is the ideal solution. My preferred ideal solution would not involve a KVM at all, but that's not how things typically work and being the smart guy on the team who would love to reverse engineer everything usually results in burnout. Two products of the same kind should have the same functionality and the better or cheaper product wins on the market. That's how it should be. Nobody should have to discuss this with you. Stop patronizing and gaslighting people who have to keep proprietary server appliances running.

[Snazzie]

Its literally a valid challenge to your idea. If you cant give a reasonable scenario that is unsolvable unless this feature is implemented, then its not really a needed feature.

As stated, your issue is directly solvable at OS level without this feature on nanokvm. If you're running headless, its not going to sleep anyway.

Its not patronizing or gaslighting to challenge ideas.

In ideal world everything is available, but there are constraints, and fitting nonsense features take up resources and increase complexity.

Now if there is an actual scenario people are unaware of, maybe educate them and make your case instead of crying about your idea being challenged and downvoting them.

[lwbt]

Check your privileges and have a little empathy man, not everyone can be a smug jerk working perfect products.

Sure, you are much smarter than me, but that doesn't change the fact that the world outside your tiny bubble still looks like a dumpster fire.

take up resources

NanoKVM developers can learn a few things by looking at JetKVM to make their product more stable and secure which has been criticized a few times here. Bringing up this topic reveals that this is just an attempt of derailing and neglecting or ignoring the current state of the product.

[Snazzie]

Check your privileges

Ive seen enough. have a nice day.

[ucki007]

I have to take @Snazzie 's side.

The NanoKVM is a very low cost part of hardware with a limited amount of ressources. It is designed for remote controlling / installing hardware and should run stable (each new component increases the chances of instabilities) and not suffer from something I like to call "featuritis" (an overload of features).

For me, even VPN (via tailscale) is one feature to much and to proof the stability aspect: we see in some other posts that it breaks the hardware limits of nanoKVM in some constellations / versions. But I get the point that this allows access to remote locations without configuring portforwarding etc.

Something like a mouse jiggler (or even debugging tools like aircrack and tcpdump) should not be part of a KVM as discussed in #248 . If something like that is needed it should be implemented on the host / network itself (e.g. disabling lockscreen / standby or installing the jiggler in Host OS).

[dudududodododedede]

this would be a great feature for my work laptop -- I cannot install software on it, and can't disable locksreen/standby/screensaver