I intended for it to close and re-open the session every 5 minutes, so I’m not certain why it’s 2 minutes in the screenshot. I’ll have to revisit this.
The only “local event” that comes to mind is a timer, which is how this is implemented now.
These units have been calling
le_avdata_Push() frequently for a long time, so if this supposed to keep things alive and prevent the NAT timeout issues, it does not work.
What “flow” is recommended with the AirVantage data API? I’m not too particular about how this is implemented, but we need to meet the following requirements:
Push data every 5 minutes under normal conditions, or as quickly as possible if a sensor reading exceeds a certain delta (in a similar fashion to this sample code https://github.com/mangOH/RedSensorToCloud)
Receive commands as quickly as possible
Sync down settings as quickly as possible
Based on what I’ve seen so far, this seems feasible if we keep the session alive, but is it feasible to keep the session alive at almost all times? I’m not sure yet, I’ll have to keep testing.
I’m also going to be comparing this to an MQTT based solution (I did a bit of work on the MangOH MQTT client to get it running on the latest firmware). To my understanding, LWM2M/CoAP will use far less data than MQTT, but will this still be the case given how much overhead will be required to keep the session alive?
Thanks again for all the help guys, cheers!