xDrip Internal session (sensor)

[Navid200]

@Der-Schubi
The internal session is legacy.
We needed it for G5.
Now, it is used so much in the code that it will take a while to make the code independent of it.
We cannot just abandon it and maintain backward compatibility with G5. We are still supporting G5.
Unfortunately, a proposal was made to add raw capability to modified G6 devices and unfortunately, it was passed. So, we are going to be stuck with it even after we retire G5.

[Der-Schubi]

So, we are going to be stuck with it even after we retire G5.

If we're stuck with it, why not use it? If I'm not missing something, many of the G7 quirks you fixed in the last few months would not have been necessary, if we would make sure to always stop the internal session when a new sensor code is entered.

But I see what you are suggesting, getting rid of the internal session has its charm.

I'm not seeing why

Unfortunately, a proposal was made to add raw capability to modified G6 devices and unfortunately, it was passed.

I have no idea why someone would want that...

[Der-Schubi]

using Dexcom app and you stop it using Dexcom app

I re-enabled the stop option in xDrip. This should do the trick without using Dexcom app, right?

[Navid200]

If you mean you have your own version of xDrip, yes. You will have to wait for the stop command to clear from the queue.

---

I used to see people make mistakes and call Dexcom complaining and asking for a replacement.
So, my guide states the only way to confirm something is wrong with the device is to use the official app, not xDrip.

But, what if someone stops a G7. After the damage is done, there is no way to undo it. You can restart a G6. But, you cannot restart a G7. That was the beginning for me to look for a way to remove the stop option.

It is not just technical matters that I have to worry about. I also have to worry about what xDrip users may do. The last thing we need is for Dexcom to think we (xDrip) are causing return devices for them.

[Navid200]

@Dainem21 I am on my way out. When I return in a few hours, I will answer your questions.

[Der-Schubi]

If you mean you have your own version of xDrip, yes. You will have to wait for the stop command to clear from the queue.

Yes and I know.

But, what if someone stops a G7.

If necessary, we could omit queing the stop command for G7 but still stop the internal session.

[Navid200]

I will think about that.
So far, my focus has been to train users to know what really matters with no need for stopping the session. I still prefer to accomplish that and I intend to add a page that goes over what could go wrong at the time you have more than one active device and how to deal with it.

if we bring the stop option back and someone stops the old one and asks why is it still interfering, we have accomplished nothing. I will still have to hold their hands to get them to a working state. The new page in the guide will hopefully accomplish that.

[Navid200]

@Dainem21 A G7 that is in rapid reconnect mode will be a serious cause of interference.
I have talked about what rapid reconnect is here: https://navid200.github.io/xDrip/docs/Dexcom/G7OnceAMinuteScan.html

No, you cannot rely on the pairing code entered letting you connect to it in presence of other G7 devices that are in rapid reconnect mode.

Please don't think of the option to stop a sensor as a solution. Stopping a sensor does not change any of this. It will still continue to interfere.

What if you have a sensor that malfunctions and you want to switch to a new one without peeling it off?
You will need a second phone!
Use the second phone to connect to the new sensor.
What is unique about this problem that I need to document for everyone is that if you are connected to a G7, it will be almost harmless with respect to you trying to connect to another.

After you are connected to a sensor, you don't need to stay connected to the other. As soon as you have connectivity to a G7 with decent phone that does not have an inherent intermittent connectivity problem, you cab have other sensors in the area. They cannot interrupt your connectivity.
They can interfere if you are trying to establish connectivity. But, after you are connected to the right sensor, you can have 200 other sensors around you and you have nothing to worry about.

Now, let's make this really ugly!
What if you are connected to the new sensor with the temporary phone and you are connected to the malfunctioning sensor with your main phone. What if you want to swap them meaning you want to switch the two phones with respect to the two sensors?
This is something that should work, but I have not verified it myself. Otherwise, you will need a third phone:

Install Dexcom app on the temp phone as well as xDrip. Disable collection on the main phone from the malfunctioning sensor. Wait 15 minutes.
Set up Dexcom app on the temp phone to connect to the malfunctioning sensor.
After that is accomplished, disable collection in xDrip on the temp phone from the new sensor.
After 15 minutes, set up xDrip on the main phone to connect to the new sensor.

Yes, this is a mess. I agree. Stopping the sensor will change nothing. What you need to stop is the transmitter and there is no way to do that.