diff --git a/docs/build/cgm.md b/docs/build/cgm.md index abfb05f11c2..377dcefc27a 100644 --- a/docs/build/cgm.md +++ b/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 diff --git a/docs/build/phone.md b/docs/build/phone.md index de0e4557c3c..2aec93e3353 100644 --- a/docs/build/phone.md +++ b/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,9 +47,9 @@ 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 +These phones are compatible with *iOS* 17, 18 and 26. The next version of the *Loop* app will require *iOS* 18 as a minimum. - iPhone 15, all variants - iPhone 14, all variants @@ -68,7 +68,7 @@ These phones are compatible with *iOS* 17, 18 and 26 ### Older Devices -These phones are limited to *iOS* 16. No longer supported by *Dexcom*. Update ASAP. +These phones are limited to *iOS* 16. No longer supported by *Dexcom*. Update ASAP. The next version of the *Loop* app will require *iOS* 18 as a minimum. - iPhone X, without an extra letter - iPhone 8, all variants diff --git a/docs/build/pump.md b/docs/build/pump.md index 3e7e308452a..820168421cd 100644 --- a/docs/build/pump.md +++ b/docs/build/pump.md @@ -29,7 +29,7 @@ These types of pumps are compatible with the *Loop* app. * [Omnipod Eros Pods](pump.md#omnipod-pumps) * [Omnipod DASH Pods](#omnipod-dash) * See caveat about [iPhone 16 and 17e](phone.md#compatible-device){: target="_blank" } -* [Omnipod 5 Pods](#omnipod-5) are not supported yet +* [Omnipod 5 Pods](#omnipod-5) are not in released code, for [details](#omnipod-5) * [Medtrum Touchcare Nano](#medtrum-nano) (v3.14.2 or newer) * [Older Medtronic pumps](pump.md#check-medtronic-pump-version) @@ -47,13 +47,13 @@ You must build a special branch to test some pumps. Please only test if you are ### Omnipod Eros -Eros pods (also known as Gen 3 or Classic) were launched in 2013 and continue to be sold by Insulet in some countries. Insulet stopped providing Eros pods in the US end of December 2023. As far as we know, there are no timelines announced for the discontinuation of Eros pods for other countries. Insulet doesn't specifically call these "Eros" anymore, they just use the term "Omnipod system". For clarity, from [Insulet's webpage](https://www.omnipod.com/discontinuation): +Eros Pods (also known as Gen 3 or Classic) were launched in 2013 and continue to be sold by Insulet in some countries. Insulet stopped providing Eros Pods in the US end of December 2023. As far as we know, there are no timelines announced for the discontinuation of Eros Pods for other countries. Insulet doesn't specifically call these "Eros" anymore, they just use the term "Omnipod system". For clarity, from [Insulet's webpage](https://www.omnipod.com/discontinuation): !!! info "Alternative Names for Omnipod Eros Pump and Pods" **Eros** pump is also known as **Classic**, or **UST400**, or *Omnipod Insulin Management* **System**. - 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 Pods. Eros system has a big Personal Diabetes Manager (PDM) that does not look like a phone. @@ -62,7 +62,7 @@ Eros system has a big Personal Diabetes Manager (PDM) that does not look like a ### Omnipod DASH -The DASH system has the newer, slimmer locked-android Personal Diabetes Manager (PDM) and built-in BLE communications in the pod, so there is no requirement for a RileyLink compatible device. +The DASH system has the newer, slimmer locked-android Personal Diabetes Manager (PDM) and built-in BLE communications in the Pod, so there is no requirement for a RileyLink compatible device. **A RileyLink-compatible device is not required to use DASH with the *Loop* app. The communication with your iPhone uses Bluetooth.** @@ -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 - - - diff --git a/docs/faqs/cgm-faqs.md b/docs/faqs/cgm-faqs.md index 75f7daade18..eec2b09273c 100644 --- a/docs/faqs/cgm-faqs.md +++ b/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 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. diff --git a/docs/faqs/omnipod-faqs.md b/docs/faqs/omnipod-faqs.md index f85f37d5fd2..484d28badaf 100644 --- a/docs/faqs/omnipod-faqs.md +++ b/docs/faqs/omnipod-faqs.md @@ -1,51 +1,67 @@ -## 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 (under test), DASH and Eros Pods with the *Loop* app. -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. +* 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. The PDM may be needed in some countries to get replacements for failed Pods. !!! 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 Pods - * DASH pods have DASH in the name - * The Reference number on the box should be similar to POD-BLE-P1-525 (note the **P**) + * **DASH** Pods have DASH in the name + * The Reference number on the box should be similar to POD-BLE-P1-525 * 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 * 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-faults) 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 @@ -53,13 +69,13 @@ Beginning in 2025, some of the DASH pods are produced with a newer version of ch * 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 are likely to 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 diff --git a/docs/loop-3/add-cgm.md b/docs/loop-3/add-cgm.md index 5e5480cfe78..9009b298b34 100644 --- a/docs/loop-3/add-cgm.md +++ b/docs/loop-3/add-cgm.md @@ -15,6 +15,7 @@ Loop can be connected to the following CGMs: * [Dexcom G7 or ONE+](#dexcom-g7-or-one) * [Libre](#libre) **(v3.4 or newer)** * Only some Libre sensors are supported; some have encryption that limits DIY use + * Coming soon *Libre* 3/3+ support is available in [next-dev branch](../version/development.md#updates-in-dev){: target="_blank"} for experienced users * [Eversense E3/365](#eversense-e3365) **v3.14.2 or newer** * [Minimed Enlite CGM](#medtronic-enlite-cgm) * Medtronic Pump only @@ -141,7 +142,9 @@ The Libre plugin for Loop, [LibreTransmitter](https://github.com/LoopKit/LibreTr * Libre 1 is supported but must use a third-party transmitter (miaomiao and bubble transmitters are supported) * European Libre 2 can be used directly or via transmitter * American Libre 2 is not supported -* Libre 3 is not supported +* Libre 3 is not supported in the released code + +> Coming soon *Libre* 3/3+ support is available in [next-dev branch](../version/development.md#updates-in-dev){: target="_blank"} for experienced users !!! tip "Connecting to Libre" The first reading for a new sensor will often take 2-4 minutes. This is due to some technicalities on how the Libre sensor announces its presence via Bluetooth. diff --git a/docs/loop-3/add-pump.md b/docs/loop-3/add-pump.md index 7663d844f6e..b95d4eab957 100644 --- a/docs/loop-3/add-pump.md +++ b/docs/loop-3/add-pump.md @@ -15,7 +15,7 @@ Loopers can choose from multiple pumps and a simulator: * [All Omnipod Types](#omnipod-setup) (available with v3.14.2 and newer) * Omnipod Classic (Eros) * Omnipod DASH - * Omnipod O5 (coming soon) + * Omnipod O5 (`dev` and `next-dev` only) See [Updates in dev](../version/development.md#updates-in-dev){: target="_blank" } * [Medtrum Nano patch pump](#medtrum-nano-setup) (available with v3.14.2 and newer) * [Minimed](#medtronic-setup) * Note: only some Medtronic Minimed pumps are compatible @@ -28,8 +28,9 @@ Loopers can choose from multiple pumps and a simulator: The Loop app and LoopDocs use these terms. For any supported Pod Type, select `All Omnipod Types` when choosing your pump. * **Omnipod Classic** is the older (Eros) pods (requires [RileyLink](../build/rileylink.md){: target="_blank" } compatible device to Loop) - * **Omnipod DASH** is the newer BLE pods (phone talks directly to pod - no extra device needed to Loop) - * **Omnipod 5** is not yet supported but will be included with the `All Omnipod Types` selection when it is added + * The next two Pod types are BLE pods - no extra device needed + * **Omnipod DASH** is the first version of Insulet BLE pods + * **Omnipod 5** is not yet supported in the released code but when it is, it will be included when selecting a Pod Type - - - @@ -83,11 +84,15 @@ In this screen, you choose the Insulin type you use for your pods. This screen i In this screen you choose the Pod Type you will be pairing. After you make your selection, tap on the blue Confirm Pod Type button. +> If you are an experienced tester running a development branch, you will see the Omnipod 5 Pod type as an option on this screen. + ![initial selection for pod type](img/pod-type.png){width="250"} {align="center"} If you select Classic (Eros) pods, you will be routed to the [Select RileyLink](#select-rileylink) screen before reaching the Pair Pod screen. +If you select Omnipod 5 and you do not have a certificate installed yet, you will be routed to [obtain a certificate](omnipod.md#o5-certificate-status) and then land in the Pair Pod screen. + ### Pair Pod At this point - you can pair your pod or hit `Cancel` (upper right of screen). You have completed the onboarding of the pump manager that handles all supported types of Omnipod Pods. diff --git a/docs/loop-3/img/pair-pod-duo.svg b/docs/loop-3/img/pair-pod-duo.svg deleted file mode 100644 index 80802a178d9..00000000000 --- a/docs/loop-3/img/pair-pod-duo.svg +++ /dev/null @@ -1,7448 +0,0 @@ - -image/svg+xml diff --git a/docs/loop-3/img/pair-pod-screens.svg b/docs/loop-3/img/pair-pod-screens.svg new file mode 100644 index 00000000000..6edd1b9ca67 --- /dev/null +++ b/docs/loop-3/img/pair-pod-screens.svg @@ -0,0 +1,134 @@ + +image/svg+xml diff --git a/docs/loop-3/omnipod.md b/docs/loop-3/omnipod.md index c2443aceefd..623bbe11a92 100644 --- a/docs/loop-3/omnipod.md +++ b/docs/loop-3/omnipod.md @@ -1,34 +1,47 @@ -## Omnipod and Omnipod DASH Pump +## Overview -The information and user interface for Omnipod (Eros) and DASH pods is the same, except Omnipod DASH pods do not require a RileyLink compatible device. They communicate directly with the phone through Bluetooth. +The information and user interface for all Omnipod Pods is the same, except Omnipod 5 and DASH Pods do not require a RileyLink compatible device. They communicate directly with the phone through Bluetooth. + +!!! warning "O5 is in beta test" + Omnipod 5 Pods should only be tested by experienced users willing to build a development branch: + + * LoopWorkspace `dev` + * LoopWorkspace `next-dev` + + The timing for when O5 is supported in these branches depends on when Pull Requests are merged. + + Please thoroughly read [Updates in dev](../version/development.md#updates-in-dev){: target="_blank" } before attempting to use one of these branches. + + +- - - ## Pair Pod !!! danger "Max Fill is 200 Units" When you fill the Pod do not exceed 200 units. - If you overfill the pods, you may get a pod fault right after priming. + If you overfill the Pod, you may get a Pod fault right after priming. !!! info "Pod Filling and Insertion" The Pod filling and insertion instructions are the same with the Loop app as they are for the PDM. These videos: [Filling a Pod with Insulin](https://youtu.be/qJBN6rlvn_Y) and [Inserting the Cannula](https://youtu.be/ss1vpsmaLoI), may be useful. - For DASH Pods: + For Omnipod 5 and DASH Pods: - * You will use your phone instead of the PDM. Be sure to keep the phone close to the pod during pairing and insertion because the Pod uses a low-power mode during these activities. + * You will use your phone instead of the PDM. Be sure to keep the phone close to the Pod during pairing and insertion because the Pod uses a low-power mode during these activities. - For Eros Pods: + For Classic or Eros Pods: * You will use your phone and RileyLink compatible device instead of the PDM. Be sure to keep the phone and RileyLink close during pairing and insertion because the Pod uses a low-power mode during these activities. -You'll be pairing a pod every 2 or 3 days (max pod life is 80 hours). +You'll be pairing a Pod every 2 or 3 days (max Pod life is 80 hours). You'll see this screen every time you ask Loop to `Pair New Pod`. -The Omnipod Common pairing protocol is the same for all pods. The difference is that Omnipod requires a RileyLink compatible device and Omnipod DASH does not. There are also slight differences in some of the text and graphics, e.g., Omnipod DASH uses a blue needle cap and Omnipod has a clear needle cap. +The Omnipod Common pairing protocol is the same for all Pods. The difference is that Classic or Eros Pods require a RileyLink compatible device and Omnipod 5 and DASH do not. There are also slight differences in some of the text and graphics, e.g., Omnipod DASH uses a blue needle cap and both the Classic and Omnipod 5 Pods use a clear needle cap. -Graphic below shows the Pair Pod screen for Omnipod (left) and Omnipod DASH (right). +Graphic below shows the Pair Pod screen for Eros (left), DASH (middle) and O5 (right). -![pair pod screens for Omnipod and Omnipod DASH](img/pair-pod-duo.svg){width="500"} +![pair pod screens for Classic, DASH and Omnipod 5 Pods](img/pair-pod-screens.svg){width="750"} {align="center"} !!! abstract "" @@ -36,30 +49,32 @@ Graphic below shows the Pair Pod screen for Omnipod (left) and Omnipod DASH (rig It makes sure you are really ready to do the insertion. - Please watch the [video of the *Loop* app screen when pairing a DASH pod](https://drive.google.com/file/d/1mN5s8-oorvoa-gbjAaYbnUnl_-vvuhNC/view?usp=sharing) to see the full process before pairing your first pod. In this video, once the pod starts priming, you may want to skip forward (it takes about a minute to prime). + Please watch the [video of the *Loop* app screen when pairing a DASH Pod](https://drive.google.com/file/d/1mN5s8-oorvoa-gbjAaYbnUnl_-vvuhNC/view?usp=sharing) to see the full process before pairing your first Pod. In this video, once the Pod starts priming, you may want to skip forward (it takes about a minute to prime). !!! danger "Keep Gear Close" - * Make sure the phone (and RileyLink if using one) are close to the pod before you tap Pair Pod - * Do NOT move devices away from the pod until you see the blue check mark and the `Continue` button on the phone screen - * You can then move away to attach the pod to your body - * Make sure the phone (and RileyLink if using one) are close to the pod before you tap `Insert Cannula` - * Do NOT move devices away from the pod until you see the blue check mark and the `Continue` button on the phone screen + * Make sure the phone (and RileyLink if using one) are close to the Pod before you tap Pair Pod + * Do NOT move devices away from the Pod until you see the blue check mark and the `Continue` button on the phone screen + * You can then move away to attach the Pod to your body + * Make sure the phone (and RileyLink if using one) are close to the Pod before you tap `Insert Cannula` + * Do NOT move devices away from the Pod until you see the blue check mark and the `Continue` button on the phone screen ### New Slider !!! tip "The Insert Cannula and Deactivate Pod now use a Slider instead of a Button" - For version 3.4.x and later there is a new slider to control insertion of the cannula and deactivation of a pod. + For version 3.4.x and later there is a new slider to control insertion of the cannula and deactivation of a Pod. - The slider looks like the graphic below. (The Deactivate Pod slider is red.) You place your finger on the dark circular icon and, while keeping your finger in contact with the screen, drag all the way to the other side. (The direction depends on the natural direction for your selected language). After the drag operation, as soon as you lift your finger off the phone, the cannula insertion command is sent to the pod. + The slider looks like the graphic below. (The Deactivate Pod slider is red.) You place your finger on the dark circular icon and, while keeping your finger in contact with the screen, drag all the way to the other side. (The direction depends on the natural direction for your selected language). After the drag operation, as soon as you lift your finger off the phone, the cannula insertion command is sent to the Pod. ![slider to insert cannual for Omnipod or Omnipod DASH pumps](img/omnipod-insert-slider.svg){width="250"} {align="center"} -The Screen that says Setup Complete allows you to change the Scheduled Reminder for this pod if you want a different reminder time (including none) from your usual setting. +The Screen that says Setup Complete allows you to change the Scheduled Reminder for this Pod if you want a different reminder time (including none) from your usual setting. -* This only changes the reminder for this one pod +* This only changes the reminder for this one Pod * If you want to change all future reminders, tap on Notifications to modify the Reminder Default -* In that same location, you can also change notification for the current pod at any time +* In that same location, you can also change notification for the current Pod at any time + +- - - ## Pod Status @@ -70,24 +85,24 @@ The Pod Status screen is shown in the graphic below. The dashed green outline in ### Play Beeps -If you want to make sure Loop can talk to your pod, click on the sound icon (highlighted by the red box) in the graphic above. If the icon is greyed out - that means Loop is having a communication issue reaching your pod. Follow the usual [Troubleshoot: Pump is Not Responding](../troubleshooting/red-loop.md#pump-is-not-responding) steps to resolve this problem. +If you want to make sure Loop can talk to your Pod, click on the sound icon (highlighted by the red box) in the graphic above. If the icon is greyed out - that means Loop is having a communication issue reaching your Pod. Follow the usual [Troubleshoot: Pump is Not Responding](../troubleshooting/red-loop.md#pump-is-not-responding) steps to resolve this problem. !!! tip "Other Uses" * Find (or startle) your child - * Find the pod that fell off overnight and is mixed with the laundry + * Find the Pod that fell off overnight and is mixed with the laundry ### Pod Expires -* This line provides a count-down until expiration along with a graphical representation of pod life +* This line provides a count-down until expiration along with a graphical representation of Pod life * Once you are on the final day, the time remaining until expiration starts to report in Hours and Minutes - * The solid bar is proportional to pod hours since activation + * The solid bar is proportional to Pod hours since activation * It is blue for the first 48 hours * It is orange for the last 24 hours and also appears in the [HUD Pump Status](displays-v3.md#pump-status-icon) icon * After expiration, a full-width red bar is shown here and in the HUD Pump Status icon -* Once the pod officially expires, at 72 hours, there is an 8 hour grace period - * Insulet does not guarantee the pod will keep working that long, but it often does +* Once the Pod officially expires, at 72 hours, there is an 8 hour grace period + * Insulet does not guarantee the Pod will keep working that long, but it often does * A note will appear on the [Pod Status](#pod-status) screen with count-down text: - * Change pod now. Insulin delivery will stop in HH hours, MM minutes or when no more insulin remains + * Change Pod now. Insulin delivery will stop in HH hours, MM minutes or when no more insulin remains ### Basal Report @@ -107,8 +122,10 @@ Pods start reporting reservoir values when 50 U are left. |---|---| |50+ U|Pod reservoir is greater than 50 U| |Value U|Pod reservoir is estimated to be at least as great as the indicated value.| -| 0 U|Pod will attempt to deliver up to 4 U after it reports 0 U.

