AAPS Omnipod Insulin Pump Driver Documentation

These instructions are for configuring the Omnipod Eros generation pump (NOT Omnipod Dash). The Omnipod driver is available as part of AAPS (AAPS) as of version 2.8.

This software is part of a DIY artificial pancreas solution and is not a product but requires YOU to read, learn, and understand the system, including how to use it. Tik Jūs pats atsakote už tai, ką darysite su šia sistema.

Hardware and Software Requirements

  • Pod Communication Device

Component that bridges communication from your AAPS enabled phone to Eros generation pods.

  • Android_phone Mobile Phone Device

Component that will operate AAPS and send control commands to the Pod communication device.

  • Omnipod_Pod Insulin Delivery Device

Component that will interpret commands received from the Pod communication device originating from your AAPS enable phone.

  • A new Omnipod pod (Eros generation - NOT DASH)

These instructions will assume that you are starting a new pod session; if this is not the case, please be patient and attempt to begin this process on your next pod change.

Before You Begin

SAFETY FIRST - do not attempt this process in an environment where you cannot recover from an error (extra pods, insulin, charged RileyLink, and phone devices are must-haves).

Your Omnipod PDM will no longer work after the AAPS Omnipod driver activates your pod. Previously you used your Omnipod PDM to send commands to your Omnipod Eros pod. An Omnipod Eros pod only allows a single device to send communication to it. The device that successfully activates the pod is the only device allowed to communicate with it from that point forward. This means that once you activate an Omnipod Eros pod with your RileyLink through the AAPS Omnipod driver, you will no longer be able to use your PDM with your pod. The AAPS Omnipod driver with the RileyLink is now your acting PDM. This does NOT mean you should throw away your PDM, it is recommended to keep it around as a backup, and for emergencies with AAPS is not working correctly.

You can configure multiple RileyLinks, but only one selected RileyLink at a time can communicate with a pod. The AAPS Omnipod driver supports the ability to add multiple RileyLinks in the RileyLink configuration, however, only one RileyLink at a time can be selected to be used for sending and receiving communication.

Your pod will not shut off when the RileyLink is out of range. When your RileyLink is out of range or the signal is blocked from communicating with the active pod, your pod will continue to deliver basal insulin. Upon activating a pod, the basal profile defined in AAPS will be programmed into the new pod. Should you lose contact with the pod, it will revert to this basal profile. You will not be able to issue new commands until the RileyLink comes back in range and re-establishes the connection.

30 min Basal Rate Profiles are NOT supported in AAPS. If you are new to AAPS and are setting up your basal rate profile for the first time please be aware that basal rates starting on a half hour are not supported and you will need to adjust your basal rate profile to start on the hour. For example, if you have a basal rate of say 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, this will not work. You will need to update this 1.1 unit basal rate to a time range of either 9:00-11:00 or 10:00-12:00. Even though the 30 min basal rate profile increments are supported by the Omnipod hardware itself, AAPS is not able to take them into account with its algorithms currently.

Enabling the Omnipod Driver in AAPS

You can enable the Omnipod driver in AAPS in two ways:

Option 1: The Setup Wizard

After installing a new version of AAPS, the Setup Wizard will start automatically. This will also occur during in place upgrades. If you already have exported your settings from a previous installation you can exit the Setup Wizard and import your old settings. For new installations proceed below.

Via the AAPS Setup Wizard (2) located at the top right-hand corner three-dot menu (1) and proceeding through the wizard menus until you arrive at the Pump screen. Then select the Omnipod radio button (3) .

Enable_Omnipod_Driver_1 Enable_Omnipod_Driver_2

On the same screen, below the pump selection, the Omnipod Driver Settings are displayed, under the RileyLink Configuration add your RileyLink device by pressing the Not Set text.

On the RileyLink Selection screen press the Scan button and select your RileyLink by scanning for all available Bluetooth devices and selecting your RileyLink from the list. When properly selected you are returned to the pump driver selection screen displaying the Omnipod driver settings showing your selected RileyLink with the MAC address listed.

Press the Next button to proceed with the rest of the Setup Wizard. It can take up to one minute for the selected RileyLink to initialize and the Next button to become active.

Detailed steps on how to setup your pod communication device are listed below in the RileyLink Setup Section.


Option 2: The Config Builder

