What to Do When Your Verkada Device Won't Sync
Verkada's cloud-based platform, Verkada Command, relies on a constant, stable connection with its hardware devices to provide real-time access and control. When a camera, access controller, or sensor "won't sync," it means this crucial communication link has been broken. This can lead to missing footage, delayed notifications, and an inability to manage your system.
This guide will help you understand and troubleshoot the common reasons why a Verkada device might fail to sync with the cloud, allowing you to restore full functionality to your security system.
Understanding Syncing in the Verkada Ecosystem
Every Verkada device, from cameras to alarms, needs to regularly "check in" with Verkada Command. This sync process involves:
- Uploading Video and Data: Cameras upload thumbnails, metadata, and footage to the cloud.
- Reporting Status: The device reports its health and online status.
- Receiving Configuration Updates: Any changes you make in Command (e.g., changing a camera's name or motion sensitivity) are downloaded and applied by the device.
A failure in this process is a critical issue that needs immediate attention.
Step-by-Step Guide to Fixing Verkada Sync Issues
Follow these steps to diagnose and resolve the problem.
1. Check the Device's Physical Status and LED Light
The first step is always to check the hardware itself.
- Look at the LED Light: The status light on the device is your primary diagnostic tool. A solid blue light indicates a healthy, synced state. A flashing amber light typically means the device has power but cannot establish a connection to Verkada's servers, which is a clear sign of a sync issue.
- Verify Network Cable: For wired devices, ensure the Ethernet cable is securely plugged in at both the device and the network switch. Look for link lights on the switch port to confirm a physical connection.
- Power Cycle the Device: The simplest fix is often the most effective. Disconnect the device from its power source (either by unplugging the PoE cable or the power adapter), wait for 30 seconds, and then plug it back in. This will force it to reboot and attempt a fresh connection.
2. Investigate Network and Connectivity
The vast majority of sync problems are rooted in network issues.
- Confirm Internet Access: Is the local network connected to the internet? Check if other devices on the same network can access external websites. A total internet outage will prevent any device from syncing.
- Review Firewall Settings: This is a major culprit in corporate environments. Verkada devices need to make outbound connections over TCP port 443 to communicate with the cloud. Your network firewall must be configured to allow traffic to
*.verkada.com. Consult with your IT administrator to ensure these connections are not being blocked. - Check DHCP and DNS: Ensure the device is able to obtain a valid IP address from your network's DHCP server. It also needs to be able to resolve Verkada's domain names via DNS. If the device has a static IP, double-check that the IP, subnet, and gateway settings are correct.
3. Use the Tools in Verkada Command
The Command platform itself can offer clues.
- Review Device Status: In your Command dashboard, navigate to the device that won't sync. It will likely be marked as "Offline." The platform may provide additional details about the last time it was successfully connected.
- Check Network Settings: For some devices, the Command interface shows basic network information, such as the IP address it last used. This can help you confirm if it's on the correct network segment.
If after following all these steps your Verkada device still refuses to sync, it may be time to contact Verkada's support team. They can perform more in-depth remote diagnostics to identify the root cause of the problem.