You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The *LoopFollow* app and *Trio* app are already changed. This change will propagate to other apps in the Open-Source ecosystem.
141
+
142
+
New method - there will be one automatic run of the build action each week on Sunday.
143
+
144
+
* If it is the second Sunday of the month, the app will be built and uploaded to TestFlight
145
+
* If updated code is detected, the new version of the app will be built and uploaded to TestFlight
146
+
* If no updated code is detected, the build will be skipped (except for the second Sunday of the month)
147
+
148
+
The table below indicates **planned** time for the automatic build schedule. For apps not yet changed to the new method, the weekly runs are on Wednesday and the monthly runs are on the 1st of each month.
149
+
150
+
| Open-Source App | AutoCerts? | Weekly<br>UTC | Once a Month<br>UTC |
@@ -166,6 +177,8 @@ The table below indicates **planned** time for the automatic build schedule.
166
177
Initially, all builds started at the "top of the hour" (HH:00), but it turns out that is when *GitHub* has the most activity.
167
178
In an attempt to minimize build failures due to resource limitations, the minute of the hour for all the apps is gradually being shifted.
168
179
180
+
When the first of the month and Wednesday came on the same day, there were many failed builds. This triggered us to redesign the timing. The new design is for only one run of a build action per week, on Sunday, and inside that build action there is logic to decide if it is the second Sunday of the month. If so, the build is always run and not skipped.
181
+
169
182
170
183
Even if an app doesn't have automatic certificates implemented yet, they are added to the table as suggested values to use when this capability gets added. All times are UTC. If other apps decide to add this feature, please make a pull request to LoopDocs so we can add those times to the deconfliction table.
Copy file name to clipboardExpand all lines: docs/faqs/loop-faqs.md
+15Lines changed: 15 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,21 @@ Each step needed to successfully build your *Loop* app is found in these docs. T
10
10
11
11
If you have any questions, use the [Search](../intro/loopdocs-how-to.md#website-search) feature to find topics in LoopDocs.
12
12
13
+
- - -
14
+
15
+
## What about *Tidepool Loop*?
16
+
17
+
*Tidepool Loop* was approved by the FDA in Jan 2023. In 2025, the [Sequel twiist pump](https://www.twiist.com/) became available with *Tidepool Loop*. Check their site to see if it available in your area.
18
+
19
+
*Tidepool Loop*, cleared by the FDA, is the first:
20
+
21
+
* App that provides automated insulin dosing **and** is configured to be fully interoperable with pump and CGM partners
22
+
* App that originated as a patient-led initiative
23
+
24
+
With this approval, there is now an FDA-approved pathway for independent selection of an app, a pump, and a CGM. Stay tuned for updates at [https://tidepool.org/tidepool-loop](https://tidepool.org/tidepool-loop).
25
+
26
+
- - -
27
+
13
28
## Can I use an android phone or iPad for Loop?
14
29
15
30
Loop requires an *Apple* device. Older iPads do not support *Apple* Health which is required for Loop. It may be possible with newer iPads and newer iOS, but this has not been tested.
Copy file name to clipboardExpand all lines: docs/faqs/omnipod-faqs.md
+38-7Lines changed: 38 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,21 +23,22 @@ You do not need the Omnipod Personal Diabetes Manager (PDM), just the pod suppli
23
23
24
24
DASH pumps communicate with the phone via Bluetooth so they do not require a RileyLink compatible device.
25
25
26
-
## What about *Tidepool Loop*?
26
+
- - -
27
27
28
-
*Tidepool Loop* was approved by the FDA in Jan 2023, but at the current time, there are no announced pump or CGM partners. What does this mean?
28
+
## What about *Tidepool Loop*?
29
29
30
-
*Tidepool Loop*, cleared by the FDA, is the first:
30
+
*Tidepool Loop* was approved by the FDA in Jan 2023. In 2025, the [Sequel twiist pump](https://www.twiist.com/) became available with *Tidepool Loop*. Check their site to see if it available in your area.
31
31
32
-
* App that provides automated insulin dosing **and** is configured to be fully interoperable with pump and CGM partners
33
-
* App that originated as a patient-led initiative
32
+
There is no arrangement for using an FDA cleared version of the Loop app with Omnipod. You must still build it yourself to use Omnipod Eros or DASH pods.
34
33
35
-
With this approval, there is now an FDA-approved pathway for independent selection of an app, a pump, and a CGM. Stay tuned for updates at [https://tidepool.org/tidepool-loop](https://tidepool.org/tidepool-loop).
34
+
- - -
36
35
37
36
## Do I still need a PDM with Omnipod Loop?
38
37
39
38
No, pods are monogamous little creatures. They will pair with only one device at a time for safety reasons...so a pod is either paired with a PDM or your *Loop* app on your iPhone. In other words, your PDM can stay in the diabetes closet while you are Looping. You cannot use the PDM for a pod that has been activated with the *Loop* app. That doesn't mean you should get rid of your PDM if you have one. Instead, keep it for backup situations if you lose your phone. See below for what to do if you lose your phone or RileyLink.
40
39
40
+
- - -
41
+
41
42
## Can I cancel a bolus?
42
43
43
44
Yes, you can cancel a bolus in progress. In fact, because it is very easy to cancel, make sure your phone is locked prior to being put away to avoid inadvertently cancelling a bolus. (This behavior is very similar to the Insulet PDM - which also needs to be locked once a bolus has started.)
@@ -51,6 +52,8 @@ As soon as a bolus is initiated, look at your phone in portrait orientation. Yo
51
52
{width="300"}
52
53
{align="center"}
53
54
55
+
- - -
56
+
54
57
## Can I cancel a temp basal?
55
58
56
59
### Cancel Temp Basal with the *Loop* app
@@ -62,20 +65,42 @@ You can tap on disable Closed-Loop and then immediately tap on enable Closed-Loo
62
65
!!! tip "Bolus in progress"
63
66
Even if a bolus is in progress, you can still switch to Open-Loop and restore scheduled basal. The current bolus continues unless you separately cancel the bolus.
64
67
68
+
- - -
69
+
65
70
## Can I set my own temp basal on Loop?
66
71
67
72
With version 3, the *Loop* app provides a [Manual Temp Basal](../loop-3/omnipod.md#manual-temp-basal) feature.
68
73
74
+
- - -
75
+
76
+
## How much insulin is left when Pod reservoir say zero or 0 U?
77
+
78
+
When the Pod reports 0 U in the reservoir, there can be up to 4 U more delivered.
79
+
80
+
* You will not see a report of these units on the reservoir icon or on the Pod screen
81
+
* The pod keeps track of how many units are delivered after it reports 0 U in the reservoir and it will stop when it delivers 4 more units
82
+
* The pod also keeps track of whether insulin is being delivered and it will start to scream when there is not any more
83
+
84
+
Do **not** count on those 4 U, but be aware that they might be available.
85
+
86
+
The Event Log for dose delivery keeps track of what was actually delivered. The Insulin on Board (IOB) for the app updates if a bolus is interrupted because the pod runs out of insulin or hits the 4 U below zero limit.
87
+
88
+
- - -
89
+
69
90
## What if I lose my phone or RileyLink?
70
91
71
-
For pod users, your pod will finish any currently running temporary basal rate and then revert back to your scheduled basal rate. Without a phone or RileyLink, however, you will not be able to affect any pod use; no basal change, suspend, cancel, or bolus. To do anything other than let basals continue, you will need to take action depending on the situation.
92
+
Most users are now on DASH and no longer need a RileyLink, but you might still walk away from your phone - we just hope you didn't lose it.
93
+
94
+
For pod users, your pod will finish any currently running temporary basal rate and then revert back to your scheduled basal rate. Without a phone (or RileyLink with Eros pod), however, you will not be able to affect any pod use; no basal change, suspend, cancel, or bolus. To do anything other than let basals continue, you will need to take action depending on the situation.
72
95
73
96
* Lost RileyLink only: You can replace your missing RileyLink with one from your backup supplies. No problem to [switch out to a different Rileylink mid-pod session](rileylink-faqs.md#adding-or-changing-rileylink). If you don't have a backup RileyLink to use, then you will need to remove the pod and put on a new pod paired with your PDM until you can get a new RileyLink. In the interim, you are still getting basal from the pod. If you are taking bolus insulin via injection, just add it to Apple Health under insulin. The *Loop* app will read it and keep making predictions for you. Once you inject, then add the carbs that go with that injection into Loop.
74
97
75
98
* Lost iPhone only: You will need to remove the pod and put on a new pod paired with your PDM or a backup phone (with a copy of the *Loop* app on it). You cannot use the old pod with a new device. In the interim, the pod will continue to deliver your scheduled basal until the pod reaches 80 hours. See [New Phone](new-phone.md) for more information.
76
99
77
100
* Lost both RileyLink and phone: You're having a really bad day. You'll need a hug and to follow the same directions as if you lost the phone as shown in the bullet above.
78
101
102
+
- - -
103
+
79
104
## Is there an increase in pod failures on Loop?
80
105
81
106
There is more communication between the pod and the controller (your *Loop* phone) than is typical with the PDM (Insulet provided controller). This increases the load on the pod battery. Most people have no increase in pod failures, but there are steps to take to limit "extra pod battery use". Every time the *Loop* app requests an update of the pod state or issues a command (bolus, basal schedule, temp basal), messages are exchanged with the pod.
@@ -86,10 +111,14 @@ There is more communication between the pod and the controller (your *Loop* phon
86
111
* If uncertain communications are detected such that the *Loop* app cannot determine if a dosing command sent to the pod was actually received, the app will try once a minute to get a response
87
112
* The combination of Eros pods with a RileyLink device with poor signal leading to uncertain comms may cause excessive battery use and contribute to pod faults
88
113
114
+
- - -
115
+
89
116
## What do I do if a pod fails to pair?
90
117
91
118
If you get a pod that is failing to pair, please see [this page](../troubleshooting/pod-pairing.md){: target="_blank" } for steps on how to fix the problem. Follow these steps before filling and trying another pod. If the pod is not screaming, you can probably recover it.
92
119
120
+
- - -
121
+
93
122
## What do you do to stop a screaming pod?
94
123
95
124
Screaming pods indicate the pod is out of insulin or out of time (80 hours) or there has been a critical pod fault. In all these cases, there is no more delivery of insulin.
@@ -103,6 +132,8 @@ Once you have removed the screaming pod, it can be silenced using a paperclip. S
0 commit comments