This is not guaranteed. The pod senses when it is not successful delivering pulses and that can happen before 4 U have been delivered.| +| 0 U|Pod will attempt to deliver up to 4 U after it reports 0 U.

This is not guaranteed. The Pod senses when it is not successful delivering pulses and that can happen before 4 U have been delivered.| + +- - - ## Actions @@ -116,16 +133,16 @@ Pods start reporting reservoir values when 50 U are left. You may want to consider using a [Manual Temp Basal](#manual-temp-basal) of 0 U/hr instead of suspend. -Tapping on `Suspend Delivery` brings up a timed reminder screen. You can choose to be reminded (via a beep on the pod itself) with 4 choices (or you can cancel the request): +Tapping on `Suspend Delivery` brings up a timed reminder screen. You can choose to be reminded (via a beep on the Pod itself) with 4 choices (or you can cancel the request): * 30 minutes * 1 hour * 1 hour 30 minutes * 2 hours -After you select the reminder time, Loop issues a command to the pod to halt all insulin delivery: basals, temp basals, and boluses in progress. The label on the `Suspend Delivery` row changes to `Suspending` while Loop is communicating with the pump. When the label changes to `Resume Delivery`, all insulin delivery is stopped until the user resumes using the [HUD Status Row](displays-v3.md#hud-status-row) or the [Pod Status](#pod-status) screen. +After you select the reminder time, Loop issues a command to the Pod to halt all insulin delivery: basals, temp basals, and boluses in progress. The label on the `Suspend Delivery` row changes to `Suspending` while Loop is communicating with the pump. When the label changes to `Resume Delivery`, all insulin delivery is stopped until the user resumes using the [HUD Status Row](displays-v3.md#hud-status-row) or the [Pod Status](#pod-status) screen. -As long as the spinning icon is spinning, Loop is trying to execute the Suspend or Resume command. If it fails to complete, a modal alert will appear that says "Error Suspending" or "Failed to Resume Insulin Delivery" which you must acknowledge. You must then repeat the command to try again. For Omnipod, make sure your RileyLink device is powered on and close to the phone and pod. +As long as the spinning icon is spinning, Loop is trying to execute the Suspend or Resume command. If it fails to complete, a modal alert will appear that says "Error Suspending" or "Failed to Resume Insulin Delivery" which you must acknowledge. You must then repeat the command to try again. For Omnipod, make sure your RileyLink device is powered on and close to the phone and Pod. When the phone is in portrait mode, so the HUD is visible: @@ -141,14 +158,14 @@ When the phone is in portrait mode, so the HUD is visible: #### No Manual Bolus While Pod is Suspended -If you request a manual bolus with Loop while a pod is suspended, Loop will send a notification that Bolus Failed with instructions that Pump is Suspended, Resume Delivery. In other words, you must resume delivery before you will be allowed to bolus with pods. +If you request a manual bolus with Loop while a Pod is suspended, Loop will send a notification that Bolus Failed with instructions that Pump is Suspended, Resume Delivery. In other words, you must resume delivery before you will be allowed to bolus with Pods. #### Suspend Timer Reminder -At the end of the reminder time, an alert beep is issued by the pod and a modal alert will be provided on the Loop app. You must acknowledge the modal alert on the phone to silence future pod alerts. +At the end of the reminder time, an alert beep is issued by the Pod and a modal alert will be provided on the Loop app. You must acknowledge the modal alert on the phone to silence future Pod alerts. -* If you do not acknowledge the modal alert, the pod will keep beeping -* If you need a silent pod, consider using [Manual Temp Basal](#manual-temp-basal) of 0 U/hr instead of Suspend +* If you do not acknowledge the modal alert, the Pod will keep beeping +* If you need a silent Pod, consider using [Manual Temp Basal](#manual-temp-basal) of 0 U/hr instead of Suspend ![reminder that insulin is suspended](img/modal-alert-suspended.svg){width="300"} {align="center"} @@ -160,7 +177,7 @@ At the end of the reminder time, an alert beep is issued by the pod and a modal * Basal Delivery automatically resumes at the end of the selected duration without need for Loop to command it * At the end of the duration, Loop will restore Closed Loop, if you were in closed loop when you issued the Manual Temp Basal command - * There are no beeps on the pod to remind you to resume insulin delivery + * There are no beeps on the Pod to remind you to resume insulin delivery ### Manual Temp Basal @@ -171,7 +188,7 @@ This brings up the `Temporary Basal` screen shown on the left of the graphic bel * You can select any basal rate from 0 U/hr to your maximum basal rate set in [Delivery Limits](therapy-settings.md#maximum-basal-rate) * You can choose any duration up to 12 hours in half-hour increments -* Once you select rate and duration and tap `Set Temporary Basal`, Loop goes into Open Loop mode and the pod is commanded to that rate and duration. +* Once you select rate and duration and tap `Set Temporary Basal`, Loop goes into Open Loop mode and the Pod is commanded to that rate and duration. In other words, you can leave your phone behind and the selected basal rate continues for the selected basal duration. There will be no automated adjustments of delivery for the temp basal duration.

