-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[3.3] Faulty calculation of delta #3688
Comments
I use G7 with xDrip direct connection 3.3 master and Fake data source 3.3 dev and I don't experience this. Can you provide more info. |
I use the Libre 3 via Juggluco -> xDrip (Nightscout Follow) -> AAPS. Here is an excerpt from the log (cut at the invokation of onReceive of the Data Receiver):
|
this is not easy to find from logs |
I have exactly the same error, but with a slightly different setup. FSL3 via Juggluco --> xDrip (Source: Libre patched) --> AAPS Since we have another family member with diabetes, I can inform that the delta ("0") issue doesn't exist with G7 via BYODA --> xDrip --> AAPS. Best regards |
It happend to our setup but only for a few readings. Seems like delta is not calculated when a new sensor is started with different time interval on BG arrival than previous sensor. I sent Milos screens and logs on discord. After a few readings delta is calculated and again and hasn't occurred again during this sensor session. Setup is G7 and direct connection via xDrip+ |
I have the same issue with 3.3.0. The delta is not always 0, but it is wrong. The 5 minutes delta and 15 minutes delta appear to be the same always and the 40 minute delta is some other number. The strangest thing is that the arrow does seem to agree with Xdrip measurements. I tried installing Juggluco next to Xdrip to see if that helped. It did not. since AAPS started intervening based on the incorrect deltas, I had to downgrade again. |
someone affected: give me credentials to setup AAPSClient with the bug |
Warning: due to this issue Automations that make use of delta's as conditions will not work as expected. |
@MilosKozak I'm experiencing this issue too. I'm currently on AAPS v3.3.1.0, FSL2 with Xdrip/OOP2, Dana-i and Nightscout v3. What exactly do you need to set up your test? |
I'm also have this issue, with AAPS 3.3.1.0 - FSL2 - Xdrip - Juggluco or OOP2. One thing I noticed is that if I scan FSL2 with NFC in Xdrip, Delta is doing something. |
Could it be this has something to do with the recalculations AAPS frequently does on FSL2 values? Can't really support this with data, but I noticed there are a lot of open/transparent dots in my BG graph since version 3.3. I suppose this points at recalculated BG's, can't find that in the docs though. I suspect that when such a recalculated BG value occurs the delta's may not be calculated correctly. |
I would like to add that I left Xdrip out and sticked with only FSL2 - Juggluco - AAPS and the delta values are coming through just as you would expect. So I still think the issue is somehow Xdrip related and not so much linked to the FSL2 specific |
Wait, if you run juggluco without xdrip, you get deltas. Are they the correct deltas? |
repeating: if you can replicate it in AAPSClient I can have a look |
I'm not using AAPSclient myself but I suppose if I share NS credentials with you you will be able to see my data in AAPSclient? Will a "readable" token do in this case? |
I send you Nightscout details via Facebook DM, did that work? I'm currently on 3.3.1.0, when I send you the link I was on 3.3.1.3. Both have the same error |
i need admin token to be able connect via AAPSClient |
It replicates in AAPSClient. |
I tried this with my new sensor (fsl2). I removed xdrip from phone, started with just juggluco and aaps (3.3.1.0). This seems to give correct deltas. If you try this, don't forget to tell aaps to upload your glucose to NS instead of xdrip Current setup fsl2 (eu) - - > juggluco - - > aaps 3.3.1.0 |
With the current master (3.3) I face a serious problem with the calculation of the deltas. Most of the time, the delta is calculated as zero although the bg values show differences:
The graph also shows many pale bg values:
I can provide more informations or logs if needed
The text was updated successfully, but these errors were encountered: