• Guest - w'd love to know what you think about the forum! Take the 2025 Survey »

Juggluco to Xdrip configuration

S

Sizewell

Member
Messages
16
I was forced to change from libre 2 to libre 2+ so I updated xdrip and OOP2 to latest versions but found the bluetooth connection was very unstable, it was more missed signals than actual connections. I also use Xdrip to communicate data to my watch.
I tried installing Juggluco and just scanned through Juggluco and connection was established immediately and remained very stable for several days. I did not make any configuration changes in Juggluco or xdrip (other than turn off jugglugo alarms). Last night I lost the BT connection and after fiddling about, I managed to re-establish a connection.
I have googled for Juggluco to Xdrip settings but have not found anything has anyone any idea what the ideal settings should be ie what should be the hardware source, I currently have LIbre bluetooth.
Next I noticed that Juggluco can send data to Libreview, I currently use a reader and scan 3 times a day for data for my medical team. It would be much easier if Juggluco can automatically send it.
 
I use the following:

Juggluco > Settings > Exchange Data > Patched Libre (which is crossed out)
XDrip+ > Settings > Hardware Data Source > Libre (patched App)

There is talk from the developer of Juggluco of removing the "Patched Libre" Intent broadcast (which is why it's crossed out in the UI), I've opened a Discussion Ticket on GitHub to ask why this is planned, hopefully it won't happen as the suggested alternative is not very useful for me (and at least one other commenter): https://github.com/j-kaltes/Juggluco/discussions/314

I don't use LibreLink at all so can't advise you on how to set this up, but my understanding is that it works. There might be something useful in the discussion posts on github (see link above), otherwise there seems to be a reasonable amount of documentation: https://www.juggluco.nl/Jugglucohelp/libreview.html

Let us know how you get on :)
 
Should I have OOP2 still running?
I made those changes and Juggluco is working but Xdrip is not although I can scan with xdrip.
 
Hi,

I got Librelink, Juggluco & for some reason xDrip running in tandem on my phone?
Each has thier benefits for me..
Librelink runs independent, just sending data to Libreview.
Juggluco sends to my watch & acts as a quick view widget on my phone.
XDrip? It only (at least for me.) updates every 5 minutes as opposed to juggluco. (Every minute.) xdrip takes the data direct from juggluco I could never get the 00P2 app to work for me…
I reinvested in xdrip when a sensor didn’t seem right once & I couldn’t find a way to calibrate it in Juggluco. & Diabox was getting unreliable for me? (With the watch & in general.)
But it does have a nice “screensaver” with my BG levels & graph when the phone is on charge. So I kept it.

Lol, you probably just realised.
I’ve tried all the apps out.. ;p
 
Sizewell said:
Should I have OOP2 still running?
I made those changes and Juggluco is working but Xdrip is not although I can scan with xdrip.
Click to expand...
You don't need OOP2 running as the encryption is removed by Juggluco.

Can you check what the settings are on both Juggluco and XDrip+ as per my post above?
 
SimonP78
Xdrip is working fine. It was the logs which was throwing me.
I have now uninstalled OOP2. One other question, when starting a new sensor is it the same as before ie scanning with a reader to start sensor?

Jaylee
OOP2 was working perfectly for me with Libre 2 but very badly with 2+.
The ticked boxes of Xdrip broadcast & Glucodata broadcast is that for your watch or are they both needed in general? as I have not got them ticked at the moment.

Thanks a lot guys for your help :)
 
Sizewell said:
Jaylee
OOP2 was working perfectly for me with Libre 2 but very badly with 2+.
The ticked boxes of Xdrip broadcast & Glucodata broadcast is that for your watch or are they both needed in general? as I have not got them ticked at the moment.

Thanks a lot guys for your help :)
Click to expand...
Yep, I feel the updated librelink in readiness for the 2+ may have caused issue with the OOP2 app??
Diabox struggled for me too.. (separate issue.& not relevant here.)