Via the top-left hand corner hamburger menu under Config Builder (1)PumpOmnipod by selecting the radio button (2) titled Omnipod. Selecting the checkbox (4) next to the Settings Gear (3) will display the Omnipod menu as a tab in the AAPS interface titled POD. This is referred to in this documentation as the Omnipod (POD) tab.

NOTE: A faster way to access the Omnipod settings can be found below in the Omnipod Settings section of this document.

Enable_Omnipod_Driver_3 Enable_Omnipod_Driver_4

Verification of Omnipod Driver Selection

Note: If you have exited the Setup Wizard early without selecting your RileyLink, the Omnipod Driver is enabled but you will still need to select your RileyLink. You may see the Omnipod (POD) tab appear as it does below

To verify that you have enabled the Omnipod driver in AAPS swipe to the left from the Overview tab, where you will now see an Omnipod or POD tab.


Omnipod Configuration

Please swipe left to the Omnipod (POD) tab where you will be able to manage all pod and RileyLink functions (some of these functions are not enabled or visible without an active pod session):

refresh_pod_status Refresh Pod connectivity and status

pod_management Pod Management (Activate, Deactivate, Play test beep, RileyLink Stats and Pod history)

Activating a Pod

Before you can activate a pod please ensure you have properly configured and connected your RileyLink connection in the Omnipod settings

REMINDER: Pod communication occurs at limited ranges for pod activation pairing due to security safety measures. Before pairing the Pod’s radio signal is weaker, however after it has been paired it will operate at full signal power. During these procedures, make sure that your pod is within close proximity (~30 cm away or less) but not on top of or right next to the RileyLink.*

  1. Navigate to the Omnipod (POD) tab and click on the POD MGMT (1) button, and then click on Activate Pod (2).

    Activate_Pod_1 Activate_Pod_2

  2. The Fill Pod screen is displayed. Fill a new pod with at least 80 units of insulin and listen for two beeps indicating that the pod is ready to be primed. When calculating the total amount of insulin you need for 3 days, please take into account that priming the pod will use 12 to 15 units.


    Ensure the new pod and RileyLink are within close proximity of each other (~30cm or less) and click the Next button.

  3. On the Initialize Pod screen, the pod will begin priming (you will hear a click followed by a series of ticking sounds as the pod primes itself). If RileyLink is out of range of the pod being activated, you will receive an error message No response from Pod. If this occurs, move the RileyLink closer (~30 cm away or less) to but not on top of or right next to the Pod and click the Retry (1) button.

    Activate_Pod_4 Activate_Pod_5

  4. Upon successful priming a green checkmark will be shown and the Next button will become enabled. Click on the Next button to complete the pod priming initialization and display the Attach Pod screen.


  5. Next, prepare the infusion site of the new pod. Remove the pod’s plastic needle cap and white paper backing from the adhesive and apply the pod to your usually selected site on your body. When finished, click on the Next button.


  6. The Attach Pod dialog box will now appear. ONLY click on the OK button if you are ready to deploy the cannula.


  7. After pressing OK, it may take some time before the Omnipod responds and inserts the cannula (1-2 minutes maximum), so be patient.

    If RileyLink is out of range of the pod being activated, you will receive an error message No response from Pod. If this occurs, move the RileyLink closer (~30 cm away or less) to but not on top of or right next to the Pod and click the Retry button.

    If the RileyLink is out of Bluetooth range or does not have an active connection to the phone, you will receive an error message No response from RileyLink. If this occurs, move the RileyLink closer to the phone and click the Retry button.

    NOTE: Before the cannula is inserted, it is good practice to pinch the skin near the cannula insertion point. This ensures a smooth insertion of the needle and will decrease your chances of developing occlusions.


    Activate_Pod_10 Activate_Pod_11

  8. A green checkmark appears, and the Next button becomes enabled upon successful cannula insertion. Click on the Next button.


  9. The Pod activated screen is displayed. Click on the green Finished button. Congratulations! You have now started a new active pod session.


  10. The Pod management menu screen should now display with the Activate Pod (1) button disabled and the Deactivate Pod (2) button enabled. This is because a pod is now active and you cannot activate an additional pod without deactivating the currently active pod first.

    Click on the back button on your phone to return to the Omnipod (POD) tab screen which will now display Pod information for your active pod session, including current basal rate, pod reservoir level, insulin delivered, pod errors and alerts.

    For more details on the information displayed go to the Omnipod (POD) Tab section of this document.

    Activate_Pod_14 Activate_Pod_15

