Merge pull request #24 from loopandlearn/release_4.6

Update LoopFollow Docs for LoopFollow Release 4.6

Author: marionbarker

docs/faqs/lf-faqs.md

@@ -6,4 +6,5 @@
 
 -->
 
-Pro Tip:  If you are experiencing audible and visible glucose alerts every single minute, disable Persistent Notifications. Go to LoopFollow, Settings, General Settings to see the screen in the graphic below.
+Pro Tip:  If you are experiencing audible and visible glucose alerts every single minute, disable the *LoopFollow*, Settings, General Settings, Persistent Notifications slider. This is completely different from the persistent notifications that you might want enabled to see the APNS messages returned from real-time responses to remote command.
+

docs/remote/img/lf-loop-remote-apns-real-time.png

@@ -1,16 +1,17 @@
 ## Remote Control of the *Loop* App
 
-This option is available for remote control of a *Loop* phone using *LoopFollow* 3.2 and newer.
+This option is available for remote control of a *Loop* phone using *LoopFollow* 4.6 and newer. The real-time notifications require *Loop* v3.11.1 and newer.
 
-* *Loop* Remote Control
+* *Loop* Remote Control with Real-Time Notifications
     * Remote control with *LoopFollow* includes adding remote carbs, enacting remote bolus, and starting and canceling Overrides
-    * Available with all versions of *Loop* 3
-    * Requires *LoopFollow* 3.2 or newer
+    * The *LoopFollow* phone sends directly through APNS to the *Loop* phone
+    * The *Loop* phone, if it gets the APNS message, returns an APNS response with success or error message for carb or bolus commands
+    * The override commands do not get an APNS message returned
 
 
 ### Quick Access
 
-The bullets below take you to the indicated topics. The configuration step is listed first but only needs to be done once, so is located at the end of this page:
+The bullets below take you to the indicated topics.
 
 * [Configure *LoopFollow* for Remote Control](#configure-loopfollow-for-remote-control)
 * [Use *LoopFollow* *Loop* Remote Control](#use-loopfollow-loop-remote-control)
@@ -38,11 +39,25 @@ Once the *LoopFollow* phone is [configured](#configure-loopfollow-for-remote-con
         * discarded, ignored by *Apple* or the phone
         * significantly slowed down due to network connectivity
     1. The *Loop* app processes the remote command and either **enacts** it or **rejects** it
+    1. For *Loop* v3.11.1 or newer, an APNS message is returned to the originating *LoopFollow* phone where it is presented as a real-time notification
     1. The *Loop* app uploads to *Nightscout* with result shown on *LoopFollow* main screen in a few minutes
         * If the remote request was **enacted**, the result is visible on the *LoopFollow* main plot
         * If the remote request was **rejected**, a gray dot is visible on the *LoopFollow* main plot - touch it to see the reason why the request was rejected
 
-    > If no result shows up at *LoopFollow* (no gray dot, no response to remote request), then it is most likely step 2 that failed. We have limited control over that.
+    > If no result shows up at *LoopFollow* (no APNS message, no gray dot, no response to remote request), then it is most likely step 2 that failed. We have limited control over that.
+
+### Real-Time Notifications
+
+To improve your ability to see the APNS real-time notifications returned by *Loop* v3.11.1 or newer, be sure to enable persistent notifications.
+
+* iPhone Settings, Apps, *LoopFollow*
+* Notifications, make sure Banner Style is Persistent
+
+Example messages are highlighted by red rectangles in the composite below for remote carb and remote bolus. The example on the right is an example error message that was returned.
+
+![remote real-time-notifications ](img/lf-loop-remote-apns-real-time.png){width="650"}
+{align="center"}
+
 
 ### Remote Meal
 

docs/remote/remote-control-loop.md

@@ -2,7 +2,14 @@
 
 *LoopFollow* remote commands are sent directly using the [Apple Push Notification System (APNS)](#apple-push-notifications-system-apns) for all Open-Source Automated Insulin Delivery systems that support this feature.
 
-The *Loop* app and the open beta version of the *Trio* app (0.5.x or newer) support direct APNS from *LoopFollow*.
+* *Trio* and *Loop* accept a direct APNS message sent from *LoopFollow*
+    * minimum versions: *Trio* 0.6.x; all versions of *Loop*
+* *Trio* and *Loop* send a direct APNS message back to the originating *LoopFollow* phone with a success or error message
+    * minimum versions: *Trio* 0.6.x; *Loop* 3.11.1
+* This is subject to the *Apple* APNS servers but tends to be faster and more reliable than going through the Nightscout careportal
+
+> The return APNS message is only available for a meal or bolus entry.
+
 
 !!! warning "Browser Build Update"
     If you use Browser Build and your current build is older than v4.0.0, follow the one-time updates needed to transition from *LoopFollow* v3.x:
@@ -21,12 +28,14 @@ The *Loop* app and the open beta version of the *Trio* app (0.5.x or newer) supp
 
 ## *LoopFollow* Remote Options
 
-> With the release of *LoopFollow* 3.2, remote options for the *Loop* app are updated.
+> With the release of *LoopFollow* 3.2, remote options for the *Loop* app were updated to send directly to the *Loop* phone via APNS
 
 > With the release of *LoopFollow* 4.0, you can [share remote control configuration](#export-remote-settings-with-qr-code) using a QR code.
 
 > With the release of *LoopFollow* 4.3, [multiple QR codes are provided which are separated by function](../setup/lf-setup.md#importexport-settings){: target="_blank" } so you can share Nightscout URL, Dexcom Share and Alarm Settings without sharing Remote Control Configurations.
 
+> With the release of *LoopFollow* 4.6, return messages sent from the *Loop* phone are displayed as notifications (requires *Loop* v3.11.1 or newer)
+
 * Keep checking back on this page, the remote capability is under development and there may be new features for you to read about.
 
 The graphic below shows the Remote Settings screen for *LoopFollow*. You must first enter a *Nightscout* URL before any remote options are offered and then only the option suitable for that *Nightscout* site can be selected.

docs/remote/remote-control-overview.md

@@ -81,6 +81,7 @@ The table below indicates the minimum token access for each type of remote contr
 When you enter your credentials, *LoopFollow* tries to reach the site and then provides the status. 
 
 * The *Loop* Remote Control option requires *LoopFollow* version 3.2 or newer
+    * With LoopFollow 4.6 and later, the ability to get direct success or failure responses back to the LoopFollow phone is enhanced but requires Loop version 3.11.1 or newer
 * The *Trio* Remote Control option requires the user be on version 0.5.x or newer of Trio
     * **Breaking change** on 2025-October-06
     * *Trio* 0.6 or newer requires *LoopFollow* 4.0 or newer