I wouldn’t recommend that config for a battery-powered tracker
but while testing it’s fine. And you’re correct, with heartbeat:true
and hours:1
you’ll always get an event at least every hour. Also the sync:true
parameter will immediately sync any new tracking data instead of waiting for the next periodic cellular sync (again, good for testing, not great for battery life!).
Also, a little tip if you’re building a tracker without a host MCU. You may want to look into the event data itself to see if you’re gathering GPS location data or not. For instance, with a tracker solution I built, here is an example of an event that was not able to get a GPS fix:
"body": {
"status": "heartbeat",
"temperature": 26.3125,
"voltage": 4.0976562
},
"best_location_type": "tower",
"best_lat": 3.4645875,
"best_lon": -76.531921875,
"best_location": "Cali region",
"best_country": "CO",
"best_timezone": "America/Bogota",
"tower_when": 1635020330,
"tower_lat": 3.4645875,
"tower_lon": -76.531921875,
"tower_country": "CO",
"tower_location": "Cali region",
…versus when I was able to get a GPS fix:
"body": {
"hdop": 2,
"status": "heartbeat",
"temperature": 23.5,
"time": 1637742502,
"voltage": 3.9726562
},
"best_location_type": "gps",
"best_lat": -15.474297499999999,
"best_lon": 28.39407421875,
"best_location": "Lusaka",
"best_country": "ZM",
"best_timezone": "Africa/Lusaka",
"where_olc": "5GPCG9GV+7JP3",
"where_lat": -15.474297499999999,
"where_lon": 28.39407421875,
"where_location": "Lusaka",
"where_country": "ZM",
"where_timezone": "Africa/Lusaka",
"tower_when": 1637936607,
"tower_lat": -15.468895,
"tower_lon": 28.388693,
"tower_country": "ZM",