What should I do if a deactivated Omnipod 5 keeps beeping?
Answer
Treat the removed Omnipod and the Dexcom alert as separate issues: a deactivated pod can keep sounding until it is discarded per Omnipod guidance, while “Sensor not found” points to the Dexcom G7/transmitter session on the phone or controller—not usually to the old pod. Follow official Omnipod and Dexcom app prompts; for insulin dosing questions, use your clinician’s instructions.
Before you start: stop right away if…
- Insulin pump and CGM issues can affect therapy; follow your healthcare provider’s backup plan if glucose management is interrupted.
- Do not cut, burn, or microwave a pod; dispose of it using the manufacturer’s instructions.
Follow these steps
Identify what is beeping
Hold the removed pod away from the new pod and phone one at a time so you can tell which device is making the sound.
You should see: You know whether the old pod, new pod, or phone/controller is the source.
Finish deactivation and discard the old pod
In the Omnipod 5 app or controller, confirm the old pod is deactivated. Follow Omnipod’s official guidance for silencing/discarding a removed pod (including any recommended discard steps). Do not ignore a new pod’s hazard alarm.
You should see: The old pod is treated as discarded and any remaining chirps are isolated from the active system.
Confirm the new Omnipod session
Check the Omnipod 5 app for an active pod, no unresolved hazard alarm, and a normal status after activation of the replacement pod.
You should see: The active pod shows a healthy session, or a specific Omnipod error you can act on.
Address the Dexcom “Sensor not found” alert
Open the Dexcom G7 app (or Watch/phone companion you use), check Bluetooth is on, keep the phone near the sensor, and use the app’s official troubleshooting for lost sensor signal—wait, reconnect, or start a new sensor only as the app instructs.
You should see: Dexcom resumes glucose readings, or the app gives a clear next action for the sensor session.
Restart phone Bluetooth session if needed
Toggle Bluetooth off and on, or restart the phone, then reopen Omnipod and Dexcom apps and wait for each to reconnect.
You should see: Both apps reconnect without the old pod’s beeping being confused with a Dexcom outage.
Contact official support if alarms continue
If a new pod keeps alarming or Dexcom never recovers, contact Omnipod or Dexcom support with the exact alert text and product versions, and use your backup plan from your care team for insulin if needed.
You should see: You have a support path and a safe interim plan from your clinician’s guidance.
Not sure this is the right page? Check here
0 of 5 checked
Extra tips
What to look for: Whether the beeping comes from the removed pod versus the new pod or phone, and the exact Dexcom alert text such as “Sensor not found.”
Before you change anything: Confirm which device is beeping (old pod, new pod, phone, or watch). Do not puncture or heat a pod in an unsafe way. Keep your Omnipod and Dexcom apps updated from official app stores. For therapy or dosing changes, follow your healthcare provider—not generic internet advice.