Extra status line stats ("In Percentage" at the very least) do not use Plugin Calibration BG value, even when selected for display

[simonpickering]

It would be useful if the values on the Extra Status Line use the Plugin Glucose value as their input if this is selected (Settings > Less common settings > Advanced Calibration > Use Plugin Glucose).

[Navid200]

Why is there a need for a plugin calibration?
If the manufacturer offers calibration, there should be a way to submit calibration to the CGM.
If there is no way to calibrate a sensor because the manufacturer does not offer calibration, I don't believe xDrip should offer a way to manipulate the readings coming from the sensor as it could lead to dangerous situations.

[simonpickering]

The data can already be calibration which is what e.g. datricsae is doing, but do you really think what you say above? Surely that's up to the user (with copious warnings and the like) to decide whether they should calibrate their sensor data, even if the manufacturer does their own calibration.

Unfortunately the standard calibration doesn't work for everyone all the time. Fine, one could argue that a new sensor should be used and the "faulty" one replaced, but this is a major faff/means sore arms/sometimes just isn't convenient (no replacements to hand), so being able to perform calibration simply makes life better.

But onto the point of my post, the libre2+ data from Juggluco or OOP2 can be calibrated using the Calibration Plugins, and that calibrated value from the Plugin can be displayed on the screen. Surely if both of these are happening then the statistics ought to also be calculated from the data being presented?

[Navid200]

There is a lot in xDrip that is there because in the past it was needed. We gradually retire items that have no reason to exist any longer.

You can still calibrate Libre devices if you use xDrip as a collector.
If xDrip cannot directly collect from a device, and if the manufacturer of such device does not offer a calibration option with their native app, xDrip in my opinion should not be used to calibrate.

If xDrip becomes known by the manufacturers as an app that can endanger lives, they will have no reason to remain silent about xDrip's existence.
If the volunteers who support xDrip are targeted by manufacturers in litigation, xDrip will die. I need xDrip. I don't want xDrip to die. And the obsession that a few have with calibration is not a valid justification to take such a risk.

The entire plugin option in xDrip is something I need to understand and justify for myself. If I understand it and see the reason for it to exist today, I can then justify spending time on it for something related to extra status line that may malfunction.

[simonpickering]

Whether or not you believe in calibration, it does exist can (thankfully) be used to provide the data that is displayed on the screen.

I am very thankful for this, as without calibration the CGM data are often of very little value to me because they are so far offset (more negative than actual BG, and how one actually feels).

We're all different, some of us require additional calibration because whatever Abbott offers doesn't work for us (unless I wanted to run high all the time to avoid "hypo" alarms.)

So my Discussion point was merely that if one does happen to use a calibration and it's displayed on the screen, the Extra Status line values ought to use the same data surely?

[Navid200]

So my Discussion point was merely that if one does happen to use a calibration and it's displayed on the screen, the Extra Status line values ought to use the same data surely?

I agree. But, I cannot fix it until I understand why that calibration mechanism exists. I will fix it when/if that happens.