Hi there,
I also am testing the LTE Beacons, and have a different issue. I’ve found with the new firmware (0.0.7) it does the GPS fix properly with just line of sight from a window. My issue is that they don’t reliably continue to report position after some time, without a reset.
I have a block of code like the following:
var reportingInterval = 600;
var reportingDistance = 150;
var reportingTimeout = 0;
location.startUpdates((position) => {
if (position.lat && position.long) {
lastPosition = position;
print("Handling Position Update.. " + new Date() + " at " + position);
sendReport();
} else {
print("Skipping distributing position update since GPS not found.");
}
}, {minInterval: reportingInterval, minDistance: reportingDistance, timeout: reportingTimeout });
This code calls a function to report, and should do it with the minInterval while stationary, so I would expect every 10 minutes / 600 seconds. What I see is that it does this reporting for a while and then stops.
At the same time, with the minDistance set, my understanding is that it should report when I’ve moved that far, so in this case 150m. Again, it seems to do this report for a little while and then stop once again.
Now in my test application, I made a long press handler that stops the location subscription (and turns off LTE) and then pressing it again will re-enable this and start the location monitoring. This seemed to kick the location back in again and started returning updates, at least for a little while.
Looking at last night, between midnight and around 7AM the beacon stopped reporting, and then started again without any intervention. This seems almost like the pausing issue on the early firmware, where the device would become unresponsive for hours at a time, and then return to service.
I also tried one thing, which was to stop the location monitoring in the location callback/promise, and then restart it. That didn’t seem to make a difference.