Verify Your Verkada Camera’s Network Configuration
A Verkada camera showing no video despite powering on may indicate a misconfigured network setting, firmware incompatibility, or VMS integration failure. Common root causes include VLAN mismatches, insufficient PoE budget, or outdated firmware channels. This guide provides enterprise-level steps to resolve these issues using Verkada Command and brand-specific diagnostic tools.
Quick Fixes for Verkada No Video Issues
Before diving into advanced diagnostics, perform these 30-second checks:
- Check VMS Dashboard Status: In Verkada Command, navigate to Cameras → [device] → Overview. If the camera shows 'Offline' but responds to ping, verify the 'Stream Profile' is set to 'Standard' (not '4K Ultra' or 'AI Analytics').
- Verify PoE Link Light: Ensure the switch port’s PoE LED is green (Class 3 or 4). For the CB62 Bullet, a red LED indicates failed negotiation.
- Ping the Camera IP: From the management platform, use the 'Ping Camera' button in Verkada Command. A timeout suggests firewall or VLAN issues.
- Check Status LED: A solid red LED on the camera housing indicates a hardware failure (e.g. lens obstruction or sensor fault). A blinking amber LED suggests firmware update pending.
- Power Cycle via Switch: Disable the switch port for 30 seconds, then re-enable. This resets the PoE negotiation and clears transient errors.
Diagnose Verkada Command Connectivity Issues
Check VLAN Assignment
Verify the camera’s VLAN matches the switch port configuration. In Verkada Command, navigate to Cameras → [device] → Network Settings. If the VLAN ID differs from the switch port’s configuration, update the camera’s VLAN ID in the management platform. For Layer 3 switches, ensure 802.1Q trunking is enabled on the uplink port.
Validate PoE Budget
Access the 'Device Health' dashboard in Verkada Command (Cameras → [device] → Diagnostics → Power). If the camera shows 'Power Overload', adjust the PoE allocation in the switch’s management interface. For example, on a Cisco switch, use the show power inline command to identify overdrawn ports. Ensure the switch supports 802.3at (PoE+) for 4K models like the CB60 Bullet.
Check Firmware Channel
Navigate to Cameras → [device] → Settings → Firmware. Ensure the camera is set to the 'Stable' channel (not 'Beta'). If the firmware update is stuck in 'Pending', perform a staged rollout via Verkada Command’s 'Firmware Deployment' tool. For enterprise environments, use the 'Rollback' option to revert to a previous version if the update causes instability.
Verify ONVIF/RTSP Settings
In Verkada Command, go to Cameras → [device] → Settings → Video. Ensure the ONVIF profile is set to 'Profile S' for compatibility with most VMS platforms. Test the RTSP stream URL directly using a media player (e.g. VLC): rtsp://[camera_ip]:554/stream1. If the stream fails, check the camera’s authentication mode (e.g. 'Basic' vs. 'Digest') and ensure the VMS platform is configured to match.
Use Video Quality Analytics
In Verkada Command, access the 'Video Quality Analytics' tool under Cameras → [device] → Diagnostics. This tool identifies issues like lens obstructions, infrared filter lock, or motion detection misalignment. For example, if the analytics show 'No Motion Detected' despite activity, the camera may be facing a wall or has a misaligned lens.
Advanced Diagnostics for Persistent Issues
Perform a Factory Reset (Model-Specific)
For the CD62 Dome Camera, a factory reset requires deregistering the device from Verkada Command via an organisation administrator. Navigate to Organisation → [device] → Deregister, then re-provision the camera using the 'Add Camera' wizard. For the CB62 Bullet, ensure the switch port is set to 'PoE+ (802.3at)' before re-provisioning.
Capture Network Traffic
Use Verkada Command’s Network Diagnostics tool to capture a packet trace. Navigate to Cameras → [device] → Diagnostics → Network, enable 'Capture Traffic', and reproduce the issue. Save the trace and submit it to Verkada Support via the platform’s 'Escalate' button. This trace will include RTSP handshake failures, NTP sync issues, or MTU mismatches.
Check VMS Database Consistency
If the camera is registered in the VMS (e.g. Milestone XProtect) but shows no video, run a database consistency check. In the VMS platform, navigate to System → Database → Verify. This scan identifies orphaned camera entries or licensing conflicts. If the VMS license is expired, renew it via the platform’s 'Licensing' menu.
Escalate to Enterprise Support
If basic fixes fail, escalate to Verkada’s enterprise support via the platform’s 'Escalate' button. Include the device serial number, firmware version, and any packet traces. Verkada’s support team will guide you through an RMA process if hardware failure is suspected.
Root Causes of Verkada No Video Issues
PoE Power Budget Exhaustion
A common cause of no video is insufficient PoE budget. Ensure the switch supports 802.3at (PoE+) for 4K models. For example, a 24-port switch with 30W per port may fail to power a CB62 Bullet (which requires 30W). Use the 'Power Overload' indicator in Verkada Command to identify overdrawn ports.
VMS Licensing Conflicts
If the camera is registered in the VMS but shows no video, verify the license is active. In Milestone XProtect, navigate to System → Licensing and check for expired or invalid licenses. A deactivated license will prevent the VMS from ingesting video streams.
UK-Specific Considerations
In the UK, modern windows with low-E coating may block WiFi signals, affecting cameras relying on wireless connectivity. For outdoor cameras (e.g. CB62 Bullet), ensure the PoE switch is located within 100m of the camera. For indoor models, verify the switch supports 802.3at and that the PoE budget accounts for 30% headroom for future expansion.
Prevention and Long-Term Maintenance
Schedule Firmware Updates
Use Verkada Command’s 'Firmware Deployment' tool to schedule updates during off-peak hours. Set up a 'Stable' channel for production environments and a 'Beta' channel for testing. For enterprise deployments, enable 'Staged Rollout' to update 20% of cameras at a time.
Configure Dedicated VLANs
Assign a dedicated VLAN for Verkada cameras to isolate traffic from other network segments. In the switch’s management interface, set the VLAN ID to 100-200 and enable 802.1Q trunking on uplink ports. This prevents conflicts with DHCP servers or firewalls.
Monitor PoE Budget
Use Verkada Command’s 'Power' dashboard to track PoE usage. For a 48-port switch, ensure the total power budget exceeds 300W (30W per port × 10 cameras). For high-density deployments, use a PoE++ (802.3bt) switch to power multiple 4K cameras.
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 and Lifecycle Planning
Assess Camera Lifespan
Wired Verkada cameras (e.g. CD62 Dome) typically last 5-8 years, while battery-powered models degrade after 300-500 charge cycles. Use the 'Device Health' dashboard in Verkada Command to monitor sensor degradation or firmware end-of-life (EOL) warnings.
UK Procurement and Warranty
Under the Consumer Rights Act 2015, UK consumers have up to 6 years to claim faulty goods. For enterprise deployments, ensure contracts include extended warranties covering firmware updates and hardware replacements. For surveillance-rated HDDs, use WD Purple or Seagate SkyHawk drives to avoid premature failure.
Troubleshooting Time Estimates
Basic fixes (e.g. VLAN reconfiguration) take 10-15 minutes. If troubleshooting exceeds 30 minutes and basic steps fail, hardware failure is likely. For example, a CB62 Bullet with a stuck infrared filter will show no video despite stable network and firmware.