For some locations the connection with the internet or the capability of the server MMW is error prone.
The result is that a small number of readings are delivered to MMW every POST attempt.
For a site like GV01 or NA13, which have not had their readings delivered for a couple of months, there can be 5000+ readings outstanding.
GV01 was initially set to an update every 60minutes (COLLECT_READINGS=4) and with very poor internet connection, readings very rarely got through.
When the setting was changed to every 15minutes (COLLECT_READINGS=1) it was sufficient for readings to be steadily delivered. However the cost is the extra power.
Similarly Na13, with good solar aspect was set to POST every 30minutes, (COLLECT_READINGS=2, SEND_OFFSET_MIN=4, POST_MAX_NUM=100 ), however it appears errors at the server still only allowed updates very slowly.
Under normal conditions, having a POST attempt every hour does result in power savings, and enables the battery to be fully charged.
However it would be valuable to have a stored queue threshold, that when exceeded would have the POST attempted every reading until complete.
Suggest add
POST_FAST_THRESHOLD=200 ; When 200 readings outstanding, override COLLECT_READINGS logic
When 0 or not present has no effect.
For any flash program updates to the mega1284, this probably requires the onboard EEPROM be updated.
Interacts with COLLECT_READINGS=?
This only has an impact if COLLECT_READINGS is 2 or greater, as effectively over-rides it to attempt to force a POST.
All battery threshold settings still apply.
For some locations the connection with the internet or the capability of the server MMW is error prone.
The result is that a small number of readings are delivered to MMW every POST attempt.
For a site like GV01 or NA13, which have not had their readings delivered for a couple of months, there can be 5000+ readings outstanding.
GV01 was initially set to an update every 60minutes (COLLECT_READINGS=4) and with very poor internet connection, readings very rarely got through.
When the setting was changed to every 15minutes (COLLECT_READINGS=1) it was sufficient for readings to be steadily delivered. However the cost is the extra power.
Similarly Na13, with good solar aspect was set to POST every 30minutes, (COLLECT_READINGS=2, SEND_OFFSET_MIN=4, POST_MAX_NUM=100 ), however it appears errors at the server still only allowed updates very slowly.
Under normal conditions, having a POST attempt every hour does result in power savings, and enables the battery to be fully charged.
However it would be valuable to have a stored queue threshold, that when exceeded would have the POST attempted every reading until complete.
Suggest add
POST_FAST_THRESHOLD=200 ; When 200 readings outstanding, override COLLECT_READINGS logic
When 0 or not present has no effect.
For any flash program updates to the mega1284, this probably requires the onboard EEPROM be updated.
Interacts with COLLECT_READINGS=?
This only has an impact if COLLECT_READINGS is 2 or greater, as effectively over-rides it to attempt to force a POST.
All battery threshold settings still apply.