can be possible to convert this reconnection time with an “antiflood like” system?
'cause a battery powered system need 1 connection at xx minutes to make a low energy purpose, instead of a “normal” system that turn on and stay on…
can be possible to convert this reconnection time with an “antiflood like” system?
'cause a battery powered system need 1 connection at xx minutes to make a low energy purpose, instead of a “normal” system that turn on and stay on…
Battery powered systems are recommended to use our HTTP API
I’ve written another code for my project, it uses HTTP API but, I think there is no way to update “last seen” section via HTTP API. Device seems always offline. Is there anyway?
What exactly?
I’m talking about this
What is “last seen” section?
The hardware online status always reads offline because it technically isnt actively connected to the Blynk server… I think he’s asking for a way to ignore the hardware is offline popup in the app by sending an HTTP REQ
No. And I don’t understand why would you want to do that .
Me neither, for a “low power system”.
Because it will be useful to see when the hardware updated the virtual pins.
If you want to know what is happening look at the project via the http API.
Oh, I see. I think that in exactly this case opening Blynk connection is preferable. @vshymanskyy let’s discuss this.
perfectly right