nightscout / nightscout/AndroidAPS
Omnipod Dash activation "Found too many pods for activation"
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 1.2k
- Forks
- 6.4k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 19
Description
This issue has only started to happen with my last two pods. Nothing has changed with my Setup.
Samsung S24 Ultra on Android 14.
Omnipod Dash
AAPS build version: 3.3.1.2
Build: 202df2cebf-2025.01.15
When activating my Omnipod I repeatedly get a message "Found too many pods for activation"
This take up to 30 minutes to bypass by repeatedly trying again and disabling and reenabling Bluetooth.
I don't have any discarded pods in the house. This message was occuring even when I was 100 yards down the road.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the attached AndroidAPS_LOG_1743106938457.log.zip and tracing the Omnipod Dash activation flow described in the report. Done means explaining why activation reports too many pods in this environment and addressing the false detection or handling path, with verification that activation no longer repeatedly fails.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100