AAPS treatements has a strange date in the future

nightscout / AndroidAPS

Opensource automated insulin delivery system (closed loop)

https://wiki.aaps.app

GNU Affero General Public License v3.0

724 stars 1.76k forks source link

AAPS treatements has a strange date in the future #1421

Closed robertrub closed 2 years ago

robertrub commented 2 years ago

EDIT : This is NOT an NS problem as I started issuing. It is about a strange date in AAPS treatments. You can skip the first messages...

I use BYODA and G6 sensor. I Stop sensor and then Start new sensor in BYODA. This information arrives and is treated correctly in AAPS. I can see sensor age in AAPS.

The bug is (maybe) in the way this information (new sensor insertion/start) is sent to NS by AAPS. The sensor inserted message is on the treatments tab of NS but NS doesn't show SAGE data.

People seem to have the SAGE working in NS if they note the sensor change in AAPS. In my case, the sensor change information arrives from BYODA to AAPS.

robertrub commented 2 years ago

I might have found the culprit. This had happened before. The CGM change date is totally wrong in treatments in AAPS...

And here is the real sensor change date from BYODA.

Screenshot_20220308-193802_Dexcom G6.jpg

Sorry, no logs :(

robertrub commented 2 years ago

It is becoming more and more strange...

AAPS has the real insertion date too. I don't know from when the 2106 entry dates...

I can't delete the 2106 entry, it says invalid after I tried to delete it...

CaptainBalou commented 2 years ago

Same entry for the same date here... I can't see the year but because it is on the top of the list I assume it is in the future and so it would be the same.

Screenshot_2022-03-08-20-43-35-90_3eaa31bb2c2a38a1c605d9dc918cf694 Screenshot_2022-03-08-20-44-13-99_3eaa31bb2c2a38a1c605d9dc918cf694

robertrub commented 2 years ago

@CaptainBalou Funny, it is the same exact date as mine... Even the same time stamp ! It is not something that came from BYODA most probably but where did AAPS get this entry is a mystery...

CaptainBalou commented 2 years ago

@robertrub Yes, just because it is a full match I decided to write that comment. :-) I also use BYODA. Unfortunately I have no suggestions what the issue could be. Just wante to tell that you're not alone with this. ;-)

Alamo04 commented 2 years ago

Had the same in the past, deleted this entry in AAPS and it comes back, again deleted and also deleted all future treatments in NightScout. This issue didn't come back since that.

kristinsmotz commented 2 years ago

I have seen this as well a few weeks ago, definitely year 2106, don't remember exact date. Also resolved it by deleting future treatments in Nightscout Admin tools.

happygirlnyc70 commented 2 years ago

I also had the future entry. I removed it from the treatment tab. Nightscout resolved itself at my next sensor change. Using dev-e.