Verify Your Verkada Camera's Feature Availability
If your Verkada camera is missing expected features, it may be due to firmware limitations, subscription tier restrictions, or misconfigured management tools. This guide provides advanced troubleshooting steps specific to Verkada's ecosystem, including Verkada Command, firmware channels, and enterprise diagnostics. Begin with quick checks, then proceed to in-depth diagnostics.
Quick Checks for Missing Features
Perform these 30-second checks before proceeding to advanced troubleshooting:
- Check VMS dashboard status: In your VMS (e.g. Wisenet WAVE or MxManagementCenter), confirm the camera is online and features are enabled.
- Verify PoE link light: Ensure the switch port shows a solid green light for the camera (Class 3 or 4).
- Ping the camera IP: Use
ping [camera_ip]to confirm network connectivity. - Check Verkada Command status: Open Cameras → [device] → Diagnostics to view Device Health and Cloud Connection Status.
- Power cycle via switch: Disable and re-enable the switch port to reset the camera's network stack.
Diagnose Verkada Command Connectivity Issues
Check Firmware Channel
In Verkada Command, navigate to Firmware → Channels and ensure the camera is enrolled in the correct channel (stable or beta). Some features may only be available in the beta channel or require a subscription upgrade. If the camera is on the stable channel, check the Release Notes for the latest firmware and initiate a staged rollout via Firmware → Deployments.
Validate Stream Profile Settings
Access Cameras → [device] → Stream Profiles and ensure the profile matches your VMS requirements (e.g. H.265 for high compression). If the VMS is not receiving the stream, verify the RTSP URL in the VMS configuration matches the one shown in Verkada Command. For ONVIF compatibility, check Cameras → [device] → ONVIF Settings and ensure the profile is set to Profile S (for PTZ cameras) or Profile G (for fixed cameras).
Use Device Health Dashboard
In Verkada Command, open Cameras → [device] → Diagnostics and review the Device Health report. Look for errors related to firmware updates, cloud connectivity, or hardware failures. If the Cloud Connection Status is unstable, check the camera's internet gateway and ensure it is not behind a CGNAT (e.g. EE/Three/Vodafone mobile broadband users should use the cloud service or a VPN-based P2P connection).
Verify Subscription Tier
Some features (e.g. facial recognition or advanced analytics) are restricted to specific subscription tiers. In Verkada Command, go to Organisation → Licenses and confirm your subscription includes the required modules. If not, contact Verkada support to upgrade your plan or request a trial.
Analyse Network Bandwidth
Use the Bandwidth Monitor in Verkada Command to ensure the camera has sufficient upload bandwidth. If the camera is on a VLAN with strict QoS policies, adjust the settings to allow higher bandwidth for video streams. For switches with multicast/IGMP snooping enabled, verify the camera's VLAN supports multicast traffic.
Advanced Diagnostics for Missing Features
Check for Region-Locked Features
Some Verkada features (e.g. GDPR-compliant retention policies or Building Regulations Part Q compliance tools) are region-locked. In Verkada Command, navigate to Cameras → [device] → Settings and ensure the Region is correctly configured. If the camera is in the UK but shows incorrect settings, contact Verkada support to reconfigure the region-specific features.
Perform a Firmware Rollback
If a recent firmware update caused feature loss, use the Firmware → Rollback option in Verkada Command. Ensure the camera is on the same VLAN as the management platform and has a stable internet connection. After rollback, check if the missing features return. If not, contact Verkada support with the Device Health Report and Firmware Channel details.
Use Packet Capture Tools
In Verkada Command, open Cameras → [device] → Diagnostics and initiate a Packet Capture to analyse traffic between the camera and the network. Look for errors related to RTSP stream drops, ONVIF handshake failures, or cloud connectivity issues. Save the capture file and share it with Verkada support for further analysis.
Factory Reset and Hardware Diagnostics
Reset Verkada Camera
Verkada cameras do not have a user-accessible factory reset button. To reset a camera, it must be deregistered from Verkada Command by an organisation administrator. Navigate to Cameras → [device] → Actions → Deregister. After deregistration, re-provision the camera via Cameras → Add New → [model]. Ensure the camera is on the correct VLAN and has sufficient PoE power.
Hardware Diagnostics
If the camera still lacks features after software checks, use the Hardware Diagnostics tool in Verkada Command. This tool checks for sensor failures, memory errors, or hardware degradation (e.g. in CB62 Bullet cameras). If hardware issues are detected, initiate an RMA process via the Verkada support portal with the Device Health Report and Packet Capture data.
Understanding Verkada Feature Gaps
PoE Budget Exhaustion
Some Verkada features (e.g. PTZ control or high-resolution streaming) require higher PoE power (Class 4). If the switch port shows Class 0 instead of expected Class 3 or 4, the PoE budget may be exhausted. In Verkada Command, check Network → Switches → PoE Budget to identify switches with insufficient power. Reconfigure the network to use a higher-powered switch or adjust the camera's power requirements via Cameras → [device] → PoE Settings.
Subscription Tier Limitations
Features like facial recognition or edge storage failover are restricted to specific subscription tiers. In Verkada Command, go to Organisation → Licenses and confirm your subscription includes the required modules. If not, contact Verkada support to upgrade your plan or request a trial.
UK-Specific Compliance Issues
Verkada cameras in the UK may have features disabled due to GDPR retention policies or Building Regulations Part Q compliance. In Verkada Command, navigate to Cameras → [device] → Settings and ensure the Region is correctly configured. If the camera is in the UK but shows incorrect settings, contact Verkada support to reconfigure the region-specific features.
Protecting Your Verkada Investment
Schedule Firmware Updates
Use Verkada Command's Firmware → Deployments tool to schedule regular updates. Ensure all cameras are on the same firmware channel (stable or beta) to avoid feature gaps. For enterprise deployments, use staged rollouts to test new features before full deployment.
Monitor VMS Health
Use the Bandwidth Monitor and Device Health tools in Verkada Command to track camera performance. Set up alerts for network latency, PoE budget exhaustion, or firmware update failures. For UK deployments, ensure all cameras comply with GDPR retention policies and Building Regulations Part Q.
Plan for PoE Budget Headroom
Ensure switches have sufficient PoE budget for all cameras. Use Verkada Command's Network → Switches → PoE Budget tool to monitor usage. For high-power cameras like the CP62 PTZ, allocate additional power or use a higher-powered switch.
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.