• Guest, the forum is undergoing some upgrades and so the usual themes will be unavailable for a few days. In the meantime, you can use the forum like normal. We'd love to know what you think about the forum! Take the 2025 Survey »

Best settings for Xdrip and LibreLink together?

If it's this page then the linked version of OOP2 is too old, despite saying it's the latest version: https://www.minimallooper.com/post/...to-use-a-native-bluetooth-connection-in-xdrip

I'm on version 27da3f5-2023.05.25

I don't actually recall where I got it from, though this is probably the place: https://xdrip.readthedocs.io/en/latest/use/OOP/#oop2

I did post on the gitter chat (you should be able to find my post, otherwise I'll have a look later on) to raise the point that the instructions above are not correct, though they have perhaps not been changed, I didn't check back once I got it all up and running
 
Appreciate the heads up. Just found it..

I’ll play about with it later.
 
Jaylee said:
I got both running bluetooth so there’s no need to scan.
Click to expand...
Ah, in the Netherlands we didn't get the update for Libre 2 to have it send numbers through bluetooth, so it's only used for alarms.
Something to do with funding rules where everyone on MDI or pump is eligible for a flash monitor (Libre 2) but only some are eligible for a full CGM. The rules were made before it was possible to use Libre as a CGM unless you used an add on device.
 
It seems I spoke too soon, and the problems are continuing!
I realised Xdrip+(via OOP2) only gets the data every 5 minutes, which isn't ideal.

So I decided to give DiaBox another go simultaneously with LL, since many here say that works well for them. I've used Diabox before on its own and liked it well enough.

I started a new sensor today with LL, and about 20 minutes into the startup period, I scanned with Diabox (freshly installed latest version, Xdrip now uninstalled).
Diabox then started a 60 minute countdown, which I thought seemed a little odd, since it hadn't picked up that LL had already started it.
The LL countdown finished and allowed NFC readings, but would not connect via BT.
I waited another 20 minutes for diabox to finish its countdown, and it then switched to saying just "starting", but would not receive any readings, either by NFC or BT. LL still won't connect
So I now have a new sensor with no BT connection in either app, and no alarms .
I tried force closing each app, then starting each one on its own. I tried turning bluetooth off and on again. I restarted my phone multiple times.
Still no BT onnection.
I tried uninstalling diabox and restarting my phone again. LL still won't connect BT.

Has Diabox broken the transmitter in my sensor?
 
Okay, I uninstalled Diabox, and uninstalled then reinstalled LibreLink, and at least that now connects via BT. It meant losing the data in the app though (I know it's still there in LibreView, but it's nice to have the stats on the phone).

It's all a bit frustrating.
 
Last edited:
Hi,

Sometimes I clear the Bluetooth memory & cache, then restart the phone & scan with both apps. if it gets like that.
 
Thanks, I was thinking restarting the phone and switching Bluetooth off and on was enough, but I didn't try clearing the cache.

For those that have Diabox and LibreLink working together, have any of you successfully started Diabox after the 1 hour startup period of LibreLink? and if so, does Diabox still do its own 60 minute countdown before giving readings?
 
I use the same combination of Diabox & Librelink. Both work independently as a CGM.

But I turn the alarms off Librelink (except lost signal.) The widget function & calibration feature are great.
Yes Diabox does the 60 minute startup from the first scan of a new sensor..
I normally start Diabox straight after librelink..
 
Westley said:
For those that have Diabox and LibreLink working together, have any of you successfully started Diabox after the 1 hour startup period of LibreLink? and if so, does Diabox still do its own 60 minute countdown before giving readings?
Click to expand...
I always start DiaBox after the 1 hour warm up of LibreLink, not before. There's no warmup period but is sometimes does struggle picking it up.
When I start DiaBox I first start the new sensor, then I go to 'apps', find the DiaBox app, force stop it and empty cache. Then I restart my phone.
Sometimes it needs multiple times for it to work, and I have no idea which of those actions does the trick so I simply perform them all.
 
For those successfully using both, which Android are you on? and which version of Diabox? I'm on Android 13, and wondering if it's related to the changes in Bluetooth low energy.

I tried once more, and again, scanning with DB after LL is started and running breaks the BT connection with LL, and fails to start the connection with DB, leaving me with no alarms.
 
Westley said:
I tried once more, and again, scanning with DB after LL is started and running breaks the BT connection with LL,
Click to expand...
From what I understood from the DB Facebook group you can't have BT running on both apps, so to use DB you'll have to disable BT for LL.
But things might be slightly different in the UK where L2 sends BG to your phone and not just alarms like in my country.
 
That seems reasonable, and I was expecting to only be able to have the BT connection with one, but @Jaylee and @SimonPC seemed to be saying they keep both?

I'd be happy with LL as NFC only, and the alarms only on DB with BT, but just can't get this working.
 
Westley said:
It seems I spoke too soon, and the problems are continuing!
I realised Xdrip+(via OOP2) only gets the data every 5 minutes, which isn't ideal.
Click to expand...
Sorry I missed the post, and realise I'm going back quite some way but I just wanted to add that using Juggluco to connect to the sensor and forward the data to XDrip+ by emulating the patched version of librelink will provide 1min data to XDrip+ (you need to enable 1min data handling in XDrip+ too)
 
I always start a new sensor with LL and wait the 60 mins and then connect with Diabox. Sometimes it takes a couple of hours before things settle down before both apps will read every minute.
 
I used to restart, clear cache, cycle BT etc etc but now I just wait a bit and it always connects after 1 or 2 hours.
 
eventhorizon said:
I used to restart, clear cache, cycle BT etc etc but now I just wait a bit and it always connects after 1 or 2 hours.
Click to expand...
I'll see if I can find enough patience to try this with my next sensor!
It's annoying because you can't start calibrating DiaBox before it has a good connection with the sensor, and I always hope to get the calibrating hassle over with as soon as possible.
 
How fast does the glucose number refresh on your smartwatch ?
Every minute, as in Librelink?
 
Hi.
I'm a newbie. Just installed LL (never/haven't used it yet). My dream is to get my continuous readings on a smartwatch.
Is the easiest way to get the numbers (and trend arrow) on the watch is indeed xDrip via Diabox?
No need for LibreLinkUP (LLU)?
If so, how do I config Diabox and xDrip to communicate ?
Btw, I can't find the app (Diabox) in the Play Store. it's installed as APK only? Which version?
Thanks.
Vic.
 
Last edited:
You must log in or register to reply here.
Menu
Log in
Register
Cookies are required to use this site. You must accept them to continue using the site. Learn More.…