Verkada Air Quality Sensors provide the option to configure/assign a static IP to ensure that your air quality sensor devices maintain consistent network communication without relying on dynamic IP allocation protocols, such as the Dynamic Host Configuration Protocol (DHCP).
Only the SV20 series models support Static IP:
SV21
SV23
SV25
SV25-128
The SV11 does NOT support static IP.
Verkada devices support private IP addresses, as defined in RFC 1918. This means that only private IP ranges specified in the RFC, such as 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16, are compatible with the static IP configuration feature.
Before you begin
To configure a static IP address on a sensor device, it must initially connect to Command and update to the latest firmware using DHCP. Once the update process is complete, the device can receive the new static IP configuration.
Configure a static IP address
Only Site Admins have the ability to enable this feature or modify static IP configurations.
In Verkada Command, go to All Products > Air Quality
.Select a sensor to configure.
In the top right, click Settings
. Under Device > Device IP, click the dropdown and select Manual.
Under Manual, enter the static IP addressing information.
Click Apply to save the configuration. This change is immediately applied to the sensor interface.
Recovery mechanisms
Sensors have a recovery mechanism in case of configuration mistakes or network changes. The device performs the following checks at regular intervals to ensure connectivity. If any of these tests fail, the device falls back to the DHCP operation.
Recovery Mechanism | How to Perform this Task |
On the subnet, verify there is no duplicate IP conflict | Send Address Resolution Protocol (ARP) requests for the configured sensor IP. If the sensor receives an ARP request, the reply it considers it as a duplicate IP conflict. |
Verify there is a default gateway | Send ARP requests for the configured gateway IP. If no reply is received by the sensor, the gateway is considered unreachable. The device on the network with the configured IP of the gateway. |
DNS resolution is operational for Verkada domains | Perform Domain Name Server (DNS) lookups for Verkada domains. In case the device doesn't receive a response from any of the domains, this test fails. |
SSL/TLS sessions can be established with the required endpoints | Send HyperText Transfer Protocol Secure (HTTPS) requests to the Verkada endpoints required for sensor operation. In case the device is unable to perform a Transport Layer Security (TLS) handshake with any of the endpoints, or in case there is any error while performing this handshake, this makes the test fail. |
Endpoints for DNS tests
The following list of endpoints is used for DNS tests, as these are critical for sensor device operation. For a full list of endpoints, see Air Quality Sensor Network Settings.
api.control.verkada.com - TCP/443
relay.control.verkada.com - TCP/443
index.control.verkada.com - TCP/443
firmware.control.verkada.com - TCP/443
update.control.verkada.com - TCP/443
Endpoint for TLS tests
For TLS tests, only the api.control.verkada.com endpoint is used. If the sensor is unable to establish a TLS connection with this endpoint, it falls back to DHCP operation.
Troubleshoot workflow
If the sensor encounters any issues during these checks, it attempts to fall back to its default DHCP operation and perform the connectivity tests listed above.
If the DHCP connection fails, the sensor retries using the static IP configuration.
If the sensor again fails to connect using its static IP configuration, it alternates between static IP and DHCP operations in exponential backoff increments, ranging from 20 seconds up to 1 hour.
If the sensor successfully connects to Verkada Command using DHCP, it continues to operate on DHCP until it is rebooted—via Command or by power cycling the sensor.
Bulk configuration for static IP addressing is not supported for sensor devices.
Need more help? Contact Verkada Support.