Full review and update of Omnipod DASH wiki page with updates and new Bluetooth troubleshooting#2478
Merged
Merged
Conversation
added 23 commits
October 17, 2025 13:29
psonnera
reviewed
Oct 22, 2025
| - 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: 5-10 meters (YMMV). |
Collaborator
There was a problem hiding this comment.
Refrain from changing formatting only, unless absolutely necessary, as this will send all strings to translation again.
Contributor
Author
There was a problem hiding this comment.
No worries, my thought here was to ensure that the style of everything is consistent in the doc. For future I'll leave it as it is in other docs. How do you want me to address this here though, I make a lot of re-formatting changes would be a bunch of effort to undo all that in this instance.
psonnera
reviewed
Oct 22, 2025
| - The following Apps are known to cause problems for OmniPod DASH and should be avoided if possible (See [Troubleshooting](#Troubleshooting) for advice on other Bluetooth issues): | ||
| - MyBMW app | ||
| - Amazon Alexa | ||
| - For **Android 15** or below: You **MUST** use **Version 3.0 or newer of AAPS** using the [**Build APK**](../SettingUpAaps/BuildingAaps.md) instructions, however it's advisable to run the latest released version of Master branch. |
Collaborator
There was a problem hiding this comment.
"latest release" as the wiki doesn't document other branches (dev, ...)
psonnera
reviewed
Oct 22, 2025
| **Your Omnipod Dash PDM will become redundant after the AAPS Dash driver activates your pod.** Previously a user may have operated a PDM to send commands to your DASH. A DASH will only faciiliate a single device to send commands to communicate with 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 a DASH with your Android phone through the **AAPS**, **you will no longer be able to use your PDM with that pod**. The **AAPS** Dash driver in your Android phone is now your acting PDM. | ||
|
|
||
| **Your Omnipod Dash PDM will become redundant after the AAPS Dash driver activates your pod.** Previously a user may have operated a PDM to send commands to your DASH. A DASH will only facilitate a single device to send commands to communicate with 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 a DASH with your Android phone through the **AAPS**, **you will no longer be able to use your PDM with that pod**. The **AAPS** Dash driver in your Android phone is now your acting PDM. | ||
| D:\Projects |
psonnera
reviewed
Oct 22, 2025
| - MyBMW app | ||
| - Amazon Alexa | ||
| - For **Android 15** or below: You **MUST** use **Version 3.0 or newer of AAPS** using the [**Build APK**](../SettingUpAaps/BuildingAaps.md) instructions, however it's advisable to run the latest released version of Master branch. | ||
| - For **Android 16**: you **MUST** use **Version 3.3.2.1 or newer of AAPS** using the [**Build APK**](../SettingUpAaps/BuildingAaps.md) instructions, due to Android 16 changing how it's bluetooth works any version earlier than 3.3.2.1 will likely cause pod failures and/or activation issues. |
psonnera
reviewed
Oct 22, 2025
|
|
||
| ## Omnipod DASH known AAPS constraints/issues: | ||
| - Android 16 must use AAPS version 3.3.2.1 or later ([Github issue - Can't connect to Omnipod DASH pods after Android 15 upgrade](https://github.com/nightscout/AndroidAPS/issues/3471)) | ||
| - [Too frequent basal updates may cause basal insulin delivery problems with Omnipod Dash](https://github.com/nightscout/AndroidAPS/issues/4158) if using Super Micro Bolas limit to 5 minute interval to avoid this issue. |
Collaborator
There was a problem hiding this comment.
Typo. Bolas.
Whilst technically interesting, I'm wondering if we want to have too many GitHub issues links: they might confuse non-tech users who will click them hoping to find the solution to their problem there...
psonnera
reviewed
Oct 22, 2025
| 2. Spare Insulin and MDI equipment | ||
| 3. A working Omnipod PDM (In case **AAPS** fails) | ||
| 4. Supported Phones are a must! | ||
| 5. Correct version of AAPS built and installed (See [Hardware/Software Requirements](#Hardware/Software-Requirements)) |
Collaborator
There was a problem hiding this comment.
That link won't work. I added a new anchor (omnipod-dash-hardware-software-requirements) to make sure #hardware-software-requirements won't be broken by translation
psonnera
reviewed
Oct 22, 2025
|  | ||
|
|
||
| When in doubt you can also select “Virtual Pump” and select “DASH” later, after setting up **AAPS** (see option 2). | ||
| When in doubt you can also select “Virtual Pump” and select “DASH” later, after setting up **AAPS** (See [Option 2](#Option-2:-The-Config-Builder)). |
Collaborator
There was a problem hiding this comment.
Mind the format #option-2-the-config-builder, same as before: better an achor for this call, I added (omnipod-dash-option-2-config-builder)
psonnera
reviewed
Oct 22, 2025
|
|
||
|  'Pod Management' (Activate, Deactivate, Play test beep, and Pod history) | ||
|
|
||
| (omnipod-dash-activate-pod)= |
Collaborator
There was a problem hiding this comment.
Do not remove anchors unless you can confirm they are not in use and will not be used
psonnera
reviewed
Oct 22, 2025
| ## Before You Begin | ||
|
|
||
| **Ensure you have read and understand all the [Omnipod and AAPS Constraints and Issues](#Omnipod-DASH-known-AAPS-constraints/issues:)** | ||
| **Ensure you have read and understand all the [Omnipod and AAPS Constraints and Issues](#Omnipod-DASH-known-AAPS-constraints/issues)** |
Collaborator
There was a problem hiding this comment.
This is not a valid link due to the /, if the anchor exists it must be %coded
Updated formatting and corrected links in the Omnipod DASH documentation. Removed tables.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Many changes to formatting, language, improvements and updates made to improve quality of the documentation.
Provided known constraints and issues section at the start useful for new users.
Added a more detailed section on Bluetooth issues, around problematic applications using the "nearby detection" permission.
Moved information better suited to a table into a table.