temporary communication loss with my Omnipod 5 #2482

Describe the bug

I had a temporary communication loss with my Omnipod 5 today on next-dev 3.15.1.

Around 14:00 Loop reported that it could no longer communicate with the pod and automation was suspended. I received the "Pump cannot be reached" / "Pod cannot be reached" messages shown in the attached screenshots.

The issue resolved after I turned Bluetooth off and back on again in iOS. Communication was successfully restored and the pod continued working normally afterwards.

I don't know whether this was an iOS Bluetooth issue or something related to the new BLE/disconnected-mode implementation, but I wanted to report it in case others have seen something similar.

Device:

iPhone 17 Air
iOS 26.6
Loop next-dev 3.15.1
Omnipod 5
Dexcom G7
Has anyone else experienced this?

Attach an Issue Report
Loop.Report.2026-08-03.17.25.16+02.00.md

To Reproduce

Expected behavior

Screenshots

Phone

• Hardware: iphone 17 Air
• OS Version: ios 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 5
• Model: [e.g. 723]
• Firmware version: [e.g. 2.3A 1.1 0B 0B]

Additional context
Add any other context about the problem here.