Verkada Subscription Cost? Enterprise Troubleshooting Guide

Verkada Subscription Cost? Enterprise Troubleshooting Guide

You're facing high Verkada subscription costs, and it's impacting your budget. This guide focuses on enterprise-specific tools and strategies to optimise Verkada Command licensing and reduce recurring expenses. Root causes often include unoptimised licence tiers, lack of edge storage integration, or underutilised features. The solution lies in Verkada Command's advanced licensing tools and strategic deployment planning.

Quick Checks for IT Administrators

Before diving into detailed troubleshooting, perform these immediate checks:

• Check the VMS dashboard status: In Verkada Command, navigate to Cameras → [device] → Status to confirm the camera is registered and licensed.
• Verify PoE link light on the switch: Ensure the PoE port is active and showing the correct class (e.g. Class 3 for 4K cameras like the CB62 Bullet).
• Ping the camera IP: Use ping [camera IP] to confirm network connectivity. If the camera responds, the issue is likely licensing-related.
• Check the status LED on the camera: A solid green light indicates proper power and connectivity. A blinking red light may signal a licence expiration.
• Power cycle via PoE switch port: Disable and re-enable the PoE port on the switch to reset the camera's connection. This can resolve transient network issues.

Verify Your Verkada Camera's Network Configuration

A misconfigured network can lead to unexpected subscription costs if the camera is not properly integrated into Verkada Command. Follow these steps to ensure your network is optimised:

Check VLAN Assignment

• Ensure the camera is assigned to a dedicated VLAN in your network infrastructure. This prevents conflicts with other devices and ensures proper communication with Verkada Command.
• In your switch configuration, confirm that the VLAN is correctly tagged and that the camera's port is set to trunk mode if multiple VLANs are in use.

Validate PoE Budget

• Calculate the total PoE power budget for your deployment. For example, a deployment of 20 CB62 Bullet cameras (each requiring 15W) would need a minimum of 300W on the switch port.
• Use Verkada Command's Device Health dashboard to monitor PoE usage in real time. If the budget is exceeded, consider upgrading to a higher-capacity PoE switch or reducing the number of cameras on the same switch.

DHCP Lease Check

• Ensure the camera's IP address is obtained via DHCP and that the lease time is sufficient to avoid frequent reboots. In the DHCP server configuration, set the lease time to at least 24 hours.
• If static IP addresses are used, verify that they are correctly configured in Verkada Command under Organisation → Devices → [camera] → Network Settings.

Diagnose Verkada Command Connectivity Issues

If the camera is properly networked but subscription costs persist, the issue may lie in Verkada Command's integration or licensing configuration:

Re-Register the Camera

• If the camera is not properly registered in Verkada Command, it may default to a lower-tier licence or fail to activate cloud features. To re-register the camera:

1. Navigate to Cameras → [device] → Actions → Deregister.
2. Re-add the camera to the organisation via Organisation → Devices → Add Device.
3. Assign the appropriate licence tier during re-registration.

Verify Licence Tier

• In Verkada Command → Organisation → Licences, ensure that the licence tier matches the deployment size and required features (e.g. AI analytics, 24/7 recording).
• If the licence is outdated or mismatched, update it via the Licence Management section. Enterprise-tier licences may require contacting Verkada sales for bulk discounts.

Configure Stream Profile

• Ensure that the camera's stream profile is optimised for your network and subscription tier. In Verkada Command → Cameras → [device] → Video Settings, select the appropriate profile (e.g. 4K for high-resolution needs, 1080p for cost savings).
• Avoid over-subscription by selecting the lowest possible resolution that meets your requirements.

Advanced Troubleshooting for Enterprise Deployments

For large-scale deployments, advanced diagnostics and enterprise-specific tools can help identify and resolve subscription cost issues:

Enable Edge Storage