Edit: the watch? I got 2 apps running on that. "Gwatch wear." & juggluco. Both do different complications on the watchface?
Juggluco seems to do a larger BG interface.

Best wishes getting things to play nicely.. :)
 
Last edited:
Sizewell said:
Xdrip is working fine. It was the logs which was throwing me.
Click to expand...
Great :)

Sizewell said:
I have now uninstalled OOP2. One other question, when starting a new sensor is it the same as before ie scanning with a reader to start sensor?
Click to expand...
Apparently one can start a sensor with Juggluco, however I always use a Reader so I can post log data to Abbott in case of a failure. As a last resort (while abroad without a reader) I've started with the Librelink app for similar reasons, though I far prefer the reader as it won't phone home without me transcribing information.

Sizewell said:
Thanks a lot guys for your help :)
Click to expand...
You're welcome :)
 
@SimonP78
Hi, I started a new sensor this evening and had problems with it. What I done was scan with the reader to start new sensor, then after 1 hour I scanned with Juggluco. I was getting sensor error, but after a few scans it started ok. But on the sensor page it showed unknown address. After a bit of fiddling about and pressing the terminate button and rescanning, It showed the address, but still getting occasionally no connection. Can you kindly confirm what the starting new sensor procedure step by step is?
Many thanks.
 
