Misc updates (#1050)

* Add more information about next-dev

* Incorporate changes from pr 1046

* incorporate changes from pr 1047

* be consistent with Libre names

Author: marionbarker

docs/faqs/cgm-faqs.md

@@ -4,8 +4,7 @@ The following CGM are supported by some or all versions of Loop:
 
 * 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
+* *EU Libre 2/2+* CGM (Loop 3.4 and later), *Libre 3/3+* CGM (via an experimental testing branch, [next-dev branch](../version/development.md#updates-in-dev))
 * 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)
@@ -108,23 +107,25 @@ sequenceDiagram
 
 ### Troubleshoot Connections
 
-The "normal" *Libre* 2 sensors have a firmware configuration that makes them slow to reconnect when they lose the connection to iOS (both iOS and the sensors are to blame for this). What usually helps is to make sure your app is open and in the foreground and that your phone is unlocked. iOS seems to be better at reconnecting Bluetooth devices under such conditions (i.e. it gives more Bluetooth priority to the foreground app). If you need to modify how quickly your phone locks, this is found under iOS settings, Display & Brightness, Auto-Lock.
+*EU Libre* 2 sensors have a firmware configuration that makes them slow to reconnect when they lose the connection to iOS (both iOS and the sensors are to blame for this). What usually helps is to make sure your app is open and in the foreground and that your phone is unlocked. iOS seems to be better at reconnecting Bluetooth devices under such conditions (i.e. it gives more Bluetooth priority to the foreground app). If you need to modify how quickly your phone locks, this is found under iOS settings, Display & Brightness, Auto-Lock.
 
 If you try to pair a sensor in the app multiple times in a short period (let's say within a couple of minutes), you may need to just stop and wait.
 
 * A "pairing" sends a lot more (16 times the normal amount) of data between the app and sensor than a normal NFC scan to retrieve glucose data
 * Multiple pairing attempts may make the sensor temporarily unable to function
 * If this matches your use case, shut off your phone and let it stay shut down for up to five minutes
 
-Optionally: you can use miaomiao or bubble third-party transmitters attached on top of your normal *Libre* 2 sensors. Although the setup is a bit more bulky, it works and does not have connection problems. LibreTransmitter supports bubble and miaomiao on top of *Libre* 1 sensors, but it also works with *Libre* 2 sensors.
+Optionally: you can use miaomiao or bubble third-party transmitters attached on top of your normal *EU Libre* 2/2+ sensors. Although the setup is a bit more bulky, it works and does not have connection problems. LibreTransmitter supports bubble and miaomiao on top of *Libre* 1 sensors, but it also works with *Libre* 2 sensors.
 
 ### Can I use *Libre* sensors with a reader like Miao Miao?
 
-Loop 3.4.x and later enables the use of those *Libre* sensors supported by [LibreTransmitter](https://github.com/LoopKit/LibreTransmitter#libretransmitter-for-loop){: target="_blank" }.
+Loop 3.4.x and later enables the use of *Libre* sensors supported by [LibreTransmitter](https://github.com/LoopKit/LibreTransmitter#libretransmitter-for-loop){: target="_blank" }.
 
 ### 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
+*Libre 3/3+* is currently available for testing in a special branch, next-dev; it is not yet part of the released version of Loop.
+
+* See [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.
 

docs/loop-3/add-cgm.md

@@ -137,23 +137,19 @@ It is suggested that you enable [Remote Upload from Loop](#remote-upload-from-lo
 
 ### Libre
 
-The Libre plugin for Loop, [LibreTransmitter](https://github.com/LoopKit/LibreTransmitter/), connects directly via Near Field Communication (NFC) during pairing (for some sensors) and via Bluetooth (direct to sensor or direct to a transmitter attached to the sensor) for regular readings. No other app is needed.
-
 * 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
+* European Libre 2/2+ can be used directly or via transmitter
 * American Libre 2 is not supported
-* Libre 3 is not supported in the released code
+* Libre 3/3+ is not supported by the released version of *Loop*, but is being tested in a special branch (next-dev)
 
 > 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.
 
-There are solutions for some Libre 3 but they cannot reside on an iPhone. The Android solution can be uploaded to Nightscout, with Loop using Nightscout as a Remote CGM; but this requires internet access to continue closed-loop performance.
-
 Part of the problem with Libre sensors is that there are differences in region, type and "security generations" which makes it hard to account for all variants. For example, the Libre 2 US has a different "security generation" than European Libre 2 sensors (different encryption in the data transmitted over Bluetooth).
 
-Libre 3 sensors have started appearing as well, but are unsupported. Other Libre sensors that are unsupported: Libre Pro, Libre H, and Libre Sense Glucose Sport Biosensors.
+Libre sensors that are unsupported: Libre Pro, Libre H, and Libre Sense Glucose Sport Biosensors.
 
 ### Eversense E3/365
 
@@ -253,9 +249,6 @@ In addition to the risks of missing data, if the internet is not reliable, you m
     There are third-party apps that bring some models of Libre data to your Loop phone. Customization instructions are provided at the `Loop and Learn` website: [New CGM and Pump](https://www.loopandlearn.org/custom-code-add-cgm-pump/) that explain how to modify Loop to add a CGM or Pump that is not part of the released `Loop` code.
 
     It is suggested that you use Open Loop during warmup until the new sensor begins to provide reasonable data. This is especially important with European Libre 2 using a direct Bluetooth connection.
-    
-    The xDrip4iOS app (which can also be found in the app store under the name Shuggah) may have a problem during the warmup of a new sensor (European Libre 2 using a direct Bluetooth connection). There were two instances of crazy high values being reported and picked up by Loop 3. One Shuggah user and one xDrip4iOS user who connected via Nightscout as a CGM with Loop 3 had a serious overdose of insulin because of bad readings with a new sensor. The developers of xDrip4iOS fixed their application - so make sure you have the latest version. Those developers have no control over what is provided by Shuggah.
-
 
 ![Nightscout Remote CGM acknowledgement screen](img/nightscout-cgm-acknowledge.svg){width="350"}
 {align="center"}

docs/version/development.md

@@ -141,6 +141,12 @@ The version number in the feature branch will match either the `dev` branch vers
 
 ### Status for `next-dev` Branch
 
+The document linked below provides an overview of updates brought from Tidepool *Loop* to "DIY *Loop*", as found in next-dev.
+
+* [*Loop* DIY: What's new](https://github.com/LoopKit/LoopWorkspace/blob/next-dev/docs/loop-diy-whats-new.md)
+
+The document linked above does not include more recent updates which you find discussed in zulipchat and highlighted below. But the document does provides a solid basis for understanding the new features.
+
 !!! 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.
 
@@ -156,6 +162,17 @@ This is the open PR for `next-dev`: [PR 454](https://github.com/LoopKit/LoopWork
 
 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) 
 
+#### Preset Behavior in *Loop* 4
+
+The next-dev branch will eventually be released as *Loop* version 4. The preset (override) behavior is quite different than in *Loop* versions 2 and 3.
+
+!!! tip "Preset Behavior is Different"
+    The preset (override) behavior of the released version of *Loop* remembers the insulin needs factor at the time a dose is delivered throughout the duration of insulin activity.
+
+    The new code no longer does that. As soon as the preset is cancelled, the ISF and CR return to their scheduled values. The old, often repeated, do not use extreme overrides because they mess up predictions, is no longer true.  You may need to adjust your preset values when you switch to the next-dev branch.
+
+    In particular - tricks like changing the insulin needs factor of a currently running override, no longer work and should be forgotten.
+
 ### Status for Open Beta for Omnipod 5
 
 !!! warning "Use of Omnipod 5 Pods requires a CGM with a heartbeat"