diff --git a/docs/faqs/cgm-faqs.md b/docs/faqs/cgm-faqs.md index 9000e563a47..3b4be62172a 100644 --- a/docs/faqs/cgm-faqs.md +++ b/docs/faqs/cgm-faqs.md @@ -79,6 +79,7 @@ sequenceDiagram Note over dexcom: New sensor warmup... ⏱️ user ->> loop_app: Add CGM user ->> loop_app: Enter new Transmitter Serial Number + user ->> loop_app: Enable Remote Upload dexcom -->> user: New Sensor operational deactivate dexcom ``` diff --git a/docs/faqs/new-phone.md b/docs/faqs/new-phone.md index 5b4067cf332..6cc78c484c6 100644 --- a/docs/faqs/new-phone.md +++ b/docs/faqs/new-phone.md @@ -1,10 +1,12 @@ ## Overview -Changing phones means you have to rebuild the Loop app onto the new phone. When you transfer information from your old phone to your new one, all your Loop information is included and the Loop icon will appear, but the app will not open. +Changing phones means you have to rebuild the Loop app onto the new phone. When you transfer information from your old phone to your new one, all your Loop information is included and the Loop icon will appear, but the app will not open until you install Loop from either TestFlight (Browser Build) or Xcode (Mac-Xcode Build). -### Most Recent iOS is Required +Some people don't have access to their old phone. There are instructions for handling that on this page. It makes the whole process more stressful, but remember, pods continue to deliver basal rate and Medtronic pumps can be controlled on the pump itself. Use your backup plan until you can get Loop running on a new phone. -When you change phones, *Apple* will force you to the latest iOS version available for your new phone. +### Forced iOS Update + +When you change phones,  Apple  will force you to the latest iOS version available for your new phone. ### Prepare Before Upgrade @@ -12,19 +14,23 @@ If you are using Dexcom G7, make sure you keep the 4-digit code for your current If you still have your old phone, you can prepare before switching to the new phone. +* Be sure to record your Loop Settings (screenshots work well) + +If you don't have your old phone, hopefully you have an iCloud backup and can use that to transfer your information to your new phone. + !!! tip "Keep the Old Phone Until Loop is Working on the New One" Even if you plan to turn your old phone in for a rebate, you can ask to keep the old one for a week or two. Most vendors will agree to this. -Update your old phone to the latest iOS the hardware supports - this simplifies the automatic transfer process *Apple* provides to move all your data and apps from your old phone to your new phone. - -!!! abstract "New Phone Checklist for *Mac-Xcode Build*" - * Are your [Mac and Xcode versions](../build/xcode-version.md#how-do-all-the-minimum-versions-relate-to-each-other) compatible with the latest iOS version? - * If not, you should configure and build the app with [Browser Build](../gh-actions/gh-overview.md) +Update your old phone to the latest iOS the hardware supports - this simplifies the automatic transfer process  Apple  provides to move all your data and apps from your old phone to your new phone. !!! abstract "New Phone Checklist for *Browser Build*" * The Loop app will install from TestFlight onto the most recent iOS * If a new version of Loop is available, we recommend updating and building to the latest [GitHub Update](../gh-actions/gh-update.md) +!!! abstract "New Phone Checklist for *Mac-Xcode Build*" + * Are your [Mac and Xcode versions](../build/xcode-version.md#how-do-all-the-minimum-versions-relate-to-each-other) compatible with the latest iOS version? + * If not, you should configure and build the app with [Browser Build](../gh-actions/gh-overview.md) + ### Different Developer ID !!! important "Different Developer ID" @@ -33,21 +39,18 @@ Update your old phone to the latest iOS the hardware supports - this simplifies * The new app that you build with the new Developer ID will open and you can [Onboard](../loop-3/onboarding.md) * The old app will still be on the phone: find it and delete it to avoid confusion -## Step-by-Step Instructions - -### Procure a New Phone +## Procure a New Phone 1. Procure the new phone and keep the old one (if possible) + * [Loop with the old phone](#loop-with-the-old-phone) until it is convenient to switch to the new phone 1. Transfer your information to your new phone * Let the new phone vendor help you * Use an [iCloud back-up](https://support.apple.com/en-us/HT210217) for the transfer * Use both devices with [Quick Start](https://support.apple.com/en-us/HT210216) to transfer from the old to the new phone -If you cannot keep the old phone, or it is not available, then skip ahead to the [Use New Phone to Loop](#use-new-phone-to-loop). +### Loop with the Old Phone -### Keep the Old Phone - -Start using the new phone as a phone, but wait for a convenient time to complete the process. +If you cannot keep the old phone, or it is not available, then skip ahead to the [Loop with the New Phone](#loop-with-the-new-phone). * You can use the old phone to Loop until you are ready to switch * Use WiFi with the old phone and use your new phone as a cellular hot-spot as needed @@ -55,22 +58,25 @@ Start using the new phone as a phone, but wait for a convenient time to complete * If using Dexcom, use the Dexcom app on the old phone * If using Libre, the Libre is connected to Loop on the old phone -### Use New Phone to Loop +## Loop with the New Phone -Make sure the new phone has bluetooth turned on. +### Install Loop -It's important to do the transfer of information from the old phone to the new phone before you install and open Loop on the new phone. If this is not possible, then you will do the normal [Onboarding](../loop-3/onboarding.md) for a new Loop app. +It is easier if you transfer information from the old phone to the new phone before you install and open Loop on the new phone. If this is not possible, then you will do the normal [Onboarding](../loop-3/onboarding.md) for a new Loop app. -* When you transfer information from your old phone to your new phone, all the Loop settings files get copied to the new device including information about the pod - * If you have changed pods after the transfer, then you should swap at your next pod change - * If you time things well, you can keep the pod -* Be sure to record (or screenshot) all your settings from your old phone before you start -* Install Loop on the new phone (all your settings should be there) - * Install via [*Mac-Xcode Build*](#build-using-mac-xcode) or from [*TestFlight*](#install-from-testflight) for *Browser Build* +1. When you transfer information from your old phone to your new phone, all the Loop settings files get copied to the new device including information about the pod + * If the timing works, you can keep the pod if you switch to using the new phone for Loop after the information transfer and before changing pods with the old phone + * If this is not possible, you will need to start a new pod with the new phone + * Medtronic users will have all their information transferred but will only have one phone connected to the RileyLink +1. Install Loop on the new phone (all your settings should be there) + * Install from [*TestFlight*](#install-from-testflight) for *Browser Build* or from Xcode for [*Mac-Xcode Build*](#build-using-mac-xcode) +1. As soon as you install Loop on the new phone, go ahead and disable Closed Loop. + * Keep closed loop disabled until you complete the full transfer and checkout. -As soon as you install Loop on the new phone, go ahead and disable Closed Loop. +#### Install from TestFlight -* Keep closed loop disabled until you completed the full transfer and checkout. +* Open TestFlight app on new phone +* Install Loop on your new phone from TestFlight #### Build using Mac-Xcode @@ -78,60 +84,69 @@ As soon as you install Loop on the new phone, go ahead and disable Closed Loop. * Plug in the new phone to the computer (trust phone/computer) and hit build * Build Loop on the new phone -#### Install from TestFlight +### Prepare to Change Loop Phones -* Open TestFlight app on new phone -* Install Loop on your new phone from TestFlight +On old phone (if available): + +1. Loop app, turn off the slider for the RileyLink if using Medtronic or Eros Pods + * Do not delete the pump; if using pods, this cannot be reversed +1. Phone Settings, Bluetooth + * Forget the connections to the CGM (Dexcom or Libre) + * Do not forget anything that says TWI_BOARD or NXP_BLE (this is your DASH pod) +1. Phone Settings, Bluetooth: Disable Bluetooth + +### Transfer Pump + +Bluetooth must be off on the old phone. + +* On the new phone, examine the pump status + * If everything transfered, your new phone should be communicating with your pump + * If using a RileyLink device and it doesn't show as connected, try a power cycle on the device + * If you need to start a new pod, do it now +* If necessary, delete the pump type and add it back ### Transfer CGM It is now time to transfer the CGM to the new phone. -#### Dexcom App +* [Dexcom CGM](#dexcom-cgm) +* [Libre CGM](#libre-cgm) + +#### Dexcom CGM -The Dexcom app might have transferred successfully, but it’s not a bad idea to install that fresh from the App Store on the new phone. It may be required to do so. +The Dexcom app might have transferred successfully, but it’s not a bad idea to install that fresh from the App Store on the new phone. Doing so may be required. -* Be sure to record your Dexcom Transmitter ID or 4-digit code (for G7) +* You need your Dexcom Transmitter ID or 4-digit code (for G7) * On the new phone, in Loop, delete Dexcom as your CGM so you can pair the new phone to the Dexcom app -* On the old phone, go into Bluetooth settings and forget every Dexcom ID you can find - * If you are not able to forget the connection between the old phone with the Dexcom transmitter, you might need to call Dexcom for help -* On the old phone, turn off Bluetooth * On the new phone, open the Dexcom app and pair to the transmitter (G5, G6 or One) or enter the four-digit code for G7 * You can keep using your current sensor session * You indicate you are starting a new sensor (it’s not really new) - * G5, G6 or ONE, enter transmitter ID and "no code" + * G5, G6 or ONE, enter transmitter ID + * If you enter no code, you will be warned that calibrations are required (don't worry) + * When the app pairs with the tranmistter, it picks up the current session, and calibrations are not required * G7, enter 4-digit code * Within 5 to 10 minutes, Dexcom app should read the current session and keep going * Wait for Dexcom to connect * On new phone, add the CGM to Loop -#### Libre +#### Libre CGM Placeholder for Libre instructions. Suggested procedures from the community are encouraged. * On the new phone, in Loop, delete Libre as your CGM -* On the old phone, turn off Bluetooth * On the new phone, in Loop, add Libre as your CGM * Wait for Libre to connect -### Transfer Pump - -* On the old phone, make sure Bluetooth is off - this disables connection from the old phone to the pump -* On the new phone, examine the pump status - * If everything tranfered, you should be communicating with your pump - * If not, delete the pump and add it back - ### Ready to Loop -1. Keep closed loop disabled until you completed the full transfer and checkout. +1. Keep closed loop disabled until you complete the full transfer and checkout. !!! important "Check Every Setting" - Make sure all the basal, ISF, CR, Insulin Selection and ranges are correct before using the new phone to Loop. - - Check permissions and notification settings. - - Check Focus mode settings - make sure Loop and Dexcom apps have permission for all Focus modes. + * Make sure all the basal, ISF, CR, Insulin Selection and ranges are correct + * Check Dosing Strategy selection + * Check permissions and notification settings + * Check Focus mode settings - make sure Loop and CGM apps have permission for all Focus modes 1. Do a manual bolus of the smallest possible amount to make sure Loop and pump are working. @@ -139,16 +154,16 @@ Placeholder for Libre instructions. Suggested procedures from the community are 1. Check COB and IOB - !!! important "Apple Health History" - Your COB and IOB might not carry over to your new phone. + !!! important "Apple Health  History" + Your COB and IOB may not carry over to your new phone. - Loop reads from Apple HealthKit and might restore COB and IOB from health – this assumes health is stored on iCloud and synchronized between old and new phone + Loop reads from  Apple Health  and may restore COB and IOB from health – this assumes health is stored on iCloud and synchronized between old and new phone If your COB and IOB show up as blank, you can go open loop for 3 to 6 hours. If you are impatient, you can try this but be cautious: - * Add back your insulin via Apple Health (on your new phone) to the time that the boluses and positive temp basals were recorded on your old phone: Apple Health/Insulin Delivery/Add Data. + * Add back your insulin via  Apple Health  (on your new phone) to the time that the boluses and positive temp basals were recorded on your old phone:  Apple Health , Insulin Delivery, Add Data. * Wait about 5 minutes for that insulin to show up in Loop as Active Insulin * Finally, add the Carbohydrates to Loop by entering them in your Add Carb Entry screen and rolling back the Date/Time wheel to the time of the original entry(ies) @@ -156,10 +171,12 @@ Placeholder for Libre instructions. Suggested procedures from the community are ### Old Phone -Once you are using Loop on your new phone, you can remove the pump from the old phone. +Once you are using Loop on your new phone, you can delete the pump from the old phone. * On the old phone, in the Loop app: - * If using Medtronic, delete the pump - * If using DASH pods, go into phone Settings -> Bluetooth and forget the pod; it will show up as TWI_BOARD or NXP_BLE + * Delete the pump +* If using DASH pods with direct Bluetooth connection to your phone + * Go into the old phone Settings -> Bluetooth and turn it back on + * Forget the pod; it will show up as TWI_BOARD or NXP_BLE -You can either keep the Old Phone as a backup or reset it and turn it in for credit or give to some deserving individual. +You can either keep the Old Phone as a backup, reset it and turn it in for credit or give it to some deserving individual. diff --git a/docs/loop-3/add-cgm.md b/docs/loop-3/add-cgm.md index eec1236e0a5..38a9ab9e140 100644 --- a/docs/loop-3/add-cgm.md +++ b/docs/loop-3/add-cgm.md @@ -36,6 +36,19 @@ If you later decide to use a different CGM type, you must first delete the CGM a * For Dexcom G5, G6 or ONE, you must delete the CGM when you change transmitters (about once every 90 days) +### Remote Upload from Loop + +Loop provides an option to upload CGM values to a remote service like Nightscout or Tidepool. In many cases this can be a preferred solution. + +With Loop 3, the data-store on the Loop phone keeps a full week of data. If there is an interruption in the upload, when it is restored, Loop will fill in up to 1-week of CGM data that was not previously uploaded. + +Some people use Dexcom Share to feed their remote services. There have been outages with Share. When those occur, the data is not back-filled like it is with Loop. + +This is the reason why there's a comment under each CGM below to select Upload Readings. + +![graphic showing upload readings selection](img/cgm-upload-readings.jpg){width="350"} +{align="center"} + ### Dexcom G5, G6, ONE To use the Dexcom G5, G6 or ONE: @@ -69,6 +82,7 @@ You can find the **transmitter ID** in your Dexcom G6 app or on the back of the ![picture of transmitter box with arrow and marking of transmitter id (sn)](img/dexcom-g6-transmitter-box-sn.svg){width="350"} {align="center"} +It is recommended that you enable [Remote Upload from Loop](#remote-upload-from-loop). #### Change Dexcom Sensor @@ -86,6 +100,7 @@ When you change the Dexcom G5, G6 or ONE Transmitter, you need to delete your CG The Dexcom G7 is handled differently - Loop automatically detects when a new sensor/transmitter pair is added to the Dexcom G7 app. +Your selection to enable [Remote Upload from Loop](#remote-upload-from-loop) must be repeated with each new Transmitter. The default setting is disabled. #### About *Dexcom Share* credentials @@ -97,7 +112,7 @@ This is only available on Loop 3. You must have the G7 app on the same phone as Loop. When the G7 app switches to the next sensor/transmitter assembly, Loop automatically switches too. -Minimal documentation is provided. +It is recommended that you enable [Remote Upload from Loop](#remote-upload-from-loop). ![graphic showing Loop searching for G7](img/g7.svg){width="500"} {align="center"} diff --git a/docs/loop-3/img/cgm-upload-readings.jpg b/docs/loop-3/img/cgm-upload-readings.jpg new file mode 100644 index 00000000000..a7987b305aa Binary files /dev/null and b/docs/loop-3/img/cgm-upload-readings.jpg differ diff --git a/docs/operation/features/overrides.md b/docs/operation/features/overrides.md index e1a72336ca7..5f92cb2473d 100644 --- a/docs/operation/features/overrides.md +++ b/docs/operation/features/overrides.md @@ -135,10 +135,7 @@ When you've made your selections, save the preset using the "Save" button in the ### Select 1% Insulin Needs -!!! warning "Not Available in 2.2.x" - This feature is only available in Loop 3 or later. - - * Not available in Loop 2.2.x +Available with Loop 3. The selectable Overall Insulin Needs values are not limited by the default picker values of 10%.