I hope all is well,
Thank you for sharing your concerns, we certainly don’t want to be a bump in the road for your IoT initiatives. Let me explain and clarify how the dots out and in consumption works:
Dots in : All the dots received and saved from any channel, Dashboards, and API.
Dots Out : The sum of the dots extracted through two (2) outbound channels.
API : Data requested by external applications or devices from our API. Meaning each value extracted using any of our supported protocols (MQTT, HTTP, TCP/UDP).
Front-end: Data requested by the web interface (Dashboard and devices). This includes all the queries required to render dashboards, CSV reports, variables, etc. Having that in mind, yes refreshing a Dashboard, or exporting data will consume dots out.
The usage is visible in your account profile. The count reset at UTC 00:00, meaning the values of today are the dots out consumption from the day before, we have an internal ticket to modify this behavior and reflect the values of the corresponding day. I will keep you posted on the updates of this ticket.
Additionally, below you can find some of the measures you can take to avoid reaching out to the daily limit.
- Refresh the Dashboards only when necessary.
- Set a short time in the Default time range of the Dashboard, so the first time you open the Dashboard, this one only requests the last data.
- Reduce the frequency of data extraction through API.
Finally, I went ahead and increased your dots out capacity to 400,000 per day, to avoid you hit any limits during your IoT application’s development.
I hope my note clarifies your concerns and let me know if you have additional comments.
All the best,