NVR Fails to Capture Wireless Mouse Movement (bug)

[schonuf]

TL;DR:
Reolink’s wireless mouse on the RLN16-410 NVR does not work because the NVR does not properly capture or render the cursor movements in real time to the operator (see attached videos). I'm not sure if anyone else has experienced the same wireless mouse issues...

I purchased Reolink’s wireless mouse for the RLN16-410 NVR, but the wireless mouse never worked with my NVR. Reolink quickly sent me a replacement wireless mouse. Unfortunately, the replacement mouse did not resolve the issue either. I then decided to cut my losses, and just use the included wired mouse.
Fast-forward some time, we recently installed a "KVM over IP" device in order to remotely manipulate some of the NVR’s features which can only be accessed when physically in-front of the NVR. The KVM enables us to interact directly with the NVR’s mouse and monitor input remotely, as if we were standing directly in-front of the NVR.
After setting up the KVM, the HDMI input worked perfectly, but the mouse would not respond. After further testing, The NVR would sporadically receive mouse clicks, but in unintended locations. I then realized that the “real cursor” was not being updated as I moved the “virtual” mouse cursor. This exact same behavior was exhibited when using Reolink’s wireless mouse with the NVR (and the KVM disconnected). The wireless mouse fails to display cursor movements to the operator, and certain keys are pressed when located on incorrect parts of the screen.


Another odd behavior was when I moved the mouse cursor (either the wireless mouse, or the KVM’s virtual mouse), the “real” cursor would not move. When I subsequently tap the actual physical wired-mouse, the “real” cursor would quickly “jump”, and catch up with virtual mouse cursor movement. This behavior can be seen in the second video I’ve uploaded.

[joseph_1979]

@schonuf Which KVM switch are you using? Note that most wireless mice and keyboards do not support working with KVM switches. Please check for compatibility with the KVM supplier.

[user_634473089658988_634473089658988]

@schonuf Which KVM switch are you using? Note that most wireless mice and keyboards do not support working with KVM switches. Please check for compatibility with the KVM supplier. mcdvoice

Thanks for sharing such an amazing post.

[schonuf]

@joseph-chircop_497308027822318 , The KVM is a "KVM over IP" device, and not your typical KVM switch which just alters keyboard and mouse input. Below is a link to tiny pilot's KVM as an example. When using the KVM, I am using my laptop's trackpad and embedded keyboard. However, the issue has nothing to do with the KVM, since the behavior works exactly the same when only using Reolink's wireless mouse (KVM disconnected). I just didn't realize what the core issue was until I hooked up this KVM and replicated the odd behavior.

https://tinypilotkvm[dot]com/tinypilot-voyager2
^This forum did not allow links so had to replace the [dot]

[joseph_1979]

@schonuf I was in a meeting with Nokia when I read this and so was not focusing. Apologize. Indeed the behaviour is identical and subsequently it seems to be an issue with your NVR as otherwise this would have certainly been raised. Did you check with Reolink support whether your NVR has the most updated firmware?

[schonuf]

@joseph-chircop_497308027822318, This was an issue since I first purchased this NVR in January 2022. Below is my NVR's current version information:

Model: RLN16-4210
Hardware No: H3MB18
Config Version: v3.0.0.0
Firmware Version: v3.0.0.200_22081549

[joseph_1979]

@schonuf There is a newer firmware. Go to Reolink download centre.

[schonuf]

@joseph-chircop_497308027822318 , I just updated to the latest firmware release from Reolink's Download Center. After updating to version v3.2.0.212_22111848, the bug is still present and the issue is unresolved.

[joseph_1979]

@schonuf Kindly report this to the Reolink support. They will delve further using their diagnostic tools.
Most probably this an issue with your nvr.

[user_642953612914768_642953612914768]

Most likely you are plugged into the default “monitor” output and thus can't see your mouse on the screen. If you are currently plugged into the HDMI port on the back of the recorder, please try plugging a cable into the VGA port on the back of the recorder and testing the mouse.

[schonuf]

@user_642953612914768_642953612914768
Update! Good News! I reached out directly to Reolink Support, and they were able to determine the issue. The latest Reolink RLN-16 NVR firmware has fixed the wireless mouse issue I was experiencing. However, I am still having an issue capturing the mouse input into the KVM over IP (e.g.: TinyPilot), but I found a weird workaround. When my wireless mouse is motionless, I am unable to control the mouse movement using the KVM over IP. However, when the mouse is moving, even slight mouse movements due to vibrations, I can control the mouse via the KMV-IP. Seems as though when the mouse’s laser detects minor movements, I am simultaneously able to move the mouse. I will upload a video later. Hope this can help someone else!

[user_662023113609221_662023113609221]

@schonuf Which KVM switch are you using? Note that most wireless mice and keyboards do not support working with KVM switches. Please check for compatibility with the KVM supplier.

I have a similar doubt.

[user_733781210611892_733781210611892]

@schonufTower Defense I think you should check Mouse Driver Update: Check if there are any updates for your wireless mouse driver. Visit the manufacturer's website and download the latest driver for your specific mouse model. Install the driver and restart the NVR.

[marcusnguyeny75258_649901616653409]

There could be several reasons why your NVR is failing to capture wireless mouse movement. Here are a few troubleshooting steps that you can try:Target Card Balance Now
Check if your wireless mouse is properly connected to your computer. Make sure that the USB receiver is securely plugged into a USB port.
Test the mouse on a different computer or laptop to see if it is functioning correctly. This will help to rule out any issues with the mouse itself.
Check if your NVR software is up to date. If it is not, update it to the latest version and try again.
Check if the mouse cursor is visible on the computer screen. If it is not, the issue may be with the computer itself and not the NVR.

[user_734960280756362_734960280756362]

Thanks for the information.

[user_756817415684246_756817415684246]

Reolink’s wireless mouse on the RLN16-410 NVR does not work because the NVR does not properly capture or render the cursor movements in real time to the operator (see attached videos). I'm not sure if anyone else has experienced the same wireless mouse issues...

I purchased Reolink’s wireless mouse for the RLN16-410 NVR, but the wireless mouse never worked with my NVR. Reolink quickly sent me a replacement wireless mouse. Unfortunately, the replacement mouse did not resolve the issue either. I then decided to cut my losses, and just use the included wired mouse.

Fast-forward some time, we recently installed a "KVM over IP" device in order to remotely manipulate some of the NVR’s features which can only be accessed when physically in-front of the NVR. The KVM enables us to interact directly with the NVR’s mouse and monitor input remotely, as if we were standing directly in-front of the NVR.

After setting up the KVM, the HDMI input worked perfectly, but the mouse would not respond. After further testing, The NVR would sporadically receive mouse clicks, but in unintended locations. I then realized that the “real cursor” was not being updated as I moved the “virtual” mouse cursor. This exact same behavior was exhibited when using Reolink’s wireless mouse with the NVR (and the KVM disconnected). The wireless mouse fails to display cursor movements to the operator, and certain keys are pressed when located on incorrect parts of the screen.