When Juggluco sees a new sensor it automatically resets the calibrations, etc., in XDrip+ (or probably XDrip+ hears that there's a new sensor s/n and resets itself).

I don't know how to start a sensor with Juggluco as I've never tried (though I imagine it will happen automatically if one scans an un-started sensor with Juggluco), but your sensor has already been started, so I don't think this step is needed (or did I misunderstand what you wanted to know?)
 
So, I done mine correctly. But still getting no connection on occasions. I find at the moment that after several scans with no joy, I reboot the phone and then it works ok. I must say, I do not find the 2+ an improvement. I much preferred the 2, which ran very smoothly for me.
 
I don't really think it anything to do with the setup (i.e. Juggluco + XDrip+ vs Librelink), though I've not checked back-to-back setups (not that this is really viable anyway) but rather than the sensors are now not as good as they once were. I think the rot set in before the 2+ came out though. Certainly the early 2 sensors seemed to work quite reliably.

I went through a long period perhaps 2 ago (iirc) where they simply worked (in terms of comms, they never worked very well and nor do they still in terms of calibration, but XDrip+ helps there to make them usable). They worked reliably for such a long time that I stashed away my MiaoMiao2 thinking I'd not need it ever again but that I ought to put it somewhere safe "just in case". Unfortunately I have wanted quite often since then and I've no idea where my super-safe storage location is!

I also get drop-outs, sometimes only a few minutes, though more likely to be an hour or more (sometimes 8h+) before it comes back to life - with the 8h+ ones I'd usually have got on and changed the sensor thinking it was completely dead had some of these not happen while I was at work or asleep. They are definitely a case of the sensor not producing data as I can scan for BLE devices and see that there are no broadcasts in these cases.

I think the sensors work marginally better (as in fewer drop-outs) if I don't scan them (when they drop-out), so I wonder if there's some link to my mobile phone (chipset/power/etc) though I only scan the sensor once to pair it with Juggluco these days. But this may simply be an effect of different batches of sensors, it certainly doesn't stop the failures and any imagines effect is very marginal, so perhaps just a figment of my wishful imagination wanting to resolve the annoying habit of them not working.

The only other possibility, and I've not got around to investigating this, is that the sensors don't like something that Juggluco does. My assumption was that the sensors broadcast and the listener app is completely passive, I may be wrong. With that said there are no endless complaints about failures on the github page, so I'm still at a bit of a loss as to the true source of the failure mechanism.

I should probably try another phone, but I don't need to change now and the faff of carrying around two phones for an extended period of time (i.e. long enough to have some confidence in any change in behaviour) doesn't appeal much (until I'm part way through a batch of failures that is!) :)
 
Sizewell said:
So, I done mine correctly. But still getting no connection on occasions. I find at the moment that after several scans with no joy, I reboot the phone and then it works ok. I must say, I do not find the 2+ an improvement. I much preferred the 2, which ran very smoothly for me.
Click to expand...
Did you try terminating the previous sensor?

I also have a therory that the phone can still get confused with the old sensor even when it's ended & possibly in BT range???
 
No, I did not terminate the previous sensor. but I did a terminate after I saw Unknown address in the sensor settings.
In future I will terminate the old address. Many thanks.
I have also moved the envelope of old sensors to another part of the house.
 
You don't need to terminate the previous one, you can run both in parallel, I've done this in the past with a failed sensor that has come back to life/one about to reach end of life. In this case it happily reads both sensors, and as long as the first one continues producing data will send that to XDrip+. At some point/under some condition it will swap to the second sensor - this certainly happens once the first sensor reaches end of life and/or if it's offline for some extended period, but I've not really paid much attention from this point.
 
SimonP78 said:
You don't need to terminate the previous one, you can run both in parallel,
Click to expand...
I would agree with you..
To be fair, I’ve done a crossover/changeover like this without too much trouble on my device.
Juggluco reflects the 2 sensors on the app & my watch. But eventually the old sensor drops out

I’ve just learned to try & keep the BT noise to a minimum?
I theorise the battery life on a Libre could last a month?
It’s just they are only designed to operate within parameters for 14 days with the L2 & 15 with the plus..
I used to get an extra 8 (maybe 12?) hours out of the Libre 1 using a Bluetooth bridge & xDrip. Experimenting & keeping a close eye with my meter, when I was self funding? :p
 
I've not really kept track of the life spans, it's all in my XDrip+ SQL data, which I will eventually have a proper look at, but certainly the libre1 and early libre2 devices used to last for ~12h extra, though I seem to recall it was a bit hit and miss quite how much longer they would last. iirc the later libre2 devices would always last exactly 12h longer, but I think the libre2+ devices only last as long as it they are supposed to (I've not had very many make it that far so hard to tell). I may be mis-remembering mind you, the data will tell, once I ask it!

Re Bluetooth noise, they seem to be more robust to noise these days (e.g. when riding my bike with lots of ANT+ devices broadcasting in the same frequency band), though this may be a combination of using the built-in broadcast of the libre2 and later devices (as opposed to a Miaomiao2) and updates to phone firmware.
 
> but I think the libre2+ devices only last as long as it they are supposed to

My libre2+ devices go on past the official end time and Juggluco reports the 'expected end' as 12 hours later than the official end time ( although I have never got one that lasted the extra 12 hours)
 
SimonP78 said:
I've not really kept track of the life spans, it's all in my XDrip+ SQL data, which I will eventually have a proper look at, but certainly the libre1 and early libre2 devices used to last for ~12h extra, though I seem to recall it was a bit hit and miss quite how much longer they would last. iirc the later libre2 devices would always last exactly 12h longer, but I think the libre2+ devices only last as long as it they are supposed to (I've not had very many make it that far so hard to tell). I may be mis-remembering mind you, the data will tell, once I ask it!

Re Bluetooth noise, they seem to be more robust to noise these days (e.g. when riding my bike with lots of ANT+ devices broadcasting in the same frequency band), though this may be a combination of using the built-in broadcast of the libre2 and later devices (as opposed to a Miaomiao2) and updates to phone firmware.
Click to expand...
What I found with pushing the life cycle of a Libre 2 using the Diabox app was I could maybe get upto 8 extra hours out of it? Then pushing further it would somehow repeat the last 6h of it’s life on the graph..
I used the MM2 & then Bublan bubble mini with Libre 1 along with a Watlaa one watch.
When the L2 happened. In the early days I could use the Bubble mini to the watch & the BT from the actual L2 to the phone..
Then somewhere along the line. The support stopped, rendering the bridge & the watch redundant.
I now have a wear OS watch with Juggluco which can (if need be.) also work as a stand alone device if I lost my phone…?
 
Back
Top