Mouse position only updating on click

[WayneColony]

Disclaimer

• I have read and understood the disclaimer.

Application version

0.5.3

System version

0.2.7

Device model

JetKVM

Extension model

None

Remote device Hardware

Reolink NVR - RLN36

Remote device OS

No response

Bug description

jetkvm-diagnostics-20260214-075309.zip
Moving the mouse on the controlling system doesn't move the cursor on the remote system. When I click the mouse it will move the remote cursor to an updated position that is not the same position as on the controlling computer. (Have tried using both "Absolute" and "Relative" settings) The end result is I can click but I have no idea where the click will be. There is no way to click on any menus because there is no way to know where it thinks the mouse has moved to.
On the control computer (Win 10) I have tried using the built in touchpad (HP Zbook G7) and the Reolink supplied USB mouse with the same effect. I have tried this both on Firefox and Chrome with identical results. Basically it looks like the KVM isn't sending a recognized signal to update the cursor position until the left mouse button is clicked. A right click doesn't update the cursor position but it does cause the right click menu to pop up on the remote system.

The attached image shows the control computer's cursor (upper left one) and the remote system's cursor (lower right one). The relative offset between the two does not stay anywhere near the same.
(For example if the local cursor is at the far left and the remote is at the far right I can force the offset to drastically change by clicking the local to the far right which kinda makes them get closer to each other on the next click.)

[dseven]

Unfortunately the Reolink mouse implementation seems to be rather buggy / non-standard. See #136. Some have reported success with a Reolink software update released in 2025. I have a RLN8-410 N3MB01 here with the latest software and still have the issue (at least I think I do - initially when testing, I still had a physical mouse plugged in), but the hackaround at #136 (comment) seems to work (it's clumsy but sortof usable). Note that the setting it's referring to is now under Hardware -> USB Device -> Classes [Custom], and make sure to click "Update USB Classes" to effect the change.

[WayneColony]

Interesting that my search for "reolink" before posting didn't pop up #136.
I just setup my NVR so it's on the latest firmware (Dec 2025 ver). I kind of flailed around with the settings you pointed out that were on #136 and finally got it to work a little bit but it isn't usable except as a last gasp. (Rebooting in a web terminal window seemed to trigger that much compliance.)
Basically it needs to support Absolute mode to keep the mouse under control. Using the JetKVM for this NVR is the only reason I got this so it kind of kills its usefulness.
(The NVR is displaying to a 65" TV in a remote location and people in that location needs to be able to change what is displayed and their settings.)

End result is I can get some mouse movement now with the weird "workaround" but users won't be able to use it.

[dseven]

Yeah. FWIW, I tried third party "real" mice with mine in the past, and found that some were completely unusable, and some were glitchy at best.

I don't think there's anything that JetKVM can do to about this. You could try ReoLink support, but ...... good luck - they'll probably paste some canned answers, argue with you that if it works with the mouse they supplied, what's the problem? then try to get rid of you by offering a discount code ..... at least that's been my experience with them ....