Skip to content

Commit 8d91dbe

Browse files
committed
add rec bolus information, update a figure
1 parent b19ea5e commit 8d91dbe

2 files changed

Lines changed: 10 additions & 9 deletions

File tree

docs/setup/img/import-settings.png

-21.6 KB
Loading

docs/setup/lf-setup.md

Lines changed: 10 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ You will then be presented with a home screen as shown below.
2525
![initial screen for LoopFollow](img/initial-screen-no-credentials.png){width="300"}
2626
{align="center"}
2727

28-
### Setup your data source
28+
### Setup Your Data Source
2929

3030
Tap on the "Setup Nightscout" button or "Setup Dexcom Share" button to enter your credentials for your preferred service.
3131

@@ -65,9 +65,7 @@ The graphic below shows the display when you tap on the *Nightscout* Settings ro
6565
When adding the Nightscout information to monitor, you can copy your *Nightscout* URL (including the token) from the [Admin Tools in *Nightscout*](https://nightscout.github.io/nightscout/admin_tools/#subjects-and-roles). When pasted into *LoopFollow* URL row, the app will automatically extract and fill in both the URL and token.
6666

6767
!!! note "Setting up a second device"
68-
With version 4.3 and newer, You can set up a second device by scanning a QR code from another LoopFollow user. See this section [Import/Export Settings](#import-export-settings).
69-
70-
- - -
68+
With version 4.3 and newer, You can set up a second device by scanning a QR code from another LoopFollow user. See this section [Import/Export Settings](#importexport-settings).
7169

7270

7371
![enter nightscout credentials](img/lf-data-source-ns.png){width="300"}
@@ -224,13 +222,16 @@ When the QR code is accepted, you will see a screen indicating what type of sett
224222
#### `Rec. Bolus`
225223

226224
!!! warning "LoopFollow Report of Trio Recommended Dose"
227-
It happens. We made a mistake. The `Rec. Bolus` feature for *LoopFollow* was reporting a value from the *Trio* app that was never meant to be used as a recommended bolus.
225+
It happens. We made a mistake. In versions before 4.0, the `Rec. Bolus` feature displayed by *LoopFollow* was a value from the *Trio* app that was never meant to be used as a recommended bolus.
226+
227+
But the mistake has been fixed and an appropriate `Rec. Bolus` is back.
228+
229+
Make sure you have these version of code before using the recommended bolus. And pay attention to the warnings about how long since that recommendation was calculated by Trio.
228230

229-
* With `LoopFollow` 4.0 and newer, users viewing a *Trio* URL will notice the `Rec. Bolus` display is always blank
230-
* Updates are planned for *Trio* and *LoopFollow* to provide the last recommended value from the *Trio* app
231-
* The value shown to users viewing a *Loop* URL matches what the user of the *Loop* phone would see when asking for a recommendation and is not changed in `LoopFollow` 4.0
231+
* LoopFollow 4.3 or newer
232+
* Trio 0.6.0.16 or newer
232233

233-
**Remember: the `Rec. Bolus` values is from the last AID app update to Nightscout**
234+
**Remember: the `Rec. Bolus` value is from the last AID app update to Nightscout**
234235

235236

236237
### Remote Settings

0 commit comments

Comments
 (0)