Deactivating a Pod

Under normal circumstances, the life of a pod should run for three days (72 hours) and an additional 8 hours after the pod expiration warning for a total of 80 hours of pod usage.

To deactivate a pod (either from expiration or from a pod failure):

  1. Go to the Omnipod (POD) tab, click on the POD MGMT (1) button, on the Pod management screen click on the Deactivate Pod (2) button.

    Deactivate_Pod_1 Deactivate_Pod_2

  2. On the Deactivate Pod screen, first, make sure the RileyLink is in close proximity to the pod but not on top of or right next to the pod, then click on the Next button to begin the process of deactivating the pod.


  3. The Deactivating Pod screen will appear, and you will receive a confirmation beep from the pod that deactivation was successful.


    IF deactivation fails and you do not receive a confirmation beep, you may receive a No response from RileyLink or No response from Pod message. Please click on the Retry (1) button to attempt deactivation again. If deactivation continues to fail, please click on the Discard Pod (2) button to discard the Pod. You may now remove your pod as the active session has been deactivated. If your Pod has a screaming alarm, you may need to manually silence it (using a pin or a paperclip) as the Discard Pod (2) button will not silence it.

    Deactivate_Pod_5 Deactivate_Pod_6

  4. A green checkmark will appear upon successful deactivation. Click on the Next button to display the pod deactivated screen. You may now remove your pod as the active session has been deactivated.


  5. Click on the green button to return to the Pod management screen.


  6. You are now returned to the Pod management menu press the back button on your phone to return to the Omnipod (POD) tab. Verify that the RileyLink Status: field reports Connected and the Pod status: field displays a No active Pod message.

    Deactivate_Pod_9 Deactivate_Pod_10

Suspending and Resuming Insulin Delivery

The process below will show you how to suspend and resume insulin pump delivery.

NOTE - if you do not see a SUSPEND button, then it has not been enabled to display in the Omnipod (POD) tab. Enable the Show Suspend Delivery button in Omnipod tab setting in the Omnipod settings under Other.

Suspending Insulin Delivery

Use this command to put the active pod into a suspended state. In this suspended state, the pod will no longer deliver any insulin. This command mimics the suspend function that the original Omnipod PDM issues to an active pod.

  1. Go to the Omnipod (POD) tab and click on the SUSPEND (1) button. The suspend command is sent from the RileyLink to the active pod and the SUSPEND (3) button will become greyed out. The Pod status (2) will display SUSPEND DELIVERY.

    Suspend_Insulin_Delivery_1 Suspend_Insulin_Delivery_2

  2. When the suspend command is successfully confirmed by the RileyLink a confirmation dialog will display the message All insulin delivery has been suspended. Click OK to confirm and proceed.


  3. Your active pod has now suspended all insulin delivery. The Omnipod (POD) tab will update the Pod status (1) to Suspended. The SUSPEND button will change to a new Resume Delivery (2) button


Resuming Insulin Delivery

Use this command to instruct the active, currently suspended pod to resume insulin delivery. After the command is successfully processed, insulin will resume normal delivery using the current basal rate based on the current time from the active basal profile. The pod will again accept commands for bolus, TBR, and SMB.

  1. Go to the Omnipod (POD) tab and ensure the Pod status (1) field displays Suspended, then press the Resume Delivery (2) button to start the process to instruct the current pod to resume normal insulin delivery. A message RESUME DELIVERY will display in the Pod status (3) field, signifying the RileyLink is actively sending the command to the suspended pod.

    Resume_Insulin_Delivery_1 Resume_Insulin_Delivery_2

  2. When the Resume delivery command is successfully confirmed by the RileyLink a confirmation dialog will display the message Insulin delivery has been resumed. Click OK to confirm and proceed.


  3. The Omnipod (POD) tab will update the Pod status (1) field to display RUNNING, and the Resume Delivery button will now display the SUSPEND (2) button.


Acknowledging Pod Alerts

NOTE - if you do not see an ACK ALERTS button, it is because it is conditionally displayed on the Omnipod (POD) tab ONLY when the pod expiration or low reservoir alert has been triggered.

