|
2 | 2 |
|
3 | 3 | ## Remote Control Overview |
4 | 4 |
|
5 | | -*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. At this time, the *Loop* app and the open beta version of the *Trio* app (0.5.x or newer) support direct APNS from *LoopFollow*. |
| 5 | +*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. |
| 6 | + |
| 7 | +The *Loop* app and the open beta version of the *Trio* app (0.5.x or newer) support direct APNS from *LoopFollow*. |
| 8 | + |
| 9 | +!!! warning "Browser Build Update" |
| 10 | + If you use Browser Build, follow the one-time updates needed to transition from *LoopFollow* v3.2 to *LoopFollow* v4.0: |
| 11 | + |
| 12 | + * [Browser Build Update for LoopFollow v4.0](../build/build-options.md#browser-build-update-for-loopfollow-v40){: target="_blank" } |
6 | 13 |
|
7 | 14 | !!! tip "`Loop` Remote Control with *LoopFollow* 3.2" |
8 | 15 | With the release of *LoopFollow* 3.2, the remote control features accessible from LoopFollow match those available from the *LoopCaregiver* app. |
9 | 16 |
|
10 | 17 | You must update to *LoopFollow* 3.2 or newer and configure remote settings in the *LoopFollow* app to use these features. |
11 | 18 |
|
| 19 | +!!! important "Breaking Change: Trio Remote Command Users" |
| 20 | + Trio users must have matching code for LoopFollow and Trio. |
| 21 | + |
| 22 | + * Trio 0.6 (or newer) requires LoopFollow 4.0 (or newer) |
| 23 | + * Trio 0.5.1.28 (or older) requires LoopFollow 3.2.11 (or older) |
| 24 | + |
| 25 | + See [Trio Remote Control](trio-remote-control.md){: target="_blank" } for more information. |
| 26 | + |
| 27 | + For Browser Builders: |
| 28 | + |
| 29 | + * [Browser Build Update for LoopFollow v4.0](../build/build-options.md#browser-build-update-for-loopfollow-v40){: target="_blank" } |
| 30 | + |
12 | 31 |
|
13 | 32 | ### Changes for *LoopFollow* Remote Control of the *Loop* App |
14 | 33 |
|
|
17 | 36 | * *LoopFollow* no longer requires the *Nightscout* site be configured with the APNS credentials |
18 | 37 | * Read access for the *Nightscout* URL is sufficient |
19 | 38 | * With *LoopFollow* 3.1 and older |
20 | | - * *Loop* remote commands are limited to Overrides, require the *Nightscout* site be configured with the APNS credentials and require a token with `careportal` access |
| 39 | + * *Loop* remote commands were limited to Overrides, required the *Nightscout* site be configured with the APNS credentials and required a token with `careportal` access |
21 | 40 |
|
22 | 41 | > With *Trio* 0.2.x, *LoopFollow* only supports temp targets and requires a token with `careportal` access. Once updated to *Trio* 0.5.x or newer, the full Trio Remote Control options are available. |
23 | 42 |
|
24 | | -!!! abstract "Remote Control Updates in Development" |
25 | | - The instructions in this section depend on the version of the *Trio* app and the *LoopFollow* app. |
26 | | - |
27 | | - * With *LoopFollow* 3.2 or newer: |
28 | | - * Remote commands are sent directly through APNS for both the *Loop* app and the *Trio* open beta version |
29 | | - * If you are using *Trio* 0.2.x, remote commands are routed via *Nightscout* and are limited to modifying `Temp Targets` |
30 | | - * With *LoopFollow* 3.1 and earlier: |
31 | | - * Using the *Loop* app: |
32 | | - * remote commands are routed via *Nightscout* |
33 | | - * Only Overrides can be modified using *LoopFollow* and only if *Nightscout* site has the APNS keys embedded |
34 | | - * Using the *Trio* app |
35 | | - * If you are using *Trio* 0.5.x or newer, remote commands are sent directly through APNS |
36 | | - * If you are using *Trio* 0.2.x, remote commands are routed via *Nightscout* |
37 | | - |
38 | | - > Using APNS directly from *LoopFollow* provides faster feedback about commanding. |
39 | | - |
40 | | - > With *LoopFollow* 3.2, APNS keys will not need to be embedded in the *Nightscout* site for remote control of the *Loop* app from *LoopFollow*, which may simplify configuration for those who use a paid service for *Nightscout*. |
41 | 43 |
|
42 | 44 | ### *LoopFollow* Remote Control |
43 | 45 |
|
44 | 46 | * *LoopFollow* Remote Control sends messages to the loopers phone using APNS |
45 | | - * Requires *LoopFollow* 3.2 or newer to use with the *Loop* app (version 3.x) |
46 | | - * Requires *Trio* 0.5 or newer for the *Trio* app |
| 47 | + * **Loop**: Requires *LoopFollow* 3.2 or newer |
| 48 | + * **Trio**: Requires matched code versions: |
| 49 | + * Trio 0.6 (or newer) requires LoopFollow 4.0 (or newer) |
| 50 | + * Trio 0.5.1.28 (or older) requires LoopFollow 3.2.11 (or older) |
47 | 51 | * Commands go via APNS to the *Loop*/*Trio* phone |
48 | | - * An immediate success or failure for sending the message to APNS is recieved |
| 52 | + * An immediate success or failure for **sending** the message to APNS is received |
49 | 53 | * There still could be a communication failure between APNS and the looper's phone or the command could be rejected by the looper's app |
| 54 | + * **Trio v0.6 or newer** an APNS response is returned to *LoopFollow* |
| 55 | + * A success or failure message is pushed back to the *LoopFollow* phone from the *Trio* phone when a remote command is received and handled |
50 | 56 | * The results show up in *Nightscout* after being uploaded from the *Loop*/*Trio* phone |
51 | 57 | * The results are plotted or displayed in *LoopFollow* after being downloaded from the *Nightscout* URL as a new treatment |
52 | 58 | * APNS keys do not need to be embedded in the *Nightscout* site |
|
0 commit comments