Temporary basal history disappears (NS 15.0.2 + AAPS 3.1.0.2)

[ireneusz-ptak]

Describe the bug Not sure if it's a NS or AAPS problem. It seems that (some) temporary basal changes disappear from NS when new data arrives.

You may see it on screenshots - between 20:15 and 20:30 a 0% basal is shown, when the percentage changes to 200% the previous entry disappears. What's worse is that it doesn't always happen and I'm not yet sure what is the key here (just switched to NS 15 and AAPS 3.2).

Expected behavior Proper temporary basal displayed.

Screenshots

Your setup information NS 15.0.2 (docker) AAPS 3.1.0.2 (NSClientV3 + websockets)

[ireneusz-ptak]

@bewest - I haven't seen anyone else reporting it, might be introduced in 15.0.2?

[ireneusz-ptak]

I've just reverted to 15.0.1 and the basal history is back. EDIT: It came back, but the issue is still happening (on 15.0.1)

[olorinmaia]

Experiencing same issue. AAPS 3.2 and NS 15.0.2. Following. Using NSClientV3 + websockets on.

[olorinmaia]

Some further testing show that basalhistory with NSClientV1 sync is OK but NSClientV3 it's not 100% right back in history.

@bewest & @MilosKozak will this be fixed when NS15 internally support v3api or is it something else causing this?

AAPS 3.2.0.1-dev Build: ddc643b83a-2023.10.31 Nightscout-versjon: master 15.0.2

Screenshot NS:

AAPS 3.2.0.1-dev: Logs AndroidAPS_LOG_1698791493172.log.zip NS-server-log.txt

[jimk9]

I have similar issue. Pics of graphs in aaps and nightscout attached as well as pics showing treatment tab. AAPS has 0 temp basal. nightscout shows basal for that time. 3.2.0.1 15.0.2 Uploads only from AAPS using V3

[jimk9]

@ireneusz-ptak Just checked the treatment report in nightscout and compared with treatments in AAPS, They are identical. Beginning to think this is nightscout and how the graph is being produced, which does not make sense. Can you check to see if your treatment information in reports in nightscout agree with AAPS

[jimk9]

I think #7771 is the same issue.

Will look to see if there are any more issues that could be linked

[ireneusz-ptak]

Can you check to see if your treatment information in reports in nightscout agree with AAPS

It looks that everything is the same (I cannot check the exact moment from the screenshots, because I broke the DB while trying to update the Mongo version, but I was able to compare two other days).

[ireneusz-ptak]

I think #7771 is the same issue.

Will look to see if there are any more issues that could be linked

Not sure about that - the problem disappears after switching back to NSClientV1 (from NSClientV3) in AAPS, so it's probably related to V3 API.

[jimk9]

Yep I understand that and to be honest I'm not sure either. What confuses me is that nightscout has all the correct information in the reports which suggests the communication between nightscout and aaps was complete and the database is accurate. Viewing the data in treatments report or in the daily report it all looks correct. Only bit that is wrong is the live basal graph. The good thing for me is the reports are accurate so I'm going to stay with v3 at the moment. Not sure anyone is looking at this issue

[sulkaharo]

This sounds like AAPS is doing something different with the 0 basal marking from what it's stored before. I think @MilosKozak might be the only NS dev who also uses the new AAPS and is thus able to debug what's happening.

[MilosKozak]

It's rendering issue

[yuvsketch]

Same problem here... Any solution?

[roco5]

V3 API presents issues with Nightscout for us, 15.0.2 and AAPSClient 3.2.04, like not being able to update profiles and not showing COB.