Skip to content

communication issue involving the same Omnipod 5 pod on next-dev #2485

Description

@jenneman

Describe the bug

Yesterday, I experienced a temporary pod communication failure. At that time, communication was restored after toggling Bluetooth off and back on.

Today, the same pod became unreachable again. This time none of the recovery actions worked:

Bluetooth off/on
Force-closing and reopening Loop
Rebooting the iPhone
The pod never reconnected and ultimately had to be replaced.

The reason I am posting this in Zulip first is that I am currently on-site with a customer and do not have enough time today to create a proper GitHub issue with logs and a full investigation.

I understand that a GitHub report may still be needed, but repeated communication failures with the same pod are concerning enough that I wanted to document the behavior immediately.

Attach an Issue Report
Loop.Report.2026-08-04.12.19.53+02.00.md
Export-20260804T101347Z.zip

To Reproduce

Expected behavior

Screenshots
image
image

Phone

  • Hardware: iPhone Air
  • OS Version: 26.6

Loop Version

  • Version Number: next-dev 3.15.1
  • Repo: [LoopKit/Loop, Katie, etc]

CGM

  • Device: Dexcom G7
  • Manager app: [e.g. Dexcom App, Spike]

Pump

  • Manufacturer: Omnipod
  • Model: 5
  • Firmware version: [e.g. 2.3A 1.1 0B 0B]

Additional context
Add any other context about the problem here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions