Hi all. I am developing an IOT solution that uses Tempest as part of the system. These are deployed at remote airfields, some with unmetered Internet connectivity and some are on LTE modems with data caps. I am using the UDP API for my own purposes and am happy to contribute my site data to the Weatherflow network. However, LTE site connectivity is a premium and I can’t let the HUB send data at the rate and frequency it normally uses.
The purpose of my post is to inquire about any existing capabilities with the hub to limit the number of pushes it sends to the cloud.
In my study of the API, I have not seen any references to such a capability so one idea I have is to blackhole the traffic coming from the hub and going to the Internet except for when I want it to send data to the cloud. I think I read elsewhere that the design of the hub is such that it will store readings when Internet connectivity is down and send all the cached data when connectivity is restored. If that’s the case, then my proposal will not work as the data usage will be unchanged.
Ideally there would be an API call that would allow me to configure the hub to send updates on a periodic basis (e.g. once every 15 minutes) and also asynchronously if a measured value changes suddenly (e.g. wind speed and/or direction). In the aviation world, this would mimic the AWOS update cycles, which are every hour unless a special (SPECI) update is required to communicate a dramatic change in the weather.
Thanks for reading and appreciate any insights.