Hi everyone,
I’m currently using Omnipod 5 and Dexcom G7, but I’ve found that the two dont connect very well. Many times my pdm will say that it’s either searching for a sensor (like it got disconnected or something) or that the sensor just isn’t found. I thought this would just be a temporary problem, but I’ve had the two for about 2 months now and it’s consistently disconnected.
Does anyone else have this problem? If so, is there anyway to fix this?
Welcome back Taylor @Darth_Yader.
I don’t use the Pod, but recall there was a discussion here recently about failure to pair properly - perhaps if you use the “search” you may find a solution. Of course, a call to Dexcom Technical would be in order.
Someone maybe had the same problem with a different pump, although just to be sure is the problem happening when you try to start.a new sensor or anytime?
If anytime I suggested some generic Bluetooth tips to keep in mind in
No, not all Dexcom G7 versions are compatible with all devices:
Not all Dexcom G7 sensors are compatible with the t:slim X2 insulin pump. To check if your sensor is compatible, you can:
Look for a white line under the number starting with “LBL” on the side of the sensor box.
Open the Dexcom G7 app, select “Connections,” and then tap “Sensor”. Check the sensor’s firmware, which should be 32.192.105.64 or later.
Smartphones
The Dexcom G7 can be used with certain smartphones, but you’ll need to download the Dexcom G7 app. You can check the Dexcom compatibility guide for a list of compatible smart devices.
You can use a smartwatch to get sensor readings and alerts, but it must be connected to and within range of your phone. You’ll also need to make sure your smartwatch meets the minimum operating system requirements.
The Dexcom G7 is not currently compatible with Android 15. Dexcom has identified that signal loss will occur with phones on Android 15.
I upgraded to the G7 a few weeks ago and am on my second sensor (or is it my third 
?). I’ve been getting frequent “Searching” messages on my controller as well, even if I’m wearing the pod and sensor on the same arm and have the controller practically on top of me. I’ve got one right now and the last reading my controller got was 40 minutes ago!
Annoying but at least I can still see my numbers on my iPhone.
I guess I should call Dexcom support but don’t feel like going through the third degree of questions at the moment.
I’ll also search for the discussion Dennis mentioned.
Dorie @wadawabbit, I don’t know if the same “fix” that works with t:Connect will work with Dash, but what I have done when I receive a Tandem disconnect on my phone is to switch off BLE/Bluetooth momentarily and when it is turned back on, I receive a listing of all corrected devices and those available for connecting, if wanted. Can Bluetooth be turned off on the Omni Controller?
As a sidenote to indicate the strength of the G7 transmitter, on Thanksgiving when I had to reconnect to t:Connect, my phone picked up the transmitter code [DXC???] of another G7 nearby, and my neighbors on each side were away - indicating a visitor to the neighbor hood across the pond or down the street was wearing a G7.
Well it happened again so I called Dexcom tech support - but since I was getting the readings on my phone they transferred me to Omnipod. Omnipod suggested a few things to try:
Well that’s kind of freaky and concerning. While I suppose we may be closer than we realize to other people using G7s I find it a bit worrisome that somebody might “pick up” my code. Wonder if they might be able to pair mine by mistake if they weren’t paying attention:thinking:? Probably not - I’m sure one of our great technical gurus knows the definitive answer 
.
Nothing to worry about here, Dorie. In order to pair, another party would need your -digit pin that appears only on your applicator. Transmitter ID and pin are not the same thing; just like you cant pair your phone with the signal transmitted by a neighbor’s refrigerator or TV. As you have seen in the info on your phone, “if your G7 is taking too long to pair” move away from other wearers - like when at a diabetes convention where there may by scores of other users.
@wadawabbit I’ve never had the issue of connecting to another G7 in the area. I have had the experience of reconnecting to the sensor that was being replaced. I followed the directions to replace a sensor, it connected to the new sensor without a problem, but then re-connected itself to the old sensor…really freaked me out when it happened! I had not removed the BT connection on my iPhone, but had connected it to the new one. I reported the issue to Dexcom and the FDA. I took to “destroying” the old sensors for the next 3 with hammer and screw driver; but then learned I could just delete the old BT connection on my phone to inhibit the problem.
I think the security mechanism of connecting to BT is pretty good as long as people pay attention to the code for the device being connected to. I know the FDA addressed software connectivity to medical devices about a year or so ago, seeking input from industry and users. While the issue was seemingly driven by the safety aspects of an outsider accessing/directing a device, the additional concern was whether the user would have access to and who owned the data. I don’t know what resolution the FDA came to.
@wadawabbit Next time you see the error can you please check if it says “Searching for Pod” or “Searching for sensor”? Taylor posted about searching for sensor which occurs when the Pod didn’t receive an update from the CGM. Looking at the Omnipod docs the PDM will display searching as soon as a reading is missed which means its going to happen often.
If the PDM says “Searching for Pod” the PDM can’t connect to the Pod.
Thanks for your comments. Regarding the
freakout - that’s understandable! On occasion I’ve had a pod that didn’t disconnect completely so I wasn’t able to connect a new one. I called Omnipod and they recommended putting the old one in the freezer and voilà! It worked! Probably more trouble than reconnecting Bluetooth but I thought I would mention it - might work for sensors as well.
It was definitely searching for the sensor. Thanks!
Thanks Dorie! Short answer: Ignore the message, there is nothing you can do. Check in 20 minutes to see if the Pod has gotten a reading or has changed to Automated Mode: Limited. After an hour of the Pod not receiving CGM values you’ll see “Missing Sensor Values” on the PDM and Smart Adjust will stop adjusting the basal rate.
Long answer: The message is misleading. The pod can’t “search”, it can only listen for the CGM.
Lets start with the CGM. Every 5 minutes the G7 turns on its bluetooth, attempts to connect with the devices that have paired with it, in this case the Pod and your phone, transmits the reading(s) then turns off its bluetooth radio.
The Pod is listening for the CGM. When the Pod gets a reading it logs the reading and updates the PDM. When 5 minutes go by since the last reading without an update it logs that it didn’t get a reading and updates the PDM.
The PDM doesn’t even have to be turned on for the CGM to transmit to the Pod, of course at some point the Pod will start screaming for its PDM. I assume if the PDM misses an update from the Pod it can ask for the data again when they are connected.
The only thing the Pod can ask the CGM to do is pair, and that can only happen when the CGM has its bluetooth on every 5 minutes. Last bit of info, I found n the back of the Omnipod 5 user guide that the Pod is only supposed to hear from the CGM 80% or more of the time so this message can come up often. Since the G7 doesn’t seem to transmit as clearly as the G6 seeing the message more often isn’t surprising. Sorry, I hate problems that don’t have solutions but this is one unless you or @Darth_Yader want to talk about choosing sensor and pod sites for good communication and like similes.
Thank you - the is helpful. It’s a shame the connection is not a clear as with the G6 (due to size perhaps ?), not to mention annoying, but at least I know now.
When I changed my pod yesterday I inserted it just a few inches from the sensor and so far no issues, so it looks like it will be best to place the two closer together and maybe with a more direct line of sight than with the G6🤞🏾.
Thanks again!