This article outlines the required network settings that your Verkada Air Quality Sensors ("sensors") need to communicate with Verkada Command. For more information on the required network settings for other Verkada product lines see Required Network Settings.
Verkada devices are incompatible with LANs that require proxy servers or Secure Socket Layer (SSL)/Transport Layer Security (TLS) inspection. If either is in use, a bypass for all Verkada devices must be implemented for Verkada devices to communicate with Verkada 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 with 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.
IP address
Verkada Air Quality Sensors must be assigned an IPv4 address to communicate on the LAN and to Verkada Command. Verkada sensors use Dynamic Host Configuration Protocol (DHCP) and User Datagram Protocol (UDP) to obtain their IP addresses and network configurations.
If you want to have a specific IP address on your sensor device, you can:
Set up a static IP address through Command for SV20 series sensors (SV21, SV23, SV25)
Set a DHCP reservation using the device's Media Access Control (MAC) address (found on the device's label or in Command).
To configure a static IP address on a sensor device, the device must initially connect to Command and update to the latest firmware using DHCP. Once the update process is complete, it will have the ability to receive the new static IP configuration.
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.
DNS over HTTPS (DoH) is currently not supported.
Power
Sensors are powered through Power over Ethernet (PoE). This means the network switch needs to provide power to the sensor, or a PoE injector needs to be utilized. For specifics on power requirements, see the 1st generation and 2nd generation sensor datasheets.
Network Time Security (NTS)
SV20 series sensors can use Network Time Security (NTS) which uses a Secure Socket Layer (SSL) for secure time synchronization, unlike NTP. We recommend you exempt these connections from SSL decryption policies.
Firewall settings
Sensors require access to many endpoints to ensure they can communicate with Command and all features will be accessible. Many customers may want to allow the sensors to communicate with the general required endpoints.
These are the general domains to allow, applicable for all organization-regions:
34.216.15.26 - UDP/123
*.verkada.com - UDP/123 + TCP+UDP/443
time.cloudflare.com - TCP/4460 + 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, you can add the domains to your allowlist based on the region your devices are in.
Your region is selected when you create an organization in Command.
Region: United States
34.216.15.26 - UDP/123
api.control.verkada.com - TCP+UDP/443
api.global-prod.control.verkada.com - TCP+UDP/443
device-nlb.verkada.com - TCP+UDP/443
firmware.control.verkada.com - TCP+UDP/443
index.control.verkada.com - TCP+UDP/443
nlb.verkada.com - TCP+UDP/443
relay.control.verkada.com - TCP+UDP/443
relay.global-prod.control.verkada.com - TCP+UDP/443
time.control.verkada.com - UDP/123
update.control.verkada.com - TCP+UDP/443
vconductor.command.verkada.com - TCP+UDP/443
vconductor.global-prod.command.verkada.com - TCP+UDP/443
vsensor.command.verkada.com - TCP+UDP/443
time.cloudflare.com - TCP/4460 + UDP/123
Region: Europe
api.global-prod.control.verkada.com - TCP+UDP/443
api.prod2.control.verkada.com - TCP+UDP/443
index.prod2.control.verkada.com - TCP+UDP/443
relay.global-prod.control.verkada.com - TCP+UDP/443
relay.prod2.control.verkada.com - TCP+UDP/443
time.control.verkada.com - UDP/123
update.control.verkada.com - TCP+UDP/443
vconductor.global-prod.command.verkada.com - TCP+UDP/443
vconductor.prod2.command.verkada.com - TCP+UDP/443
vsensor.prod2.command.verkada.com - TCP+UDP/443
Region: Australia
api.global-prod.control.verkada.com - TCP+UDP/443
api.prod-ap-syd.control.verkada.com - TCP+UDP/443
index.prod-ap-syd.control.verkada.com - TCP+UDP/443
relay.global-prod.control.verkada.com - TCP+UDP/443
relay.prod-ap-syd.control.verkada.com - TCP+UDP/443
time.control.verkada.com - UDP/123
update.control.verkada.com - TCP+UDP/443
vconductor.global-prod.command.verkada.com - TCP+UDP/443
vconductor.prod-ap-syd.command.verkada.com - TCP+UDP/443
vsensor.prod-ap-syd.command.verkada.com - TCP+UDP/443
Need more help? Contact Verkada Support.