Confirm Your Verkada Camera's Snapshot Configuration
If your Verkada camera is failing to take snapshots while video works normally, the issue likely resides in snapshot-specific settings or permissions. This guide covers Verkada-specific tools like Device Health Dashboard, Snapshot Settings, and Motion Search. By following these steps, you can isolate whether the problem stems from cloud connectivity, storage allocation, or firmware channel misconfiguration.
Quick Fixes for Verkada Snapshot Failures
Before diving into advanced diagnostics, perform these immediate checks:
- Verify VMS dashboard status: In Verkada Command, check Cameras → [device] → Snapshot Status. A red Offline indicator may signal a permissions issue.
- Check PoE link light: Ensure the switch port shows a Class 3 negotiation for the CD62 or CB62 camera. A Class 0 state indicates a power budget exhaustion or cable fault.
- Ping the camera IP: From the switch or VMS server, run
ping [camera_ip]to confirm basic network connectivity. - Power cycle via PoE: Disable the switch port for 10 seconds, then re-enable. This resets the camera's network stack.
- Check status LED: A blinking green LED on the camera indicates normal operation. A red LED may suggest a firmware update failure.
Diagnose Verkada Command Connectivity Issues
Check VLAN Assignment
Verkada cameras require a dedicated VLAN for snapshot transmission. Navigate to Network Settings in Verkada Command and confirm the camera's VLAN matches the switch port configuration. If the VLAN is misconfigured, snapshots may fail due to multicast/IGMP snooping blocking the camera's traffic. Use the Network Diagnostics tool to test connectivity between the camera and the Verkada cloud endpoint.
Validate PoE Budget
For CD62 or CB62 models, ensure the switch port is allocated sufficient power. Navigate to PoE Budget in the switch's management interface and confirm the port is not in Class 0. If the switch is managed, enable LLDP to verify power allocation. For enterprise deployments, use SNMP monitoring to track PoE usage across the network.
Check Firmware Channel
In Verkada Command, go to Cameras → [device] → Firmware and confirm the camera is on the Stable channel. Cameras on the Beta channel may experience snapshot instability due to untested features. If a firmware update is pending, use the Staged Rollout feature to apply updates to a subset of cameras first.
Verify Snapshot Permissions
Navigate to Cameras → [device] → Snapshot Settings and confirm Storage Allocation is set to Local + Cloud. If the camera is set to Cloud-Only, local snapshots may fail due to insufficient bandwidth. Adjust the Retention Period to ensure snapshots are stored long enough for retrieval. Also, check that the Snapshot Schedule aligns with your operational needs.
Use Motion Search for Event Verification
If snapshots are failing intermittently, use the Motion Search feature in Verkada Command. Draw a search region in the timeline to find events without manually scrubbing through footage. This helps identify if the failure is tied to specific movement patterns or camera angles.
Advanced Diagnostics for Verkada Snapshot Failures
Analyse Cloud Connectivity
If snapshots are failing consistently, check the Cloud Connectivity Status in Verkada Command. A Latency more than 200ms reading may indicate a cloud outage or network bottleneck. Use the Bandwidth Monitor to identify unexpected traffic spikes that may interfere with snapshot transmission. For enterprise deployments, enable Edge Storage Failover to retain snapshots locally during cloud outages.
Check VMS Integration Settings
Ensure the VMS platform (e.g. Verkada Command) is configured to accept snapshot data. In Cameras → [device] → VMS Integration, verify that the Stream Profile is set to Snapshot-Optimised. If the VMS is not properly licensed, snapshot features may be disabled. For AXIS Camera Station or Wisenet WAVE VMS users, ensure compatibility with Verkada's ONVIF profile.
Perform a Device Health Check
In Verkada Command, navigate to Cameras → [device] → Diagnostics and run a full Device Health Check. This tool identifies issues like memory corruption, storage allocation errors, or firmware incompatibility. If the health check reports a Storage Allocation Error, reconfigure the camera's Snapshot Retention Period or increase the local storage capacity.
Test RTSP Stream Manually
If snapshots are failing, test the RTSP stream manually using a tool like VLC Media Player. Enter the RTSP URL (e.g. rtsp://[camera_ip]:554/[stream_profile]) and confirm the stream plays without interruption. If the stream drops, the issue may be related to network congestion or firewall rules blocking the camera's traffic.
Use Packet Capture for Deep Analysis
For enterprise users, deploy a packet capture tool (e.g. Wireshark) on the network to analyse traffic between the camera and the Verkada cloud. Look for TCP retransmissions, RTSP handshake failures, or cloud authentication errors. This helps identify if the issue is related to cloud latency, firewall rules, or incorrect authentication modes.
Factory Reset and Enterprise Support Escalation
Reset Verkada Camera via Command Platform
If all else fails, log into Verkada Command as an Organisation Administrator and navigate to Cameras → [device] → Deregister. This clears any corrupted snapshot configurations. For CD62 or CB62 models, ensure the PoE Budget on the switch is not exhausted. Use the Bandwidth Monitor to identify unexpected traffic spikes that may interfere with snapshot transmission.
Escalate to Enterprise Support
If snapshot failures persist after factory reset, contact Verkada's enterprise support team via help.verkada.com. Provide details about the Device Health Dashboard, Firmware Channel, and Snapshot Settings. For large deployments, use the RMA Process to replace faulty cameras under warranty.
Root Causes of Verkada Snapshot Failures
Snapshot failures often stem from VLAN misconfigurations, insufficient PoE budget, or cloud connectivity issues. For example, a VLAN mismatch between the camera and the switch port may block snapshot traffic. Similarly, DHCP scope exhaustion in the camera's VLAN can prevent the camera from obtaining an IP address. In the UK, Building Regulations Part Q may require additional network redundancy for critical security systems.
Prevention and Long-Term Camera Maintenance
Schedule Firmware Updates
Use Verkada Command's Staged Rollout feature to apply firmware updates to a subset of cameras first. This minimises disruption while ensuring snapshot features remain stable. Set a Firmware Update Schedule to apply updates during off-peak hours.
Monitor Network Health
Implement QoS policies to prioritise snapshot traffic over less critical data. Use SNMP monitoring to track PoE usage across the network and ensure sufficient budget for all cameras. For large deployments, allocate a dedicated VLAN for snapshot transmission.
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
If snapshot failures persist despite troubleshooting, consider replacing the camera. For CD62 or CB62 models, check the warranty period under the Consumer Rights Act 2015 (6 years in England and Wales). If the camera is beyond warranty, contact Verkada's enterprise support for a RMA process. For large deployments, replace cameras with newer models that support edge storage and AI-powered snapshot analytics.