This article outlines the required settings that your Verkada Air Quality Sensors ("sensors") need to communicate with Verkada Command and to operate properly.

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.

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.

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).

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.

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:

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:

Need more help? Contact Verkada Support