Currently, our devices only support 2.4GHz. If you are trying to provision a sensor to a 5GHz network using the Density Unit Setup App, it will not connect.

Please make sure to review the following:

• You have entered the SSID and Network password correctly.
•  You are connecting via DHCP unless IT requests otherwise.

Yes, you can absolutely deploy on a VLAN — though this is not required.

Yes, Density devices work with 4G network cradlepoints. This involves additional deployment costs. If this is required for your deployment, our Sales and Implementation team will work to scope out the best approach. Density has established relationships with enterprise 4G vendors.

To ensure every device has the latest capabilities and most recent security enhancements, Density pushes firmware over-the-air (OTA) updates on a regular basis. The sensors check in to the Density update server periodically. All communication with the update server is via HTTPS.

To ensure firmware authenticity, the update server authenticates the sensor and provides the sensor with a time-limited HMAC-signed URL on AWS Simple Storage Service (S3) with the update, as well as a hash signature of the update. Updates are always a whole OS-image.

In addition, to ensure seamless firmware updates each device has a dual partitioned firmware bank with automatic failover. Details:

The device has an active and standby root partitions.

The active root partition in production sensors is always read-only.

The sensor downloads the update image to the standby partition, verifies its integrity, and then reboots with a boot flag to use the new partition.

In the unusual case that an update were fails, the sensor will automatically revert to the working partition. Our Ubuntu application servers have unattended / automatic upgrades. We have established an automated immutable infrastructure process by which major updates to the Ubuntu image are saved to an AWS AMI and the new base image is rotated throughout the cluster.

Density releases automated firmware updates on a monthly basis, ensuring that your devices have the latest capabilities and most up-to-date security enhancements. These automated updates typically consume around 60 MB per device, per month, and are included as part of your Density subscription. Security updates are pushed outside scheduled firmware releases as needed.

To ensure high data accuracy, Density conducts periodic data audits, which amount to approximately 80 MB per device, per month. During these audits, the sensor sends raw depth data files to its cloud service, which is then analyzed manually by the Density team to train our machine learning algorithms. Because Density’s technology is anonymous by default, at no point during any of these audits is personally identifiable information processed available.

Note that the amount of data used during an accuracy audit may be higher than 80MB during an initial calibration period after the installation, during which the device’s algorithms are initially trained and configured for accuracy in each particular doorway. During the calibration period, bandwidth consumption may vary based on variables such as amount of foot traffic and network environment.

Density’s sensors were designed to support enterprise deployments, making it easy to put many devices on your corporate local area network (LAN). In a steady state, the sensor utilizes approximately 35 kpbs for an average of about 50 MB per 24 hour period.

If you’re planning to run the sensors on a cellular network for connectivity we recommend a plan with 2GB / month / sensor.

To ensure Density devices can communicate with Density services, please whitelist following domains:

*.density.io

*.s3.amazonaws.com

*.pool.ntp.org (if applicable)

Connman.net

Connectivitycheck.gstatic.com

8.8.8.8 (if applicable)

8.8.4.4 (if applicable)

We do not currently support IPv6. However, our API is dual-stack IPv4/IPv6, and we can provide support IPv6 on the device if required.

The sensor communicates with the Density API, hosted on Amazon Web Services (AWS). All communication from the sensor is encrypted via TLS. The sensor uses HTTPS only (on port 443) and communicates with a limited number of subdomains under *.density.io.

Sensors download updates via signed URLs on AWS Simple Storage Service (S3).

If a sensor does not come online after attempting setup using the Unit Setup app (Android version), check the following:

1. Verify it has have power

• Sensor is plugged in and LED light is on at front of device.
• If not, then it is not receiving power or connectivity. Plug in device.

2. Verify it has IP address and network configuration, can access DNS, and can communicate with the internet

• Use the Unit Setup app to scan for the device, select Validate > Run validation.
• This will provide a high level of Network Details > Gather Network Info to download network information to help inform potential network issue. Information automatically and securely sent to Density.

3. If you see a eth0 MAC Address, validate if it is a DHCP issue (most likely issue)

• If you see that you are not connected to the internet, but can see switch information, follow these recommended steps.

1. Check that the device is on the expected port
2. Check what subdomain they’re on
3. Check what network they’re on
4. Check the VLAN
5. Verify the packets are making it to the router
6. Verify DHCP is available for VLAN/Subnet
7. Verify DNS configuration is correct
8. Verify ACLs are correct based on network config
9. Power cycle device

4. If you do not see a mac address for eth0 and no communication with the switch

Verify that port on the switch is active

Verify the switch can see the device mac address

Verify link rate on the switch

Plug the sensor into a known good port to verify the sensor is functional

If it comes online, plug the sensor back into its original port using a new cable. If it comes online, then the cable is faulty.