Automatically translate this page?

How to control my account’s limitations?

Getting the state of all flespi platform elements in your account.

Both free and commercial accounts have usage restrictions. The overflow of limits can lead to the suspension of the platform instances or ignoring new incoming messages. There are several ways to control the limits. 

UI indicators

The flespi panel features a dashboard with gauges and bars showing each platform element use. 

flespi panel dashboard

When you open any instance in the flespi panel, it will display limits at the top. A disabled instance is lighted in red:

flespi disabled instance

API tools

Limits control can be automated with flespi API GET statistics request. 

The same info can be received via MQTT on the subscription to the topic flespi/state/platform/customer/counters/#.

Each time the usage values change, MQTT client will receive an appropriate message. See the full specs of possible topics in flespi/state in the table below:


module-name/


instance-type/instance-id/

property-name/

required

optional

platform#

gw

channels

id

name

commands_ttl

configuration

enabled

messages_ttl

protocol_id

URI

blocked

commands_size

connections_count

messages_size

devices

id

name

device_type_id

ident

messages_ttl

phone

telemetry

messages_size

connected

streams

id

name

configuration

enabled

queue_ttl

queue_size

connected

modems

id

name

configuration

enabled

priority


storage

containers

id, flags, name

blocked, size

abques

id, name

blocked, size

CDNs

id, name

blocked, size

There's an nice and visual way to see all available flespi/state options with MQTT Board. Create a connection to the flespi MQTT broker, add a Flespi Subscriber and play with the switches in the offered dialog to pick the exact info you want to see:

flespi state in mqtt board

Useful tips

To reduce the total amount of storage consider lowering the messages_ttl parameter as devices have biggest amount of data for the longest possible period available. Device messages buffer is tuned to be automatically cleared once per 24 hours (so once the messages_ttl parameter has been lowered one should expect the total amount of storage reducing in the upcoming 24 hours period).


See also
The guide on how to set up a calculator to receive live customizable MQTT messages when device parameters change according to a complex condition.
Sample scripts to deploy on your server to receive the telemetry data from the flespi platform.