diff --git a/docs/browser/automatic.md b/docs/browser/automatic.md index 2c3fa7a7c84..c2e998bdf87 100644 --- a/docs/browser/automatic.md +++ b/docs/browser/automatic.md @@ -2,16 +2,42 @@ The instructions provided for building with a browser include settings to automatically update and build for you. -## Manual Action for Automatic Build +## Automatic Build -!!! warning "Browser Build for *Loop* Disabled?" - We do not know why, but GitHub is disabling the Build Loop Action for LoopWorkspace even though the repository is not stale. +!!! tip "Automatic Build Returns for Loop v3.14.7 and newer" + With v3.14.7, a new file name is used for automatic building using the Browser Build method. + + * The new file: build_loop_auto.yml has the same content as the older build_loop.yml + * It appears that just giving it a new name was enough to prevent GitHub from disabling the build process + * Once you update to v3.14.7, your automatic building will be restored + * The old file: build_loop.yml is still in your LoopWorkspace folder for your convenience + * It no longer has the instructions to run automatically (that did not work anyway) + * If you had customization lines in build_loop.yml, they should still be there + * Simply copy those lines from build_loop.yml to build_loop_auto.yml to transfer the customization instructions to the file that actually runs to build Loop once a month + +The Actions shown for Loop were modified with the v3.14.7 release. The new build_loop_auto.yml file shows up as *Build Loop Auto* and actually runs every Sunday. The existing build_loop.yml shows up as *Build Loop Manual*. It can still be run manually, but it no longer is triggered automatically and continues to show as Disabled. + +![the new build loop auto is automatic](img/build-loop-auto.svg ){width="400"} +{align="center"} + +## Skipped Build - If this is happening to you, see [What Manual Action is Required?](#what-manual-action-is-required). +The automatic build process checks once a week for updates to the `main` branch. If there are no updates, it skips the build unless it is the second Sunday of the month. - * The automatic build actions should occur every Sunday - * The automatic build using the same code works for all OS-AID apps except for *Loop* - * See this [GitHub Discussion topic for details](https://github.com/orgs/community/discussions/181236) +* The skipped build used to show a green check mark which caused some confusion +* With v3.14.7, the indications were updated as shown in the graphic below + * top row: a scheduled build was successful (this one was the second Sunday of a month) + * middle row: the build was manually triggered and was successful + * bottom row: a schedule run of the build_loop_auto file, determined there was no reason to build, the icon shows the build was skipped + +![clear indication if build was skipped or successful](img/build-skip-or-success.svg ){width="300"} +{align="center"} + + +## Manual Action for Automatic Build + +!!! warning "Browser Build for *Loop* Disabled?" + GitHub disables the Build Loop Action for LoopWorkspace for v3.14.2 and older. Please update your fork to bring in the changes for v3.14.7 (or newer). See: [Automatic Build](#automatic-build) ??? tip "Stale Repositoriy Always Requires Manual Action (Click to Open Close)" *GitHub* automatically **disables actions** that run according to a schedule if the repository in question is **inactive**. diff --git a/docs/browser/img/build-loop-auto.svg b/docs/browser/img/build-loop-auto.svg new file mode 100644 index 00000000000..fdfcc213021 --- /dev/null +++ b/docs/browser/img/build-loop-auto.svg @@ -0,0 +1,72 @@ + + + + diff --git a/docs/browser/img/build-skip-or-success.svg b/docs/browser/img/build-skip-or-success.svg new file mode 100644 index 00000000000..43716908f1c --- /dev/null +++ b/docs/browser/img/build-skip-or-success.svg @@ -0,0 +1,75 @@ + + + + diff --git a/docs/faqs/cgm-faqs.md b/docs/faqs/cgm-faqs.md index ba9a2ca16f8..d6592fe53f9 100644 --- a/docs/faqs/cgm-faqs.md +++ b/docs/faqs/cgm-faqs.md @@ -139,7 +139,7 @@ If you prefer not to customize Loop, then you can configure [Nightscout](https:/ ## Can I use Eversense E3 or Eversense 365? -With `dev` branch, 3.14.2 and later, Eversense is included in the Loop build. +For Loop versions 3.14.2 and newer, Eversense is included. ## Can the *Loop* app read CGM data from Nightscout? diff --git a/docs/faqs/omnipod-faqs.md b/docs/faqs/omnipod-faqs.md index d25f9add812..b3586101c96 100644 --- a/docs/faqs/omnipod-faqs.md +++ b/docs/faqs/omnipod-faqs.md @@ -49,24 +49,28 @@ OmnipodKit replaces the need for OmniKit and OmniBLE submodules and provides sup ### Table of OmnipodKit Versions -For details about the different Bluetooth connection methods nicknamed *keep-connected*, *ble-heartbeat* and *eager-connect*, please read [OS-AID Omnipod History](#os-aid-omnipod-history). Some of the Loop versions listed below are works-in-progress suitable only for expert testers. +For details about the different Bluetooth connection methods nicknamed *keep-connected*, *ble-heartbeat* and *eager-connect*, please read [OS-AID Omnipod History](#os-aid-omnipod-history). -| Loop | Status |Pod Pump Manager | BLE Method | Supports | -|:--|:--|:--|:--|:--| -| before Loop 3.14.2 | released | OmniKit
OmniBLE | *keep-connected*| Classic, DASH | -| Loop 3.14.2 | released | OmnipodKit | *keep-connected* | Classic, DASH | -| Loop 3.14.7 | dev | OmnipodKit | *ble-heartbeat* | Classic, DASH, Omnipod 5 | -| Loop 3.15.2 | next-dev | OmnipodKit | *eager-connect* | Classic, DASH, Omnipod 5 | +The table below references which *Loop* version is associated with which Bluetooth connection method in OmnpodKit. The released *Loop* version, 3.14.7, is recommended for the general user. Please update as soon as possible if your version is 3.14.2 or older. The development branches are suitable only for expert testers. + +| Loop Version | Branch | OmnipodKit BLE Method
- known issues | Supports | +|:--|:--|:--|:--| +| Loop 3.14.7 | `main`
- current release | *ble-heartbeat*
- iPhone 16/17e + Atlas DASH needs Pod Keep Alive | Classic, DASH, Omnipod 5 | +| Loop 3.14.7 | `dev` | same as `main` but subject to change
- will use for *eager-connect* testing soon | Classic, DASH, Omnipod 5 | +| Loop 3.15.2 | `next-dev` | *eager-connect*
- iPhone 16/17e connect delay improved | Classic, DASH, Omnipod 5 | +| Loop 3.14.2 | - previous release | *keep-connected*
- increased 203 faults with Atlas DASH
- iPhone 16/17e + Atlas DASH needs Pod Keep Alive | Classic, DASH | + +Versions before Loop 3.14.2 used the older repositories of OmniKit or OmniBLE, which are no longer included in the *Loop* app. The Bluetooth communications used the *keep-connected* method and was subject to increased 203 faults with Atlas DASH for all phone models. The combination of iPhone 16/17e with Atlas DASH required use of [Pod Keep Alive](../loop-3/omnipod.md#pod-keep-alive-feature){: target="_blank" }. #### Map of OmnipodKit SHA Users do not need this but developers may find this helpful in selecting which version of OmnipodKit to use for their release and development branches. -**OmnipodKit Branches / SHA as of 2026-09-12** +**OmnipodKit Branches / SHA as of 2026-09-14** * subject to modification - be sure to check [GitHub](https://github.com/loopandlearn/OmnipodKit/branches) * all these branch support Classic, DASH, and Omnipod 5 Pods -* all these branches support a connect on demand Bluetooth method +* all these branches support a connect-on-demand Bluetooth method **At this snapshot in time**, the OmnipodKit `main` and `dev` branches have the same code with two different SHA. There are open PR to modify `dev` so that additional *eager-connect* testing can start. The `next-dev` branch is where most of the early testing happens. Both the `dev` and `next-dev` branches are subject to rapid change. @@ -80,9 +84,11 @@ Users do not need this but developers may find this helpful in selecting which v ## Is Omnipod 5 available for open-beta testing? -Yes it is. +Yes it is, however, the open-beta was successful and is complete. -* We encourage anyone interested in participating in the Omnipod 5 Open Beta to read [these FAQs](https://nightscout.github.io/omnipod-five/open-beta.html) +Support is found in the released version of the *Loop* app. Please switch your build to the Loop `main` branch. There is no need for a development branch to get Omnipod 5 support. (If you are a Trio user, then check [TrioDocs](https://triodocs.org) for branch information.) + +* For historical purposes, this link has information about the [Omnipod 5 Open Beta FAQs](https://nightscout.github.io/omnipod-five/open-beta.html) Specific information about using Omnipod 5 Pods with Loop is found in LoopDocs. @@ -96,24 +102,19 @@ This is all handled for you automatically. You simply need to ensure you have in ### Should I switch to Omnipod 5 now? -Don't be in a rush, the open beta testing is almost completed and Omnipod 5 will be in released code soon - -### How can I switch to Omnipod 5? +That's a personal decision and may be affected by your ability to change prescriptions and get insurance coverage. With the new connect-on-demand method for Omnipod Bluetooth communications, the pressure from the increased frequency of 203 faults has been removed. -!!! important "You need to be comfortable building a development branch, updating frequently, and reporting problems." +There is still an issue, in the released code, for iPhone 16/17e users with Atlas DASH pods, but work is on-going to improve that situation as well. (A new connection method, nicknamed *eager-connect* is under test.) -If you decide to test: help us by [reporting any problems](#how-do-i-report-problems). +### How can I switch to Omnipod 5? #### Build the correct version of code -To get access to Omnipod 5, build the `dev` branch for Loop. - -* Please read: [Updates in dev](../version/development.md#updates-in-dev) -* Please follow along in zulipchat at [Loop-dev status](https://loop.zulipchat.com/#narrow/channel/144182-development/topic/Loop-dev.20Status/with/606368226) +To get access to Omnipod 5, build the released code, from the `main` branch, and ensure your new code indicates version 3.14.7 (or newer). #### Perform a one-time step to support Omnipod 5 -There is a one-time step to get a certificate needed for you to use an Omnipod 5 Pod. This is pretty automatic, but this is new code so be prepared to handle issues if they happen. +There is a one-time step to get a certificate needed for you to use an Omnipod 5 Pod. This step requires you to have **internet access**. After this step is done, you can pair an Omnipod 5 Pod with this phone and this app with no need for internet access. @@ -131,46 +132,9 @@ At this point, you can tap Continue and will be taken to the Pair Pod screen. It Because of the extra exchanges required to handle the security added to Omnipod 5 Pods, the pairing and some of the insulin dosing commands may seem slow compared to a DASH Pod. This is normal. -### How do I report problems? - -* You can report problems (and compliments) in the [Loop Open Beta for Omnipod 5](https://loop.zulipchat.com/#narrow/channel/144182-development/topic/Loop.20Open.20Beta.20for.20Omnipod.205/with/607418710) topic in zulipchat. - -Please report any Fault you experience and upload your [Loop Report](../loop-3/settings.md#issue-report){: target="_blank" } that contains the Fault using the [OmnipodKit Testing Log form](https://docs.google.com/forms/d/e/1FAIpQLSeuclLr4jU-5Vr5oF1vYgmUv_FoN12nxXR0-Bzu_JW1J3bn5w/formResponse). - -You are not required to upload a Loop Report following each successful Pod change, although if you do - that successful report will be processed and added to our statistics. - - -### What are the known issues? - -These are known issues for the `dev` branch of Loop. - -* The `dev` branch uses a connect-on-demand method for connecting to both DASH and Omnipod 5 Pods so you may notice a slight delay in connecting, getting status and then responding to a command from Loop - * This is normal, be patient -* [Will I still get 203 errors?](#will-i-still-get-203-errors) - there have always been some reports of 203 faults with DASH that ramped up significantly with the Atlas version of DASH. Early testing indicates reduced frequency of 203 faults for Atlas DASH Pods with the newer Bluetooth protocols. -* If you are using an iPhone 16/17e, the connection delay is variable and can be quite severe (up to minutes to connect) - * Use the [Pod Keep Alive Feature](../loop-3/omnipod.md#pod-keep-alive-feature){: target="_blank" } - unless you have a RileyLink device, select the Silent Tune option for Atlas DASH pods with an iPhone 16/17e - -#### Updates in `next-dev` branch only - -A new BLE management protocol is under test in the `next-dev` branch. This branch fixes the following issues: - -* [Will I still get 203 errors?](#will-i-still-get-203-errors) - there have always been some reports of 203 faults with DASH that ramped up significantly with the Atlas version of DASH. Early testing indicates reduced frequency of 203 faults for Atlas DASH Pods with the newer Bluetooth protocols. -* If you are using an iPhone 16/17e, the connection delay has been dramatically redused using the new *eager-connect* connect-on-demand method - * Early testing indicates the Pod Keep Alive option might not be needed, but it is available if you have difficulty with the iPhone 16/17e plus Atlas DASH combination - -#### No Pump Heartbeat - -* An early implementation (dev v3.14.3) did not provide an Omnipod 5 heartbeat; please rebuild if your CGM does not provide a hearbeat - -### Will I still get 203 errors? - -Both the `dev` and `next-dev` branches use a new connect-on-demand method that appears to reduce the frequency of 203 faults for Atlas DASH pod. In addition, no 203 faults have been observed to date by any of the Omnipod 5 testers. - ## Which Pods work with the *Loop* app? -You can use Omnipod 5 (under test), DASH and Eros Pods with the *Loop* app. - -* The Omnipod 5 is only available in the development branches while in open beta testing +You can use Omnipod 5, 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 PDM may be needed in some countries to get replacements for failed Pods. @@ -178,33 +142,50 @@ You do not need the Omnipod Personal Diabetes Manager (PDM), just the pod suppli 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** - * The Reference number on the boxes should be similar to POD-ZXP425 + * **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 - * 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 * 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-OMNI-I1-6720 + * **Eros** Pods are also known as **Classic** or **UST400** or **Gen 3** + * The Reference number on the boxes should be similar to POD-ZXP425 * They have a clear needle cap + * You must have a RileyLink device to use Eros Pods 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 when pairing than the DASH because of the extra layer of security added to these Pods. **To date, no iPhone model specific issues have been found with Omnipod 5 Pods variants tested.** -### Increase in DASH Faults +- - - + +## Is connect-on-demand for Omnipod slower to respond? + +With the new connect-on-demand code, *ble-heartbeat*, you may see delays for the app to connect to the pod when you unlock the phone for a manual action. This should take less than 5 sec to resolve and is normal. Do not report this as an issue. The *eager-connect* method, still under still, will shorten this delay. -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). +* connect-on-demand means the Pod wakes up at 5 minute intervals for automatic control or when you open the app for manual control +* the *ble-heartbeat* version does not improve connection time for iPhone 16/17e so you will still need to use [Pod Keep Alive](../loop-3/omnipod.md#pod-keep-alive-feature){: target="_blank" } for those phones -It took a while, but we are testing (in `dev` and `next-dev` branches) a different method of connecting to Pods that appears to reduce the frequency of 203 Faults. There are faults that can happen with any pods, including 203, but the Atlas DASH pods exhibited almost 20 times the rate of 203 faults as earlier pods and that particular problem is improved. +- - - + +## Increase in DASH Faults + +There are 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) using the older *keep-connected* method for Bluetooth communication. 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). + +It took a while, but we modified the method of connecting to Pods with release v3.14.7 and this appears to reduce the frequency of 203 Faults. There are faults that can happen with any pods, including 203, but the Atlas DASH pods exhibited almost 20 times the rate of 203 faults as earlier pods when we used the keep-connected method for Bluetooth communcation and that particular problem is improved using connect-on-demand. + +### Status for released code + +If you experience increased 203 faults with Atlas DASH pods, please rebuild to the released code, v3.14.7 or newer. -#### Status for released code +This is found in the `main` branch and provides a connect-on-demand Bluetooth method to resolve this issue. Plus there are other [updates to the *Loop* app with this release](../version/releases.md#loop-v3146){: target="_blank" }. -This section remains valid for folks using released code, v3.14.2 or earlier, which used the *keep-connected* method for Bluetooth between the phone and pod. The new methods under test, which connect on demand, provide reduced frequency for 203 faults. +### Status for older code + +This section remains valid for folks using older code, v3.14.2 or earlier, which used the *keep-connected* method for Bluetooth between the phone and pod. Please rebuild at your earliest convenience People who have boxes that fail early find most Pods in that box fail early. @@ -221,10 +202,12 @@ We have looked at the analytics reported from Loop users who [share their data]( **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) when using the *keep-connected* Bluetooth method which affects all phone models and seems to be box specific. -> * Note that the BLE Management modifications found in the `dev` branch, known as *ble-heartbeat*. cannot fix the slow reconnection time for Atlas DASH Pods using iPhone 16 and 17e. +> * Note that the BLE Management modifications, known as *ble-heartbeat*, found in released code v3.14.7 or newer cannot fix the slow reconnection time for Atlas DASH Pods using iPhone 16 and 17e. > * The `next-dev` code offers yet another version of connect on demand, nicknamed *eager-connect*. It senses if the connection is taking too long, quits the attempt and retries until the connection goes through. For iPhone 16/17e, this can still be a few seconds, but much faster than before. +#### Historical Information about 203 Fault increase with Atlas DASH pods + Beginning in 2025, DASH Pods began using the 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. These `Atlas` Pods, which report electronically as `InPlay BLE`, are the new version. **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.** @@ -249,7 +232,7 @@ Beginning in 2025, DASH Pods began using the newer version of chips and firmware * 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. * 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. > 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. @@ -339,9 +322,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). +This section used to be accurate. But there was an issue with some Atlas DASH pods. The statistics indicated a big increase in frequency of faults (Pods starting to scream). This has been resolved with the latest release, so update to v3.14.7 as soon as possible. + +See [Increase in DASH Faults](#increase-in-dash-faults). + +### Bluetooth Communication with v3.14.2 or older code + +This section is only true for v3.14.2 or older code. With v3.14.3 and newer versions, a connect-on-demand method is used instead of keep-connected for Bluetooth communication. -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. +With v3.14.2 or older code, 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 diff --git a/docs/version/development.md b/docs/version/development.md index 43d3bcad649..5e63e06a9f6 100644 --- a/docs/version/development.md +++ b/docs/version/development.md @@ -40,13 +40,10 @@ Please read this entire page before using any version of *Loop* other than the r ## Updates in `dev` -This section provides an overview of changes to `dev` compared to the current release: [`Loop v3.14.2`](releases.md#v3142-highlights){: target="_blank" }. +This section provides an overview of changes to `dev` compared to the current release: [`Loop v3.14.7`](releases.md#v3147-highlights){: target="_blank" }. -The current version of `dev` is v3.14.7. The differences with respect to `main` are found in [PR 459](https://github.com/LoopKit/LoopWorkspace/pull/459), [PR 469](https://github.com/LoopKit/LoopWorkspace/pull/469), [PR 488](https://github.com/LoopKit/LoopWorkspace/pull/488), [PR 493](https://github.com/LoopKit/LoopWorkspace/pull/493) and [PR 496](https://github.com/LoopKit/LoopWorkspace/pull/496). +At this time, there are no changes between the released version and the `dev` branch, but expect that to change soon. -* Those who want to participate in the Open Beta for using Omnipod 5, should build the `dev` branch; it is also supported in the `next-dev` branch -* Those who have been using feature branches for Medtrum or Eversense support can build the released code, which has support for both Medtrum Pumps and Eversense CGM - * There are updates to both Medtrum and Eversense in the `dev` branch (v3.14.6 or later); the `dev` branch should be released to `main` very soon * Those on the Dana pump must keep building the feature branch, `feat/all-managers` Please check the [development channel in zulipchat](https://loop.zulipchat.com/#narrow/channel/144182-development) for notifications when an update to the `dev` branch is expected so you will be prepared. Do this **before** you install a `dev` build from TestFlight. @@ -79,7 +76,7 @@ The table below lists active branches. |
branch | version # |
last updated | comments | |:--|:--|:--|:--| -| main | 3.14.2 | 6 June 2026 | release | +| main | 3.14.7 | 14 Sep 2026 | release | | dev | 3.14.7 | 14 Sep 2026 | uses the *ble-heartbeat* method for OmnipodKit plus improves G7 Sensor drop-outs
adds support for Omnipod 5
Please read [Status for Open Beta for Omnipod 5](#status-for-open-beta-for-omnipod-5)
See [PR 459](https://github.com/LoopKit/LoopWorkspace/pull/459)
See [PR 469](https://github.com/LoopKit/LoopWorkspace/pull/469)
See [PR 488](https://github.com/LoopKit/LoopWorkspace/pull/488)
See [PR 493](https://github.com/LoopKit/LoopWorkspace/pull/493)
See [PR 496](https://github.com/LoopKit/LoopWorkspace/pull/496) | | `feat/all-managers`
- SHA `27195b0` | 3.14.7 | 14 Sep 2026| This branch contains all the managers and is primarily for developers to use for testing
It also provides `DanaKit @ 7f4f3e4f` 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.2 | subject to rapid change | [Status for `next-dev` Branch](#status-for-next-dev-branch)| @@ -168,14 +165,11 @@ The next-dev branch will eventually be released as *Loop* version 4. The preset ### Status for Open Beta for Omnipod 5 -!!! warning "Use of Omnipod 5 Pods requires a CGM with a heartbeat" - * Omnipod 5 code is experimental - * The current versions of `dev` and `next-dev` both provide a heartbeat for Omnipod 5 - * The `dev` branch uses the *ble-heartbeat* Bluetooth connection method - * The `next-dev` branch uses the *eager-connect* Bluetooth connection method - * See [Table of OmnipodKit Versions](../faqs/omnipod-faqs.md#table-of-omnipodkit-versions){: target="_blank"} for more information about Bluetooth connection methods - * The initial implementation for Omnipod 5 Pods from an older `dev` build, v3.14.3, did not provide a heartbeat for Omnipod 5 Pods - * If you are running this older version and your CGM does not supply a heartbeat, the app will stop running when it is not open; please rebuild +The Open-Beta is completed for Omnipod 5. Support is found in the released version of the *Loop* app. Please switch your build to the Loop `main` branch. There is no need for a development branch to get Omnipod 5 support. + +!!! warning "Earlier development code required a CGM with a heartbeat" + * The initial implementation for Omnipod 5 Pods in an older development branch (v3.14.3), did not provide a heartbeat for Omnipod 5 Pods + * If you are running this older version and your CGM does not supply a heartbeat, the app will stop running when it is not open; please rebuild to the released code Please read the open beta [Omnipod 5 FAQS](../faqs/omnipod-faqs.md#is-omnipod-5-available-for-open-beta-testing){: target="_blank" }. @@ -201,7 +195,7 @@ You can also create an [Issue](https://github.com/loopandlearn/OmnipodKit/issues 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. -The Pod Keep Alive code was completely revamped and cleaned up with v3.14.6 or later. See [OmnipodKit Information](#omnipodkit-information) for more details. Be sure to check your selection after a rebuild because it is not carried over from the older versions. +The Pod Keep Alive code was completely revamped and cleaned up with v3.14.7 or later. See [OmnipodKit Information](#omnipodkit-information) for more details. Be sure to check your selection after a rebuild because it is not carried over from the older versions. For experts, the new Bluetooth connection method, nicknamed *eager-connect*, is currently available for use with the `next-dev` branch, with interim version number 3.15.2 or higher. This needs testing by individuals who use an iPhone 16 or 17e with Atlas DASH pods. @@ -299,14 +293,15 @@ If you previously used a feature branch for Medtrum or Eversense support, you ca When you build the `main` or `dev` (v3.14.2 or newer) branch or `next-dev` (v3.15.0 or newer) branch over an older build, your Pod is automatically transitioned to use a new Pump Manager: OmnipodKit. You will notice the user interface is a little different from the older managers (OmniKit and OmniBLE). -The OmnipodKit pump manager comes with improved user interface and user experience for Omnipod Classic (Eros) and DASH pods including - * Some layout adjustments * Some new labels * Some reworked sub-menus with added information or features +* Omnipod 5 Support added to Classic and DASH support + * Released version v3.14.7 or newer + * Starting with development versions v3.14.3 -!!! warning "Pod Keep Alive v3.14.6 or later" - The Pod Keep Alive feature was rewritten with v3.14.5 but a bug was introduced which was fixed in v3.14.6. If you have the interim v3.14.5, please rebuild to v3.14.6 or later as soon as possible. +!!! warning "Pod Keep Alive v3.14.7 or later" + The Pod Keep Alive feature was rewritten with v3.14.5 but a bug was introduced which was fixed in v3.14.7. If you have the interim v3.14.5, please rebuild to v3.14.7 or later as soon as possible. * Old Pod Keep Alive (PKA) settings are not transferred and must be reselected * The RileyLink connections will be shown in the pump (Omnipod DASH) view under the Pod Keep Alive button when the RileyLink option is selected diff --git a/docs/version/releases.md b/docs/version/releases.md index c6e8d1f0f84..10288834bc4 100644 --- a/docs/version/releases.md +++ b/docs/version/releases.md @@ -8,7 +8,7 @@ For information about version 2 releases and compatibility between version 2 and ## Current Release -The current released version for the *Loop* app is v3.14.2 and is built from the `main` branch of LoopWorkspace. The dates and contents for releases are summarized below in reverse chronological order (so newest release information comes first). +The current released version for the *Loop* app is v3.14.7 and is built from the `main` branch of LoopWorkspace. The dates and contents for releases are summarized below in reverse chronological order (so newest release information comes first). ### What Version Do I Have? @@ -29,6 +29,52 @@ Release information is found on the [*GitHub* _LoopKit - - - +## Loop v3.14.7 + +[*Loop* v3.14.7](https://github.com/LoopKit/LoopWorkspace/releases/tag/v3.14.7) was released on 15 September 2026. + +#### v3.14.7 Highlights + +**Loop Features** + +* Provide support for Omnipod 5 Pods +* Bring in the first connect-on-demand Omnipod Bluetooth modification + * This version reduces the frequency of the 203 faults observed with Atlas DASH pods + * Warning, the [Pod Keep Alive](../loop-3/omnipod.md#pod-keep-alive-feature){: target="_blank" } feature was modified, read the updated documentaion at that link if you use an iPhone 16 (all models) or iPhone 17e +* Dexcom G7 + * Trade off reduced drop-outs of G7 data for a 15-minute delay in picking up new sensor + * User can initiate a scan manually to avoid the 15 minute delay +* Dexcom G6 + * Add support for Anubis Transmitters +* Various fixes and additional support features for EversenseKit and MedtrumKit + * Medtrum now supports Manual Temp Basal and logging is found in the standard Loop Report +* Various fixes to prevent crashes for Loop and for RileyLink users + + +**Support** + +* Modify the Browser Build method to restore [Automatic Build](../browser/automatic.md#automatic-build){: target="_blank" } +* Modify the Browser Build method to differentiate between a skipped build and a successful build + * Only the successful build shows the green check mark [Skipped Build](../browser/automatic.md#skipped-build){: target="_blank" } +* Update fastlane to 2.237.0 +* Update the code to be compatible with Xcode 27 + * Minimum deployment target is now iOS 17.6 + * Users are encouraged to update to the latest iOS 26 version before iOS 27 is released + +#### Details from v3.14.2 to v3.14.7 + +The detailed list of updates from v3.14.2 to v3.14.7 are found in the table of PRs below. Most users do not need this level of detail. + +| Interim Version | PR | +|:--|:--| +| dev 3.14.3 | [PR 459](https://github.com/LoopKit/LoopWorkspace/pull/459)| +| dev 3.14.4 | [PR 469](https://github.com/LoopKit/LoopWorkspace/pull/469)| +| dev 3.14.5 | [PR 488](https://github.com/LoopKit/LoopWorkspace/pull/488)| +| dev 3.14.6 | [PR 493](https://github.com/LoopKit/LoopWorkspace/pull/493)| +| dev 3.14.7 | [PR 496](https://github.com/LoopKit/LoopWorkspace/pull/496)| + +- - - + ## Loop v3.14.2 [*Loop* v3.14.2](https://github.com/LoopKit/LoopWorkspace/releases/tag/v3.14.2) was released on 6 June 2026.