These instructions are for configuring the Omnipod DASH generation pump (NOT Omnipod Eros), available in AAPS from version 3.0.
These are the specifications of the Omnipod DASH ('DASH') and what differentiates it from the Omnipod EROS ('EROS'):
- The DASH pods are identified by a blue needle cap (EROS has a clear needle cap). The pods are otherwise identical in terms of physical dimensions.
- DASH does not require a BLE link/bridge device (NO RileyLink, OrangeLink, or EmaLink needed).
- The DASH's Bluetooth connection is used only when sending a command (e.g a Bolus), and disconnects right after issuing the command.
- No more "no connection to link device / pod" errors with DASH.
- AAPS will wait for pod's accessibility to send commands.
- On pod activation, AAPS will find and connect to a new DASH pod.
- Expected range from phone: 5-10 meters (YMMV).
(omnipod-dash-constraints)=
- Android 16 requires AAPS version 3.3.2.1 or later.
- General advice is to run AAPS on Android 14 or 16. Android 15 has many reported issues from the community. However, if you do run on Android 15 you will likely need to enable Bluetooth Bonding to successfully activate and use Pods, see General Troubleshooting for more info on the Bonding settings.
- Too frequent basal updates may cause basal insulin delivery problems with Omnipod Dash. When using SMB, limit the interval to 5 minutes minimum to avoid this issue.
- Dash only supports basal rate in 0.05 U/h steps. If you try to set basal with 0.01 steps in your AAPS profile, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. If you view POD MGMT/Pod History it will display that 0.05 basal was set. This also means the lowest basal rate allowed by the DASH in AAPS is 0.05U/h.
- The activation status of a Pod is stored in the settings file, if you export a settings file with an active pod. Then change to a new pod, then restore the settings from your previous export you will have now restored the old pod activation and removed the new pod activation. This is why we recommend to export settings after each pod activation to allow a restore of that pods activation state if something happens to your rig.
- When setting a new basal profile, DASH will suspend delivery before setting the new basal Profile. If there is a communication interruption or error, the basal profile won't automatically re-start. See section Resuming Insulin Delivery for details.
- If alerts are configured, and the pod is about to expire, the pod will keep beeping until alerts are silenced, see Silencing Pod Alerts for details.
- There are a number of known issues with Bluetooth which can cause pod activation problems. See Bluetooth Troubleshooting for the known issue and solutions to these problems.
(hardware-software-requirements)=
(omnipod-dash-hardware-software-requirements)=
- Omnipod DASH is identified by the blue needle cap.
- A Compatible Android phone with a Bluetooth Low Energy (BLE) (see Phones for more info), additionally the following information will help guide you on other key considerations around successfully activating and using the DASH on a compatible phone:
- The AAPS Omnipod Dash driver connects with the DASH Pod using Bluetooth.
AAPS will automatically establish a new Bluetooth connection to the Pod every time it needs to send a command (e.g a Bolus), after sending the command the Bluetooth connection is immediately disconnected.- POZNÁMKA:
- The Bluetooth connection can be interrupted/disturbed by other Bluetooth devices linked to the phone that is running AAPS, like earbuds etc... Devices like this can cause connection errors or pod activation issues on some models of phones. It's a good idea to review the tested hardware setups list for known working configurations before committing to a new rig built around Omnipod DASH.
- There are a number of known issues with Bluetooth which can cause pod activation problems (See Troubleshooting for advice on other Bluetooth issues) specifically the Bluetooth related issues section.
- POZNÁMKA:
- For Android 15 or below: You MUST use Version 3.0 or newer of AAPS using the Build APK instructions, however it's advisable to run the latest released version.
- For Android 16: you MUST use Version 3.3.2.1 or newer of AAPS using the Build APK instructions, due to Android 16 changing how its Bluetooth works. Any version earlier than 3.3.2.1 will likely cause pod failures and/or activation issues.
- The AAPS Omnipod Dash driver connects with the DASH Pod using Bluetooth.
- A supported Continuous Glucose Monitor (CGM)
The instructions below explain how to activate a new pod session using AAPS. You should wait for your current Pod to be close expiry, as you will need to activate a new Pod with AAPS. Once a pod is de-activated it cannot be reused/re-activated, the de-activation is final.
Ensure you have read and understand this whole guide, have read and understand the Before You Begin section, as well as Omnipod and AAPS Constraints and Issues to avoid running into a known problem.
SAFETY FIRST - You SHOULD NOT try to connect AAPS to a pod for the first time without having access to all of the following:
- Extra pods (3 or more spare)
- Spare Insulin and MDI equipment
- A working Omnipod PDM (In case AAPS fails)
- Supported Phones are a must! (See Hardware/Software Requirements)
- Correct version of AAPS built and installed
- Before using AAPS you or your care giver would have had to manage the Pod using the Omnipod PDM (or in some regions a Phone app) to send commands to your DASH (e.g a Bolus).
- The DASH can only facilitate a single Bluetooth device (e.g PDM or Phone) connection to manage and send commands.
- The device that successfully activates the pod is the only device allowed to communicate with that Pod from that point forward. This means that once you activate a DASH with your Android phone using AAPS, you will no longer be able to use your PDM with that pod! For the time that Pod is active the AAPS Dash driver running on your Android phone is now the new PDM for your pod.
- DO NOT Throw away your PDM! It is recommended to keep it around as a backup and for emergencies, for instance when your phone gets lost or AAPS is not working correctly.
Default basal rates are programmed on the pod on activation as defined in the current active Profile.
As long as AAPS is operational it will send basal rate adjustment commands that run for a maximum of 120 minutes.
When for some reason the pod does not receive any new commands (for instance because communication was lost due to Pod ➜ phone distance) the pod will automatically fall back to default basal rates as defined in your Profile.
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 basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact basil Profile in AAPS.
You will need to change this 1.1 unit basal rate to a time range of either 9:00-11:00 or 10:00-12:00. Even though the DASH hardware itself supports the 30 minute basal rate Profile increments, AAPS does NOT support this feature.
While the DASH does support a zero basal rate, AAPS uses multiples of the user's Profile basal rate to determine automated treatment; it cannot function with a zero basal rate.
Instead a temporary zero basal rate can be achieved through the "Disconnect pump" function, or through a combination of Disable Loop/Temp Basal Rate or Suspend Loop/Temp Basal Rate.
NOTE: The lowest basal rate allowed by the DASH in AAPS is 0.05U/h.
There are two available options to configure Omnipod in AAPS:
When installing AAPS for the first time, the Setup Wizard will guide new users through key features and installation requirements for AAPS.
Select “DASH” when you reach Pump selection.
When in doubt you can also select “Virtual Pump” and select “DASH” later, after setting up AAPS (See Option 2).
(omnipod-dash-option-2-config-builder)=
On an existing installation you can select the DASH pump from the Config builder:
On the top-left hand corner hamburger menu select Config Builder (1) ➜ Pump ➜ Dash ➜ Settings Gear (3) by selecting the radio button (2) titled Dash.
Selecting the checkbox (4) next to the Settings Gear (3) will allow the DASH menu to be displayed as a tab in the AAPS interface titled DASH. Checking this box will facilitate your access to the DASH commands when using AAPS.
NOTE: A faster way to access the Dash settings can be found below in the DASH settings section of this document.
To verify that you have selected the DASH in AAPS, if you have checked the box (4), swipe to the left from the Overview tab, where you will now see a DASH tab on AAPS. If this box is left unchecked, you’ll find the DASH tab in the hamburger menu upper left.
Swipe left to the DASH tab where you will be able to manage all pod functions (some of these functions are not enabled or visible without an active pod session):
'Refresh' pod connectivity and status, be able to silence pod alarms when the pod beeps
'Pod Management' (Activate, Deactivate, Play test beep, and Pod history)
(omnipod-dash-activate-pod)=
-
Navigate to the DASH tab and click on the POD MGMT (1) button, and then click on Activate Pod (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.
NOTE: When calculating the total amount of insulin you need for 3 days, please take into account that priming the pod will use about 3-10 units.
Ensure that the new pod and the phone running AAPS are within close proximity of each other and click the Next button.
NOTE: if the error message below pops up 'Could not find an available pod for activation' (this can happen), do not panic. Click on the Retry button. In most situations activation will continue successfully.
-
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).
A green checkmark will be shown upon successful priming, and the Next button will become enabled. Click on the Next button to complete the pod priming initialization and display the Attach Pod screen.
-
Next, prepare the infusion site ready to receive the new pod. Wash hands to avoid any risk of infection. Clean the infusion site by either using soap and water or an alcohol wipe to disinfect and let the skin air dry completely before proceeding.
If you get skin irritation from the adhesive consider using a Barrier Wipe or Barrier Spray.Remove the pod's blue plastic needle cap. If you see something that sticks out of the pod or it looks unusual, STOP the process and start with a new pod. If everything looks OK, proceed to take off the white paper backing from the adhesive and stick the pod to the selected site on your body.
When finished, click on the Next button.
-
The Attach Pod dialog box will now appear. click on the OK button ONLY if you are ready to deploy the cannula!
-
After pressing OK, it may take some time before the DASH responds and inserts the cannula (1-2 minutes maximum). Be patient!
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.
-
A green checkmark is shown on the screen, and the Next button becomes available to select upon successful cannula insertion.
Click on the Next button.
-
The Pod activated screen is displayed.
Click on the green Finished button.
Congratulations! You have now started a new pod session.
-
The Pod management menu screen should now display 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 DASH 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.
NOTE: For more details on the information displayed go to the DASH Tab section of this document.
NOTE: It is good practice to export settings AFTER activating the pod. Settings should be exported after each pod change and once a month, ensure you copy the exported settings file to a cloud storage location (e.g. Google Drive) or somewhere off your phone in case you loose your phone (see Export settings).
(omnipod-dash-deactivate-pod)=
Under normal circumstances, the expected lifetime of a pod is three days (72 hours) and an additional 8 hours after the pod expiration warning for a total of 80 hours of total pod usage.
To deactivate a pod (either from expiration or from a pod failure):
-
Go to the DASH tab, click on the POD MGMT (1) button, on the Pod Management screen click on the Deactivate Pod (2) button.
-
On the Deactivate Pod screen, click on the Next button to begin the process of deactivating the pod.
You will receive a confirmation beep from the pod that deactivation was successful.
-
A green checkmark will be displayed 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.
-
Click on the green button to return to the Pod Management screen.
-
You are now on the Pod Management menu; press the back button on your phone to return to the DASH tab.
Verify that the Pod status: field displays a No active Pod message.
(omnipod-dash-resuming-insulin-delivery)=
NOTE: During Profile Switches, like when using the PDM, AAPS must suspend delivery on the Pod before setting the new basal Profile. If communication fails between the suspend and resume commands, then delivery can stay suspended, Read Delivery suspended in the troubleshooting section for more details.
When insulin delivery is suspended you will need to issue a 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.
-
Go to the DASH 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.
-
When the Resume delivery command is successful, a confirmation dialog will display the message Insulin delivery has been resumed. Click OK to confirm and proceed.
-
The DASH tab will update the Pod status (1) field to display RUNNING, and the Resume Delivery button will no longer be displayed
(omnipod-dash-silencing-pod-alerts)=
The process below will show you how to acknowledge and dismiss pod beeps 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 Dash alerts setting. The maximum life of a pod is 80 hours (3 days 8 hours), however Insulet recommends not exceeding the 72 hours (3 days) limit.
NOTE: The SILENCE ALERTS (3) button is only available on the DASH tab when the pod expiration or low reservoir alert has been triggered. If the SILENCE ALERTS button is not visible and you hear beep sounds from the pod, try to 'Refresh pod status'.
-
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 be required soon.
You can verify this on the DASH 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 the status message Pod will expire soon is displayed. This also will trigger displaying the SILENCE ALERTS (3) button.
-
Go to the DASH tab and press the SILENCE ALERTS (2) button. AAPS sends the command to the pod to deactivate the pod expiration warning beeps and updates the Pod status (1) field with ACKNOWLEDGE ALERTS.
-
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 Silenced. Click the OK button to confirm and dismiss the dialog.
-
Go to the DASH 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.
(omnipod-dash-view-pod-history)=
This section explains 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 days (72 - 80 hours) life.
This feature is helpful in verifying boluses, TBRs and basal commands that were sent to the pod. The remaining categories are useful for troubleshooting issues and determining the order of events that occurred leading up to a failure.
NOTE: Only the last command can be uncertain. New commands will not be sent until the last 'uncertain' command becomes 'confirmed' or 'denied'. The way to 'fix' uncertain commands is to 'refresh pod status'.
-
Go to the DASH 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.
-
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 DASH tab in the main AAPS interface.
(omnipod-dash-tab)=
Below is an explanation of the layout and meaning of the icons and status fields on the DASH tab in the main AAPS interface.
NOTE: If any message in the DASH tab status fields report (uncertain), then you will need to press the Refresh button to clear it and refresh the pod status.
-
Bluetooth Address: Displays the current bluetooth address of the connected Pod.
-
Bluetooth Status: Displays the current connection status.
-
Sequence Number: Displays the sequence number of the active POD.
-
Firmware Version: Displays the firmware version for the active connection.
-
Time on Pod: Displays the current time on the Pod.
-
Pod status: Displays the Pod status.
-
Last connection: Displays time of last communication with the Pod.
-
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 amount 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 per hour} @{TBR start time} ({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 50 U, the exact units are displayed.
-
Total delivered: Displays the total number of units of insulin delivered from the reservoir. This includes insulin used for activating and priming.
-
Errors: Displays the last error encountered. Review the Pod history and log files for past errors and more detailed information.
-
Active pod alerts: Reserved for currently running alerts on the active pod.
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 alerts beeps and notifications (expiry, low reservoir..).
- Tlačítko je zobrazeno pouze v případě, že na PODu vypršel čas pro uzpozornění.
- Upon successful dismissal, this icon will no longer appear.
Resumes the currently suspended insulin delivery in the active pod.
Below is describes the purpose of each icon on the Pod Management menu, accessed by pressing POD MGMT (1) button from the DASH tab.
The table below describes each button and it's function:
| Button | Function |
|---|---|
| 1 | Access the Pod Mgmt settings |
| 2 | Activate Pod: Primes and activates a new pod. |
| 3 | Deactivate Pod: Deactivates the currently active pod. |
| 4 | Play Test Beep : Plays a single test beep on the pod when pressed. |
| 5 | Pod history : Displays the active pod activity history. |
(omnipod-dash-settings)=
The Dash driver settings are configurable from the top-left hand corner hamburger menu under Config Builder (1) ➜ Pump Dash ➜ Settings Gear (3) by selecting the radio button (2) titled Dash. Selecting the checkbox (4) next to the Settings Gear (3) will allow the Dash menu to be displayed as a tab in the AAPS interface titled DASH.
NOTE: A faster way to access the Dash settings is by accessing the 3 dot menu (1) in the upper right hand corner of the DASH tab and selecting Dash 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 setting is enabled.
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 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 DASH tab and press the Silence 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.
The Notification section allows the user to select their preferred notifications and audible phone alerts when AAPS is uncertain about the status of TBR, SMB, or bolus, and when delivery suspended 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.
Sound when delivery suspended notifications enabled: Enable or disable this setting to trigger an audible alert and visual notification when suspend delivery was successfully delivered.
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 DASH differs from tube based pumps, especially after the processes of applying a new pod.
-
Go to the Actions (ACT) tab in the main AAPS interface.
-
Under the Careportal (1) section the Insulin and Cannula fields will have their age reset to 0 days and 0 hours after each pod change. This is done because of how the Omnipod pump is built and operates. 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). The pump battery and insulin reservoir are self contained inside of each pod.
Insulin Level
Insulin level displayed is the amount reported by DASH. However, the pod only reports the actual insulin reservoir level when it is below 50 units. Until then “Above 50 units” will be displayed. The amount reported is not exact: when the pod reports ‘empty’ in most cases the reservoir will still have some additional units of insulin left.
The DASH overview tab will display as described the below:
- Above 50 Units - The pod reports more than 50 units currently in the reservoir.
- Below 50 Units - The amount of insulin remaining in the reservoir as reported by the Pod.
Additional note:
- 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.
(omnipod-dash-troubleshooting)=
(omnipod-dash-delivery-suspended)=
This section covers common known issues and solutions for Omnipod DASH use with AAPS. There is also General Troubleshooting section in the documentation that should be reviewed as it covers relevant topics for some Pod issues too.
(omnipod-dash-bluetooth-related-issues)=
For known issues with Bluetooth connections, dropouts of pump/pods, or activation and connection issues Bluetooth Troubleshooting
- There is no suspend button anymore. If you want to "suspend" the pod, you can set a zero TBR for x minutes.
- During Profile Switches, DASH must suspend delivery before setting the new basal Profile. If communication fails between the two commands, then delivery can stay suspended. When this happens:
- There will be no insulin delivery, that includes Basal, SMB, Manual bolusing etc.
- There might be notification that one of the commands is unconfirmed: this depends on when the failure happened.
- AAPS will try to set the new basal profile every 15 minutes.
- AAPS will show a notification informing that the delivery is suspended every 15 minutes, if the delivery is still suspended (resume delivery failed).
- The Resume delivery button will be active if the user chooses to resume delivery manually.
- If AAPS fails to resume delivery on its own (this happens if the pod is unreachable, sound is muted, etc), the pod will start beeping 4 times every minute for 3 minutes, then repeated every 15 minutes if delivery is still suspended for more than 20 minutes.
- For unconfirmed commands, "refresh pod status" should confirm/deny them.
NOTE: When you hear beeps from the pod, do not assume that delivery will continue without checking the phone, delivery might stay suspended, so you need to check !
- Pods fail occasionally due to a variety of issues, including hardware issues with the Pod itself.
- It is best practice not to raise support / replacement cases with Insulet, since AAPS is not an approved method of using the Pods.
- A list of fault codes can be found here to help determine the cause.
This failure is related to an incorrect pod state for a command or an error during an insulin delivery command. This is when the driver and Pod disagree on the actual state. The Pod (out of a built-in safety measure) then reacts with an unrecoverable error code 49 (0x31) ending up with what is know as a “screamer”: the long irritating beep that can only be stopped by punching a hole at the appropriate location at the back of the Pod. The exact origin of a “49 pod failure” often is hard to trace. In situations that are suspected for this failure to occur (for instance on application crashes, running a development version or re-installation).
When no communication can be established with the pod for a pre-configured time a “Pump unreachable” alert will be raised. Pump unreachable alerts can be configured by going to the top right-hand side three-dot menu, selecting Preferences ➜ Local Alerts ➜ Pump unreachable threshold [min]. Recommended value is alerting after 120 minutes.
Exporting AAPS settings enables you to restore all your settings, and maybe more importantly, all your Objectives. You may need to restore settings to the “last known working situation” or after uninstalling/reinstalling AAPS or in case of phone loss, reinstalling on the new phone.
NOTE: The active pod information is included in the exported settings. If you import an "old" exported file, your actual pod will "die". There is no other alternative. In some cases (like a programmed phone change), you may need to use the exported file to restore AAPS' settings while keeping the current active Pod. In this case it is important to only use the recently exported settings file containing the pod currently active.
It is good practice to do an export immediately after activating a pod. This way you will always be able to restore the current active pod in case of a problem. For instance when moving to another backup phone.
Regularly (after each export preferably) copy your exported settings to a safe place (a cloud drive e.g. Google Drive) that is accessible by any phone when needed. This allows you to restore to a phone from anywhere in case of a phone loss or factory reset of your phone while you are not at home.
WARNING: Please note that importing settings will possibly import an outdated Pod status (depending when you made the last export/backup).
As a result, there is a risk of losing the active Pod! (see Exporting Settings).
- Only try an import when no other options are available.
- When importing settings with an active Pod, make sure the export was done with the currently active pod.
Importing while on an active Pod: (you risk losing the Pod!)
- Make sure you are importing settings that were recently exported with the currently active Pod!
- Import your settings.
- Check all preferences.
Importing (no active Pod session)
- Importing any recent export should work (see above)
- Import your settings.
- Check all preferences.
- You may need to Deactivate the "non existing" pod if the imported settings included any active pod data.
When importing settings containing data for a Pod that is no longer active, AAPS will try to connect with it, which will obviously fail. You can not activate a new Pod in this situation.
To remove the old pod session:
- “try” to de-activate the Pod. The de-activation will likely fail.
- Select “Retry”.
- After the second or third retry you will get the option to remove the pod.
- Once the old pod is removed you will be able to activate a new pod.
Generic error: java.lan.illegalStateException: Trying to set a Bluetooth Address to ***, but it is already set to ***.
If you receive this error when attempting to Initialize a new pod AAPS fails as it still has settings for an old pod stored in configuration.
This can happen if you restore from a backup, or a pod deactivation fails.
To resolve keep clicking on RETRY until a Discard option is shown, then discard. This procedure should work for De-Activating a pod too.
You should now be able to Activate a new pod.
When uninstalling AAPS you will lose all your settings, objectives and the current Pod session. To restore them make sure you have a recent exported settings file available!
When on an active Pod, make sure that you have an export for the current pod session or you will lose the currently active pod when importing older settings.
- Export your settings and store a copy in a safe place (e.g Google Drive).
- Uninstall AAPS and restart your phone.
- Install the new version of AAPS.
- Import your settings.
- Verify all preferences (optionally import settings again).
- Activate a new pod.
- When done: Export current settings.
In most cases there is no need to uninstall. You can do an “in-place” install by starting the installation for the new version. This is also possible when on an active Pod session.
- Export your settings.
- Install the new AAPS version.
- Verify the installation was successful
- RESUME the Pod or activate a new pod.
- When done: Export current settings.
The Omnipod Dash 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 requiring their input to resolve the cause of the triggered alert.
A summary of the main alerts that you may encounter is listed below:
- 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 command success could not be verified, you will need to verify the Last bolus field on the DASH 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.
(omnipod-dash-where-to-get-help-for-dash)=
All of the development work for the DASH is done by the community on a volunteer basis; please keep this in mind and use the following guidelines before 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 #AAPS channel on Discord by using this invite link. There are also numerous Facebook and other groups you can ask in too (see Getting Help)
- Level 2: Search existing issues to see if your issue has already been reported at Issues if it exists, please confirm/comment/add information on your problem. 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.
When requesting help come prepared with the following information to help those in the community with your specific questions and problems:
- Android phone make and model
- Android OS version (e.g 15 or 16)
- Did you recently upgrade your Android OS version?
- The version of AAPS you are running
- Plain english description of the problem you are facing considering some of the following things
- Was it working before now?
- When did it work or not work?
- Did you make any changes to configuration or profile settings?
- Did you pair a new bluetooth device?
- Did you upgrade or install a new app?
- How long was it working before it stopped working?