Heartbeats

One of the most essential requirements in any IoT application is to ensure that devices are online and functioning correctly. Anedya allows you to send heartbeats from devices and analyze them.

Heartbeat is a simple MQTT or HTTP message that can be sent periodically from the devices. As it does not contain any data, it is pretty lightweight and can be even sent from battery-operated devices without impacting the battery life.

Heartbeat vs Keepalive in MQTT

Please note that heartbeats are not the same as keepalives. Keepalives are used to ensure that the connection between the device and the broker is still alive. Heartbeats are used to ensure that the device is still online and functioning properly.

Anedya processes the heartbeat messages and stores them as a count of heartbeats received in intervals of 5 seconds. Anedya provides a direct visualization of the heartbeat data on the node page.

Heartbeat APIs

Using Anedya's platform API, you can easily get a list of online devices. You can define the threshold for the time interval at which, Anedya considers a device online.

Anedya's Recommendation

We recommend that devices send heartbeats to indicate their normal functioning. If the device is connected to the internet, but not functioning properly due to some other error, a heartbeat should not be sent.

Limits

Anedya stores heartbeat data in the form of counts in intervals of 5 seconds. Any rate that is higher than 1 heartbeat/5 second will be stored as a count. Also, you can send a maximum of 60 heartbeats/minute. At a higher rate, Anedya will drop the heartbeats.

Anedya stores heartbeat data for a period of 6 months.

Pricing

There's no additional cost for heartbeat data storage and access through APIs.