Asked if the sensor was started today (and still have to wait an hour..)

[razerrazer]

If I select "No", xDrip starts to warm up the sensor even though it is already activated. Is there a way to avoid the waiting time?

I believe this might be a bug.

[PhilTU]

which sensor ? I started a Libre 2+ and said "not today" and it worked straight away. Had yours been running some time ?

[razerrazer]

This is a Libre 2 sensor. Unfortunately, I already started it using the Libre app, along with the MiaoMiao 3.

So I believe this might be the issue since MiaoMiao is no longer necessary? xDrip can handle the sensor directly (if I choose to start a new sensor directly in xDrip next time).

But still, even if I continue using the MiaoMiao 3, shouldn't this setup work without the warm-up issue?

Had yours been running some time ? Yes since yesterday!

[PhilTU]

xDrip+ can't start a Libre 2 sensor so using the "Libre app" isn't an issue.

Which version of xDrip+ do you have I will try to duplicate the 1 hour issue. Ah, hold on, you're still using the MM3 so the NFC scanning is being done by the transmitter ?

[razerrazer]

So, do we have to keep using the MiaoMiao 3 for this to work properly?

Yes, I started the transmitter by scanning it with the Libre app.

I tried switching to the latest nightly build of xDrip today to check if this was a bug, but the behavior is the same as in the latest stable release.

[PhilTU]

no, I never had a transmitter device and the L2 / L2+ works well. From what you just wrote am I right in thinking that the one hour delay you saw was repeated when you tried later with a different version ?

I realised I can't duplicate it as I don't have a transmitter.

[razerrazer]

This is not a transmitter, i started it via the LibreAPP via NFC.

[PhilTU]

MiaoMiao is a transmitter. When you come to "start" it in xDrip this is done via Bluetooth presumably - I can try the connecting thing but it will be direct to the phone via BLE

[PhilTU]

So first attempt it connected up and running now with 1 minute values via Bluetooth. I realise I didn't stop the previous sensor session which is a different process. So now I will stop session and try start again.

[PhilTU]

So I stopped the sensor, rescanned and did not do "Start sensor" and now I have "Please wait while sensor warms up" counting down. xDrip+ moved itself to this state at 12:34 "Created new default sensor" when previous sensor stopped at 12:32.

I received 5 one minute values so far and in fact the warm up message has disappeared at 12:38. xDrip+ showed glucose data regardless.

Back to menu. Stop sensor. Start sensor (no scanning), said "not today" and one hour warning reappears. Bluetooth data continues to flow. 12:45 one hour warning has disappeared.

So the reason I don't see the warning is I don't stop sensors. The automatic warnings seem to self correct after about 5 minutes.

Hope that helps.

[razerrazer]

So, if you switch the sensor without stopping it first, does that mean you’re just replacing it?

Honestly, I don’t really like the MiaoMiao 3. The battery is nearly dead, and the unit is quite expensive — especially since they don’t seem to offer any battery replacements.

From what I’ve read online, it seems that some users in the EU have managed to use xDrip+ with Libre 2 without an external transmitter like MiaoMiao. Is that correct? I would even say that the MM1 is better than MM3, and the best one of them all was MM2.

[PhilTU]

Yes, practically all Libre 2 users in UK / EU don't use a transmitter device. They were only really necessary to add Bluetooth to the original Libre.

Outside of EU/UK Juggluco or Diabox can often connect direct to L2 or 3 (or plus variants).

MM does have a higher Bluetooth power than Libre 2 I suspect.

The whole stop/start thing is a bit of a misnomer. I regard it as starting a session rather than a sensor, and the prior and subsequent history of that sensor has little effect on the session.

[razerrazer]

The whole stop/start thing is a bit of a misnomer. I regard it as starting a session rather than a sensor, and the prior and subsequent history of that sensor has little effect on the session.

Yes this is possible a bug, right?

Yes, practically all Libre 2 users in UK / EU don't use a transmitter device. They were only really necessary to add Bluetooth to the original Libre.

So in this case, next time I set up a new Libre sensor, should I just try to see if I can start it directly without the transmitter and without the Libre App?

[PhilTU]

You can't start it with xDrip+ so you need a plan to start it before connecting to xDrip+

I don't think it's a bug. An inconsequential warning that goes away and has no effect. There are actual bugs that matter and are higher priority.

[Pipecity]

