Flow Gateway V3 Network Requirements

Created by Paul Mumby, Modified on Mon, 15 Jul, 2024 at 2:48 PM by Paul Mumby

Outbound access required by Flow Gateway

Direction (from flow gateway)	Remote Endpoint FQDN	Protocol	Port	Purpose/Notes
Outbound	http-ota.iot.flowcoffee.co.nz	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.iot.flowcoffee.co.nz	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: Command & Control Firmware Updates Monitoring / Device Health Checks Transmission of Coffee Extraction Data to the cloud for processing.
Outbound	diagnostics.iot.flowcoffee.co.nz	HTTPS (HTTP+TLS via TCP)	443	Device fetches some information from our cloud which is used to aid in the diagnostics process (networking latency, geolocation, etc)
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.