This article outlines the required settings that your Verkada Air Quality Sensors ("sensors") need to communicate with Verkada Command and to operate properly.
Requirement: Verkada devices are incompatible with LANs that require the use of proxy servers or that require Secure Socket Layer (SSL)/Transport Layer Security (TLS) inspection. If either are in use, a bypass for all Verkada devices must be implemented for Verkada devices to communicate with Command.
Status LED
A flashing white or flashing blue status LED on the front of the sensor indicates the sensor is not communicating with Verkada Command. If you see this behavior, check that the network is set up correctly for the sensor's requirements.
If the problem persists, contact Verkada Support.
When sensors are offline, alerts/events do not trigger. They continue to record measurements and sync with Command once they reconnect.
Power
Sensors are powered through Power over Ethernet (PoE). The sensors need to receive power from the network switch they are connected to, or through a PoE injector. See the 1st gen or 2nd gen datasheets for the PoE spec your Verkada sensor requires.
IP address
Sensors need an IPv4 address to communicate to Command through the internet. Sensors use Dynamic Host Configuration Protocol (DHCP), User Datagram Protocol (UDP) ports 57 and 58, to obtain their IP addresses and network configurations.
If you want to have a specific IP address on your sensor, set a DHCP reservation using the sensor’s Media Access Control (MAC) address (found on the device's label).
Domain Name System
Sensors use the DNS server to resolve Verkada’s fully qualified domain names (FQDN) to IP addresses to communicate with them. Your DHCP server tells the sensor where the DNS server is on the network and the sensor communicates using UDP port 53.
Note: DNS over HTTPS (DoH) is currently not supported.
Firewall settings
Verkada devices require access to many endpoints to have the full-featured experience. Many customers may want to restrict devices to only communicate with the specific required endpoints.
These are the general domains to allow, applicable for all organization-regions:
*.verkada.com - UDP/123 + TCP+UDP/443
34.216.15.26 - UDP/123
If your firewall does not allow wildcard masking, or you prefer to have the entire FQDN of the endpoint in your firewall rules, these are the domains to allowlist, by region:
Region: United States
Note: Your region is selected when you create an organization in Command.
vsensor.command.verkada.com - TCP+UDP/443
vconductor.command.verkada.com - TCP+UDP/443
api.global-prod.control.verkada.com - TCP+UDP/443
relay.global-prod.control.verkada.com - TCP+UDP/443
vconductor.global-prod.command.verkada.com - TCP+UDP/443
api.control.verkada.com - TCP+UDP/443
relay.control.verkada.com - TCP+UDP/443
index.control.verkada.com - TCP+UDP/443
firmware.control.verkada.com - TCP+UDP/443
update.control.verkada.com - TCP+UDP/443
time.control.verkada.com - UDP/123
user.pyramid.verkada.com - TCP+UDP/443
device.pyramid.verkada.com - TCP+UDP/443
nlb.verkada.com - TCP+UDP/443
device-nlb.verkada.com - TCP+UDP/443
34.216.15.26 - UDP/123
Region: Europe
Note: Your region is selected when you create an organization in Command.
vsensor.prod2.command.verkada.com - TCP+UDP/443
vconductor.prod2.command.verkada.com - TCP+UDP/443
api.global-prod.control.verkada.com - TCP+UDP/443
relay.global-prod.control.verkada.com - TCP+UDP/443
vconductor.global-prod.command.verkada.com - TCP+UDP/443
api.prod2.control.verkada.com - TCP+UDP/443
relay.prod2.control.verkada.com - TCP+UDP/443
index.prod2.control.verkada.com - TCP+UDP/443
update.control.verkada.com - TCP+UDP/443
vconductor.prod2.command.verkada.com - TCP+UDP/443
time.control.verkada.com - UDP/123
Related resources
Video Security Network Settings (Cameras)
Workplace Network Settings (Guest, Mailroom)
Visit the Verkada Training Center for bite-sized video tutorials on how to accomplish role-based tasks in Command.
Need more help? Contact Verkada Support