Nightscout : missing BGs

nightscout / AndroidAPS

Opensource automated insulin delivery system (closed loop)

https://wiki.aaps.app

GNU Affero General Public License v3.0

685 stars 1.67k forks source link

Nightscout : missing BGs #2938

Closed robertrub closed 10 months ago

robertrub commented 10 months ago

Not sure if it is a NS or AAPS bug... Using last Dev for both. In AAPS, NS is set to update only when charging. Usually, when charging the last BGs are filled up. They are no more filled. There are holes in the BGs on NS

Trying a full resync of NS in AAPS. 350k entries to update...

robertrub commented 10 months ago

I see this alert on my NS. I don't know if it's related and why there was this alert.

Full resync is uploading ok for the moment.

MilosKozak commented 10 months ago

without logs i cannot resolve anything

robertrub commented 10 months ago

After a full resync, the holes are there.

Sorry for the logs. Here they are

AndroidAPS_LOG_1697634941992.log.zip

You have the approximate times on the graph.

robertrub commented 10 months ago

It looks like AAPS is uploading only during in charge but doesn't fill up the past BGs.

Setting is G6 to xDrip to AAPS. AAPS does the BG upload to NS.

robertrub commented 10 months ago

More info : When I set xDrip to upload to NS and to fill in the past 48h, all the holes are filled up.

MilosKozak commented 10 months ago

I need logs 8-10AM

robertrub commented 10 months ago

Sorry, bizarre but I have a huge hole in the logs too. I'll recreate the situation and will come with newer logs.

robertrub commented 10 months ago

Ok, advancing :) Might be related to the token.

There was a hole while I was walking. Once back home, I connected to the charger. Couldn't read on the NS tab as it goes very fast. Once the queue was at zero, I looked at my NS page and saw that 1/ there are missing BGs 2/ there is also a connection alert 1 min ago.

I think that when AAPS reconnects there is a handshake problem. Don't know why AAPS doesn't send (or NS doesn't receive) some BGs.

The logs. Look around 17:20

AndroidAPS_LOG_1697642531984.log.zip

MilosKozak commented 10 months ago

if you are using v3 nothing else using v1( xdrip) must upload to NS

robertrub commented 10 months ago

Till the "bug" only AAPS was uploading to NS and via API V3. I used xDrip and v1, just to fill in the holes after the bug.

MilosKozak commented 10 months ago

Around 17.20 there are upload errors caused by using xdrip uploads before

robertrub commented 10 months ago

Yes possible as I had used xDrip just before testing to fill in the holes.

Just tested now again (no xDrip connection for hours) but still not uploading.

Will build again and test tomorrow with your last commit on NSCV3 start.

robertrub commented 10 months ago

@MilosKozak Sorry but your last commit did not solve the problem of filling the past BGs. No xDrip/V1 connection for over 18 hours.

Look around 9:56 when I reconnected the phone to the charger.

AndroidAPS_LOG_1697875146048.log.zip

Seems like this time, there are no more the connection errors alerts I had on my NS page. So the commit solved one problem for sure 😃

MilosKozak commented 10 months ago

i see data properly uploaded to NS but i see errors like HTTP FAILED: java.io.IOException: unexpected end of stream on ... which are related to your NS instance

robertrub commented 10 months ago

I see that NS Master reverted and updated to 15.0.1 Will update my NS and check again. BBS

robertrub commented 10 months ago

Ok, I'm back to NS v15.0.2 Dev.

Good news : the missing BG backfill was a NS bug. Now, when on charge, AAPS is backfilling the BGs. There are no more holes.

The less good news : I got the Failed authentication error on my NS page when AAPS connected :( But the data got updated anyway. I don't know if this is a NS or AAPS bug...

Maybe we can close this issue and keep an eye on the Failed auth error problem later in another issue.