Does XDrip+ accept and display historical data via Intent? Other options?

[simonpickering]

I often get comms failures on my sensors, I've no idea why this happens. It doesn't appear to be a phone failure (the Libre2 Reader also reports that there's no comms), though I've not ruled out the phone breaking the sensor when it's first scanned to make Juggluco listen to it.

In any case with a failed sensor if I then manually scan it with Juggluco, it would be great for XDrip+ (which I use for the data display and prediction features) to accept the NFC scanned data and backfill its screen. This may be a thing that needs to be enabled in Juggluco (I don't know whether it broadcasts and Intent when NFC scans occur), but thought I'd ask whether such Intents are accepted by XDrip+ in any case?

Part of the value of the sensors is that they can alert you if you're running low/high (especially overnight) but during the day (if I can't replace a sensor ASAP) I derive massive value from being able to see BG trend data alongside insulin and carb intakes and their absorption curves.

This may already be possible by some combination of settings, so I wanted as pose the question.

I guess one thing that might work out be to make XDrip+ the follower and have Juggluco provide an "XDrip+/Nightscout" webserver itself. I'm not sure whether that setup would work correctly so am open to suggestions.

[Navid200]

You are using an app other than xDrip as a CGM. Have you asked them to address this?

[simonpickering]

I was trying to understand what methods XDrip+ has for accepting historic data, and separately about what capabilities Juggluco has for providing historic data on an NFC scan. I thought someone might know off-hand, and that this was the right place to ask such a question.

Looking at the code, it appears that e.g. the "640G / Eversense" Intent is routed to NSEmulatorReceiver.java and eventually ends up calling bgReadingInsertFromJson() in models/BgReading.java and that it should accept multiple readings and reject those which conflict with existing readings based on their timestamp.

So I think that answers my question, and my next port of call is Juggluco.

If I've got any of that wrong please do let me know though, thanks :)

[PhilTU]

I presume you're using the Libre 2 patched app input on xDrip+ and sending data from Juggluco. If it were an actual patched app I think the NFC scan of the sensor would deliver 8h worth of history, so it would seem to be a juggluco question about sending history values to xDrip+

I see the juggluco site says "EverSense Broadcast: a better alternative for the Patched Libre broadcast." is that the route your using ?

[simonpickering]

Yes, that's correct I use the "Libre patched app"/"Patched Libre" from Juggluco. I was trying to understand whether the full historic data was a feature and which end of the pipeline was not doing what I had hoped. The answer is that Juggluco only provides a single data point and afaict it doesn't provide any data point (i.e. no Intent) when performing an NFC scan (see my Discussion post on the Juggluco github here: j-kaltes/Juggluco#315).

It's interesting to hear that the original app would deliver the full 8h's worth of data, which I think adds some credence to my thoughts voiced in the Juggluco discussion post above that an NFC scan is an "event" and therefore packaging up the data from that event and forwarding it makes sense (vs the suggested alternative of looking at the Juggluco provided web interface, which I think will conflict with the XDrip+ webinterface which I use with my Garmin devices.

Are there alternatives? I used to use OOP2, but for reasons I don't recall I started using Juggluco as the CGM scanner (though I never look at that app aside from when I need to add a new sensor/look at error messages), perhaps returning to OOP2 would make more sense?

Regarding the suggestion of moving to the EverSense Broadcast (which is a separate issue), I did indeed try this as suggested as the "Libre patched app"/"Patched Libre" Intent broadcast is deprecated and will be removed from Juggluco at some point in the future.

However, this also doesn't provide historic data on NFC scan and additionally results in XDrip+ only plotting a data point every ~3min, rather than 1min data if supplied via "Libre patched app"/"Patched Libre" (I also quite like the dual display I see in XDrip+ atm, with the little white raw data dots + the blue "processed" values as I mention in the ticket I've opened requesting that the "Libre patched app"/"Patched Libre" Intent is not removed as unless there's some maintenance burden I can't see something that works should be removed because of what the downstream consumer (in this case specifically XDrip+) chooses to do with the data: j-kaltes/Juggluco#314

There's a patch which one can apply to apparently change this behaviour in XDrip+ (the patch code can be seen in the Juggluco help on the Settings > Exchange Data > Help page), though I don't think this is all that useful for most users who won't want/are not able to patch and recompile the code (I include myself in this group - I can, but I don't particularly want to have setup the toolchain again just to do this and then maintain my own build setup going forwards. I've not yet looked to see if this patch has been suggested in the XDrip+ project, which would be a better option if acceptable, though I would still prefer to keep the "Libre patched app"/"Patched Libre" Intent).

[PhilTU]

OOP2 and direct Libre 2 connection to xDrip would give standard NFC scan capability.

If juggluco was providing web interface could the Garmin collect from there and have xDrip+ as a Nightscout follower reading data from juggluco. Apparently "xDrip+ performs limited (24 hours) data backfilling from Nightscout." https://xdrip.readthedocs.io/en/latest/install/nightscoutfollower/#nightscout

[simonpickering]

I wasn't clear with the Nightscout Follower whether it just follows (read-only) or whether it also allows read-write access so data entered via XDrip+ (i.e. finger prick test, carbs, insulin) can be uploaded and made available to the Garmin. I'll do some digging through the documentation.