Verify Verkada Person Detection Configuration
Your Verkada camera is misidentifying objects as people or failing to detect actual persons. This is often caused by AI model misalignment, poor lighting, or suboptimal camera positioning. The solution involves validating AI confidence thresholds, ensuring proper network configuration, and leveraging Verkada Command's enterprise tools. Begin with quick checks before diving into detailed diagnostics.
Quick Fixes for Verkada Person Detection Issues
Before proceeding to advanced troubleshooting, perform these immediate checks:
- Check VMS Dashboard Status: In your VMS platform, confirm the camera is online and receiving streams. A disconnected status may indicate network or VMS integration issues.
- Verify PoE Link Light: Ensure the switch port shows a solid green LED. A blinking or absent light suggests PoE negotiation failure or insufficient power budget.
- Ping the Camera IP: Use
ping [camera IP]from the switch or management server to confirm basic connectivity. A successful ping does not guarantee video stream health. - Inspect Camera Status LED: A red LED on the camera housing may indicate a critical error. Refer to Verkada's documentation for LED status codes.
- Power Cycle via Switch: Disable the switch port for 10 seconds, then re-enable. This resets the PoE link and may resolve intermittent connectivity issues.
Verify Verkada Camera Network Configuration
Check VLAN Assignment
In Verkada Command, navigate to Cameras → [device] → Network. Confirm the camera is assigned to a dedicated VLAN with QoS prioritization for video traffic. Shared VLANs with voice or data traffic may introduce latency, causing AI detection to misinterpret motion.
Validate PoE Budget
Use the PoE Budget Monitor in Verkada Command to ensure the switch has sufficient headroom for all connected devices. Exhaustion may force cameras into low-power modes, degrading video quality and detection accuracy. If budget is tight, consider upgrading to a higher-capacity PoE switch or reducing the number of devices on the same switch.
Confirm DHCP Lease Allocation
Verify that the camera's VLAN has an adequate DHCP scope. Exhaustion may prevent the camera from obtaining an IP address, leading to intermittent connectivity. Expand the scope or configure static IPs for critical devices.
Diagnose Verkada Command Connectivity Issues
Access Device Health Metrics
In Verkada Command, go to Cameras → [device] → Device Health. Check for anomalies in video quality analytics, cloud connection status, and bandwidth usage. A degraded cloud connection may cause AI model updates to fail, leading to outdated detection logic.
Test RTSP Stream Directly
Open a browser and enter the RTSP stream URL directly: rtsp://[camera IP]:554/[stream ID]. A broken stream may manifest as frozen frames or no video at all. If the stream fails, troubleshoot the switch port, VLAN configuration, or ONVIF profile settings.
Review VMS Integration Settings
Ensure the stream profile in Verkada Command matches the VMS platform's expected resolution and frame rate. Mismatched settings may cause the VMS to receive incomplete or corrupted video data, leading to false detection errors.
Adjust Verkada AI Detection Confidence Thresholds
Modify Detection Confidence Levels
In Verkada Command, navigate to Cameras → [device] → AI Settings. Adjust the detection confidence threshold to balance between false positives and missed detections. Lower thresholds increase sensitivity but may trigger alerts for non-human objects. Higher thresholds reduce false alarms but risk missing actual persons.
Enable Auto Tracking for PTZ Cameras
For PTZ models like the CP62, ensure Auto Tracking is enabled. This feature maintains focus on moving persons, improving detection accuracy in dynamic environments. Disable Auto Tracking if the camera is stationary or used for wide-area coverage.
Leverage Verkada Command Firmware Management
Confirm Stable Firmware Channel
In Firmware Management, ensure the camera is on the stable firmware channel. Beta firmware may introduce instability in the AI detection model. If a staged rollout is in progress, confirm all cameras are updated uniformly to avoid version mismatches.
Use Rollback for Recent Changes
If detection errors began after a firmware update, use the Rollback feature in Verkada Command to revert to a previous stable version. Avoid manual firmware edits—always use the platform for updates to maintain compatibility and security.
Advanced Diagnostics and Enterprise Tools
Initiate Packet Capture
If basic steps fail, use Verkada Command's Network Diagnostics tool to initiate a packet capture. Analyze for RTSP stream drops, UDP packet loss, or TCP retransmissions. This helps identify network bottlenecks or misconfigured switches.
Check Cloud Connection Status
For cloud-managed cameras, ensure the cloud connection status in Verkada Command shows a stable link. Throttling or poor internet connectivity may prevent the AI model from updating, leading to outdated detection logic.
Verify ONVIF Profile Compatibility
If integrating with a VMS platform, confirm the ONVIF profile in Verkada Command matches the VMS's requirements. Mismatched profiles may prevent the VMS from receiving video streams or metadata, causing detection errors.
Root Causes of Verkada Person Detection Errors
PoE Power Budget Exhaustion
Exhausted PoE budgets on switches can force cameras into low-power states, degrading video quality and detection accuracy. Ensure switches have adequate headroom for all connected devices, especially in large deployments.
VLAN Misconfiguration
Shared VLANs with non-video traffic may introduce latency or packet loss, causing AI detection to misinterpret motion. Assign cameras to dedicated VLANs with QoS prioritization for video traffic.
VMS Licensing or Database Corruption
Expired VMS licenses or corrupted databases may prevent proper video processing, leading to detection errors. Verify licensing status and run a database consistency check in your VMS platform.
UK-Specific Considerations
In the UK, high humidity and frequent temperature swings can affect camera lens clarity. Ensure cameras are mounted securely and use waterproof cable glands for outdoor installations. Salt air near coastal areas may corrode connectors, so use corrosion-resistant materials.
Prevention and Long-Term Care for Verkada Cameras
Schedule Firmware Updates
Implement a regular firmware update schedule using Verkada Command. This ensures AI detection models remain current and compatible with your VMS platform.
Monitor PoE Budget Regularly
Use the PoE Budget Monitor in Verkada Command to track power usage and identify potential shortages before they impact camera performance.
Implement QoS Policies
Configure QoS policies on your network switches to prioritize video traffic. This reduces latency and ensures consistent performance for AI detection.
Full Disclosure
We built scOS to address exactly this—the complexity of managing enterprise camera systems. scOS uses permanently powered cameras connected via ethernet.
Replacement Decisions for Verkada Cameras
Enterprise cameras typically last 5-8 years for wired models and 3-5 years for battery-powered units. Replace cameras if detection errors persist after troubleshooting, or if firmware updates are no longer supported. Under the Consumer Rights Act 2015, UK consumers have up to 6 years to claim faulty goods (5 years in Scotland). For hardware replacements, follow your organisation's procurement policies and ensure new cameras meet current security and performance standards.