I am now also experienced this issue after updating xDrip+ to version 041244d-2025.05.09. This is a new behavior as it didn't functioning like this before.

My Libre2+ was started with the LibreLink yesterday. When I today, like I always do when switching Libre, I stopped the old one, clicked the Forget Device, then scanned the new Libre and selected "Not today", xDrip would still display sensor warm up message and only after would I be able to calibrate it. Tried it multiple times.

After the warm up of 60 minutes it works as before.

[PhilTU]

After the warm up of 60 minutes it works as before.

so you didn't have the experience I did where that 60 minutes message just went away on its own. Did you get glucose values ?

I didn't do any calibration, so maybe there is a constraint on calibration that I didn't see.

[Pipecity]

Well, it goes away after 60 minutes but asks directly after for calibration. In earlier versions it would try to get 3 readings and then ask for calibration. Now I need to wait 60 minutes before getting any values and the calibration message if I choose "Not today". Haven't tried selecting "Yes today" and select a time more than 1 hour ago.

From the documentation here: https://xdrip.readthedocs.io/en/latest/use/startsensor/#libre it says:

If you're using OOP1 or OOP2 without calibration, BG will start displaying immediately without need of the initial calibration.

If you're using an already started sensor you will have a calibration request within 15 minutes.

This new behavior clearly goes against the documentation, right?

[PhilTU]

This new behavior clearly goes against the documentation, right?

seems inconsistent, although whether it's "new" behaviour isn't clear as the OP says it's the same in the stable release but I'm not sure if that's the very recent one or the one from last September.. I would be fairly sure there's been no change to the Libre code. It doesn't yet recognise the 15 day life of the L2+

If it's a significant problem first step would be to identify the version in which th behaviour first appears.

[razerrazer]

Nope, you have to wait for 60 minutes. It doesn't disappear after a while it's just there, and you have to wait until you're able to calibrate.

[PhilTU]

yeah, but I didn't have to wait it just disappeared. It also had no effect on getting readings. But I didn't calibrate.

So it's not clear to me when this occurs, as I can't reproduce it. Odd.

[razerrazer]

This is how to reproduce:

1. Stop your sensor.
2. Start a new sensor and choose "Not today"

[PhilTU]

Where do you set "no calibration"?

https://xdrip.readthedocs.io/en/latest/use/misc/?h=oop#oop2 search Settings for oop, it's in Other Settings > Less common settings > Other misc. options.

[razerrazer]

No, I don't use a transmitter / bridge device. Only direct connection with Libre.

@PhilTU Where do you set "no calibration"? Couldn't find that setting. Just curious.

So libre2 works now without a transmitter?

[PhilTU]

So libre2 works now without a transmitter?

For many years, since patched app (2019?) at least European variants.

[razerrazer]

So libre2 works now without a transmitter?

For many years, since patched app (2019?) at least European variants.

hm, you said this before: You can't start it with xDrip+ so you need a plan to start it before connecting to xDrip+

[PhilTU]

hm, you said this before: You can't start it with xDrip+ so you need a plan to start it before connecting to xDrip+

yes. The Libre sensor must always be initiated by something other than xDrip+ as xDrip cannot do this itself.

Libre 1 or 2 reader device, patched Librelink app, juggluco, Diabox, official app, official app on a different phone.

It's quite common for people to initiate L2 sensor with Librelink with alarms off and Bluetooth disabled. That prevents BLE conflict. xDrip is then used routinely and occasional NFC scans with Librelink to upload data to doctor etc are possible.

[razerrazer]

Why has it been activated on a different phone?

Right now, i have tested to start it with juggluco, and the values are there, but xDRIP are not getting any data even if i select "Pached app".

[PhilTU]

Why has it been activated on a different phone?

Don't understand. I said that was one option.

Did you set Juggluco to send data to xDrip? It's not the default.

[razerrazer]

Why has it been activated on a different phone?

Don't understand. I said that was one option.

Did you set Juggluco to send data to xDrip? It's not the default.

I have set hardware under settings to "Pached app", then i don't know if there is anything else i need to do?

[razerrazer]

ok, i get it worked, but it took the actual value from Juggluco, and not that value that i have set my self (calibrated it). so there is no way you are able to calibrate the glucose of it?

[PhilTU]

Calibration may have been rejected.

