Usage tracking for Omnipod basal drift compensation

Usage tracking: Omnipod basal drift compensation

This feature is available in 3.4.2.3 and later. It is currently gated by a semaphore file. We want to understand how many users have enabled it so we can confirm sufficient real-world usage and testing before safely removing the gating.

This feature compensates for basal insulin that the pump did not deliver as intended (e.g. due to frequent updates affecting delivery timing). The resulting deficit is detected and compensated for by delivering small (0.05U) boluses. For background and discussion, see issue #4158 and PR #4499.

Enable drift compensation

Create an empty file called omnipod_drift_compensation in the extra subfolder (lower case!) of your phone’s AAPS directory. After that, restart AndroidAPS.

Notes

• Basal drift may have (un)intentionally propagated into profiles — reassess your profile after enabling this feature.
• Compensation is delivered as a 0.05U bolus and will appear as such in the GUI and Watch app.

Are you using it?

Please leave a 👍 reaction on this issue if you enabled basal drift compensation.

Issues

Please do not report issues here. Open a separate issue with logs, steps to reproduce, and relevant details.

No source file, test, or implementation entry point is identified; the issue only describes the omnipod_drift_compensation semaphore file and asks users to react if they enabled it. Start by reviewing the linked background issue #4158 and PR #4499, then clarify what usage-tracking change is expected and how completion would be measured.