Update LoopDocs for Open Beta Test of O5

docs/build/cgm.md

@@ -44,9 +44,9 @@ If the *Dexcom* app is on the same device as the *Loop* app, your system can fun
 
 ## *Dexcom* G7 and ONE+ CGM
 
-The *Dexcom* G7 and ONE+ CGM transmits data directly to the *Dexcom* app on your iPhone via Bluetooth.
+The *Dexcom* G7 (10-day and 15-day) and ONE+ CGM transmits data directly to the *Dexcom* app on your iPhone via Bluetooth.
 
-The *Dexcom* ONE+, available in some countries, acts just like the G7 as far as the *Loop* app is concerned. 
+The *Dexcom* ONE+, available in some countries, acts just like the G7 as far as the *Loop* app is concerned.
 
 ## *Libre* CGM
 
@@ -57,6 +57,7 @@ With Loop 3.4 and newer versions, some *Libre* CGM are supported.
 * These *Libre* CGM are not supported within the *Loop* app
     * American (Canada, US, South American) *Libre* 2
     * *Libre* 3
+* Coming soon *Libre* 3/3+ support is available in [next-dev branch](../version/development.md#updates-in-dev) for experienced users
 * See [CGM Customization](../faqs/cgm-faqs.md#cgm-customization){: target="_blank" }
 
 ## *Eversense* E3 and 365 CGM

docs/build/phone.md

@@ -37,7 +37,7 @@ These phones require *iOS* 26 and `Loop version 3.8.x` or newer
 
 - 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
+    * See [Keep Alive: Atlas or InPlay DASH pod](../faqs/omnipod-faqs.md#keep-alive-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.
@@ -47,7 +47,7 @@ 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 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
+    * See [Keep Alive: Atlas or InPlay DASH pod](../faqs/omnipod-faqs.md#keep-alive-atlas-or-inplay-dash-pods){: target="_blank" } warning
 
 These phones are compatible with *iOS* 17, 18 and 26
 

docs/build/pump.md

@@ -73,10 +73,11 @@ The DASH system has the newer, slimmer locked-android Personal Diabetes Manager
 
 ### Omnipod 5
 
-Loop does not support Omnipod 5 pods yet but it is coming soon. 
+Loop does not support Omnipod 5 pods in the released code.
 
-* There is an on-going private beta test with Omnipod 5
-* We cannot give a timeline for when this will land in `dev` for public beta
+* There is an on-going public beta test with Omnipod 5
+* You must build a development branch to test Omnipod 5 - we encourage most people to wait while experienced users test this implementation
+    * See [Updates in dev](../version/development.md#updates-in-dev){: target="_blank" } if you are an experienced user who wants to help with testing and are willing to build frequently and report any issues to the development team
 
 - - -
 

docs/faqs/cgm-faqs.md

@@ -2,13 +2,15 @@
 
 The following CGM are supported by some or all versions of Loop:
 
-* All *Dexcom* CGM (Loop 3 and later)
-* Some *Libre* CGM (Loop 3.4 and later)
-* Eversense E3 and 365 (Loop 3.11 and later, via an experimental feature branch)
+* All *Dexcom* CGM (*Loop* v3 and later)
+    * This includes 15-day G7 CGM
+* Some *Libre* CGM (*Loop* v3.4 and later)
+    * Coming soon *Libre* 3/3+ support is available in [next-dev branch](../version/development.md#updates-in-dev) for experienced users
+* Eversense E3 and 365 (included with *Loop* v3.14.2 and newer)
 * Medtronic Enlite CGM when used with a compatible pump
 * Remote CGM (requires internet access)
     * *Dexcom* Share
-    * Nightscout as CGM (Loop 3 and later)
+    * Nightscout as CGM (*Loop*  v3 and later)
 
 See also: [Compatible CGM](../build/cgm.md){: target="_blank" } and [CGM Customization](#cgm-customization)
 
@@ -28,6 +30,10 @@ With no recent glucose readings, your pump returns to the scheduled basal delive
 
 Loop continues to accept carb entries and manual bolus commands. [Manual Temp Basal](../loop-3/omnipod.md#manual-temp-basal) can also be commanded.
 
+### Is the 15-day *Dexcom* G7 Supported?
+
+Yes. Support for the 15-day *Dexcom* G7 was added with *Loop* v3.10.0 in January 2026.
+
 ### *Dexcom* G7 Warmup
 
 The *Dexcom* G7 (and ONE+) begins warming up as soon as you insert the device and completes in less than half an hour. Many Loopers use the combination of this warmup upon insertion and the 12-hour grace period offered by the G7 to have continuous CGM readings with no gap.
@@ -118,6 +124,8 @@ Loop 3.4.x and later enables the use of those *Libre* sensors supported by [Libr
 
 ### What about other *Libre* sensors?
 
+> Coming soon *Libre* 3/3+ support is available in [next-dev branch](../version/development.md#updates-in-dev){: target="_blank"} for experienced users
+
 There are a number of *Libre* sensors in which the only option for digital access to the CGM readings is to use the app provided by the vendor: [*LibreLinkUp*](https://librelinkup.com/). This enables you to upload your data to the *LibreLinkUp* servers and then access the data from there.
 
 **The use of *LibreLinkUp* requires internet access via WiFi or Cell service.**
@@ -139,6 +147,8 @@ Yes.
 
 ## CGM Customization
 
+> Coming soon *Libre* 3/3+ support is available in [next-dev branch](../version/development.md#updates-in-dev){: target="_blank"} for experienced users
+
 If you can connect your CGM directly to *Loop* that is preferred. You can customize the *Loop* app to interface with the *xDrip4iOS* DIY CGM app if you prefer.  You can use *xDrip4iOS* as a follower instead of a client to get some features from *xDrip4iOS* without any need to customize the *Loop* app.
 
 If possible, it is recommended that *Libre* users take advantage of [LibreTransmitter](https://github.com/LoopKit/LibreTransmitter/blob/main/readme.md) which is incorporated into the *Loop* app for version 3.4 and later. However, some *Libre* sensors have encryption that limits ability to get data through open-source code and instead requires using the *LibreLinkUp* server.

docs/faqs/omnipod-faqs.md

@@ -1,65 +1,81 @@
-## Which pods work with the *Loop* app?
+## Which Pods work with the *Loop* app?
 
-You can use DASH and Eros Omnipod pods with the *Loop* app. You cannot use Omnipod 5 pods.
+You can use Omnipod 5, DASH and Eros Omnipod Pods with the *Loop* app.
+
+* The Omnipod 5 is only available in the development branches while in open beta testing
 
 You do not need the Omnipod Personal Diabetes Manager (PDM), just the pod supplies. Your insurance or pharmacy coverage may cover some of the cost.
 
 !!! info "Alternative Names for Omnipod Pods"
 
-    All three types of pods can be packaged five to a box, don't let the 5-pack indication confuse you. 
+    All three types of Pods can be packaged five to a box, don't let the 5-pack indication confuse you. 
 
-    * **Eros** pods are also known as **Classic** or **UST400**
+    * **Eros** Pods are also known as **Classic** or **UST400**
         * The Reference number on the boxes should be similar to POD-ZXP425
         * They have a clear needle cap
-        * Pharmacy sites sometimes may refer to the **Eros pods** as **Gen 3** but they are the same exact pods
+        * Pharmacy sites sometimes may refer to the **Eros Pods** as **Gen 3** but they are the same exact Pods
 
-    * DASH pods have DASH in the name
+    * **DASH** Pods have DASH in the name
         * The Reference number on the box should be similar to POD-BLE-P1-525 (note the **P**)
         * They have a blue needle cap
 
-    * Omnipod 5 pods have 5 in the name
-        * The Reference number on the box should be similar to POD-BLE-H1-525 (note the **H**)
+    * **Omnipod 5** Pods have 5 in the name
+        * The Reference number on the box should be similar to POD-OMNI-I1-6720 (note the **OMNI**)
         * They have a clear needle cap
 
-DASH pumps communicate with the phone via Bluetooth so they do not require a RileyLink compatible device.
+DASH and Omnipod 5 pumps communicate with the phone via Bluetooth so they do not require a RileyLink compatible device.
+You may find the Omnipod 5 a little slower than the DASH because of the extra layer of security added to these Pods.
+
+!!! tip "To date, no iPhone model specific issues have been found with Omnipod 5 Pods"
+
+### Increase in DASH Faults
+
+There have been a number of lots of Atlas DASH Pods that exhibit an increase in the frequency of certain DASH Faults when used with iOS Open-Source Automated Insulin Delivery Systems (OS-AID). This is different from the Bluetooth connection issues for some iPhone models: see [Keep Alive: Atlas or InPlay DASH Pods](#keep-alive-atlas-or-inplay-dash-pods).
 
+To the best of our knowledge this is not something that we (as OS-AID developers and users) can control. People who have boxes that fail early find most Pods in that box fail early.
 
-### Atlas or InPlay DASH pods
+* The 203 fault is the most common one to exhibit an increase in frequency; occuring on the third day of Pod life
+* The 016 fault also exhibits an increased frequency and this one happens early in Pod life
+* You may be able to get Insulet to replace these, but there is no guarantee
+
+We have looked at the analytics reported from Loop users who [share their data](../loop-3/onboarding.md#usage-data-sharing){: target="_blank" }. The increase in fault rate appears to go along with the increased used of Atlas Pods. Reports from users that their Pods failed early started in November/December of 2025 and continues to increase through at least May 2026. Note that 203 and 016 faults have been around for a long time. The increased fault rate (almost 20 times more likely for 203 and 4 times more likely for 016) is associated with the Atlas DASH Pods which use a different internal card with different firmware.
+
+### Keep Alive: Atlas or InPlay DASH Pods
 
 !!! 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.
+    **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 models other than 17e, work fine with InPlay DASH pods**
+    **Other phones, including iPhone 17 models other than 17e, do not have the reconnection problems with InPlay DASH Pods** - but see [Increase in DASH Faults](#increase-in-dash-fault) which affects all phone models and seems to be box specific.
 
-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.
+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 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
+* The left images show the SAW marking for `TWI Board` DASH Pods
+* The right images show the Atlas marking for `InPlay BLE` DASH Pods
 * The exact location of the marking varies according to manufacture location and date but the `SAW` or `Atlas` notation indicates the internal BLE configuration for that pod
 
-![identifying marks for SAW and Atlas DASH pods](img/saw-atlas-identifiers.svg){width="750"}
+![identifying marks for SAW and Atlas DASH Pods](img/saw-atlas-identifiers.svg){width="750"}
 {align="center"}
 
 #### 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 and iPhone 17e
-* Although `InPlay` pods do work with the iPhone 16 and 17e 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 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 the phone. 
+    * 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 [Pod Keep Alive Feature](../loop-3/omnipod.md#pod-keep-alive-feature){: target="_blank" } section. This used to be found only in a feature branch but as of v3.14.0 is part of the released Loop code
+        * If you are forced to use an iPhone 16 or 17e with InPlay Pods, please read the [Pod Keep Alive Feature](../loop-3/omnipod.md#pod-keep-alive-feature){: target="_blank" } section. This used to be found only in a feature branch but as of v3.14.0 is part of the released Loop code
 
-> 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.
+> 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. 
+> 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 or iPhone 17e. Otherwise, you won't notice a difference.
 
@@ -70,13 +86,15 @@ We have no insight into the deployment plans from Insulet. Just pay attention if
 
 *Tidepool Loop* was approved by the FDA in Jan 2023. In 2025, the [Sequel twiist pump](https://www.twiist.com/) became available with *Tidepool Loop*. Check their site to see if it available in your area.
 
-There is no arrangement for using an FDA cleared version of the Loop app with Omnipod. You must still build it yourself to use Omnipod Eros or DASH pods.
+There is no arrangement for using an FDA cleared version of the Loop app with Omnipod. You must still build it yourself to use Omnipod Eros or DASH Pods.
 
 - - -
 
 ## Do I still need a PDM with Omnipod Loop?
 
-No, pods are monogamous little creatures. They will pair with only one device at a time for safety reasons...so a pod is either paired with a PDM or your *Loop* app on your iPhone. In other words, your PDM can stay in the diabetes closet while you are Looping. You cannot use the PDM for a pod that has been activated with the *Loop* app. That doesn't mean you should get rid of your PDM if you have one. Instead, keep it for backup situations if you lose your phone. See below for what to do if you lose your phone or RileyLink.
+You don't need a PDM to use Pods with your OS-AID system but you might need a PDM serial number registered to your Insulet account to get replacements for failed Pods.
+
+Pods are monogamous little creatures. They will pair with only one device at a time for safety reasons...so a pod is either paired with a PDM or your *Loop* app on your iPhone. In other words, your PDM can stay in the diabetes closet while you are Looping. You cannot use the PDM for a pod that has been activated with the *Loop* app. That doesn't mean you should get rid of your PDM if you have one. Instead, keep it for backup situations if you lose your phone. See below for what to do if you lose your phone or RileyLink.
 
 - - -
 
@@ -144,13 +162,15 @@ For pod users, your pod will finish any currently running temporary basal rate a
 
 ## Is there an increase in pod failures on Loop?
 
+This section used to be accurate. But there is an issue with some Atlas DASH pods that we don't understand, but we have statistics indicating a big increase in frequency of faults (Pods starting to scream). See [Increase in DASH Faults](#increase-in-dash-faults).
+
 There is more communication between the pod and the controller (your *Loop* phone) than is typical with the PDM (Insulet provided controller). This increases the load on the pod battery. Most people have no increase in pod failures, but there are steps to take to limit "extra pod battery use". Every time the *Loop* app requests an update of the pod state or issues a command (bolus, basal schedule, temp basal), messages are exchanged with the pod.
 
 * Set your correction range to be 10 to 20 mg/dL (0.5 to 1.1 mmol/L) instead of a single number
     * The number of commands will be reduced
 * The pod state is updated every 3 minutes for DASH and every 5 minutes for Eros
 * If uncertain communications are detected such that the *Loop* app cannot determine if a dosing command sent to the pod was actually received, the app will try once a minute to get a response
-    * The combination of Eros pods with a RileyLink device with poor signal leading to uncertain comms may cause excessive battery use and contribute to pod faults
+    * The combination of Eros Pods with a RileyLink device with poor signal leading to uncertain comms may cause excessive battery use and contribute to pod faults
 
 - - -
 
@@ -237,3 +257,5 @@ stateDiagram-v2
 !!! tip "What to do if the Pod becomes useless?"
     - Be sure to [break the sound card connection](#what-do-you-do-to-stop-a-screaming-pod) before discarding the Pod - it will scream after 80 hours, if not sooner.  
     - Be sure to move the old Pod far away before attempting to pair a new Pod.
+        - You can put the old Pod in the microwave to shield it while pairing the new one - be sure to take it out before you start the microwave
+        - Breaking the connection to the sound card does **not** deactivate the Pod communications - it only stops the noise