You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently Freestyle Libre 3 was launched in Europe providing GCM, readings are now through Bluetooth instead of NFC.
Is there any move to support it?
Thanks
@malloy139 this is the wrong thread to address this problem. But the pr that needs to get merged to get this feature is the following one: #1686
Please comment there (like I did) perhaps this bumps it up a little :)
@twinko Looks like #1686 doesn't solve this problem. It synchronizes followers, but doesn't solve issues with per 4.5 min xdrip plot, and, I assume, sends data to AndroidAPS via local broadcast.
It is possible to broadcast that Libre3 raw values to AndroidAPS
I am not sure if that is a good idea though.
Case @malloy139 showing is valid, I observe the same. However, on relatively smooth periods there are always tiny deviations in Libre 3 data. I don't know if AndroidAPS will work correctly with them.
Good example of this:
For sure I would prefer if AndroidAPS realized dropping BG earlier and had extra time to react.
However, these small perturbations undesirable for AndroidAPS, as far as I know
@gringyb tried the ghost app. Doesn't launch, crashes immediately. Wiping my phone now and restore my backup. Afterwards i tried jkaltes (juggluco) patched app. This one is working like a charm. So i guess its not my phone that is the problem.
@gringyb tried the ghost app. Doesn't launch, crashes immediately. Wiping my phone now and restore my backup. Afterwards i tried jkaltes (juggluco) patched app. This one is working like a charm. So i guess its not my phone that is the problem.
I got the same issue.
Both LL Patched and Juggluco works fine, but juggluco does not send all values to xDrip+ more than once each 5 min or so.
xDrip itself transforms values coming in every minute to one value very 5 minutes.
Take a new version of xDrip and turn on Settings->Less Common settings->Advanced settings for Libre2->"Show Raw values in Graph" and you will see that every minute a new "raw" value arrives in xDrip.
In old versions of xDrip the raw values are badly displayed. In a new version you can find all 1 minutes values between the 5 minutes values created by xDrip. Lastest download is in reality old and displays them wrongly, take a nightly build for example: https://github.com/NightscoutFoundation/xDrip/releases/download/2022.11.16/xDrip-plus-20221116-344deb4.apk
EDIT:
The only values that are represented in Juggluco, but not in xDrip are values that were not send to Juggluco at the moment itself because of a connection error. Libre3 sensors, but not Libre2 sensors, will send these measurements later. When you sends there values later to xDrip in the same way you send immediate values, it will not accept them.
Values send later don't have a rate of change, so you can see the difference by saving values with left middle menu->Export->Stream and looking at rate and ChangeLabel
Sensorid nr UnixTime YYYY-mm-dd-HH:MM:SS TZ Min mmol/L Rate ChangeLabel
XX0A0DZ6J3C 20124 1669374592 2022-11-25-12:09:52 1 20123 6.0 +nan NOT_DETERMINED
Hi, just want to express my appreciation from US. I received Fl3 as sample from my Dr. I started using lb3 with juggluco and xdrip. It is working correctly for two days for now. I experienced two incidents in relating to Bluetooth disconnection. One for phone battery power lost (4hrs)and other for swimming class(45min). Both cases, I could reconnect bluetooth with retouching phone to sensor. But I could not import those data to xdrip even though juggluco showing one of those data(for 45min). Is this legitimate condition? I'm wondering whether I can connect watch and sensor directly?
But anyway I appreciate for those developers very much.
For your information I'm using following devises: Samson S22 phone and Garmin vivoactive3 watch.
@kaz45242
Afaik there is no possibility to reimport missed data from juggluco to xdrip. This question was asked multiple times in the original juggluco thread (its in german), even though juggluco is capable of reading data from the sensor of the past 8h.
If you are more into mibands or amazfit watches (7 days battery life) , there is no direct connection but its working flawless with watchdrip+ (it takes the data from. Xdrip) https://bigdigital.home.blog/
Any further information about Libre 3? Could we implement the sensor according to juggluco ? It seems that Juggluco is open source
Juggluco code is open source but it needs proprietary libs in order to be built and run, so I don't think that a L3 direct connection could be ever implemented in xDrip.
Using juggluco as data source for xDrip is fine, the app is stable, frequently updated, and very light on battery and resources.
The only big missing feature is calibration because you have to set patched app source in order to collect data ( adding full calibration to that source would be very appreciated ).
Given that ( according to what the juggluco's devleper reports ) with L3 you don't have access to raw data, another source like a possible OOP3 or the Diabox app when it will enable its support would make no difference with the current solution.
@enpa23 sorry but your information is only partially right :)
The only big missing feature is calibration because you have to set patched app source in order to collect data ( adding full calibration to that source would be very appreciated ).
Please do not use the horrible patched libre app. Just scan the sensor with juggluco when you want to start a new one, thats it.
I already updated the german version of the instructions here, but didnt had the time yet to translate it. https://github.com/maheini/FreeStyle-Libre-3-patch/blob/main/Juggluco-solution/instructions/de/instructions.md
Regarding calibration: Please read the part jka wrote at the bottom of the page about calibration: https://www.juggluco.nl/Juggluco/mgdL/index.html i dont understand why people want to calibrate a libre sensor. This is not a dexcom, calibration is not needed. And yes the data never matches if you prick your finger and compare the results, because the libre data is alway 15-20min older than the real blood glucose level. Thats how it is for all CGMs. Please google the reason for that by yourself :)
Given that ( according to what the juggluco's devleper reports ) with L3 you don't have access to raw data, another source like a possible OOP3 or the Diabox app when it will enable its support would make no difference with the current solution.
you are absolutely right, but to specifiy you can get a data point every minute
@twinko
I do use Juggluco, not the patched app. xDrip has to be set to patched app data source in order to receive data from it.
In my experience both L3 ( less ) and L2 ( way more ) often come bad calibrated, while still inside the error range that can entitle to a substitution from the vendor.
I easily have a 60 mg/dl difference with fingerprick on the 180-200 range, and so on, even when bg is stable for 15 minutes.
With a good calibration ( I have to enable experimental secondary plugins in xDrip, add few points at the beginning with stable bg - some in the ~100, some in the 180-200 ), add a new value after two days or so to check if sensor has stabilized to a different offset, and then in case check every few days ) I get almost identical values from xDrip and fingerprick test for the whole sensor life.
Switching from a so-so calibrated sensor to a close to perfect one has a great added value to me.
@twinko I do use Juggluco, not the patched app. xDrip has to be set to patched app data source in order to receive data from it.
In my experience both L3 ( less ) and L2 ( way more ) often come bad calibrated, while still inside the error range that can entitle to a substitution from the vendor. I easily have a 60 mg/dl difference with fingerprick on the 180-200 range, and so on, even when bg is stable for 15 minutes. With a good calibration ( I have to enable experimental secondary plugins in xDrip, add few points at the beginning with stable bg - some in the ~100, some in the 180-200 ),
I agree, it makes sense to calibrate. Some of the L3 sensors are always given too high values. For those saying that differences are due to a lag between interstitial and blood glucose, there is one recent academic study by Alva and colleagues (2023) that shows it quite short (on average below 5 minutes). I personally found the calibration as is possible with Dexcom makes life easier as you can really rely. Good to hear that Twinko found the calibration working well, I haven't tried it myself with L3.
Activity
tolot27 commentedon Oct 21, 2020
Abbott just announced the Libre 3. It is not available yet. Hence, nobody can start implementing support or investigate whether it is possible or not.
schrackschorsch commentedon Aug 4, 2021
libre 3 is now available in Germany. The libre-app for ios is ready. The app for android soon will be available.
https://www.freestylelibre.de/libre/freestyle-libre-3-entdecken.html
marekmand commentedon Sep 16, 2021
Shouldn't be this ticket reopened since FL3 is available publicly in Germany?
I don't see any reason to postpone this anymore.
renele commentedon Oct 5, 2021
any update on this or where can we track progress or is something blocking ?
yoshimo commentedon Oct 5, 2021
The missing android app makes analysis harder
tolot27 commentedon Oct 5, 2021
It is unlikely that xDrip will support L3, natively. Likely, it will be implemented similar to L2 OOP external app.
48 remaining items
twinko commentedon Nov 17, 2022
@malloy139 this is the wrong thread to address this problem. But the pr that needs to get merged to get this feature is the following one:
#1686
Please comment there (like I did) perhaps this bumps it up a little :)
harentius commentedon Nov 22, 2022
@twinko Looks like #1686 doesn't solve this problem. It synchronizes followers, but doesn't solve issues with per 4.5 min xdrip plot, and, I assume, sends data to AndroidAPS via local broadcast.
It is possible to broadcast that Libre3 raw values to AndroidAPS
I am not sure if that is a good idea though.
Case @malloy139 showing is valid, I observe the same. However, on relatively smooth periods there are always tiny deviations in Libre 3 data. I don't know if AndroidAPS will work correctly with them.
Good example of this:
For sure I would prefer if AndroidAPS realized dropping BG earlier and had extra time to react.
However, these small perturbations undesirable for AndroidAPS, as far as I know
twinko commentedon Nov 24, 2022
@gringyb tried the ghost app. Doesn't launch, crashes immediately. Wiping my phone now and restore my backup. Afterwards i tried jkaltes (juggluco) patched app. This one is working like a charm. So i guess its not my phone that is the problem.
master3395 commentedon Nov 26, 2022
I got the same issue.
Both LL Patched and Juggluco works fine, but juggluco does not send all values to xDrip+ more than once each 5 min or so.
j-kaltes commentedon Nov 26, 2022
xDrip itself transforms values coming in every minute to one value very 5 minutes.
Take a new version of xDrip and turn on Settings->Less Common settings->Advanced settings for Libre2->"Show Raw values in Graph" and you will see that every minute a new "raw" value arrives in xDrip.
master3395 commentedon Nov 26, 2022
Jiggluco sends all the raw data to xDrip+ only once each 5 min, along side the 1 min raw.
So it's not each min even with that turned on.
I have it on.
j-kaltes commentedon Nov 26, 2022
In old versions of xDrip the raw values are badly displayed. In a new version you can find all 1 minutes values between the 5 minutes values created by xDrip. Lastest download is in reality old and displays them wrongly, take a nightly build for example: https://github.com/NightscoutFoundation/xDrip/releases/download/2022.11.16/xDrip-plus-20221116-344deb4.apk
EDIT:
The only values that are represented in Juggluco, but not in xDrip are values that were not send to Juggluco at the moment itself because of a connection error. Libre3 sensors, but not Libre2 sensors, will send these measurements later. When you sends there values later to xDrip in the same way you send immediate values, it will not accept them.
Values send later don't have a rate of change, so you can see the difference by saving values with left middle menu->Export->Stream and looking at rate and ChangeLabel
Sensorid nr UnixTime YYYY-mm-dd-HH:MM:SS TZ Min mmol/L Rate ChangeLabel
XX0A0DZ6J3C 20124 1669374592 2022-11-25-12:09:52 1 20123 6.0 +nan NOT_DETERMINED
malloy139 commentedon Nov 27, 2022
This is not what I observe. You can see a new white dot every minute in xdrip.
kaz45242 commentedon Jan 31, 2023
Hi, just want to express my appreciation from US. I received Fl3 as sample from my Dr. I started using lb3 with juggluco and xdrip. It is working correctly for two days for now. I experienced two incidents in relating to Bluetooth disconnection. One for phone battery power lost (4hrs)and other for swimming class(45min). Both cases, I could reconnect bluetooth with retouching phone to sensor. But I could not import those data to xdrip even though juggluco showing one of those data(for 45min). Is this legitimate condition? I'm wondering whether I can connect watch and sensor directly?
But anyway I appreciate for those developers very much.
For your information I'm using following devises: Samson S22 phone and Garmin vivoactive3 watch.
twinko commentedon Jan 31, 2023
@kaz45242
Afaik there is no possibility to reimport missed data from juggluco to xdrip. This question was asked multiple times in the original juggluco thread (its in german), even though juggluco is capable of reading data from the sensor of the past 8h.
You can connect a smartwatch to the sensor directly if it has wearOS (1 day battery life) , read here: http://jkaltes.byethost16.com/JugglucoWearOS/mgdL/index.html
If you are more into mibands or amazfit watches (7 days battery life) , there is no direct connection but its working flawless with watchdrip+ (it takes the data from. Xdrip) https://bigdigital.home.blog/
henrycoding commentedon Jul 13, 2023
Any further information about Libre 3? Could we implement the sensor according to juggluco ? It seems that Juggluco is open source
enpa23 commentedon Jul 13, 2023
Juggluco code is open source but it needs proprietary libs in order to be built and run, so I don't think that a L3 direct connection could be ever implemented in xDrip.
Using juggluco as data source for xDrip is fine, the app is stable, frequently updated, and very light on battery and resources.
The only big missing feature is calibration because you have to set patched app source in order to collect data ( adding full calibration to that source would be very appreciated ).
Given that ( according to what the juggluco's devleper reports ) with L3 you don't have access to raw data, another source like a possible OOP3 or the Diabox app when it will enable its support would make no difference with the current solution.
twinko commentedon Jul 13, 2023
@henrycoding this wont happen any time. Read explanation here: #1474 (comment)
@enpa23 sorry but your information is only partially right :)
Please do not use the horrible patched libre app. Just scan the sensor with juggluco when you want to start a new one, thats it.
I already updated the german version of the instructions here, but didnt had the time yet to translate it. https://github.com/maheini/FreeStyle-Libre-3-patch/blob/main/Juggluco-solution/instructions/de/instructions.md
Regarding calibration: Please read the part jka wrote at the bottom of the page about calibration: https://www.juggluco.nl/Juggluco/mgdL/index.html i dont understand why people want to calibrate a libre sensor. This is not a dexcom, calibration is not needed. And yes the data never matches if you prick your finger and compare the results, because the libre data is alway 15-20min older than the real blood glucose level. Thats how it is for all CGMs. Please google the reason for that by yourself :)
you are absolutely right, but to specifiy you can get a data point every minute
enpa23 commentedon Jul 13, 2023
@twinko
I do use Juggluco, not the patched app. xDrip has to be set to patched app data source in order to receive data from it.
In my experience both L3 ( less ) and L2 ( way more ) often come bad calibrated, while still inside the error range that can entitle to a substitution from the vendor.
I easily have a 60 mg/dl difference with fingerprick on the 180-200 range, and so on, even when bg is stable for 15 minutes.
With a good calibration ( I have to enable experimental secondary plugins in xDrip, add few points at the beginning with stable bg - some in the ~100, some in the 180-200 ), add a new value after two days or so to check if sensor has stabilized to a different offset, and then in case check every few days ) I get almost identical values from xDrip and fingerprick test for the whole sensor life.
Switching from a so-so calibrated sensor to a close to perfect one has a great added value to me.
klaaslusterbroodvan commentedon Aug 1, 2023
I agree, it makes sense to calibrate. Some of the L3 sensors are always given too high values. For those saying that differences are due to a lag between interstitial and blood glucose, there is one recent academic study by Alva and colleagues (2023) that shows it quite short (on average below 5 minutes). I personally found the calibration as is possible with Dexcom makes life easier as you can really rely. Good to hear that Twinko found the calibration working well, I haven't tried it myself with L3.