Update for model 17e and Atlas pods (#1000)

marionbarker · web-flow · commit f97aa5b90ac4 · 2026-03-16T10:14:15.000-07:00
diff --git a/docs/build/phone.md b/docs/build/phone.md
@@ -35,7 +35,9 @@ All the devices listed below are currently compatible with Loop. They are separa
 
 These phones require *iOS* 26 and `Loop version 3.8.x` or newer
 
-- iPhone 17, all variants
+- iPhone 17, all variants except 17e
+    - iPhone 17e models are compatible but **not recommended for use with Omnipod DASH**
+    * See [Atlas or InPlay DASH pod](../faqs/omnipod-faqs.md#atlas-or-inplay-dash-pods){: target="_blank" } warning
 
 !!! important "iOS 26 requires `Loop v3.8.2` or newer"
     Any iPhone 17 must run iOS 26. You must install `Loop v3.8.2` or newer before updating to iOS 26.  `Loop v3.7.x` and earlier do not to support iOS 26.
@@ -44,8 +46,8 @@ These phones require *iOS* 26 and `Loop version 3.8.x` or newer
 
 These phones require *iOS* 18 and are compatible with *iOS* 26.
 
-- iPhone 16 is compatible but **not recommended for use with Omnipod DASH**
-    * See [InPlay DASH pod](../faqs/omnipod-faqs.md#iphone-16-and-atlas-or-inplay-dash-pods){: target="_blank" } warning
+- iPhone 16 models are compatible but **not recommended for use with Omnipod DASH**
+    * See [Atlas or InPlay DASH pod](../faqs/omnipod-faqs.md#atlas-or-inplay-dash-pods){: target="_blank" } warning
 
 These phones are compatible with *iOS* 17, 18 and 26
 
diff --git a/docs/faqs/omnipod-faqs.md b/docs/faqs/omnipod-faqs.md
@@ -24,16 +24,16 @@ You do not need the Omnipod Personal Diabetes Manager (PDM), just the pod suppli
 DASH pumps communicate with the phone via Bluetooth so they do not require a RileyLink compatible device.
 
 
-### iPhone 16 and Atlas or InPlay DASH pods
+### Atlas or InPlay DASH pods
 
-!!! warning "iPhone 16 and Omnipod DASH"
-    **iPhone 16 only**
+!!! warning "iPhone 16 (all models) and 17e model with Omnipod DASH"
+    **iPhone 16 all models** and **iPhone 17e model only** can be slow to reconnect to Atlas versions of DASH pods. This can cause delays to automatic and manual insulin dosing.
 
-    **Other phones, including iPhone 17, work fine with InPlay DASH pods**
+    **Other phones, including iPhone 17 models other than 17e, work fine with InPlay DASH pods**
 
 Beginning in 2025, some of the DASH pods are produced with a newer version of chips and firmware. The only way to tell the difference before use is to examine the paper cover over the pods inside the box for the word `Atlas` (newer) or `SAW` (older) as shown in the graphic below. It is anticipated that `Atlas` pods, which report electronically as `InPlay BLE`, will become more common.
 
-**If you do not already own an iPhone 16, it is strongly suggested you choose an older (iPhone 15 or SE or older) or newer (iPhone 17) phone.**
+**If you do not already own an iPhone 16 or a 17e, it is strongly suggested you choose an older (iPhone 15 or SE or older) or newer (iPhone 17 that is not the 17e) phone.**
 
 * The left images show the SAW marking for `TWI Board` DASH pods
 * The right images show the Atlas marking for `InPlay BLE` DASH pods
@@ -42,26 +42,27 @@ Beginning in 2025, some of the DASH pods are produced with a newer version of ch
 ![identifying marks for SAW and Atlas DASH pods](img/saw-atlas-identifiers.svg){width="750"}
 {align="center"}
 
-#### Characteristics of Atlas with iPhone 16
+#### Characteristics of Atlas with iPhone 16 or 17e
 
-* The Atlas DASH pods, which advertise a Bluetooth Device name of `InPlay BLE` and indicate `-Atlas` in small print on the paper pod cover are fully compatible with all iPhone models except iPhone 16
-* Although `InPlay` pods do work with the iPhone 16 you may notice some communication issues
+* The Atlas DASH pods, which advertise a Bluetooth Device name of `InPlay BLE` and indicate `-Atlas` in small print on the paper pod cover are fully compatible with all iPhone models except iPhone 16 and iPhone 17e
+* Although `InPlay` pods do work with the iPhone 16 and 17e you may notice some communication issues
     * It can take many attempts to get the pod to initially connect when pairing; just keep hitting retry
     * Once the pod disconnects itself from the phone Bluetooth, the phone is slow to reconnect the pod to the *Loop* app
         * Pod firmware initiates the disconnect 3 minutes after the last message exchange
         * With other models, the reconnect happens in about 1 sec
-        * With iPhone 16, this can take many seconds and sometimes a few minutes
+        * With iPhone 16 or 17e, this can take many seconds and sometimes a few minutes
     * When the pod is not connected, neither automatic nor manual commands can be sent to the pod to modify insulin delivery
     * No solution to this issue is known
-    * 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, please read the [Updates in dev](../version/development.md#updates-in-dev){: target="_blank" } section for information about building a feature branch for Loop that contains this code
+    * 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 the phone. 
+        * Although it does increase the number of messages to the pod slightly, this is not thought to be a big issue. Pods with marginal batteries are as likely to fault without this feature as with the feature.
+        * If you are forced to use an iPhone 16 or 17e with InPlay pods, please read the [Updates in dev](../version/development.md#updates-in-dev){: target="_blank" } section for information about building a feature branch for Loop that contains this code
         * If you are using Trio or iAPS, the same OmniBLE `pod-keep-alive` branch can be used by that app - check with mentors for those apps for instructions
 
-> DASH pods that advertise a Bluetooth Device name of `TWI Board` and indicate `-SAW` in small print on the paper pod cover are fully compatible with all phones including the iPhone 16.
+> DASH pods that advertise a Bluetooth Device name of `TWI Board` and indicate `-SAW` in small print on the paper pod cover are fully compatible with all phones including the iPhone 16 and 17e.
 
 > The earliest `Atlas` DASH pods noticed by the OS-AID community were manufactured in Feb 2025. Some TWI DASH pods were manufactured in May 2025. Later in 2025, `Atlas` DASH pods with July 2025 and later manufacture dates were seen. 
 
-We have no insight into the deployment plans from Insulet. Just pay attention if you have an iPhone 16. Otherwise, you won't notice a difference.
+We have no insight into the deployment plans from Insulet. Just pay attention if you have an iPhone 16 or iPhone 17e. Otherwise, you won't notice a difference.
 
 
 - - -
diff --git a/docs/version/development.md b/docs/version/development.md
@@ -25,7 +25,7 @@ Please check the [development channel in zulipchat](https://loop.zulipchat.com/#
 In addition to the main and dev branches, which are tightly controlled and only updated through a formal pull request and approval process, there are also some feature and update branches. These branches are subject to more frequent updates, so users testing these branches should follow along in zulipchat for information.
 
 * The `update_dev_to_M.m.#` is where the next version of dev is tested before becoming part of `dev` and later being released as `main`
-* The branches starting with `feat/` have one or more special features, like support for new pumps, CGM or the keep-alive work-around for Atlas DASH pods with by iPhone 16
+* The branches starting with `feat/` have one or more special features, like support for new pumps, CGM or the keep-alive work-around for Atlas DASH pods with by iPhone 16 or iPhone 17e
 
 The graphic below shows the `main` and `dev` branches along with some feature branches and an update branch.
 
@@ -46,7 +46,7 @@ The table below lists active branches. Note that updates may occur and be announ
 |:--|:--|:--|:--|
 | main | 3.12.0 | 24 Feb 2026 | release|
 | dev | 3.13.0 | 24 Feb 2026 | code is currently the same as `main` |
-| [feat/pod-keep-alive](#feature-branch-pod-keep-alive-feature)<br>- SHA `f51cf70` | 3.13.0 | 26 Feb 2026| - uses the OmniBLE pod-keep-alive branch to support users of iPhone 16 phones with InPlay BLE (-Atlas) DASH pods<br>  - SHA for OmniBLE is `9992773`<br>**Please read [Feature Branch: Pod Keep Alive Feature](#feature-branch-pod-keep-alive-feature)** |
+| [feat/pod-keep-alive](#feature-branch-pod-keep-alive-feature)<br>- SHA `f51cf70` | 3.13.0 | 26 Feb 2026| - uses the OmniBLE pod-keep-alive branch to support users of iPhone 16 or 17e phones with InPlay BLE (-Atlas) DASH pods<br>  - SHA for OmniBLE is `9992773`<br>**Please read [Feature Branch: Pod Keep Alive Feature](#feature-branch-pod-keep-alive-feature)** |
 | [feat/dev-dana-medtrum](#feature-branch-medtrum-and-dana-support) <br>- SHA `309b448` | 3.13.0 | 26 Feb 2026 | - adds experimental support for Dana and Medtrum pumps<br>- this branch is ready for expert testers to evaluate and report back<br>  - SHA for DanaKit is `3970b2a` (TBR issues fixed)<br>  - SHA for MedtrumKit is `c79a883` (TBR issues fixed) |
 | [feat/eversense](#feature-branch-eversense-support) <br>- SHA `efe5f5c` | 3.13.0 | 26 Feb 2026 | - adds experimental support for Eversense (includes Dana and Medtrum pumps support too)<br>- this branch is ready for expert testers to evaluate and report back<br>  - SHA for Eversense is `e870c22` |
 
@@ -110,7 +110,7 @@ The version number in the feature branch will match either the `dev` branch vers
 
 ### Feature Branch: Pod Keep Alive Feature
 
-The experimental `pod-keep-alive` branch has a new "Pod Keep Alive" option at the bottom of the "Omnipod DASH" screen. This is intended to assist users who have both an [iPhone 16 and DASH pods with a InPlay BLE (Atlas) board](../faqs/omnipod-faqs.md#iphone-16-and-atlas-or-inplay-dash-pods){: target="_blank" }. No action is taken automatically unless both these cases are detected to be true.
+The experimental `pod-keep-alive` branch has a new "Pod Keep Alive" option at the bottom of the "Omnipod DASH" screen. This is intended to assist users who have both an iPhone 16 (all models) or 17e and [DASH pods with a InPlay BLE (Atlas) board](../faqs/omnipod-faqs.md#atlas-or-inplay-dash-pods){: target="_blank" }. Model 17 phones, except for the 17e, do not exhibit this problem. No action is taken automatically unless both these cases are detected to be true.
 
 It was tested for LoopWorkspace and Trio.
 
@@ -145,6 +145,11 @@ All three criteria must be true or no automatic change to the setting takes plac
 * pair a new pod that is InPlay BLE (Atlas)
 * Pod Keep Alive is Disabled
 
+!!! warning "No Automatic Change for iPhone 17e"
+    Note that we did not know the 17e would exhibit the same issue. The `When Open` option does not automatically enable when a 17e is used to pair with an Atlas pod.
+    
+    The user should manually enable `When Open` or `Silent Tune`/`RileyLink` before they try to pair an Atlas pod with an iPhone 17e.
+
 Note that during the time from pair to insert, the app keeps the screen open and unlocked unless you manually lock it.
 
 This means you can take all the time you need between pair/prime and insert. As long as you don't manually lock the phone or move it out of range of the pod, the pod stays connected until you insert the cannula.
@@ -157,23 +162,23 @@ When the app is open, it will send a getStatus to the pod 2:40 (mm:ss) after the
 
 This is true as long as the phone and pod are in-range while the app is open with phone unlocked.
 
-> If the pod moves out of Bluetooth range, the pod disconnects. With iPhone 16 it might take several seconds to minutes before the app reconnects to the pod once it is back in range. This can cause disruptions until the reconnect happens.
+> If the pod moves out of Bluetooth range, the pod disconnects. With iPhone 16 or iPhone 17e it might take several seconds to minutes before the app reconnects to the pod once it is back in range. This can cause disruptions until the reconnect happens.
 
 #### Silent Tune
 
 A silent tune is played in the background which keeps the app alive even when the phone is locked. This will increase the battery usage on the phone.
 
 While Silent Tune is selected, the app will send a getStatus to the pod 2:40 (mm:ss) after the last pod message was exchanged. This means the pod does not disconnect from BLE and remains available for commands from the app so long as the phone and pod stay within Bluetooth range.
 
-> If the pod moves out of Bluetooth range, the pod disconnects. With iPhone 16 it might take several seconds to minutes before the app reconnects to the pod once it is back in range. This can cause disruptions until the reconnect happens.
+> If the pod moves out of Bluetooth range, the pod disconnects. With iPhone 16 or iPhone 17e it might take several seconds to minutes before the app reconnects to the pod once it is back in range. This can cause disruptions until the reconnect happens.
 
 #### RileyLink
 
 For those who have a RileyLink (OrangeLink, EmaLink, etc), you can use that instead of the Silent Tune but you must keep the link with the phone.
 
 While RileyLink is selected, the app is triggered by the RileyLink one minute heartbeat. The app will send a getStatus to the pod 2:00 (mm:ss) after the last pod message was exchanged. This means the pod does not disconnect from BLE and remains available for commands from the app so long as the phone and pod stay within Bluetooth range.
 
-> If the pod moves out of Bluetooth range, the pod disconnects. With iPhone 16 it might take several seconds to minutes before the app reconnects to the pod once it is back in range. This can cause disruptions until the reconnect happens.
+> If the pod moves out of Bluetooth range, the pod disconnects. With iPhone 16 or iPhone 17e it might take several seconds to minutes before the app reconnects to the pod once it is back in range. This can cause disruptions until the reconnect happens.
 
 > If the phone moves out of RileyLink range, then the app is not triggered by the RileyLink heartbeat and the pod disconnects from BLE at the 3 minute cadence. With iPhone 16 it might take several seconds to minutes before the app reconnects to the pod once it is back in range. This can cause disruptions until the reconnect happens.
 