@@ -181,17 +198,17 @@ In other words, you can leave your phone behind and the selected basal rate cont #### During Manual Temp Basal !!! warning "This Pod Only" - The manual temp basal command from Loop tells the pod to initiate a temp basal for the designated rate and duration. + The manual temp basal command from Loop tells the Pod to initiate a temp basal for the designated rate and duration. - * The pod itself takes care of the temp basal with no further interaction with Loop - * Loop will no longer issue commands to the pod without manual intervention from the user until the expected duration ends or user selects `Cancel Manual Basal` - * Loop continues to request and receive status reports from the pod while the pod is within communication range + * The Pod itself takes care of the temp basal with no further interaction with Loop + * Loop will no longer issue commands to the Pod without manual intervention from the user until the expected duration ends or user selects `Cancel Manual Basal` + * Loop continues to request and receive status reports from the Pod while the Pod is within communication range - **Deactivating this pod and pairing a new one interrupts the temp basal.** + **Deactivating this Pod and pairing a new one interrupts the temp basal.** - **If you still need that basal rate, you must initiate it on the new pod.** + **If you still need that basal rate, you must initiate it on the new Pod.** -Once the manual temp basal command is sent to the pod, Loop changes to Open Loop mode and updates displays as shown in the graphic above +Once the manual temp basal command is sent to the Pod, Loop changes to Open Loop mode and updates displays as shown in the graphic above * [Pod Status](#pod-status) screen: * The [Basal Report](#basal-report) updates with the new rate and label indicates `Insulin Delivery` @@ -204,9 +221,9 @@ Once the manual temp basal command is sent to the pod, Loop changes to Open Loop So long as you were in Closed Loop before requesting the Temp Basal, Loop returns to Closed Loop automatically when the duration ends or you cancel the temporary basal. !!! info "Automatic Resumption of Scheduled Basal" - The phone does not need to be in contact with the pod for insulin delivery to return to scheduled basal at the end of the selected duration. That duration is commanded along with the temporary rate. Once the pod accepts that command, and you'll get an error message if it does not, the pod will resume scheduled basal rate without further commanding if there is insulin in the reservoir and a pod fault does not occur. + The phone does not need to be in contact with the Pod for insulin delivery to return to scheduled basal at the end of the selected duration. That duration is commanded along with the temporary rate. Once the Pod accepts that command, and you'll get an error message if it does not, the Pod will resume scheduled basal rate without further commanding if there is insulin in the reservoir and a Pod fault does not occur. -For situations where you need a modification of your insulin needs that is not dependent on a particular pod, review the information on the [Overrides](../operation/features/overrides.md) page. +For situations where you need a modification of your insulin needs that is not dependent on a particular Pod, review the information on the [Overrides](../operation/features/overrides.md) page. ### Devices @@ -217,67 +234,98 @@ For Omnipod, there is a Devices section used to access the [RileyLink](../loop-3 The next section on the Pod screen reports: -* Time at which pod was Activated -* Time at which pod will Expire -* Access to Current Pod Details -* Access to Previous Pod Details +* **Activation**: Time at which Pod was Activated +* **Expiration**; Time at which Pod will Expire +* **No Deliver**: Time at which Pod stops delivery insulin + * If the Pod faults, this row changes to **Faulted** and reports the time of the fault +* **Pod Details**: Access to Current Pod Details +* **Previous Pod**:Access to Previous Pod Details ![section of Pod Status screen with Pod Details](img/pod-status-details.svg){width="350"} {align="center"} !!! question "Time Drift" - The pod will expire when it thinks it has been 80 hours. The pod clock may drift a few seconds with respect to phone time during the pod life. The Expiration time gets updated when the pod reports how long it thinks it has been since it was activated. + The Pod will expire when it thinks it has been 80 hours. The Pod clock may drift a few seconds with respect to phone time during the Pod life. The Expiration time gets updated when the Pod reports how long it thinks it has been since it was activated. #### Pod Details -Some additional details for the most recent pod status response message are displayed if you tap the Device Details row, as shown in the graphic below. Most people will not need to view this. +Some additional details for the most recent Pod status response message are displayed if you tap the Device Details row, as shown in the graphic below. Most people will not need to view this. The graphic shows an example for Omnipod on the left, Omnipod DASH (TWI BOARD) in the middle and Omnipod DASH (NXP BLE) on the right. Do not worry about the different board styles (Device Name) for DASH. The developers did that for you. If you are asking for help from a mentor - they may request this information. ![section of Pod Status screen with Pod Details](img/omnipod-device-details.svg){width="600"} {align="center"} -#### Previous Pod Details +#### Previous Pod -When you tap on the `Previous Pod Details` row, a graphic similar to those shown below is displayed. This provides summary information about the pod before the one currently in use. +When you tap on the `Previous Pod` row, a graphic similar to those shown below is displayed. This provides summary information about the Pod before the one currently in use. -If the previous pod had a fault and you choose to report it to Insulet, this screen reports the PDM reference code that Insulet uses in their tracking system. +If the previous Pod had a fault and you choose to report it to Insulet, this screen reports the PDM reference code that Insulet uses in their tracking system. ![previous pod information screen, both for DASH, left was nominal pod and right had a pod fault](img/omnipod-previous.svg){width="600"} {align="center"} !!! bug "Do Not Call Insulet about -049 (0x31) Faults" - If you should happen to get a fault where the last 3 digits of the PDM ref code are "-049" (the Hex Designation is fault code 0x31), do **not** report this to Insulet and do **not** ask for a replacement. This means Loop did not ensure the pod was in the correct state to accept a command. In other words, it was a bug in the Loop code. + If you should happen to get a fault where the last 3 digits of the PDM ref code are "-049" (the Hex Designation is fault code 0x31), do **not** report this to Insulet and do **not** ask for a replacement. This means Loop did not ensure the Pod was in the correct state to accept a command. In other words, it was a bug in the Loop code. We believe the code has been updated to prevent these faults. There was a brief period during development in which at least one of these happened - this was fixed July 3, 2022. If this happens to you, report it on zulipchat for the developers, save a Loop Report and rebuild if you have an older version of the development code. +- - - -## Replace Pod +## Deactivate Pod -When you tap on the `Replace Pod` row, the `Deactivate Pod` screen, shown below, is displayed. +When you tap on the `Deactivate Pod` row, the `Deactivate Pod` screen, shown below, is displayed. * Touch the circular icon and maintain contact while you slide your finger all the way across the phone - * When you release the slide, the deactivation command is sent to the pod - * This action stops insulin delivery for this pod and cannot be resumed -* If you have changed your mind, tap Back or Cancel to continue using the pod + * When you release the slide, the deactivation command is sent to the Pod + * This action stops insulin delivery for this Pod and cannot be resumed +* If you have changed your mind, tap Back or Cancel to continue using the Pod ![Deactivate pod screen](img/omnipod-deactivate.svg){width="300"} {align="center"} +When deactivation completes, you are presented with the [Pair Pod](#pair-pod) screen, ready for you to pair another Pod of the same type. + +- - - + +## Change Pod Types + +After the Pod is deactivated, you can choose to switch to a different Pod Type. Simply cancel out of the Pair Pod screen that is normally displayed following deactivation. + +At that point, you can scroll to the bottom of the Omnipod screen and select the row that says *Switch to another pod or pump type*. Tapping on that row displays the screen, shown below, where you can choose *Switch pod type* or *Switch pump type*. + +![how to switch from any omnipod pot type to a different pod or pump type](img//omnipodkit-switch-pod-pump.png){width="350"} +{align="center"} + +If you select Switch pod type, you are taken to the [Pod Type](#pod-type) Selection screen + +* All of your configuration settings including Insulin brand are maintained when switching Pod Types + + +!!! important "The Omnipod 5 is only available in the [development branches](../version/development.md#updates-in-dev){: target="_blank"} while in open beta testing" + +If you are using a development branch and choose Omnipod 5 Pod Type and have not previously gotten a certificate, one will be automatically downloaded for you. + +* This one-time step that requires internet access +* Once a certificate is successfully downloaded, you will be taken to the [Pair Pod](#pair-pod) screen for Omnipod 5 + +For more information, see [Omnipod 5 Support](#omnipod-5-support). + + +- - - ## Configuration ### Notification Settings -When you tap on the `Notifcation Settings` row, the graphic below is displayed. The notifications are a combination of beeps on the pod with associated modal alerts on the phone app that must be acknowledged to prevent future beeps. +When you tap on the `Notifcation Settings` row, the graphic below is displayed. The notifications are a combination of beeps on the Pod with associated modal alerts on the phone app that must be acknowledged to prevent future beeps. + +If a pod is active, you can modify the Expiration Reminder and Low Reservoir Reminder for that Pod as applicable -* Expiration Reminder Default: changes the reminder time for any future pod (not the current one) -* Scheduled Reminder: affects the reminder for the current pod (not future pods) - * If no pod is connected, you will not see the Scheduled Reminder section -* Low Reservoir Reminder: changes the reminder level for the current pod and all future pods - * If no pod is connected, the app will not allow you to modify this setting - * Change it after the next pod is paired +The defaults for futures Pods are always accessible +* Expiration Reminder Default: changes the reminder time for any future Pod +* Low Reservoir Reminder: changes the reminder level for all future Pods * Critical Alerts: Information row about which alerts can be silenced by phone settings ![Notification selection screen to set up default reminders](img/omnipod-notification.svg){width="300"} @@ -286,12 +334,12 @@ When you tap on the `Notifcation Settings` row, the graphic below is displayed. ### Confidence Reminders -When you tap on the `Confidence Reminder` row, the graphic below is displayed. You can choose from three levels of audible responses that Loop requests from the pod: +When you tap on the `Confidence Reminder` row, the graphic below is displayed. You can choose from three levels of audible responses that Loop requests from the Pod: -* Disabled: no audible pod alerts to acknowledge commands +* Disabled: no audible Pod alerts to acknowledge commands * Enabled: each manual command provides an audible sound to acknowledge it: - * For manual dosage change, the pod beeps at both the beginning and end of the manual command. - * For automated dosage change, the pod does not beep. + * For manual dosage change, the Pod beeps at both the beginning and end of the manual command. + * For automated dosage change, the Pod does not beep. * Extended: Automated dosage change beeps, similar to the manual commands when set to `Enabled` ![Confidence reminder selection screen, the current selection is enabled as indicated by the blue check mark](img/omnipod-confidence.svg){width="300"} @@ -299,13 +347,13 @@ When you tap on the `Confidence Reminder` row, the graphic below is displayed. ### Silence Pod -The Silence Pod feature is new with version 3.4.x. This allows a user to tap on silence pod to prevent any noises from the pod, other than critical faults. +The Silence Pod feature is new with version 3.4.x. This allows a user to tap on silence Pod to prevent any noises from the Pod, other than critical faults. What Silence Pod will not do: * This feature cannot change the "clicking" noise that comes from insulin delivery -* This feature will not prevent the constant alarm if the pod fails for any reason such as out-of-time, out-of-insulin, occlusion detected or any other fault -* If you tap on the sound icon, the beeps will still be heard on the pod +* This feature will not prevent the constant alarm if the Pod fails for any reason such as out-of-time, out-of-insulin, occlusion detected or any other fault +* If you tap on the sound icon, the beeps will still be heard on the Pod When would you use Silence Pod: @@ -313,17 +361,17 @@ When would you use Silence Pod: * During a religious event * Attending a performance * Performing at an event -* Planning to change your pod in the morning, but you know alerts will happen overnight -* You will be away from your phone for an activity and want to avoid any Notifications from beeping on the pod - * Notifications, unless silenced, alert on the phone and the pod - * The pod beeps continue until acknowledged on the phone - * If Silence Pod is enabled, the pod beeps will be suppressed +* Planning to change your Pod in the morning, but you know alerts will happen overnight +* You will be away from your phone for an activity and want to avoid any Notifications from beeping on the Pod + * Notifications, unless silenced, alert on the phone and the Pod + * The Pod beeps continue until acknowledged on the phone + * If Silence Pod is enabled, the Pod beeps will be suppressed * When you return your phone, examine alerts for those notications Caveats: -* You must remember to disable Silence Pod if you want to hear Notifications and Confidence Reminders as pod beeps in addition to alerts on your phone -* The settings you have under Notifications and Confidence Reminders are not changed, the pod beeps associated with them are simply silenced while Silence Pod is Enabled +* You must remember to disable Silence Pod if you want to hear Notifications and Confidence Reminders as Pod beeps in addition to alerts on your phone +* The settings you have under Notifications and Confidence Reminders are not changed, the Pod beeps associated with them are simply silenced while Silence Pod is Enabled The graphic below shows the Silence Pod control. This is only available for v3.4.x and later. @@ -339,9 +387,11 @@ Tap on this row if you switch to a different type of insulin. * The model used by Loop for all the rapid insulin brands are the same, but it's a good idea to record if you change brands - some people notice differences * If you switch between rapid and ultra-rapid insulin, you need to let Loop know so it will use the appropriate model +- - - + ## Pump Time -Click on [Time Zone](displays-v3.md#time-zone) to understand how Loop treats "pump" time for pods. +Click on [Time Zone](displays-v3.md#time-zone) to understand how Loop treats "pump" time for Pods. When the Pump time zone matches the phone time zone, the Pump Time is displayed with black font. @@ -368,33 +418,33 @@ Loop 3 will display this warning modal screen if it detects a problem with the P ### Pod Error Messages -This section presents some of the error message screens you may see specific to pods. +This section presents some of the error message screens you may see specific to Pods. #### Pod Faults -You are likely to hear a pod fault before Loop notices. If your phone is locked, Loop only checks status every 5 minutes for Omnipod or 3 minutes for Omnipod DASH. +You are likely to hear a Pod fault before Loop notices. If your phone is locked, Loop only checks status every 5 minutes for Omnipod or 3 minutes for Omnipod DASH. -Unlock your phone, open Loop, navigate to the Pod Status screen and use the slider to Deactivate Pod to stop the noise. The pod fault - even if it does not show up in the HUD or the Pod Status screen, will be picked up by the process of sliding to Deactivate Pod. You can then view the Fault information in the [Previous Pod Details](#previous-pod-details) screen. +Unlock your phone, open Loop, navigate to the Pod Status screen and use the slider to Deactivate Pod to stop the noise. The Pod fault - even if it does not show up in the HUD or the Pod Status screen, will be picked up by the process of sliding to Deactivate Pod. You can then view the Fault information in the [Previous Pod Details](#previous-pod) screen. #### Updates with Version 3.4.x -The updates included with version 3.4.x make it easier to find the pod fault, should one occur. +The updates included with version 3.4.x make it easier to find the Pod fault, should one occur. The fault will appear on the Omnipod screen and more details will be shown when you tap on Replace Pod to arrive at the Deactivate screen. You can grab a quick screenshot on the Deactivate screen if desired. -The fault information can still be found under [Previous Pod Details](#previous-pod-details) if you need to find it after you Deactivate the "screaming" pod. +The fault information can still be found under [Previous Pod Details](#previous-pod) if you need to find it after you Deactivate the "screaming" Pod. - - - ## Pod Keep Alive Feature -No better solution has been found for dealing with Atlas pods with iPhone 16 (all models) and iPhone 17e. Therefore, the features previously found just in the `feat/pod-keep-alive` branch of LoopWorkspace are part of the released code as of version 3.14.0. +No better solution has been found for dealing with the difficulty reconnecting Atlas DASJ Pods with iPhone 16 (all models) and iPhone 17e. Therefore, the features previously found just in the `feat/pod-keep-alive` branch of LoopWorkspace are part of the released code as of version 3.14.0. -There is 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. +There is 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#keep-alive-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. -The concept is by choosing one of the Pod Keep Alive choices, the app sends a getStatus to the pod before the 3 minute disconnect happens. Therefore, so long as you and the pod stay close to the phone, the pod will be connected for any command (either manual or automatic) including bolus, temp basal, modify scheduled basal rates, suspend, or deactivate. +The concept is by choosing one of the Pod Keep Alive choices, the app sends a getStatus to the Pod before the 3 minute disconnect happens. Therefore, so long as you and the Pod stay close to the phone, the Pod will be connected for any command (either manual or automatic) including bolus, temp basal, modify scheduled basal rates, suspend, or deactivate. The selection for Pod Keep Alive is found at the bottom of the Pod settings screen. @@ -414,47 +464,86 @@ There are 4 choices for Pod Keep Alive: When Pod Keep Alive is disabled, the code behavior is unchanged from the nominal OmniBLE code. -!!! warning "Automatic Change for iPhone 16 or 17e and Atlas DASH pod" - If your app has Pod Keep Alive set to disabled and you have an **iPhone 16** or **iPhone 17e** and the pod you just paired is an **InPlay (Atlas) pod**, the configuration **automatically** switches to **When Open**. +!!! warning "Automatic Change for iPhone 16 or 17e and Atlas DASH Pod" + If your app has Pod Keep Alive set to disabled and you have an **iPhone 16** or **iPhone 17e** and the Pod you just paired is an **InPlay (Atlas) Pod**, the configuration **automatically** switches to **When Open**. The Pod Keep Alive configuration remains at **When Open** until you change it manually. All three criteria must be true or no automatic change to the setting takes place: * iPhone 16 (any model) or iPhone 17e -* pair a new pod that is InPlay BLE (Atlas) +* pair a new Pod that is InPlay BLE (Atlas) * Pod Keep Alive is Disabled 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. +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. -Once the pod is inserted, the phone auto-lock timing is restored to the value the user has selected. +Once the Pod is inserted, the phone auto-lock timing is restored to the value the user has selected. ### When Open -When the app is open, it 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 to the phone. +When the app is open, it 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 to the phone. + +This is true as long as the phone and Pod are in-range while the app is open with phone unlocked. -This is true as long as the phone and pod are in-range while the app is open with phone unlocked. +This mode is primarily to help out people who just paired an Atlas Pod for the first time with an iPhone 16 or 17e. It is meant to keep the Pod connected to the phone until the cannula is inserted. -> If the pod moves out of Bluetooth range, the pod disconnects. With iPhone 16 or 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. +> Imagine - you just hit retry 5 times to get the Pod to pair and prime and then when it's time to insert the cannula, the Pod has disconnected because it was more than 3 minutes since the last message exchange. Then you have to keep hitting retry until the insertion process finally starts. With When Open, the Pod stays connected through the entire process of pairing, priming and inserting so long as the user does not manually lock the phone or move to another app. + +The user should choose with Silent Tune or Riley Link going forward if they want to have reliable communication between their iPhone 16/17e and an Atlas Pod. + +> If the Pod moves out of Bluetooth range, the Pod disconnects. With iPhone 16 or 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. +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 or 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 Pod moves out of Bluetooth range, the Pod disconnects. With iPhone 16 or 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. +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 or 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 or 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. + +- - - + + +- - - + +## Pod Diagnostics + +The row is typically used by developers. It opens a new screen with a variety of diagnostic options. These are listed in the table below. + +| Name | Purpose | +|:--|:--| +| Read Pod Status | | +| Play Test Beeps | | +| Read Pulse Log | | +| Read Pulse Log Plus | | +| Read Activation Time | | +| Read Triggered Alerts | | +| Pump Manager Details | | + +- - - + +## Omnipod 5 Support + +To use Omnipod 5 Pods you must have a certificate installed on your phone. + +* Once you have a certificate, the *Omnipod 5 Support* row will show a green check mark + +If you do not have a certificate, you can get one at any time using this row. Getting a certificate ahead of time is not required, but some people will feel more comfortable knowing the certificate is installed before they switch [Pod Types](#change-pod-types). -> If the pod moves out of Bluetooth range, the pod disconnects. With iPhone 16 or 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 your *Omnipod 5 Support* row shows a yellow warning badge, you can tap on it to request a certificate +* This one-time step requires internet access +* This certificate remains available for this app on this phone, even if you delete and reinstall the app -> 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 or 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. -- - - \ No newline at end of file diff --git a/docs/operation/features/notifications.md b/docs/operation/features/notifications.md index c6fde67c730..31ae9689887 100644 --- a/docs/operation/features/notifications.md +++ b/docs/operation/features/notifications.md @@ -63,7 +63,7 @@ Most pod beep alarms are disabled for a more discrete use of pods than is availa * Loop will update the actual delivery amounts based on pod reported information - Pod deactivation acknowledgment - Pod fault alarm (also called a screamer) when reaching the max life of the Pod: 80 hours (3 days + 8 hours), running out of insulin or a fault/occlusion happens - * Screamers are silenced using the [Replace Pod](../../loop-3/omnipod.md#replace-pod) row on the pod settings page + * Screamers are silenced using the [Deactivate Pod](../../loop-3/omnipod.md#deactivate-pod) row on the pod settings page * The one exception is if communications with the pod is lost and cannot be restored - in that case, you will be offered the chance to discard the pod from Loop but will still want to [Silence the Pod](../../faqs/omnipod-faqs.md#what-do-you-do-to-stop-a-screaming-pod) ## Notification settings for Loop diff --git a/docs/version/development.md b/docs/version/development.md index 6f1b6085db8..6477bc85cea 100644 --- a/docs/version/development.md +++ b/docs/version/development.md @@ -82,9 +82,9 @@ The table below lists active branches. |
branch | version # |
last updated | comments | |:--|:--|:--|:--| | main | 3.14.2 | 6 June 2026 | release | -| dev | 3.14.2 | 5 June 2026 | identical to main | -| `feat/all-managers`
- SHA `1b4718f` | 3.14.2 | 5 June 2026| This branch contains all the managers and is primarily for developers to use for testing
It also provides `DanaKit @ c544c42` support
**Please read** [Status for Dana Support](#status-for-dana-support)
**Please read** [Feature Branch: feat/all-managers](#feature-branch-featall-managers) | -| `next-dev` | 3.15.0 | subject to rapid change | [PR 454](https://github.com/LoopKit/LoopWorkspace/pull/454)
[zulipchat: Loop next-dev Status](https://loop.zulipchat.com/#narrow/channel/144182-development/topic/Loop.20next-dev.20Status/with/600761707) | +| dev | 3.14.3 | TBD June 2026 | add open beta support for Omnipod 5
Please read [Status for Open Beta for Omnipod 5](#status-for-open-beta-for-omnipod-5) | +| `feat/all-managers`
- SHA `1b4718f` | 3.14.3 | TBD June 2026| This branch contains all the managers and is primarily for developers to use for testing
It also provides `DanaKit @ c544c42` support
**Please read** [Status for Dana Support](#status-for-dana-support)
**Please read** [Feature Branch: feat/all-managers](#feature-branch-featall-managers) | +| `next-dev` | 3.15.0 | subject to rapid change | [PR 454](https://github.com/LoopKit/LoopWorkspace/pull/454)
Please read [Status for Open Beta for Omnipod 5](#status-for-open-beta-for-omnipod-5)
[zulipchat: Loop next-dev Status](https://loop.zulipchat.com/#narrow/channel/144182-development/topic/Loop.20next-dev.20Status/with/600761707) | ??? question "What is SHA? (Click to Open/Close)" SHA-1 means Secure Hash Algorithm 1. This is used to generate an alphanumeric code to identify which version of a repository is used. @@ -136,6 +136,12 @@ The version number in the feature branch will match either the `dev` branch vers - - - +### Status for Open Beta for Omnipod 5 + +Support for Omnipod 5 is available in development branches. Please report any issues you have in the zulipchat channel for either [Loop-dev status](https://loop.zulipchat.com/#narrow/channel/144182-development/topic/Loop-dev.20Status/with/600775735) or [Loop next-dev status](https://loop.zulipchat.com/#narrow/channel/144182-development/topic/Loop.20next-dev.20Status/with/604885611). + +You can also create an [Issue](https://github.com/loopandlearn/OmnipodKit/issues) at the OmnipodKit repository. Be sure to report your configuration, be descriptive in what you observed along with a timestamp when it happened and include a [Loop Report](../loop-3/settings.md#issue-report){: target="_blank" }. + ### Status for Pod Keep Alive Support For those using iPhone 16 or 17e with Atlas DASH Pods, the keep alive support is available in the released code, `main`, v3.14.0 or later.