The process below will show you how to acknowledge and dismiss pod beeps that occur when the active pod time reaches the warning time limit before the pod expiration of 72 hours (3 days). This warning time limit is defined in the Hours before shutdown Omnipod alerts setting. The maximum life of a pod is 80 hours (3 days 8 hours), however Insulet recommends not exceeding the 72 hour (3 days) limit.

NOTE - If you have enabled the „Automatically acknowledge Pod alerts“ setting in Omnipod Alerts, this alert will be handled automatically after the first occurrence and you will NOT need to manually dismiss the alert.

  1. When the defined Hours before shutdown warning time limit is reached, the pod will issue warning beeps to inform you that it is approaching its expiration time and a pod change will soon be required. You can verify this on the Omnipod (POD) tab, the Pod expires: (1) field will show the exact time the pod will expire (72 hours after activation) and the text will turn red after this time has passed, under the Active Pod alerts (2) field where the status message Pod will expire soon is displayed. This trigger will display the ACK ALERTS (3) button. A system notification (4) will also inform you of the upcoming pod expiration

    Acknowledge_Alerts_1 Acknowledge_Alerts_2

  2. Go to the Omnipod (POD) tab and press the ACK ALERTS (2) button (acknowledge alerts). The RileyLink sends the command to the pod to deactivate the pod expiration warning beeps and updates the Pod status (1) field with ACKNOWLEDGE ALERTS.


  3. Upon successful deactivation of the alerts, 2 beeps will be issued by the active pod and a confirmation dialog will display the message Activate alerts have been acknowledged. Click the OK button to confirm and dismiss the dialog.


    If the RileyLink is out of range of the pod while the acknowledge alerts command is being processed a warning message will display 2 options. Mute (1) will silence this current warning. OK (2) will confirm this warning and allow the user to try to acknowledge alerts again.


  4. Go to the Omnipod (POD) tab, under the Active Pod alerts field, the warning message is no longer displayed and the active pod will no longer issue pod expiration warning beeps.

View Pod History

This section shows you how to review your active pod history and filter by different action categories. The pod history tool allows you to view the actions and results committed to your currently active pod during its three day (72 - 80 hours) life.

This feature is useful for verifying boluses, TBRs, basal changes that were given but you may be unsure if they completed. The remaining categories are useful in general for troubleshooting issues and determining the order of events that occurred leading up to a failure.

NOTE: Uncertain commands will appear in the pod history, however due to their nature you cannot ensure their accuracy.

  1. Go to the Omnipod (POD) tab and press the POD MGMT (1) button to access the Pod management menu and then press the Pod history (2) button to access the pod history screen.

    Pod_History_1 Pod_History_2

  2. On the Pod history screen, the default category of All (1) is displayed showing the Date and Time (2) of all pod Actions (3) and Results (4) in reverse chronological order. Use your phone’s back button 2 times to return to the Omnipod (POD) tab in the main AAPS interface.

    Pod_History_3 Pod_History_4

Omnipod (POD) Tab

Below is an explanation of the layout and meaning of the icons and status fields on the Omnipod (POD) tab in the main AAPS interface.

NOTE: If any message in the Omnipod (POD) tab status fields report (uncertain) then you will need to press the Refresh button to clear it and refresh the pod status.



  • RileyLink Status: Displays the current connection status of the RileyLink

  • RileyLink Unreachable - pod communication device is either not within Bluetooth range of the phone, powered off or has a failure preventing Bluetooth communication.

  • RileyLink Ready - pod communication device is powered on and actively initializing the Bluetooth connection

  • Connected - pod communication device is powered on, connected and actively able to communicate via Bluetooth.

  • Pod address: Displays the current address in which the active pod is referenced

  • LOT: Displays the LOT number of the active pod

  • TID: Displays the serial number of the pod.

  • Firmware Version: Displays the firmware version of the active pod.

  • Time on Pod: Displays the current time on the active pod.

  • Pod expires: Displays the date and time when the active pod will expire.

  • Pod status: Displays the status of the active pod.

  • Last connection: Displays the last time communication with the active pod was achieved.

  • Moments ago - less than 20 seconds ago.

  • Less than a minute ago - more than 20 seconds but less than 60 seconds ago.

  • 1 minute ago - more than 60 seconds but less than 120 seconds (2 min)

  • XX minutes ago - more than 2 minutes ago as defined by the value of XX

  • Last bolus: Displays the dosage of the last bolus sent to the active pod and how long ago it was issued in parenthesis.

  • Base Basal rate: Displays the basal rate programmed for the current time from the basal rate profile.

  • Temp basal rate: Displays the currently running Temporary Basal Rate in the following format

  • Units / hour @ time TBR was issued (minutes run / total minutes TBR will be run)

  • Example: 0.00U/h @18:25 ( 90/120 minutes)

  • Reservoir: Displays over 50+U left when more than 50 units are left in the reservoir. Below this value the exact units are displayed in yellow text.

  • Total delivered: Displays the total number of units of insulin delivered from the reservoir. Note this is an approximation as priming and filling the pod is not an exact process.

  • Errors: Displays the last error encountered. Review the Pod history, RileyLink history and log files for past errors and more detailed information.

  • Active pod alerts: Reserved for currently running alerts on the active pod. Normally used when pod expiration is past 72 hours and native pod beep alerts are running.




    Sends a refresh command to the active pod to update communication

    Use to refresh the pod status and dismiss status fields that contain the text (uncertain).

    See the Troubleshooting section below for additional information.



    Navigates to the Pod management menu



    When pressed this will disable the pod expiration beeps and notifications.

    Button is displayed only when pod time is past expiration warning time Upon successful dismissal, this icon will no longer appear.



    When pressed this will update the time on the pod with the current time on your phone.



    Suspends the active pod



    Resumes the currently suspended, active pod

