-
Notifications
You must be signed in to change notification settings - Fork 32
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
AAPS seeing duplicate uploads from BYODA (new problem as of yesterday) #48
Comments
What version do you use? I also experienced the behaviour you're describing in 1.4 but since I upgraded to version 1.6.1.4537 I haven't seen it on the last two sensors I started in this version. |
Thankyou @CaptainBalou - stupidly missed the new release so have just successfully run the patch and will give it a go. |
So you don't just have that during or directly after starting a new sensor but also during "normal operation"? |
Yes, happens during normal operation. Sensor is about 36 hours old. now We weren't having this problem with the previous sensor or at any other stage - this fault started yesterday. |
I've never had that before. So all I said seems to be a different thing. I just had it during setting a new sensor. Do you have any new or especially old revision of the sensor? Just interested in that. I'm using rev 008 since a few months. But I can't help here because I'm no developer. Let's hope the devs are reading your issue to hopefully help your child to have safe looping again. |
Current and previous sensor are rev 010. No problems with the previous one. And thanks, hope we're back on track soon :) |
We have the same issue, but i cannot say when it starts, only that yesterday we got the red triangle after we lost the sensor and set a new one. I cleared the entry shown behind the triangle to get loop working again, but noticed that there tones of other old entries marked as red (duplicates with 1sec delay as shown in above screenshot in previous comment). Could be the trouble maker the Dexcom receiver? Because we using both, and the app knows about that there is a connected receiver, does both devices exchange data which is broadcasted as well? ... but no clue, just guessing. |
Sorry to hear that you're having the same problem. We have never used the Dexcom receiver. We had to change to Xdrip as there was no response from the devs. |
Having same issue 😔 |
Are there any updates on this issue? |
We've switched to Xdrip which is working well for us.
…On Sat, Sep 21, 2024, 19:15 Frederik Wagner ***@***.***> wrote:
Are there any updates on this issue?
—
Reply to this email directly, view it on GitHub
<#48 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMTLAAYWRYVYXP4LBHYWUJDZXWZV5AVCNFSM6AAAAAA2ELTLYGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRVGI3TKNRVGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Started a new sensor yesterday and have had trouble since with "BG too close" red triangle in AAPS appearing intermittently, roughly every hour. Sometimes the same reading is appearing again one second later in the BYODA tab of AAPS. Persists even after removing xdrip and reinstalling on a different handset. Using AAPS dev-J and Diakem-G7 patched but will confirm version later - our daughter at nursery now so will be happy to submit logcats and any other info that would help this evening.
Everything was working fine until yesterday - no other recent config changes other than adding a Wear OS watch back in. Another user has reported the same issue on the Facebook AAPS group yesterday.
The text was updated successfully, but these errors were encountered: