search

nightscout / AndroidAPS

Opensource automated insulin delivery system (closed loop)
https://wiki.aaps.app
GNU Affero General Public License v3.0
669 stars 1.61k forks source link

Tidepool is not receiving profile basal, only temp basal #3040

Open campbellgl opened 8 months ago

campbellgl commented 8 months ago

3.2.0.1 Tidepool only receives temp basals. Profile basals show as 0.00 in Tidepool. In my logs from today, 2023-11-06 from 09:31 to 11:41 (16:31 to 18:41 GMT) my profile basal was running (0.85), but Tidepool shows zero basal. AndroidAPS._2023-11-0517-00-43.8.zip AndroidAPS._2023-11-0617-00-51.0.zip AndroidAPS.log

CeDoMain commented 8 months ago

I can confirm this problem!

rmitchell7 commented 7 months ago

Same for me, does anyone know if there's a way I can get this working or who I can ask for help?

TWilhoWI commented 7 months ago

Also conform the problem

ohjay73 commented 7 months ago

mine works fine using latest dev

Bricki85 commented 4 months ago

Hi, I have the same Problem. I am on Version 3.2.0.2. Switched to Pump (Dash) recently. Therefore now it would be nice if I would see my Basal rates correctly.

@campbellgl did you solve your Problem somehow?

campbellgl commented 4 months ago

@Bricki85 I haven't tried in dev yet. Still not working in 3.2.0.4

ohjay73 commented 4 months ago

3.3.0 dev a works just fine

On Tue, Mar 26, 2024, 23:11 campbellgl @.***> wrote:

@Bricki85 https://github.com/Bricki85 I haven't tried in dev yet. Still not working in 3.2.0.4

— Reply to this email directly, view it on GitHub https://github.com/nightscout/AndroidAPS/issues/3040#issuecomment-2021947323, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMKLQFCPDYODVAG5VG2XML3Y2JIIDAVCNFSM6AAAAAA7AOVZDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRRHE2DOMZSGM . You are receiving this because you commented.Message ID: @.***>

Bricki85 commented 4 months ago

Thanks @ohjay73 and @campbellgl Will then wait for 3.3.0. I am not yet brave enough to go full dev yet.

vanelsberg commented 4 months ago

For me (latest dev) Tidepool only shows current ("automated") basal. AFAIKT It does not support viewing the profile...

image

Bricki85 commented 4 months ago

I think you misunderstood me or the thread. What I see for you is a lot of zero TBRs and additional TBRs. Furthermore there are some gaps in our diagram where no blue line is. Rather few but some. At mine you can see it better: image There you see some blue lines with zero and then you see gaps where no blue line is. In those gaps my normal basal rate should be shown like for example 1.1U/h etc. But it seems Tidepool only shows the adjusted TBRs (deviating from the default basal rate in the profile). I do not know your normal basal rate and if it is in the picture you uploaded. At least for me none of those are in there.

ohjay73 commented 4 months ago

tidepool will only put in what your device is actually doing. Therefore if you don't have a basal all day because SMB's are being used to replace basal, you'll see nothing in basal.. same if only TBR's are used. It doesnt care what your profile is, only what is actually being reported by the device.

On Thu, Mar 28, 2024 at 11:54 AM Bricki85 @.***> wrote:

I think you misunderstood me or the thread. What I see for you is a lot of zero TBRs and additional TBRs. Furthermore there are some gaps in our diagram where no blue line is. Rather few but some. At mine you can see it better: image.png (view on web) https://github.com/nightscout/AndroidAPS/assets/62853716/989030a1-7538-4176-b9b7-21fbd292310b There you see some blue lines with zero and then you see gaps where no blue line is. In those gaps my normal basal rate should be shown like for example 1.1U/h etc. But it seems Tidepool only shows the adjusted TBRs (deviating from the default basal rate in the profile). I do not know your normal basal rate and if it is in the picture you uploaded. At least for me none of those are in there.

— Reply to this email directly, view it on GitHub https://github.com/nightscout/AndroidAPS/issues/3040#issuecomment-2025797096, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMKLQFF3D3CQGG2VGWBGLR3Y2RDLXAVCNFSM6AAAAAA7AOVZDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRVG44TOMBZGY . You are receiving this because you were mentioned.Message ID: @.***>

Bricki85 commented 4 months ago

I have basal lets say for easier disussion 1,1U/h over the whole day. I see that I have zero TBRs and increased TBRs (those are in there) but all the gaps where there is no blue line there should be my default 1,1 basal rate. I see it in AAPS but not in Tidepool.

vanelsberg commented 4 months ago

... where there is no blue line there should be my default 1,1 basal rate. I see it in AAPS but not in Tidepool. You assumption is wrong: when on zero-TBR there is no insulin administred. Ckeck your pump activity? Basal rate in profile is insuline "at rest", AAPS algo will adjust for 0 to max U/hr basal every 5 minutes .....

Bricki85 commented 4 months ago