Pod Management Menu

Below is an explanation of the layout and meaning of the icons on the Pod Management menu accessed from the Omnipod (POD) tab.


  • Activate Pod


    Primes and activates a new pod

  • Deactivate Pod


    Deactivates the currently active pod.

    A partially paired pod ignores this command.

    Use this command to deactivate a screaming pod (error 49).

    If the button is disabled (greyed out) use the Discard Pod button.

  • Play test beep


    Plays a single test beep on the pod when pressed.

  • Discard pod


    Deactivates and discards the pod state of an unresponsive pod when pressed.

    Button is only displayed when very specific cases are met as proper deactivation is no longer possible:

    • A pod is not fully paired and thus ignores deactivate commands.

    • A pod is stuck during the pairing process between steps

    • A pod simply does not pair at all.

  • Pod history


    Displays the active pod activity history

  • RileyLink stats:


    Navigates to the RileyLink Statistics screen displaying current settings and RileyLink Connection history

    • Settings - displays RileyLink and active pod settings information

    • History - displays RileyLink and Pod communication history

  • Reset RileyLink Config


    When pressed this button resets the currently connected pod communication device configuration.

    • When communication is started, specific data is sent to and set in the RileyLink > - Memory Registers are set > - Communication Protocols are set > - Tuned Radio Frequency is set

    • See additional notes at the end of this table

  • Read pulse log:


    Sends the active pod pulse log to the clipboard

Omnipod Settings

The Omnipod driver settings are configurable from the top-left hand corner hamburger menu under Config BuilderPumpOmnipodSettings Gear (2) by selecting the radio button (1) titled Omnipod. Selecting the checkbox (3) next to the Settings Gear (2) will allow the Omnipod menu to be displayed as a tab in the AAPS interface titled OMNIPOD or POD. This is referred to in this documentation as the Omnipod (POD) tab.


NOTE: A faster way to access the Omnipod settings is by accessing the 3 dot menu (1) in the upper right hand corner of the Omnipod (POD) tab and selecting Omnipod preferences (2) from the dropdown menu.


The settings groups are listed below; you can enable or disable via a toggle switch for most entries described below:


NOTE: An asterisk (*) denotes the default for a setting is enabled.

Confirmation beeps

Provides confirmation beeps from the pod for bolus, basal, SMB, and TBR delivery and changes.

  • *Bolus beeps enabled: Enable or disable confirmation beeps when a bolus is delivered.

  • *Basal beeps enabled: Enable or disable confirmation beeps when a new basal rate is set, active basal rate is canceled or current basal rate is changed.

  • *SMB beeps enabled: Enable or disable confirmation beeps when a SMB is delivered.

  • TBR beeps enabled: Enable or disable confirmation beeps when a TBR is set or canceled.


Provides AAPS alerts and Nightscout announcements for pod expiration, shutdown, low reservoir based on the defined threshold units.

