Protocols, Ports and Endpoints
We highly recommend making internet access to our hardware as open as possible for convenience, as requirements will change in future. We endeavor to keep these changes to a minimum, but we rely on third-party vendors so some changes are beyond our control.
Below are detailed minimum requirements which currently work for each Layer 3 device in an XY Sense installation.
Area Sensor
All connections are initiated by the sensor outbound to the XY Sense platform.
| Application | Transport | Port | Endpoint | Purpose |
| MQTT | TCP | 8883 | a3iun0ocnfkxx9-ats.iot.ap-southeast-2 .amazonaws.com |
Endpoint for sensor connectivity |
| NTP | UDP | 123 |
time1.google.com time2.google.com time3.google.com time4.google.com |
Time server Note: these default servers can be overridden by the customer via DHCP in some topology configurations |
| HTTPS | TCP | 443 | core-api.app.xysense.io | Configuration |
| HTTPS | TCP | 443 |
hosted.mender.io c271964d41749feb10da762816c952ee api.memfault.com ota-cdn.memfault.com |
OTA Update |
| DNS | UDP and TCP | 53 | Default DNS server provided by your network to DHCP clients. |
Entry Sensor
All connections are initiated by the sensor outbound to the XY Sense platform.
| Application | Transport | Port | Endpoint | Purpose |
| HTTPS | TCP | 443 | xovis.cloud | Connection to Remote Management Server |
| NTP | UDP | 123 | time1.google.com | Time Server |
| HTTPS | TCP | 443 | in.app.xysense.io | HTTPS data push to XY Sense Server |
| HTTPS | TCP | 443 | iot.xovis.com | Entry sensor update server |
| HTTPS | TCP | 443 | hub.xovis.cloud | New Connection to Remote Management Server replacing the above xovis.cloud in the future |
Primary Hub (with Internal Router; Layer 3 Device)
In this situation we highly recommend opening all ports and protocols on the specified endpoints, particularly for rms.teltonika.lt and 3.69.106.81
| Application | Transport | Port | Endpoint | Purpose |
| DNS | UDP and TCP | 53 | Default DNS server provided by your network to DHCP | The hub will use this for it's own DNS resolution, and that of the sensors connected to it |
| Ping | ICMP | N/A | 1.1.1.1 | Used for checking the health of the internet connection. |
| NTP | UDP | 123 |
0.pool.ntp.org 0.openwrt.pool.ntp.org 1.pool.ntp.org 1.openwrt.pool.ntp.org |
Time Server |
| HTTP (over SSH) | TCP | 20080 | 18.192.27.240 | WebUI remote configuration access. |
| SSH | TCP | 20022 | 18.192.27.240 | Remote reverse SSH tunnel. Remote management. |
| TCP |
15010, 15011, 15009, 15039, 15040, 15041-15100 |
rms.teltonika.lt | Health analytics and remote management | |
| OPENVPN | UDP | 30000-39999 |
3.69.106.81 3.65.167.143 |
Remote management of the hub and install |
Estimated Data Usage
Area Sensor
| Purpose | Application | Frequency | Estimate Data Usage |
| XY Coordinate Messages | MQTT | Every 2 seconds |
500KB to 1000KB per hour Depending on amount of sightings |
| XY Diagnostic Messages | MQTT | Every 30 minutes | 1KB - 2KB per hour |
| XY Configuration Messages | MQTT | Every hour | 1KB - 2KB per hour |
| Connectivity check | ICMP | Every 5 minutes | 2KB per hour |
| Time server sync | NTP | Every minute | 10KB per hour |
| Sensor configuration download | HTTPS | Once per day |
10KB per day |
| OTA Update Poll | HTTPS | Every 30 minutes | 20KB per hour |
| OTA Update Download | HTTPS | Once a month | 30MB per month |
| Estimated Monthly Total | 405MB to 760MB per month | ||
Entry Sensor
| Purpose | Application | Frequency | Estimate Data Usage |
| Connection to WebUI over remote connection | HTTPS | Adhoc / every login | 1mb per connection |
| Line count event | HTTPS | Every event |
~2kB per event ~400KB per 200 people |
| Remote connection heartbeat | Every hour | 2KB per hour | |
| Time server sync | NTP | Once every 5-10 min | 10KB per hour |
| OTA Update Download | HTTPS | Once a month | 30MB per month |
|
Estimated Monthly Total1 1 Based on 200 people per day |
250MB to 300MB per month | ||
Comments
0 comments