You assumption is wrong: when on zero-TBR there is no insulin administred. Ckeck your pump activity? Basal rate in profile is insuline "at rest", AAPS algo will adjust for 0 to max U/hr basal every 5 minutes .....

If Zero TBR is set I get no Insulin. That is clear. And that AAPS adjusts the TBR is also fine.

I checked the export of my data from Tidepool and there is only as said the devivations from the default basal rate in there. Here is the corresponding Screenshot von AAPS. I would assume Tidepool and AAPS look similar. Screenshot_20240329_063227_AAPS

So if you compare both screenshots you will find that the default basal rate where AAPS did not adjust anything is missing.

So from my underestanding AAPS does not report the basal rate which is inside the profile to the backend? Does it work with Nightscout?

Maybe to make it even more clear if I have 1,1U/h in my profile for the whole day and I would not have one adjustment like zero TBR etc. Then I would see nothing inside Tidepool. No blue line whatsoever. And therefore my numbers in Tidepool for Basal would be 0 for the whole day. Whereever AAPS would say 26,40 at a whole.

CeDoMain commented 3 months ago

Hi guys. I understand what @Bricki85 means and I have the same issue. I have attached a picture which show the basal of whole day in AAPS, Nightscout and Tidepool (top to bottom).

For me the pictures speak for themselves... AAPS show an active default rate in dark blue, NS also, but Tidepool not.

EDIT: I also see that NS have some errors in the last quarter of the day. There are the temps missing. Hmm.

image

Bricki85 commented 3 months ago

Yeah here we can see it good, thanks for the images. Nightscout actually does it correct somehow. Question would be why. Does Nightscout get different data than Tidepool? Or does Nightscout just do more in the backend with the same data what Tidepool gets? Maybe I dig into the code on the weekend if I find the time to see at least if the data upload is the same (I would assume it is. But you never know)

CeDoMain commented 3 months ago

I have updated my answer for better comparision of the pictures.

vanelsberg commented 3 months ago

I think that if there is a problem, it is with NS V15, not Tidepool. Actually I didn't notice. Not really looking an basal when viewing NS. Using it mainly for reporting. NS is odd: it seems to miss zero-temps?

For me AAPS and Tidepool look identical..... But please double check your AAPS vs Tidepool. Then look at your NS. This is what I see (latest AAPS dev - OpenSMB ?

Tidepool tp AAPS 3.3-dev aps NS v15.0.2 ns

CeDoMain commented 3 months ago

Thank you @vanelsberg for sharing your diagrams! Its interesting what you have shown. For me NS definetly has some problems displaying zero temps. In my diagram there are also problems.

But also in your tidepool diagram I can see the "default basal error" which the TO describes. When you carefully look around 4'clock in your aaps diagram, you can see dark blue areas at the start and end of the tbr curve. I marked what I mean with red arrows in the image below. and these dark blue areas show default rates active which are also not present in your tidepool diagram. I marked these areas with red brackets. image

vanelsberg commented 3 months ago

But also in your tidepool diagram I can see the "default basal error" ....

I think this is about graph scaling and sampling. Once should not give to much weight to de graph details. Mind that the graphs are intended to show "activity". For details, check your pump activity (NS treatments reporting)

janvitos commented 3 months ago

I have the same problem as @campbellgl and others. Normal basal isn't recorded in Tidepool, only temp basal. This means the daily basal insulin is much less than it should be. For example, on April 29th, daily basal insulin in AAPS is 9.6 U, while in Tidepool it is 5.4 U, so it's missing 4.2 U of normal basal. April 28th, daily basal insulin is 8.3 U in AAPS, and 4.8 U in Tidepool, so it's missing 3.5 U of normal basal.

CeDoMain commented 3 months ago

Thank you for sharing your expereance! So the diagrams with the missing sections in tidepool also occur at your side?

vanelsberg commented 3 months ago

Normal basal isn't recorded in Tidepool, only temp basal @janvitos @CeDoMain @campbellgl Confirming: Now also seeing this.

janvitos commented 3 months ago

So the diagrams with the missing sections in tidepool also occur at your side?

Yes, exactly the same issue. Normal basals are missing and only temp basals are recorded. You can see the large gaps in basal in the screenshot below.

markup_1000024159

Stealthwick commented 2 months ago

I am also experiencing this issue. It caused some confusion with the diabetes specialist who was trying to work out why so little basal was being delivered - turned out it was just unaccounted for due to only temp rates being counted.

Would love to see this get some attention as we're working hard in my country for our approach to be accepted by healthcare professionals!

janvitos commented 2 months ago

It caused some confusion with the diabetes specialist who was trying to work out why so little basal was being delivered

This was my exact worry. My son's endo has access to his Tidepool and normally prints out the data of the last 2 weeks, so for his next appointment, the basal data would've been wrong. This time around, I'll have to use Nightscout, get the reports send them to the diabetes team instead. Hope the bug gets fixed in the near future!