Repository navigation
Communication Issues with InPlay BLE pods for some iPhone models #2318
Description
Describe the bug
Insulet has transitioned to InPlay BLE cards in their DASH pods, replacing the older TWI BOARD cards.
Some phone hardware is not able to communicate well with these pods.
As of 2026-03-14, we do not have a solution other than using the pod-keep-alive branch for OmniBLE. The phone models affected are:
- iPhone 16, all models
- iPhone 17e only
- as far as we know, the 17, 17 pro, 17 pro max, 17 air all behave nominally with Atlas pods
Attach an Issue Report
- Each person who experiences this is welcome to create a new comment, indicate their phone model and upload a Loop Report with the messages exchanged between their phone and the pod.
- Trio users should use the related Issue (595) in Trio Communication Issues with InPlay BLE pods for some iPhone models
What Kind of Pod do I have?
If you have an InPlay pod, this can determined by looking at the Pod screen and tapping on Pod Details.
It will either say InPlay BLE or it will say TWI BOARD.
Setup Information (please complete the following information):
For each person who posts, please include this in your comment:
Important Information:
- Phone Hardware: [e.g. iPhone 16 Pro]
- iOS Version: [e.g. iOS 18.5]
- Loop Version: *[e.g. 3.6.0]
- Lot Number: read this off the box or the paper that covers the pod
- Example Lot Number: PD1U02182511
- The lot number and seq number provided electronically do not provide the same information
Activity
jgefaell commentedon May 27, 2025
Phone Hardware: iPhone 15 Pro Max
iOS Version: 18.5
Loop Version: 3.2.3
Lot Numbers: 1410445 & 140056211
Loop Report 2025-05-27 15_34_31-04_00 (1).md
Update: Switched to SAW/TWI Board pod and still having issues. This exculpates the newer Atlas/InPlay BLE in this case.
This Loop Report is from the new SAW/TWI pod for completeness.
Loop Report 2025-05-28 10_47_59-04_00.md
Rorandle1 commentedon Jun 6, 2025
iPhone 16
IOS 18.4.1
Loop version 3.4.4
Lot No. 140056211
Having lots of comm issues with pump.
two0ten commentedon Jun 14, 2025
iPhone 16 Pro
iOS 18.3.1
Loop version 3.4.1
I have no logs because the pod would not connect at all.
REF: POD-BLE-I1-520
Lot PD1U02142513
FCC ID: REV-Atlas
rsammelson commentedon Jun 23, 2025
Phone Hardware: iPhone 16 Pro
iOS Version: iOS 18.5
Loop Version: 3.7.0 (194628d)
Lot Number: PD1U02182511
hgspig commentedon Jun 28, 2025
Phone Hardware: iPhone 16 e
iOS Version: iOS 18.5
Loop Version: 3.6.1
Lot Number: PD1U02192521
DeviceLog.json
I'm mostly experiencing this in the form of lots of "pod not connected." errors (lots being around 3/5 times I try to send a bolus it throws an error). Powering off the phone, turning Bluetooth off and back on, and quitting the app don't do anything to reconnect to the pod.
Are there any known temporary fixes? (e.g. downgrading IOS, or downgrading loop version)
marionbarker commentedon Jun 28, 2025
Thank you for all the information posted.
This Loop and Learn article has the all the information that we currently know.
There are several developers looking at this, but no solutions are available at this time.
ndenicoff commentedon Dec 9, 2025
I am having communication issues with iPhone 16 and InPlay BLE DASH pods.
How can I get access to this workaround from the loopdocs Omnipod FAQs page?
"There is a work-around to keep these pods more connected by issuing a keep-alive message before the 3-minute BLE disconnect; but it uses extra battery for both the phone and the pod
If you are forced to use an iPhone 16 with InPlay pods, reach out for help and this work-around can be made available"
ndenicoff commentedon Dec 11, 2025
I followed the advice of the facebook group and traded down for an iphone 15. Issue resolved
truebassist commentedon Jun 3, 2026
Phone Hardware: iPhone 16
iOS Version: iOS 26.5
Loop Version: 3.12.1
Lot Number: 144287377
marionbarker commentedon Aug 24, 2026
Closing this Loop Issue in favor of an OmnipodKit Issue: