Getting updates only every 15 minutes

[alanruttenberg]

I'm not sure this is a LinkUpConnect issue or whether it is an issue on the side of Abbot's servers. But for some time now, probably since the last update or so, instead of getting updated values every minute I now seem to get them only every 10-15 minutes or so. The debug log shows it doing a query every minute but now many times in a row it returns a value with the same timestamp and same value. After a few minutes (5?) I get the red exclamation mark indicating that a value is old which persists until it manages to get a new reading.

I use this to hook up with xdrip+ and it's made xdrip+ much less useful to monitor trends, as it already lags and with the 15 minute delay between readings it's far enough behind that I find myself frequently opening the libre3 app, which is annoying because it is so slow.

I downloaded my data from libreview to see whether it might be that the libre3 app wasn't sending data as frequently, and it appears not. I don't see any interruption in the usual every 5 minute readings.

Any thoughts appreciated.

[cmtjk]

Hi @alanruttenberg, I can't reproduce the issue and LinkUpConnect works fine on my side. But I remember having the same issue 1-2 times but it got sorted out by itself. LinkUpConnect does nothing special and just passes the data it gets from the API but their might be occassions where the response is cached 🤷‍♂️ I'll mark this issue as invalid for now but please feel free to comment if the issue persists.

[alanruttenberg]

Interestingly there was a change when I changed sensors yesterday. Now I'm getting readings that, at 5 minute granularity, 5,10,20,25,30. In other words enough data to get two samples 5 minutes apart then one with a delay of 10 minutes, repeating. I've no idea why a different sensor would matter. I don't have information more specifically about the frequency at which I get new data from LinkUpConnect. Is there a way to dump the debug log for some period of time?

[alanruttenberg]

It recently became so bad that I invested another effort in researching options and it turned out Juggluco supports the Libre 3 and replaces the Abbott Libre 3 app. Juggluco can also send data to Abbott's servers, and I can use LibreLink and see the values. With that setup there is no delay at all (more than a minute) between the reading happening and LibreLink showing the reading. So there's definitely something in the Abbott chain that is causing the delay. Given that there is no longer latency in LibreLink the suspicion is now on the Abbott Libre 3 app, but I suppose there could also be differences in how Libre 3 and Juggluco apps are interacting with the API.

Juggluco locally broadcasts to xdrip, so I don't need LinkupConnect any more, but I thank the author for the most of a year use I made of it. In case it is of interest, there's also a fork of xdrip (https://github.com/jakobheyman/xdripJH) that updates each minute instead of each 5 minutes. The combination of Juggluco and xdripJH means I can completely avoid Abbott's software and functions vastly better.

[alanruttenberg]

You know a lot more about the details than I do and I appreciate the information and any other insights you can offer. BTW, is Trident a different name for the Libre 3 app, or is it something else? I can relate my experience with the new setup.

• xDrip does it's own smoothing. I'm not sure if that's modified in xDripJH. However xDripJH seems to lag substantially less than it used to when I was relying on Abbot's software and LinkUpConnect.
• The one minute readings show up in xDripJH as well so you can compare. To my eye it looks like the sensor is using using a predictive algorithm that overshoots when there are changes. You can sometimes see what look like oscillations on the scale of a few to dozen minutes in the direct from meter readings as compared to the xDrip smoothed estimate. I'm happy to upload a screenshot if that interests you.
• The GMI estimations in Libre 3 were consistently higher than those that xDrip calculates, by between .1 and .3. My actual A1C measurement just recently taken was .3 below the xDrip estimate.
• I do regular comparisons to finger sticks - many in the days after changing a sensor and periodically for the rest of the time. The readings track the xDrip curve very well - at least as good as they did in the Libre 3 app. I don't use xDrip calibration.
• In deciding how much insulin to dose I find the ability to know the rate of change by looking at xDrip to be invaluable and this just isn't feasible with the Libre 3 interface.
• Both Juggleco and xDrip have persistent notifications (I'm on android), as well as a status bar glucose number, so it's easy to glance at my phone to see what's going on. xDrip has much more flexible alarms, as well, including the ability to buzz me when the rate of change is above some threshold. I am type 2, BTW.
• I had to mess around to even run Libre 3 on my android phone, which isn't officially supported and moreso because I don't have google play on my phone. I use microG for privacy reasons. In fact, when I first got the meter I bought a second phone (old iPhone) and carried it around with my regular phone, just for the meter readings. Getting things to run on my main phone, then getting LinkUpConnect and xDrip were major improvements. This new regime is even better.
• The Libre 3 app was extremely slow at times, taking 10 or 15 seconds to update when I opened it up to check. There's also the slow upload issue which made xDrip hard to use effectively.
• The only concern I might have is if Juggleco is transmitting different data to the their servers than the Libre 3 app would, since my Dr. looks at that. OTOH, by my estimate the current method is just as accurate, and I'm guessing not. Do I have it right that the Libre 3 app is likely just sending up the "raw" values and receiving the recalculated values?
• I don't use WebFollower, I use the Libre(patched app) setting. As I understand it, I no longer rely on the network to relay the meter readings to xDrip.

So overall it may be "illegal" and "totally wrong" in some senses of the word, but in practice I find the open source solution to be accurate and much more flexible and useful in maintaining my health.