I can’t find a public post, but recently the Loop FB groups warned of bad functionality with Dash ‘InPlay’ pods manufactured after February 2025 using an Iphone 16 pro. Apparently they changed something in bluetooth that has specific connectivity issues with a small subset of recent Iphones.
I have both those Dash pods and an Iphone 16 pro (which I ironically splurged on in part because I figured I use it for Looping) and can confirm the connectivity is worse. Mine actually work for the most part, but get considerably more device disconnected warnings. Some pods are worse than others and this most recent one is basically never connected and I need to send it ~10 bolus deliveries before anything takes.
For me, I’m on top of it enough to not cause any major interruptions, but if you rely on Loop a little more passively you may want to avoid any of the new Dash Pods with the contraindicated Iphones until a software patch can be installed.
Ironically on Android the situation is reversed for some users. Android 15 created an incompatibility with the older Dash pods for many users, but the newly updated pods work fine. I’d be happy to swap eight boxes of the older pods (still far from expiration) for the newer ones if you’d like…
This was a topic at today’s Loop and Learn Open Mic (a regular Zoom meeting for Loop/Trio questions). Marion Barker (Loop Docs person) stated it was a known issue and being worked on by Pete Schwam (Loop Dev). Pete just rec’d a supply of the Inplay pods so he could work on a solution. In the meantime, the recommendation is for anyone with the issue to contact another person with lower # iPhone that has the TWI pods and arrange a swap. There is an alternative consisting of a lot of attention and manual actions (contact Marion or Carol Vachon via the Loop or LNL FB group or LoopZulipChat for further). The problem is the iPhone/CGM/Loop recognition that a connection exists to use, vice the actual connection. Hopefully Pete will develop a solution in the near future.