Introduction When motion detection issues arise, such as events not being detected or sent to the video portal, there are several troubleshooting steps to follow. This guide provides a step-by-step process to resolve motion detection problems and optimize camera settings. Troubleshooting Steps 1. Verify Admin Portal Configuration Check the Admin Portal configuration to ensure analytics are properly set up. The Camera events slider must be green. If the camera supports Motion Detection via ONVIF, confirm that the detection region and sensitivity are configured appropriately for the scene. 2. Check Motion Detection Settings Access the Camera UI through the Troubleshooting tab in the Camera Settings on the Admin Portal or by using the camera's IP address. Navigate to the Setup section and select the Events tab. Under Motion Detection, review the Rule Settings and ensure the Detection Mode is set to Grid. Note that some cameras may default to Area mode, which is not ONVIF compliant. 3. Adjust Motion Detection Sensitivity If the sensitivity is set too low, the camera may miss minor motion. Increase the sensitivity level to improve detection accuracy. Ensure the detection region covers the area where motion is expected. It’s recommended to use large, continuous zones rather than small, fragmented cells with gaps in the detection area. 4. Optimize Image Parameters To improve motion detection performance, adjust the camera’s image parameters. 5. Testing and Verification After making adjustments, test the camera’s motion detection by creating motion in its field of view. Monitor the Video Portal to verify if events are now detected and sent properly.

If Analytics is correctly configured and enabled in the Admin Portal, and the camera plan is set to analytics, but events from the camera are not appearing on the Video Portal or no alerts are being received, the following issues may be causing the problem: Analytics settings in the Admin Portal are correctly configured. No events are being detected or displayed for the camera on the Video Portal. The issue may arise from the motion detection settings in the Camera UI being configured to detect motion in an "Area" pattern instead of a "Grid" pattern, and the sensitivity might be set too low. For Uniview cameras, in the Events section of the camera's settings, the motion detection mode under Rule Settings may be set to "Area" rather than "Grid." The "Area" detection method is not ONVIF compliant and cannot be controlled through ONVIF commands like the "Grid" mode can. On Uniview cameras, each mode has its own configuration file. The camera will use the mode selected through the Web UI, so when the Admin Portal connects to the camera, the settings that are seen by the platform will match the configuration in the Admin Portal, which ensures proper integration. However, if the "Area" mode is used, events will not be triggered, even if the Admin Portal settings are correct. To resolve this, access the Camera UI through one of the following methods: Go to the Troubleshooting tab in Camera Settings on the Admin Portal and generate the Public URL for the camera. Alternatively, log in directly using the camera's IP address. Once logged into the Camera UI: 1. Navigate to the Setup section. 2. Go to the Events tab on the left. 3. In the Motion Detection section under Rule Settings, change the Detection Mode to "Grid" from the drop-down menu.

In some cameras, heavy rain or snowstorms—particularly at night—can cause rain droplets or snowflakes to appear illuminated by the camera's infrared light. This often results in shapes that resemble objects, with high confidence levels in the recognition. This phenomenon occurs because of the camera's slow shutter speeds, which cause droplets or snowflakes to extend across the frame, creating long streaks visible in the image. These streaks may intersect, forming shapes that resemble human figures. The pixelation caused by motion further exaggerates these shapes, leading to images that closely resemble actual objects. To reduce the impact of rain or snow, higher shutter speeds should be used, along with adjustments to improve image quality in order to minimize motion-induced pixelation. Most cameras offer the ability to modify image parameters, including shutter speed. While low shutter speeds can enhance overall brightness, they result in blur for fast-moving objects. Additionally, limiting the camera's bitrate can force increased compression to meet the set limit, which often causes further pixelation around moving objects, exacerbating the risk of misidentification.

Under certain challenging conditions, even advanced server-side analytics can mis-categorize areas of a scene as objects or mistakenly identify stationary objects as moving, leading to false alerts. Common situations that can result in false object detection include: Detection of objects outside the defined motion mask. Snow or rain creating shapes that are interpreted as objects. Moving lights or lightning strikes causing stationary objects to be recognized as moving. Stationary objects being reported as moving during PTZ (pan-tilt-zoom) camera movements.

It is possible for smart analytics to detect objects outside the motion mask, leading to unwanted alerts. This issue often arises with cameras that do not fully comply with ONVIF motion detection configuration standards, meaning the ONVIF method for retrieving the motion mask may not function correctly. For example, cameras from manufacturers like AVYCON, Axis and Vivotek use proprietary methods to configure motion detection, which are not ONVIF-compliant in this regard. In these cases, a notification may indicate that motion detection or other detectors are unavailable. As an illustration, consider a scenario where a motion mask is configured to detect movement only in the front yard. However, the object detection system may still report vehicles on the road whenever there is motion detected, even if the vehicle is moving outside the designated area. While it is currently not possible to completely eliminate the detection of objects outside the motion mask, the likelihood of false events can be reduced by fine-tuning the camera's motion detection settings. Ensuring the camera does not register excessive false alerts will help minimize the chances of detecting objects beyond the intended detection zone. Efforts are ongoing to integrate additional configuration protocols, and many manufacturers periodically release firmware updates to enhance ONVIF compatibility.

In some cases, when Line Crossing or Intrusion Detection is configured through the Admin portal for Uniview cameras, the settings may transfer correctly to the camera, but no events are generated. This typically occurs because, in addition to enabling the feature, the schedule must also be activated on the camera. In some instances, this schedule does not enable automatically. To verify this, access the camera's web interface, either through the Generate link button in the Troubleshooting tab for P&P cameras or by copying the HTTP access URL for ONVIF cameras. Then, navigate to the Intelligent → Smart → Cross Line menu. Ensure that both the Cross Line Detection and Enable Plan checkboxes are selected. The same principle applies to Intrusion Detection—if either checkbox is unchecked, the module will not function.