CGM data not appearing after Pod change; Loop stops Looping

[Ericcarbonn]

Describe the bug
Since I have updated phone from iPhone 8 to iPhone 12 Mini, including migrating to iOS18 we have had the following behavior at a pod change:

1. Loop receives Dexcom CGM data in the CGM details tab, but does not make it to the BG data in the Loop main screen so closed Loop goes stale

2. Loop pump shows "Signal Issue" even if there is a correct connection to pod, manual bolus can be done and pod status log accessible

   current fix for the above 2 problems is to "kill" both Loop and Dexcom apps, reopen, insert manual BG into Loop, wait 5 minutes and it all comes somewhat back to normal

• Afterwards for about 8 hours the predicted BG does not appear on Nightscout nor on LoopCaregiver app. Magically after this waiting period the predicted BG reappears everywhere.

Attach an Issue Report
I will get this on the next pod change

To Reproduce
In our case, change pod

Expected behavior
No interruption of BG and reconnection to new pod seamlessly

Screenshots
Will get these on next pod change

Phone

• Hardware: iPhone 12 Mini
• OS Version: iOS 18.2

Loop Version

• Version Number: 3.4.4
• Repo: Loopkit/loopworkspace.main

CGM

• Device: Dexcom G7
• Manager app: Dexcom G7 iOS app

Pump

• Manufacturer: Omnipod
• Model: DASH
• Firmware version: n/a

Additional context
Add any other context about the problem here.

[Ericcarbonn]

Here is the Loop issue export and some pictures from a couple days ago after pod change. Pictures show Loop app CGM receives BG values but they do not show up on Loop main screen, and are not taken into account. It also show the signal loss issue that is present at the same time.

I force closed Loop, Dexcom. Restarted both apps. Entered current BG manually from value in Dexcom app. After everything came back to normal. In this case I did the fix within minutes after the pod was changed.

Loop Report 2025-01-15 02_36_37-05_00.zip

[marionbarker]

There is an open PR to G7SensorKit that is improving G7 connectivity as long as the Sensor is communicating with the app. It is not perfect and some people are still having trouble.

Please see: LoopKit/G7SensorKit#33

This can be added to released version of Loop (see G7 Missing Readings option) using a the Customization Select Script:

• https://www.loopandlearn.org/custom-code/

[marionbarker]

This is the second official report of the G7 CGM missed readings in Loop. This is also seen in Trio and iAPS. This has nothing to do with the pod change, so I edited the name.

This is a real Issue and is under investigation.

Closing this Issue and keeping #2265 open.

[Ericcarbonn]

Hi Marion, You mention that this has nothing to do with the pod change. However the problem in my case is that at each pod change, yes the dexcom data does not get pulled to Loop but also Loop does not "see" the new pod after pairing unless Loop is forced closed and reopened. Is this all related to the Dexcom issue? If you want testing on a solution, on our side we are open to it, the problem is there every 3 days. Thanks Eric

…

On Wed, Mar 19, 2025 at 2:55 PM Marion Barker ***@***.***> wrote: I think this may be the first official report of the G7 CGM missed readings in Loop. This is also seen in Trio and iAPS. This has nothing to do with the pod change, so I edited the name. This is a real Issue and is under investigation. — Reply to this email directly, view it on GitHub <#2278 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIT4ZHMLTUDE6YZW2BICYNL2VG4T3AVCNFSM6AAAAABUWDYIYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMZXG4YDQNBSHE> . You are receiving this because you authored the thread.Message ID: ***@***.***> [image: marionbarker]*marionbarker* left a comment (LoopKit/Loop#2278) <#2278 (comment)> I think this may be the first official report of the G7 CGM missed readings in Loop. This is also seen in Trio and iAPS. This has nothing to do with the pod change, so I edited the name. This is a real Issue and is under investigation. — Reply to this email directly, view it on GitHub <#2278 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIT4ZHMLTUDE6YZW2BICYNL2VG4T3AVCNFSM6AAAAABUWDYIYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMZXG4YDQNBSHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[marionbarker]

Thanks for the clarification.
There must be something strange going on with Bluetooth on your phone to affect both the Pod and the G7SensorKit.