https://xdrip.readthedocs.io/en/latest/calibrate/calibrate/#libre-2-patched-app says you can do it with constraints "When using the patched app, you can calibrate but correction is applied as an offset with maximum values between -40 mg/dl to +20 mg/dL [-2,2 mmol/l to +1,1 mmol/l]. Calibrations failing this criteria will be ignored."

[AdLouwerse]

I also have the same problem as described above. I'm using Libre 2 (OOP2), start it with the libre app NFC and 4 hours later I scan it with xDrip and use the option "Not Today" as documented. In previous xDrip versions it started working after 3 times 5 minutes (asks for calibration, which I need). Now I have to wait 1 hour. Each time I stop and start the sensor it starts with waiting 60 minutes, that was not the case with older xDrip versions.
I rolled back to the old version and there it still works fine, I don't have to wait 60minutes.

[AdLouwerse]

In my tests the "wait an hour" message disappears in a few minutes
The " ... "wait an hour" message disappears in a few minutes ... " is new for me, I have to try it out and will do so. It will take time as I'm not able to work on it for a week.

[PhilTU]

I generally don't do calibration, which is probably why I don't have this problem.

[rvdheij]

I personally am not fond of providing any calibration mechanism in xDrip for a device that is FDA approved and is presented in the market with no means of calibration. However, to be transparent, I have been told that Libre may need help with calibration.

If you look at the factory calibration guarantees, you'll realize that +/- 15% is a pretty wide range when people try to get their time-in-range at 95% or better. The big advantage of using xDrip and careful calibration with finger prick is that you can get much better accuracy. Since xDrip would miss any in-flight corrections in the vendor app, I think it would be smart to calibrate when using xDrip.

For some FSM users the convenience of not having to calibrate may be more important, but I think most of those users will just stick with the vendor solution and not mess with xDrip.

[Navid200]

If you look at the factory calibration guarantees, you'll realize that +/- 15% is a pretty wide range when people try to get their time-in-range at 95% or better.

A blood glucose meter also has an accuracy of +/- 15%.
What is the point of calibration if what you are calibrating to is not more accurate than what you are calibrating?
That unfortunately, is what most users don't understand.

What changed after factory calibration was that the impact of the immune system on sensor was removed from the equation. This factor used to drift the sensor accuracy day by day. The previous generations of sensors needed to be calibrated because with that drift, the blood glucose meter was considerably more accurate than the uncalibrated CGM.

That is not the case now with factory calibrated CGMs. Their accuracy does not drift with the age of the sensor. The problem is that not every user understands most of this and have got used to the concept of calibration and have a hard time understanding that their CGM is as good as their glucometer. This does not mean they are identical. No, they are both wrong. But, their errors are not corelated. By calibrating you only bring your CGM closer to your glucometer, which is still wrong.

For some FSM users the convenience of not having to calibrate may be more important, but I think most of those users will just stick with the vendor solution and not mess with xDrip.

I use xDrip because it does what I need much better than the official app. I don't use xDrip for calibration.
Considering how misunderstood the concept of calibration of a CGM is, I will be against adding any calibration capability to xDrip.

[Navid200]

The following is not a medical advice. It is what I do. I am not telling anyone to do the same without consulting with their doctor.

I have a factory-calibrated CGM. I have a glucometer.
When, and only when, my senses (symptoms) disagree with my CGM, I use my glucometer and if needed, calibrate.

The CGM I use offers calibration. It is not xDrip doing the calibration.

[PhilTU]

Just to throw a randowm question in - do you guys have "Check Libre serial" set ? Other settings / less common settings / advanced calibration ?

I'm just trying to narrow down any differences in config.

[AdLouwerse]

Yes I have the option "Check Libre Serial" checked.
Might you want to know more of these options. I have:
"Double calibrations" not checked
"Infrequent Calibration" checked
"Non-fixed Libre slopes" checked
"Bypass quality check" not checked

[razerrazer]

I can confirmed that this issue is not present if you use Juggluco

[AdLouwerse]

Do you mean Juggluco just to start the sensor instead of the Libre app, or use Juggluco instead of OOP2? That might be an interesting alternative if I still can see the 1 minute readings in xDrip.

[PhilTU]

Patched app as hardware data source in xDrip+, juggluco sending to that. juggluco dev doesn't believe in calibration.

[razerrazer]

To be honest, it works really well with Juggluco. It's almost accurate in xDrip as mentioned, it can be off by ±2, which is acceptable. I've also confirmed the readings with a blood glucose meter.