Note an AAPS notification will ALWAYS be issued for any alert after the initial communication with the pod since the alert was triggered. Dismissing the notification will NOT dismiss the alert UNLESS automatically acknowledge Pod alerts is enabled. To MANUALLY dismiss the alert you must visit the Omnipod (POD) tab and press the ACK ALERTS button.

  • *Expiration reminder enabled: Enable or disable the pod expiration reminder set to trigger when the defined number of hours before shutdown is reached.

  • Hours before shutdown: Defines the number hours before the active pod shutdown occurs, which will then trigger the expiration reminder alert.

  • *Low reservoir alert enabled: Enable or disable an alert when the pod’s remaining units low reservoir limit is reached as defined in the Number of units field.

  • Number of units: The number of units at which to trigger the pod low reservoir alert.

  • Automatically acknowledge Pod alerts: When enabled a notification will still be issued however immediately after the first pod communication contact since the alert was issued it will now be automatically acknowledged and the alert will be dismissed.


Provides AAPS notifications and audible phone alerts when it is uncertain if TBR, SMB, or bolus events were successful.

NOTE: These are notifications only, no audible beep alerts are made.

  • Sound for uncertain TBR notifications enabled: Enable or disable this setting to trigger an audible alert and visual notification when AAPs is uncertain if a TBR was successfully set.

  • *Sound for uncertain SMB notifications enabled: Enable or disable this setting to trigger an audible alert and visual notification when AAPS is uncertain if an SMB was successfully delivered.

  • *Sound for uncertain bolus notifications enabled: Enable or disable this setting to trigger an audible alert and visual notification when AAPS is uncertain if a bolus was successfully delivered.


Provides advanced settings to assist debugging.

  • Show Suspend Delivery button in Omnipod tab: Hide or display the suspend delivery button in the Omnipod (POD) tab.

  • Show Pulse log button in Pod Management menu: Hide or display the pulse log button in the Pod Management menu.

  • Show RileyLink Stats button in Pod Management menu: Hide or display the RileyLink Stats button in the Pod Management menu.

  • *DST/Time zone detect on enabled: allows for time zone changes to be automatically detected if the phone is used in an area where DST is observed.

Actions (ACT) Tab

This tab is well documented in the main AAPS documentation but there are a few items on this tab that are specific to how the Omnipod pod differs from tube based pumps, especially after the processes of applying a new pod.

  1. Go to the Actions (ACT) tab in the main AAPS interface.

  2. Under the Careportal (1) section the following 3 fields will have their age reset to 0 days and 0 hours after each pod change: Insulin and Cannula. This is done because of how the Omnipod pump is built and operates. The pump battery and insulin reservoir are self contained inside of each pod. Since the pod inserts the cannula directly into the skin at the site of the pod application, a traditional tube is not used in Omnipod pumps. Therefore after a pod change the age of each of these values will automatically reset to zero. Pump battery age is not reported as the battery in the pod will always be more than the life of the pod (maximum 80 hours).



Insulin Level

Reporting of the amount of insulin in the Omnipod Eros Pod is not exact. This is because it is not known exactly how much insulin was put in the pod, only that when the 2 beeps are triggered while filling the pod that over 85 units have been injected. A Pod can hold a maximum of 200 units. Priming can also introduce variance as it is not and exact process. With both of these factors, the Omnipod driver has been written to give the best approximation of insulin remaining in the reservoir.

  • Above 50 Units - Reports a value of 50+U when more than 50 units are currently in the reservoir.

  • Below 50 Units - Reports an approximate calculated value of insulin remaining in the reservoir.

  • SMS - Returns value or 50+U for SMS responses

  • Nightscout - Uploads value of 50 when over 50 units to Nightscout (version 14.07 and older). Newer versions will report a value of 50+ when over 50 units.

Battery Level

Battery level reporting is a setting that can be enabled to return the current battery level of pod communication devices, such as the OrangeLink, EmaLink or DiaLink. The RileyLink hardware is not capable of reporting its battery level. The battery level is reported after each communication with the pod, so when charging a linear increase may not be observed. A manual refresh will update the current battery level. When a supported Pod communication device is disconnected a value of 0% will be reported.

  • RileyLink hardware is NOT capable of reporting battery level

  • „Show battery level reported by OrangeLink/EmaLink/DiaLink“ Setting MUST be enabled in the Omnipod settings to report battery level values

  • Battery level reporting ONLY works for OrangeLink, EmaLink and DiaLink Devices

  • Battery Level reporting MAY work for other devices (excluding RileyLink)

  • SMS - Returns current battery level as a response when an actual level exists, a value of n/a will not be returned

  • Nightscout - Battery level is reported when an actual level exists, a value of n/a will not be reported