• To reduce reliance on Verkada's cloud subscription, enable Edge Storage in Verkada Command → Cameras → [device] → Storage Settings.
• Configure the camera to store footage on a compatible NAS device. Ensure the NAS supports the required protocols (e.g. NFS, SMB) and has sufficient storage capacity.
• Monitor storage usage via the Device Health dashboard to avoid overfilling the NAS and triggering subscription alerts.

Use Video Quality Analytics

• In Verkada Command → Analytics → Video Quality, use the Video Quality Analytics tool to identify cameras with suboptimal performance (e.g. motion blur, low light conditions).
• Adjust camera settings (e.g. exposure, gain) to improve video quality and reduce the need for advanced features that may increase subscription costs.

Check Cloud Connection Status

• In Verkada Command → Cameras → [device] → Diagnostics, check the Cloud Connection Status to ensure the camera is properly connected to Verkada's cloud services.
• If the connection is unstable, troubleshoot network issues (e.g. firewall rules, port forwarding) or contact Verkada support for assistance.

Factory Reset and Packet Capture

If basic troubleshooting fails, perform a factory reset and packet capture to identify deeper issues:

Factory Reset

• For Verkada cameras like the CD62 Dome or CB62 Bullet, a factory reset requires deregistering the camera via Verkada Command → Organisation → Devices → [camera] → Deregister.
• After deregistration, re-add the camera to the organisation and assign a new licence tier. This can resolve persistent licensing issues.

Packet Capture

• Use a packet capture tool (e.g. Wireshark) to monitor network traffic between the camera and Verkada Command.
• Look for errors in the RTSP stream or failed licence activation requests. This can help identify network bottlenecks or misconfigurations.

Enterprise Verkada Analysis

Common root causes of high Verkada subscription costs include:

• PoE power budget exhaustion: Ensure the switch port can handle the power requirements of all cameras in the deployment.
• DHCP scope exhaustion: Verify that the VLAN assigned to cameras has sufficient IP addresses for all devices.
• VMS licensing or database corruption: Re-register the camera and verify that the organisation's licence tier is correctly applied.
• Firmware incompatibility: Ensure all cameras are running the latest firmware to access all features and avoid subscription-based workarounds.
• UK-specific considerations: Compliance with GDPR retention policies may require additional storage or subscription tiers. Ensure your deployment aligns with Building Regulations Part Q for security systems.

How to Prevent Future Verkada Issues

To avoid recurring subscription costs, follow these best practices:

• Schedule regular firmware updates: Use Verkada Command's Firmware Management tool to apply updates in a staged rollout, minimising downtime.
• Monitor VMS health: Use the Device Health dashboard to track camera status, licence usage, and network performance.
• Plan PoE budget headroom: Allocate 10-20% extra power capacity on switches to accommodate future expansions.
• Use dedicated VLANs: Isolate cameras on a dedicated VLAN to avoid conflicts with other devices and ensure proper communication with Verkada Command.
• Implement QoS policies: Prioritise camera traffic on your network to avoid bandwidth-related issues that may trigger subscription alerts.

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.

When to Replace Your Verkada Subscription Equipment

When considering camera replacements, factor in the following:

• Wired camera lifespan: 5-8 years typical. Wired cameras last longer but sensor degradation and firmware EOL are factors.
• Battery camera lifespan: 3-5 years typical. Battery cameras degrade over time, with battery performance dropping after 300-500 cycles.
• NVR HDD lifespan: 3-5 years for surveillance-rated HDDs. Use WD Purple or Seagate SkyHawk drives for 24/7 operation.
• SD card lifespan: 1-2 years with continuous recording. Use high-endurance cards (e.g. Samsung PRO Endurance) for reliability.
• UK warranty rights: Consumers have up to 6 years to claim faulty goods under the Consumer Rights Act 2015 (5 years in Scotland).
• Troubleshooting time: If basic fixes take more than 30 minutes, consider hardware replacement. Persistent issues may indicate a faulty camera or switch port.