Update/new ble protocol under test in next-dev branch (#1049)

* update development page with new Omnipod BLE protocol

* update next-dev version to 3.15.1

Author: marionbarker

docs/faqs/omnipod-faqs.md

@@ -67,19 +67,35 @@ You are not required to upload a Loop Report following each successful Pod chang
 
 ### What are the known issues?
 
+These are known issues for the `dev` branch of Loop.
+
+#### 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:
+
+* [No Pump Heartbeat](#no-pump-heartbeat) - the `next-dev` branch provides a heartbeat
+* [More frequent pod not connected messages](#more-frequent-pod-not-connected-messages) - limited testing, but this is no longer observed
+* [Will I still get 203 errors?](#will-i-still-get-203-errors) - we do not know but because the new method communicates much less frequently with Pods (DASH and Omnipod 5), it is possible this will reduce the frequency of 203 faults
+
 #### No Pump Heartbeat
 
 * The current implementation for Omnipod 5 requires you to [use a CGM with a heartbeat](#what-are-the-known-issues)
 * If you are using something like Nightscout as a CGM, your app goes to sleep and does not wake up if it is not in the foreground with the phone unlocked
 
+> see [Updates in `next-dev` branch only](#updates-in-next-dev-branch-only)
+
 #### More frequent pod not connected messages
 
 The private-beta testers noticed more frequent notifications that the pod is not connected. But the app continues to work. There are more periods when the spacing between automatic adjustments is 10 minutes instead of 5 minutes, but the majority of the time, every CGM reading triggers an automatic calculation.
 
+> see [Updates in `next-dev` branch only](#updates-in-next-dev-branch-only)
+
 ### Will I still get 203 errors?
 
 The increased frequency of faults noticed with DASH Atlas Pods has not been observed in the Ominpod 5 Pods tested to date.  Considering just the Pods that are not expired, there is a 3% failure rate with the failure being an occlusion (105) fault. There were testers in the private beta group using DASH instead of Omnipod 5. They had a 20% failure rate on a small sample of DASH Pods, all 203 faults near the 72 hours time frame.
 
+> see [Updates in `next-dev` branch only](#updates-in-next-dev-branch-only)
+
 ## Which Pods work with the *Loop* app?
 
 You can use Omnipod 5 (under test), DASH and Eros Pods with the *Loop* app.
@@ -125,13 +141,17 @@ To the best of our knowledge this is not something that we (as OS-AID developers
 
 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.
 
+> see [Updates in `next-dev` branch only](#updates-in-next-dev-branch-only)
+
 ### 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.
 
     **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.
 
+> Note that the BLE Management updates found in the `next-dev` branch, see [Updates in `next-dev` branch only](#updates-in-next-dev-branch-only), cannot fix the slow reconnection time for Atlas DASH Pods using iPhone 16 and 17e. The `next-dev` code still offers Pod Keep Alive, which works by always keeping the Pod connected via Bluetooth.
+
 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.**

docs/version/development.md

@@ -44,8 +44,8 @@ This section provides an overview of changes to `dev` compared to the current re
 
 The current version of `dev` is v3.14.3. The differences with respect to `main` are found in [PR 459](https://github.com/LoopKit/LoopWorkspace/pull/459).
 
-* Those who want to participate in the Open Beta for using Omnipod 5, should build the `dev` branch
-* Those who have been using feature branches for Medtrum or Eversense support can now build the released code
+* 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
 * Those on the Dana pump must keep building a feature branch, but the name of the branch changed
     * Dana users need to update the name of the branch they build to `feat/all-managers`
 
@@ -59,6 +59,7 @@ In addition to the main and dev branches, which are tightly controlled and only
 
 * The `update_dev_to_M.m.#` is where the next version of dev is tested before becoming part of `dev` and later being released as `main`
 * The branches starting with `feat/` have one or more special features, like support for new pumps, CGM or the new universal pump manager for all types of Omnipods
+* As mentioned earlier, there is also a `next-dev` branch for early adopters of what will eventually be Loop version 4, but is currently tagged as v3.15.
 
 The graphic below shows the `main` and `dev` branches along with some feature branches and an update branch. This is a snapshot in time and no longer reflects the current status. Always check [Table of Active Branches](#table-of-active-branches).
 
@@ -84,8 +85,9 @@ The table below lists active branches.
 |:--|:--|:--|:--|
 | main | 3.14.2 | 6 June 2026 | release |
 | dev | 3.14.3 | 2 July 2026 | adds support for Omnipod 5<br>Please read [Status for Open Beta for Omnipod 5](#status-for-open-beta-for-omnipod-5)<br>See [PR 459](https://github.com/LoopKit/LoopWorkspace/pull/459) |
-| `feat/all-managers`<br>- SHA `5a90eda` | 3.14.3 | 1 July 2026| This branch contains all the managers and is primarily for developers to use for testing<br>It also provides `DanaKit @ c544c42` support<br>**Please read** [Status for Dana Support](#status-for-dana-support)<br>**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)<br>Please read [Status for Open Beta for Omnipod 5](#status-for-open-beta-for-omnipod-5) <br>[zulipchat: Loop next-dev Status](https://loop.zulipchat.com/#narrow/channel/144182-development/topic/Loop.20next-dev.20Status/with/600761707) |
+| update_dev_to_3.14.4 | 3.14.4 | 20 July 2026 | work in progress for the next version<br>See [PR 469](https://github.com/LoopKit/LoopWorkspace/pull/469) |
+| `feat/all-managers`<br>- SHA `2f6b61e` | 3.14.4 | 20 July 2026| This branch contains all the managers and is primarily for developers to use for testing<br>It also provides `DanaKit @ c544c42` support<br>**Please read** [Status for Dana Support](#status-for-dana-support)<br>**Please read** [Feature Branch: feat/all-managers](#feature-branch-featall-managers) |
+| `next-dev` | 3.15.1 | subject to rapid change | [Status for `next-dev` Branch](#status-for-next-dev-branch)|
 
 ??? 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. 
@@ -137,13 +139,32 @@ The version number in the feature branch will match either the `dev` branch vers
 
 - - -
 
+### Status for `next-dev` Branch
+
+!!! important "For Expert Testers"
+    If you are willing to test using the `next-dev` branch of LoopWorkspace, this implementation provides a heartbeat from the Pod if the CGM does not have one.
+    
+    It also operates the BLE Pods (DASH and Omnipod 5) in disconnected mode instead of always connected as was done earlier.
+    
+    This new BLE management method needs people to test it and report if they find any issues.
+
+    * Please read this [post in zulipchat](https://loop.zulipchat.com/#narrow/channel/144182-development/topic/Loop.20next-dev/near/612491860)
+    * Follow along in that channel
+    * Be prepared to rebuild frequently
+
+This is the open PR for `next-dev`: [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) and [zulipchat: Loop next-dev Status](https://loop.zulipchat.com/#narrow/channel/144182-development/topic/Loop.20next-dev.20Status/with/600761707) 
+
 ### Status for Open Beta for Omnipod 5
 
 !!! warning "Use of Omnipod 5 Pods requires a CGM with a heartbeat"
-    * Omnipod 5 code is experimental and does not provide a heartbeat at this time
-    * This means you rely on your CGM to wake up the app when it is in the background or the phone is locked
-    * If your CGM does not supply a heartbeat, the app with stop automatically running when it is not open
-
+    * Omnipod 5 code is experimental
+        * The implementation found the the `dev` branch does not provide a heartbeat at this time
+            * This means you rely on your CGM to wake up the app when it is in the background or the phone is locked
+            * If your CGM does not supply a heartbeat, the app with stop automatically running when it is not open
+        * The implementation found in the `next-dev` branch does provide a heartbeat
+            * Read [Status for `next-dev` Branch](#status-for-next-dev-branch)
 
 Please read the open beta [Omnipod 5 FAQS](../faqs/omnipod-faqs.md#is-omnipod-5-available-for-open-beta-testing){: target="_blank" }.