Closed poml88 closed 1 month ago
It reads all data starting from the last item already read today:
So normally It should catch up all missed data.
Hm, ok, well, it doesn't. :)
Would expect that you had some broken data so it could read only some values. As soon it has one value retrieved, it won't catch up older ones. Could be a manual measurement as well.
Hm... Well, it happens everytime after network interruption. Maybe it depends on how the data is inserted into NS. So if network comes back, maybe first the libre3 will send the most recent value to LLU, which is then uploaded into NS. NG sees that and downloads it. Then the libre3 will send the historical data to LLU and they are added to NS. But NG "thinks" it is already at the latest data. Something like this...
Yes - that would explain it. And maybe why I didn't recognize this. I'm using xdrip to catch and upload the bg values. This could be the reason also, why some people experience missing values in uploaded healthkit data.
You can simply verify this thesis by removing the optimization and get always the data starting from midnight. You will get duplicates, but shouldn't experience any more gaps.
Is there any specific reason, why NG is not pulling past data from NS if there has been no network for a while? The data in NS is there, NG just seems to care about the current value(s). I'll attach some screen shots.