I ask myself about how the BLYNK library manage the communication between hardware and server.
It’s important to understand the behavior of the project when the hardware lost connection.
Do we lost the hardware measurements/data or is there retries untill the connection is retreived?
On the other side, do we lost the server commands or is there retries untill the connection is retreived?
I work on monitoring systems in my job, such as SNMP on which I can choose timeout time for a request, number of retries if request fails…
So I think there is same seups in the BLYNK library.
A pratical example: my system send a a mail if a event occurs on my hardware. What happens if my hardware is offline a while just before the event? The mail is sent as soon as the hardware goes online, or the mail is lost?
Any data collected in the interim would probably be lost… depending on the initial connection method, Blynk.begin() or Blynk.config()… in the former, the device will stop running the code until reconnect (generally automatic), so no data collected. In the latter, if coded so the the sketch keeps running (and keeps trying to reconnect), then unless it is somehow buffered in code, it too will simply spit out data to nothing, until point of reconnection.
Thank you for help.
I tested today and the notifications and data are well lost if disconnection happens.
No matter the datas, but notifications are critical for my project.
I’m going to improve reliability by using connection management functions.