...
Currently the Flow Gateway V3 only utilizes the following traffic flows:
Direction of Connection (from flow gateway) | Remote Endpoint FQDN | Protocol | Port | Purpose/Notes |
|---|---|---|---|---|
Outbound | HTTPS (HTTP+TLS via TCP) | 443 | Firmware Updates to Device (device makes a request to this endpoint, to download a firmware binary from the Flow Servers (the specific file URI to download is sent to the device via MQTT control stream over an authenticated and encrypted channel, and will change with each version) | |
Outbound | MQTT+TLS via TCP | 8883 | Bi-directional MQTT stream between the device and the Flow Cloud Platform. This is established as an outbound connection, and is authenticated and encrypted, allowing bi-directional communication including:
| |
Outbound | pool.ntp.org (though eventually will support local DHCP configured ntp server) | SNTP via UDP | 123 | The device synchronizes it’s internal clock to an NTP source. Currently in the prototype firmware this is using the public ntp pool servers, however in the final mass production firmware it will pull the NTP configuration via DHCP if it exists, and use the configured NTP Server address provided. If none is provided, it will fall back to using the public pool server. NTP is crucial to allow the device consistant and accurate timekeeping in order to appropriately attribute sensor readings in transmission back to the cloud. |
Outbound | diagnostics.iot.flowcoffee.co.nz | HTTPS | 443 | Network diagnostic endpoint to allow the Flow Gateway to discover its public IP address |