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.

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.

Sensors must be assigned an IPv4 address to communicate on the LAN and to Verkada Command. Intercoms use Dynamic Host Configuration Protocol (DHCP) and User Datagram Protocol (UDP) to obtain their IP addresses and network configurations.

If you require your sensor to have a specific IP address, create a DHCP reservation using the device’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.

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.

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:

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.

Need more help? Contact Verkada Support