|
| |
NEWS From Loop and Learn (15 January 2023)
- Loop 3 Has Been Released!
- Loop Safety Highlight: "Future Glucose"
- LnL Panel Discussion: Loop vs. O5
- Nightscout Host Services Billing
|
|
|
|
| |
Introducing Loop 3
 | |
The moment we've all been waiting for has arrived: Loop 3.0 is now the official released version of Loop!
You can read all about Loop 3 in LoopDocs. In addition to providing support for DASH pods and Dexcom G7, Loop 3 provides support for remote overrides, bolusing and carbohydrate entries, as well as safety enhancements.
To build Loop 3, you'll need iOS 15.1 or higher. If you're building using Xcode, then you'll need Xcode 14 or higher, which will require macOS 12.5 or higher. If your mac can't be updated, consider the GitHub build method.
The entire community thanks the development team, led by Pete Schwamb, for their tireless innovation!
|
|
|
|
|
|
|
| |
Loop Safety Highlight: "Future Glucose"...
Time to UPDATE!
| |
 |
As of 12 January 2023, an important new safety feature is available in both Loop 3 (formerly "Loop-dev") and FreeAPS-dev, in response to the below scenario.
If you are not updated, this could happen:
When a future value of glucose is entered into Loop, Loop no longer provides a prediction curve but uses that future value as the eventual glucose value, reports it on the main Loop screen and continues automatic dosing of insulin. When in closed loop, this can result in an increase or decrease of delivered insulin depending on the glucose value. This has happened when:
- the Loop phone time was changed ahead manually (for example when playing a game) and then returned to automatic time later.
- someone entered a glucose reading into Apple Health from a finger-stick reading and got the time wrong.
- For example, if it was 12:10 pm when entering a value taken at 11:45 am, and inadvertently entered 11:45 pm for the glucose time.
How to be sure this does not happen to you? Update your Loop or FreeAPS app!
|
|
|
|
|
|
|
| |
LnL Panel Discussion and Q & A Videos:
Loop vs. Omnipod 5
| |
 |
Watch this informative discussion and bonus Q & A with experienced Loopers and O5 users Jon Fawcett, Matthew Kitchin, Britni Schipper and Tina Hammer about their experiences with Omnipod 5 and how it compares to Loop.
Topics include:
- Comparison to/switching from Loop
- General O5 tips
- Understanding how the O5 algorithm works/learns, and
- How to best approach managing T1D with O5
|
|
|
|
|
|
|
| |
Nightscout Billing
| |
 |
As community members all made different decisions about how to address the 28 November shut down of Heroku's free tier, we're now curious about the general experience among our fellow loopers, who are using the following platforms:
Google Cloud (free or very cheap), Oracle Cloud (free), Northflank (free or very cheap), Azure (free), Railway app (free or very cheap) and Heroku Hobby, now known as Basic ($7) or Eco ($5).
As of this writing, with the exception of a few double-charge situations by Heroku, costs for Nightscout hosting services seem to be as expected. The Google Cloud Nightscout link below explains how to verify what your pricing should be if you're a GC Nightscout user.
Based upon what we've learned, if you want to switch to the Heroku Eco plan, sign up for Eco on the first day of the month in order to avoid double billing. It turns out that Eco is not prorated based upon the number of days in the month that you've had that plan.
Please check your billing statement or credit card to verify your actual pricing and contribute to our FB Survey Post, linked below, if you see any other anomalies.
|
|
|
|
|
|