Trikčių šalinimas

Pod Failures

Pods fail occasionally due to a variety of issues, including hardware issues with the Pod itself. It is best practice not to call these into Insulet, since AAPS is not an approved use case. A list of fault codes can be found here to help determine the cause.

Preventing error 49 pod failures

This failure is related to an incorrect pod state for a command or an error during an insulin delivery command. We recommend users to switch to the Nightscout client to upload only (Disable sync) under the Config BuilderGeneralNSClientcog wheelAdvanced Settings to prevent possible failures.

Pump Unreachable Alerts

It is recommended that pump unreachable alerts be configured to 120 minutes by going to the top right-hand side three-dot menu, selecting PreferencesLocal AlertsPump unreachable threshold [min] and setting this to 120.

Import Settings from previous AAPS

Please note that importing settings has the possibility to import an outdated Pod status. As a result, you may lose an active Pod. It is therefore strongly recommended that you do not import settings while on an active Pod session.

  1. Deactivate your pod session. Verify that you do not have an active pod session.

  2. Export your settings and store a copy in a safe place.

  3. Uninstall the previous version of AAPS and restart your phone.

  4. Install the new version of AAPS and verify that you do not have an active pod session.

  5. Import your settings and activate your new pod.

Omnipod driver alerts

please note that the Omnipod driver presents a variety of unique alerts on the Overview tab, most of them are informational and can be dismissed while some provide the user with an action to take to resolve the cause of the triggered alert. A summary of the main alerts that you may encounter is listed below:

No active Pod

No active Pod session detected. This alert can temporarily be dismissed by pressing SNOOZE but it will keep triggering as long as a new pod has not been activated. Once activated this alert is automatically silenced.

Pod suspended

Informational alert that Pod has been suspended.

Setting basal profile failed. Delivery might be suspended! Please manually refresh the Pod status from the Omnipod tab and resume delivery if needed..

Informational alert that the Pod basal profile setting has failed, and you will need to hit Refresh on the Omnipod tab.

Unable to verify whether SMB bolus succeeded. If you are sure that the Bolus didn’t succeed, you should manually delete the SMB entry from Treatments.

Alert that the SMB bolus success could not be verified, you will need to verify the Last bolus field on the Omnipod tab to see if SMB bolus succeeded and if not remove the entry from the Treatments tab.

Uncertain if „task bolus/TBR/SMB“ completed, please manually verify if it was successful.

Due to the way that the RileyLink and Omnipod communicate, situations can occur where it is uncertain if a command was successfully processed. The need to inform the user of this uncertainty was necessary.

Below are a few examples of when an uncertain notification can occur.

  • Boluses - Uncertain boluses cannot be automatically verified. The notification will remain until the next bolus but a manual pod refresh will clear the message. By default alerts beeps are enabled for this notification type as the user will manually need to verify them.

  • TBRs, Pod Statuses, Profile Switches, Time Changes - a manual pod refresh will clear the message. By default alert beeps are disabled for this notification type.

  • Pod Time Deviation - When the time on the pod and the time your phone deviates too much then it is difficult for AAPS loop to function and make accurate predictions and dosage recommendations. If the time deviation between the pod and the phone is more than 5 minutes then AAPS will report the pod is in a Suspended state under Pod status with a HANDLE TIME CHANGE message. An additional Set Time icon will appear at the bottom of the Omnipod (POD) tab. Clicking Set Time will synchronize the time on the pod with the time on the phone and then you can click the RESUME DELIVERY button to continue normal pod operations.

Best Practices

Where to get help for Omnipod driver

All of the development work for the Omnipod driver is done by the community on a volunteer basis; we ask that you please be considerate and use the following guidelines when requesting assistance:

  • Level 0: Read the relevant section of this documentation to ensure you understand how the functionality with which you are experiencing difficulty is supposed to work.

  • Level 1: If you are still encountering problems that you are not able to resolve by using this document, then please go to the #androidaps channel on Discord by using this invite link.

  • Level 2: Search existing issues to see if your issue has already been reported; if not, please create a new issue and attach your log files.

  • Be patient - most of the members of our community consist of good-natured volunteers, and solving issues often requires time and patience from both users and developers.