Connection Types
- WiFi (802.11 a/b/g/n/ac/ax)
- Frequency: 2.4GHz and 5.0GHz
- Security: WPA, WPA2 (supports WPA2-PSK authentication)
- Time: Network Time Protocol (NTPv4) configured via DHCP
- DNS
- Density strongly recommends an internal caching forwarding DNS server.
- Internal server IP address should be provided via DHCP (option 6)
- Density recommends devices be configured to access internal DNS servers.
- Density strongly recommends an internal caching forwarding DNS server.
- Proxy - Density devices support HTTP proxies, however we do NOT support SSL inspection.
- Proxies can be configured via Web Proxy Auto Discovery (wpad). DNS and DHCP wpad methods are supported.
- IP Address
- DHCP (recommended)
- Bluetooth 5.3 BR/EDR/LE supported
Unsupported Connection Types
- Captive portal
- WPA2 Enterprise
IP Configuration
Density sensors must be assigned an IPv4 address. Most commonly this is done via DHCP via our Density Spaces mobile app. A DNS server must also be configured.
Network Bandwidth
Density sensors communicate with the Density cloud service and use an average of 1-3 Kbps / per Entry sensor, 5-10 Kbps / per Open Area sensor, 1 Kbps per Waffle sensor.. Please ensure the network being used is able to support this amount of traffic for the number of devices being installed.
Device Updates
Density sensor software is automatically maintained by Density using an OTA (over-the-air) software update system. Density will notify customers when a new update is available and will schedule, perform, and monitor sensor software updates for all online sensors.
Firewall/Whitelisting
Density sensors need to be able to communicate with the following Density services. All communication from Density sensors is outbound, over HTTPS (port 443) unless otherwise specified below. Please whitelist the following services on your firewall:
- *.density.io (port 443)
- *.amazonaws.com
- *.gstatic.com
An Internal DNS server is strongly recommended. If using Public DNS, please ensure the following are whitelisted (optional):
- 8.8.8.8
- 8.8.4.4
An internal NTP server is strongly recommended. For NTP and time synchronization, please ensure the following are whitelisted:
- *connman.net
- *.ntp.org (port 123)
WebSocket Communication
Our sensors utilize WebSocket connections for real-time communication with our cloud infrastructure, securely transmitting data over port 443 with TLS encryption.
Comments
Please sign in to leave a comment.