Can you try adding this customization? (We don't know if this is a "fix" but it seems to help some people who are just having the G7 sensor problem).

• https://www.loopandlearn.org/custom-code/#g7-scan

I see you have a LoopReport posted. I'll go an look at that in detail.

[marionbarker]

I looked at your report. There is no gap in communications with the pod when you put a new pod on. I see communication between Loop and the pod every 3 minutes as expected. The act of changing the pod must be disturbing your G7 interactions, so you are not getting updated glucose. With no glucose coming in, the Loop app goes red.

@ps2 Is there a test you would like @Ericcarbonn to run the next time he changes a pod.

[marionbarker]

I am also not seeing gaps in the Dexcom "didRead" messages with the exception of one set of backfills. So I am very puzzled.

• G7 connections EricCarbonn

One more thought. The current OmniBLE version used by Loop 3.4.4 can have a rare state where the app thinks it is suspended when it really isn't, so it won't send an automated command. (We've only seen that in Trio, not in Loop).

Can you do the normal pod change through insertion.
Once pod is ready to go, suspend Insulin and then resume Insulin.
See if that resolves your issue.

[Ericcarbonn]

I will try that on next change. I have quite a big gap on yesterday’s pod change since my son forgot to do the restart work around. See picture. If I pull an issues log will it go all the way back to yesterday morning? Eric

…

On Wed, Mar 19, 2025 at 5:50 PM Marion Barker ***@***.***> wrote: I am also not seeing gaps in the Dexcom "didRead" messages with the exception of one set of backfills. So I am very puzzled. - G7 connections EricCarbonn <https://docs.google.com/spreadsheets/d/1Y_LqwV7UZuVlkuqWtBttjuU7WqY5wrK0ycXFG0uEq0A/edit?usp=sharing> One more thought. The current OmniBLE version used by Loop 3.4.4 can have a rare state where the app thinks it is suspended when it really isn't, so it won't send an automated command. (We've only seen that in Trio, not in Loop). Can you do the normal pod change through insertion. Once pod is ready to go, suspend Insulin and then resume Insulin. See if that resolves your issue. — Reply to this email directly, view it on GitHub <#2278 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIT4ZHN6MNMWOAC7KAFYXPD2VHRCTAVCNFSM6AAAAABUWDYIYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMZYGIZTQOBSGU> . You are receiving this because you were mentioned.Message ID: ***@***.***> [image: marionbarker]*marionbarker* left a comment (LoopKit/Loop#2278) <#2278 (comment)> I am also not seeing gaps in the Dexcom "didRead" messages with the exception of one set of backfills. So I am very puzzled. - G7 connections EricCarbonn <https://docs.google.com/spreadsheets/d/1Y_LqwV7UZuVlkuqWtBttjuU7WqY5wrK0ycXFG0uEq0A/edit?usp=sharing> One more thought. The current OmniBLE version used by Loop 3.4.4 can have a rare state where the app thinks it is suspended when it really isn't, so it won't send an automated command. (We've only seen that in Trio, not in Loop). Can you do the normal pod change through insertion. Once pod is ready to go, suspend Insulin and then resume Insulin. See if that resolves your issue. — Reply to this email directly, view it on GitHub <#2278 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIT4ZHN6MNMWOAC7KAFYXPD2VHRCTAVCNFSM6AAAAABUWDYIYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMZYGIZTQOBSGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Ericcarbonn]

Here is the Loop report. After POD change issue was present March 18th between 9:23am and 11:00am Eastern Standard Time Eric On Wed, Mar 19, 2025 at 6:00 PM Éric Carbonneau ***@***.***> wrote:

…

I will try that on next change. I have quite a big gap on yesterday’s pod change since my son forgot to do the restart work around. See picture. If I pull an issues log will it go all the way back to yesterday morning? Eric On Wed, Mar 19, 2025 at 5:50 PM Marion Barker ***@***.***> wrote: > I am also not seeing gaps in the Dexcom "didRead" messages with the > exception of one set of backfills. So I am very puzzled. > > - G7 connections EricCarbonn > <https://docs.google.com/spreadsheets/d/1Y_LqwV7UZuVlkuqWtBttjuU7WqY5wrK0ycXFG0uEq0A/edit?usp=sharing> > > One more thought. The current OmniBLE version used by Loop 3.4.4 can have > a rare state where the app thinks it is suspended when it really isn't, so > it won't send an automated command. (We've only seen that in Trio, not in > Loop). > > Can you do the normal pod change through insertion. > Once pod is ready to go, suspend Insulin and then resume Insulin. > See if that resolves your issue. > > — > Reply to this email directly, view it on GitHub > <#2278 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AIT4ZHN6MNMWOAC7KAFYXPD2VHRCTAVCNFSM6AAAAABUWDYIYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMZYGIZTQOBSGU> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> > [image: marionbarker]*marionbarker* left a comment (LoopKit/Loop#2278) > <#2278 (comment)> > > I am also not seeing gaps in the Dexcom "didRead" messages with the > exception of one set of backfills. So I am very puzzled. > > - G7 connections EricCarbonn > <https://docs.google.com/spreadsheets/d/1Y_LqwV7UZuVlkuqWtBttjuU7WqY5wrK0ycXFG0uEq0A/edit?usp=sharing> > > One more thought. The current OmniBLE version used by Loop 3.4.4 can have > a rare state where the app thinks it is suspended when it really isn't, so > it won't send an automated command. (We've only seen that in Trio, not in > Loop). > > Can you do the normal pod change through insertion. > Once pod is ready to go, suspend Insulin and then resume Insulin. > See if that resolves your issue. > > — > Reply to this email directly, view it on GitHub > <#2278 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AIT4ZHN6MNMWOAC7KAFYXPD2VHRCTAVCNFSM6AAAAABUWDYIYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMZYGIZTQOBSGU> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

[marionbarker]

I don’t think you posted the Loop Report. There are 84 hours of messages in the Loop Report. We picked that number to enable us to capture the complete history of a pod.

[Ericcarbonn]

Oops sorry. Here it is. Eric

…

On Thu, Mar 20, 2025 at 1:06 AM Marion Barker ***@***.***> wrote: I don’t think you posted the Loop Report. There are 84 hours of messages in the Loop Report. We picked that number to enable us to capture the complete history of a pod. — Reply to this email directly, view it on GitHub <#2278 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIT4ZHKZD7UUWTK6HEU6CFD2VJEFLAVCNFSM6AAAAABUWDYIYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMZZGE2TSOBYG4> . You are receiving this because you were mentioned.Message ID: ***@***.***> [image: marionbarker]*marionbarker* left a comment (LoopKit/Loop#2278) <#2278 (comment)> I don’t think you posted the Loop Report. There are 84 hours of messages in the Loop Report. We picked that number to enable us to capture the complete history of a pod. — Reply to this email directly, view it on GitHub <#2278 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIT4ZHKZD7UUWTK6HEU6CFD2VJEFLAVCNFSM6AAAAABUWDYIYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMZZGE2TSOBYG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[marionbarker]

You are still not attaching a Loop report. Perhaps you would have better luck with zulipchat. You can send me a private message there.

• zulipchat link

Also worth joining zulipchat to see Pete's instructions for installing a bluetooth logger and collecting a sysdiagnose for helping him resolve this issue.

LInk: #development > 3.5.0 Bluetooth oddities @ 💬