Verify Your Verkada Camera's Network Configuration
If your Verkada camera is failing to record, the root cause may lie in its network configuration or cloud subscription status. Begin by confirming that the camera is properly registered in Verkada Command and that its storage settings (local or cloud) are correctly configured. Ensure the camera's firmware is up to date and that the Device Health dashboard shows no critical warnings. If the issue persists, proceed to the following sections for deeper diagnostics.
Quick Fixes for Verkada Cameras Not Recording
Before diving into advanced diagnostics, perform these rapid checks:
- Check the VMS dashboard status: In Verkada Command, navigate to Cameras → [device] → Overview. Look for a red Offline status or yellow Degraded indicator.
- Verify PoE link light: Ensure the switch port shows a green PoE negotiation status (Class 3 for Verkada cameras). If the port shows Class 0, the switch may not support PoE or the power budget is exhausted.
- Ping the camera IP: Use
ping [camera_ip]from the same subnet. A 100% packet loss response may indicate a network partition. - Check the status LED: A solid red light may indicate a hardware fault or failed firmware update.
- Power cycle via PoE: Disable the switch port for 30 seconds, then re-enable it to force a reinitialisation.
Diagnose Verkada Command Connectivity Issues
Check the Device Health Dashboard
In Verkada Command, go to Cameras → [device] → Device Health. Look for warnings related to:
- Cloud connectivity: A failed cloud sync may prevent event-based recording.
- Storage status: If the camera is using local storage (e.g. SD card), confirm the card is not full or corrupted.
- Network performance: High latency or packet loss (e.g. more than 10ms) can disrupt streaming.
If the Cloud Connectivity status shows Disconnected, ensure the camera has a stable internet connection and that the cloud subscription is active. For hybrid storage models (local + cloud), verify that the camera's local storage retains recent footage (typically 30-365 days depending on model).
Validate Camera Storage Configuration
Navigate to Cameras → [device] → Storage Settings. For cloud-managed cameras, confirm that the subscription plan includes recording (e.g. 24/7, motion-based, or event-based). For local storage, ensure the SD card is formatted to FAT32 and has sufficient capacity. If the camera is part of a multisensor model (e.g. CM62), check that all sensors are powered and communicating via the internal bus.
Use the Motion Search Feature
In Verkada Command, use the Motion Search tool (Cameras → [device] → Timeline) to draw a search region. This feature highlights movement in specific areas of the frame, helping identify if motion triggers are misconfigured. If the camera is not detecting motion, check the Motion Detection settings (Cameras → [device] → Video Settings) for sensitivity thresholds and excluded zones.
Advanced Diagnostics for Verkada Cameras
Perform a Network Diagnostic Scan
Use the Network Diagnostics tool in Verkada Command (Cameras → [device] → Diagnostics). This scan will check:
- VLAN assignment: Ensure the camera is on the correct VLAN and that the subnet mask (e.g. 255.255.255.0) matches the camera's IP range.
- PoE budget: Verify the switch port's allocated power (e.g. 15.4W for Class 3) and that the budget is not exhausted.
- Multicast/IGMP snooping: Disable this feature on switches if the camera uses multicast streams.
- DHCP lease: Confirm the camera's IP address is assigned correctly and that the lease time is sufficient (e.g. 24 hours).
If VLAN misconfiguration is detected, reassign the camera to a dedicated camera VLAN and ensure the switch port is configured for untagged traffic.
Check Firmware Channel and Rollback
Navigate to Organisation → Devices → Firmware in Verkada Command. Ensure the camera is enrolled in the correct firmware channel (stable or beta). If a firmware update is pending, check the camera's connection status and retry the update. For critical issues, use the Rollback feature to revert to a previous version while maintaining the current configuration.
Verify RTSP/ONVIF Stream Settings
In Verkada Command, go to Cameras → [device] → Video Settings. Ensure the Stream Profile matches your VMS platform's requirements (e.g. H.265, 4K resolution). For ONVIF compliance, verify that the camera is registered to the correct profile (Profile S for standard video, Profile G for PTZ). If the RTSP stream fails, test the URL directly using a tool like VLC (e.g. rtsp://[camera_ip]:554/stream).
Factory Reset and Enterprise Support Escalation
Reset a Verkada Camera
To factory reset a Verkada camera, it must be deregistered from the Verkada Command platform by an organisation administrator. Navigate to Organisation → Devices → [camera] → Actions → Deregister. After deregistration, the camera will power cycle and revert to factory defaults. For models like the CD62 Dome or CB62 Bullet, ensure the PoE link is active during re-provisioning.
Packet Capture and Protocol Analysis
Use a network analyser (e.g. Wireshark) to capture traffic on the camera's subnet. Look for:
- RTSP handshake failures: Indicate a problem with the stream URL or authentication mode.
- NTP synchronization errors: May cause timestamping issues in recorded footage.
- Cloud API errors: If the camera is cloud-managed, check for failed sync requests.
Submit the packet capture to Verkada support for analysis. Include timestamps, IP addresses, and any relevant error codes from the Device Health dashboard.
Root Causes of Verkada Camera Recording Failures
Common enterprise-level causes include:
- PoE budget exhaustion: If multiple cameras are connected to a single switch port, ensure the total power demand (e.g. 15.4W per camera) does not exceed the switch's capacity.
- VLAN misconfiguration: Ensure the camera is on a dedicated VLAN with proper subnet settings (e.g. 255.255.255.0).
- Cloud subscription issues: Verify that the camera is registered to an active cloud plan and that the retention period aligns with your requirements.
- Firmware incompatibility: Ensure the camera is on the correct firmware channel (stable or beta) and that the update has completed without errors.
- UK-specific considerations: For premises with solid_brick or cavity_wall construction, ensure the camera's Wi-Fi signal is not attenuated beyond acceptable levels (e.g. 2.4GHz by 10-15dB per wall). Use a wired connection if signal strength is poor.
Prevention and Long-Term Maintenance
Enterprise Maintenance Best Practices
- Schedule firmware updates: Use Verkada Command's Firmware Management tool to schedule updates during off-peak hours.
- Monitor VMS health: Enable SNMP traps on your switches to detect PoE budget issues or network outages.
- Plan for PoE headroom: Allocate at least 20% extra power on switches to accommodate future camera additions.
Full disclosure: we built scOS to address exactly this—the complexity of managing enterprise camera fleets across VLANs. scOS uses permanently powered cameras connected via ethernet.
Replacement and Lifecycle Planning
For Verkada cameras, consider the following:
- Wired camera lifespan: 5-8 years for models like the CP62 PTZ, with sensor degradation and firmware EOL as key factors.
- Battery camera lifespan: 3-5 years for models like the D80 Fisheye, with battery capacity degrading after 300-500 cycles.
- UK procurement: Under the Consumer Rights Act 2015, UK consumers have up to 6 years to claim faulty goods (5 years in Scotland). Ensure all replacements comply with local Building Regulations Part Q for surveillance systems.
Enterprise Support Escalation
If troubleshooting exceeds 30 minutes without resolution, contact Verkada support via help.verkada.com. Provide the following:
- Packet captures from the camera's subnet
- Device Health dashboard screenshots
- Firmware channel and version details
- VLAN configuration and switch port settings
For critical issues, escalate to Verkada's enterprise support team and request an RMA if hardware failure is suspected. Include the camera's serial number and a detailed description of the failure (e.g. intermittent recording, complete offline status).