Entryway Sensor Network Requirements
VergeSense entryway sensors use machine learning to anonymously monitor and analyze ingress and egress occupancy of spaces, floors, and buildings in real time. The entryway sensors use IEEE 802.3af PoE protocol over a single ethernet cable to provide the sensor with both power and data. PoE makes the deployment of sensors easy and ensures the most stable and reliable data connectivity. Anonymized occupancy data securely travel outbound across your network to the VergeSense Cloud and then to the Infogrid Platform via API.
Data Flow
Sensors encrypt occupancy data (TLS 1.2) and send it directly to the VergeSense Cloud via your wired network and then to Infogrid via API.
Network Requirements
Sensors are DHCP clients by default.
Sensors initiate communication with the following DNS endpoints, and may receive response traffic (eg. updates, etc). Connections are never initiated inbound from the Cloud to your internal network.
Network Connectivity Safelist
In order to provide connectivity to the VergeSense cloud, and to provide connectivity to network resources for timestamps and serviceability, the following destinations, protocols, and ports should be opened through any corporate firewall tools.
REMOTE HOST | PROTOCOL | PORT | JUSTIFICATION |
Pool.ntp.org 0.ubuntu.pool.ntp.org ntp.ubuntu.com | UDP | 123 | Time server |
* Applicable prior to Fw5.0.4 | HTTPS | 443 | IoT service, AWS API gateway |
TCP | 443 | Encrypted connection over Device Control | |
* Applicable with Fw5.0.4 and later | HTTPS | 443 | IoT service, AWS API gateway |
Safelist changes between firmware versions
The entryway sensors' operating system was re-factored during the transition from Fw4.7 to Fw5.0 resulting in a new data model being transmitted to the IoT Platform. In order to continue supporting EN-1 sensors with either Fw4.x or Fw5.x installed, a new IoT ingestion pipeline was developed and this required a new URL in the safelist. In the likelihood that EN-1 sensors deployed within a customer site have a mixture of Fw4.x and Fw5.x, it is highly recommended that both IoT Service URLs are implemented in a firewall safelist.
Wired Sensor Network Requirements
VergeSense wired sensors have flexible and reliable network configuration options. The Power and Data Over Ethernet option uses IEEE 802.3af PoE protocol over an ethernet cable to provide the sensor with both power and data. PoE makes the deployment of sensors a breeze and ensures the most stable and reliable data connectivity. Simply install the sensor and plug in the PoE ethernet cable.
Data Flow
Each sensor requires a PoE connection (home run to a PoE port)
The sensors collect and process raw data into JSON
JSON file sent from SENSORS to the VergeSense Cloud via ethernet connection to the corporate network
All data in transit is encrypted using TLS 1.2
Network Requirements
DHCP: Dynamic IPs assigned by the network
DNS Safelist, Open port: 443
Dns.google.com
*.amazonaws.com
*.cloudfront.net