Addressing Water Damage on Verkada Professional Cameras
Water damage to Verkada IP cameras can lead to operational failures, data loss, and compliance risks. This guide provides enterprise-grade steps to diagnose and resolve water-related issues, leveraging Verkada-specific tools like Verkada Command diagnostics, firmware channels, and VMS integration. IT administrators and security integrators will find actionable steps to restore functionality and prevent recurrence.
Verify Verkada Camera’s Network Configuration
Before deep troubleshooting, perform these quick checks: Confirm the camera is online in your VMS dashboard by checking the Device Health tab in Verkada Command. Verify the PoE link light on the switch port is solid green, indicating proper power delivery. Ping the camera’s IP address from the management platform to ensure basic connectivity. Check the camera’s status LED—if it’s blinking red, power cycle the camera by disabling and re-enabling the PoE port on the switch. These steps address 80% of basic connectivity issues.
Diagnose Verkada Command Connectivity Issues
Check VLAN Assignment
Misconfigured VLANs are a common root cause for Verkada cameras failing to communicate with the VMS. In Verkada Command, navigate to Cameras → [device] → Network Settings → VLAN Assignment. Ensure the VLAN ID matches the switch port configuration. If mismatched, update the camera’s VLAN in Verkada Command and restart the device. Use the Network Diagnostics tool to test connectivity between the camera and the management platform. A failed test indicates a VLAN or switch port issue.
Validate PoE Budget
Verkada cameras require precise PoE power allocation. In Verkada Command, go to Organisation → Network → PoE Budget. Confirm the camera’s power draw (e.g. 15.4W for the CB62 Bullet) is within the switch port’s capacity. If the port shows Class 0, the switch may not be PoE-compliant or the camera is misconfigured. Adjust the PoE Mode in Verkada Command to Auto or 802.3at depending on the switch’s capabilities.
Confirm Firmware Channel
Firmware updates stuck in pending state often result from mismatched firmware channels. In Verkada Command, access Cameras → [device] → Firmware. Ensure the camera is set to the Stable channel unless a beta feature is required. If the update fails, initiate a Rollback via the Firmware Management tool and retry the update after verifying the channel configuration. Confirm the camera’s IP is reachable via Ping Test in the diagnostics section.
Test RTSP Stream Profile
Intermittent RTSP stream drops may stem from incorrect stream profiles or network congestion. In Verkada Command, navigate to Cameras → [device] → Stream Profile. Set the profile to Main for higher quality or Secondary for lower bandwidth. Test the stream URL directly in a browser or VMS using rtsp://[camera IP]:550/[stream profile]. If the stream drops, check the Bandwidth Monitor in Verkada Command for congestion and adjust QoS policies on the network switch. Verify Authentication Mode is set to None if using a third-party VMS.
Enable Edge Storage
Verkada’s Edge Storage feature caches video locally on the camera, reducing reliance on network bandwidth. In Verkada Command, go to Cameras → [device] → Edge Storage and enable it if using local caching. This mitigates issues caused by unstable network connections or VMS downtime.
Advanced Troubleshooting for Water Damage
Factory Reset Procedure
If basic fixes fail, re-register the camera via Verkada Command. Log in as an administrator and navigate to Organisation → Devices → [camera] → Deregister. Wait for the device to be removed from the platform. Re-provision the camera by adding it again via Add Device → Scan for New Cameras. Ensure the camera’s PoE Budget is confirmed in the switch port configuration and that Edge Storage is enabled if using local caching.
Packet Capture and Protocol Analysis
Use a packet capture tool (e.g. Wireshark) to monitor traffic between the camera and the VMS. Filter for RTSP and ONVIF protocols to identify dropped packets or authentication failures. If the camera is not responding to ONVIF requests, check the ONVIF Profile in Verkada Command and ensure it matches the VMS’s requirements.
VMS Database Consistency Check
Water damage may corrupt VMS configurations. In your VMS (e.g. Wisenet WAVE or Avigilon Control Center), run a Database Consistency Check to repair licensing or stream profile mismatches. Re-apply the camera’s stream profile and verify it matches the VMS’s settings.
Escalate to Enterprise Support
If the camera remains non-functional, escalate to Verkada’s enterprise support via https://help.verkada.com. Provide the camera’s serial number, firmware version, and logs from Device Health in Verkada Command. Include details of the water damage incident, such as whether the camera was submerged or exposed to prolonged moisture.
Root Causes of Verkada Water Damage Issues
PoE Budget Exhaustion
Water damage often coincides with PoE budget exhaustion, especially in large deployments. Verify that the switch port’s PoE allocation matches the camera’s requirements (e.g. 15.4W for the CB62 Bullet). If the port shows Class 0, the switch may not support PoE or the camera is misconfigured.
DHCP Scope Exhaustion
Water-damaged cameras may fail to obtain IP addresses if the VLAN’s DHCP scope is exhausted. In Verkada Command, navigate to Network → DHCP Leases and ensure there are available IPs for new devices. Expand the scope or assign static IPs if necessary.
VMS Licensing Conflicts
Water damage may expose licensing issues in the VMS. In your VMS (e.g. Avigilon Control Center), verify the camera’s license is active and matches its stream profile. Re-apply the license if necessary.
UK-Specific Considerations
UK humidity levels (75-85% year-round) increase the risk of water ingress through seals. Ensure cameras are installed with IP67-rated enclosures and weatherproof gaskets. In coastal regions, use corrosion-resistant mounting hardware to prevent long-term degradation.
Prevention and Long-Term Care
Firmware Update Schedule
Schedule regular firmware updates via Verkada Command’s Firmware Management tool. Enable Staged Rollouts to avoid disruptions during updates. Monitor the Bandwidth Monitor to ensure updates do not overload the network.
Network Best Practices
Create a dedicated VLAN for cameras to isolate traffic and reduce conflicts. Apply QoS policies to prioritize video streams and ensure SNMP monitoring is enabled for real-time alerts on PoE or connectivity issues.
Full Disclosure
Full disclosure: we built scOS to address exactly this—the complexity of managing enterprise camera systems. scOS uses permanently powered cameras connected via Ethernet, eliminating reliance on PoE switches and reducing water ingress risks.
Replacement Decisions
Camera Lifespan and Replacement
Wired Verkada cameras (e.g. CD62 Dome) typically last 5-8 years, while battery-powered models degrade after 3-5 years. Replace cameras if troubleshooting exceeds 30 minutes or if hardware failure is suspected. Under the UK’s Consumer Rights Act 2015, you have 6 years to claim faulty goods (5 years in Scotland). Always refer to Verkada’s official support for warranty claims.
UK Procurement Considerations
When replacing cameras, select models rated for IP67 or higher and install them with weatherproof enclosures. Use surveillance-rated HDDs (e.g. WD Purple) for NVRs and high-endurance microSD cards (e.g. Samsung PRO Endurance) for local storage.