-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Loop 3.5.0 (51) not updating/in sync with Dexcom G6 readings. #2217
Comments
Loop Report Analysis
General CommentsExamine the Loop Report. Parse the messages into csv files, one per podThere were 5 events where the delay between successive mesages was greater than 1000 sec. (This delta should typically be no more than 180 sec with DASH pod and no loss of connectivity). One of these events was in the first pod in the report (covering ~38 hours), and 4 were for the second pod in the report (covering ~46 hours). (The csv files are attached at the end of this comment.) Record the time stamps (these are all in UTC) to focus the review of the messages in the Loop Report.
Manually examine messagesExamine the messages in the log near those time stamps, in order:
Conclusion - there were no bluetooth messages from either the pod or the sensor during those gaps. Search for backfill in recordThese time stamps are times in which a backfill (without an error) was detected
Looking at the timestamps where deltaSec>1000, all except the last one were associated with a backfill from the sensor. Note that I only manually examined the 5 cases where deltaSec was over 1000. There 12 instances where deltaSec was >200 but <1000 sec. Some of these backfills listed above were for a very long time:
Some backfills reported errorsNot sure what this means, but some backfills reported errors:
csv files for the two pods in this report |
If G6 app is getting data, then Loop should be too, unless iOS is killing Loop or Loop is having some other problems getting runtime. If you grab a sysdiagnose while this is happening (please note explicitly what times you see data from g6 that are missing from Loop), I can take a look and see if there is anything obvious in the logs. You can post them to a sharing service (like google drive) and then share a link to them to me on zulip, as the file is quite large. |
Starting with around Loop version 3.5.0 (49) or so, Loop is not updating my G6 sensor readings correctly. If I go into the Loop Settings and click on my G6 sensor device, it is updating the readings there and everything is correct including the transmitter ID. However, in the main Loop window itself, the sensor reading is not updated and the loop breaks. When the Dexcom app gets a new sensor reading, I then go back to the Loop Settings and click on the Dexcom device and again the reading is correct there and in sync with the Dexcom app. But that updated reading is not reflected in the main Loop window.
Two reasons I believe this to be a Loop bug. First, even though the sensor reading is not updated in the main Loop window, the trend arrow information DOES update correctly. So if I get a new reading in the Dexcom app and it is also showing a change in the trend information such as two arrows up when the previous reading was one arrow up, the main Loop window WILL update the correct trending arrow to two arrows up even though the sensor reading is not updated.
The second reason I believe this to be a bug specific to Loop is that if I delete the CGM from Loop and then add a new Dexcom Share only CGM, Loop does not update the Dexcom Share data even though if I go into my Dexcom Follow app the data there is in sync with my main Dexcom app. So clearly it is not a bluetooth or communication issue as Dexcom Share gets its information over the internet, not via bluetooth.
Steps to reproduce the behavior:
Unfortunately there are no steps to reproduce the error. I have not seen the issue previously before 3.5.0 (49) as far as I am aware.
Expected behavior would obviously be that if the Dexcom/Dexcom Follow apps are updating correctly, Loop should be updating as well, especially since if one goes to the Loop settings and clicks on the Dexcom device, the correct readings and transmitter ID are displayed there and in sync with the Dexcom app.
iPhone SE gen 2
iOS 17.6.1
Loop 3.5.0 (51) Dev
Dexcom G6 with official Dexcom app + Dexcom Follow
Omnipod Dash
Firmware 4.10.0
Screenshots attached include:
Additional Attachments: Loop Issue Report:
Loop Report 2024-08-26 21_08_14-07_00.md
The text was updated successfully, but these errors were encountered: