Add Omnipod 5 IOB to xDrip

[gth001]

This is a feature request to integrate with the Omnipod 5, to bring IOB, bolus, and carbs in from the Omnipod app.

This is a feature that the Gluroo app currently has. It would be cool if xDrip did the same.

How the function would work:

• User provides ISF, CR, target BG settings from Omnipod app to xDrip
• CGM provides BG
• User grants xDrip "Notification access" permission to read all notifications on the phone
• IOB = xDrip reads the IOB: 2.0u value from the Omnipod notification every ~5 minutes
• estimated bolus = any unusually large jump in IOB
• estimated carbs = CR*(bolus - (BG - target)/ISF))

Here is an example of an app that does this:
Gluroo Omnipod 5 IOB integration documentation (it's a bit outdated and doesn't mention the estimated carbs function they added yesterday)

[Navid200]

Can you provide screenshots of the Omnipod notifications?

[gdc27health]

I too use an Omnipod 5. An IOB complication would be awesome to be able to show on a watch face.

Here is a screenshot of the Omnipod 5 Notification. From a Galaxy S22 Ultra. Sorry for the Weather and Dexcom notifications on the same screen

[gdc27health]

[Navid200]

@gdc27health Thanks

Would you also please expand that Omnipod notification and show any detail it may include?

[gdc27health]

See how the arrow on the right points up? That means that this is expanded. There is no other information.

[bart2]

I took a stab at implementing this feature: #2928 (at least the IoB part).

[gjbadros]

Imitation is the most sincere form of flattery -- thank you! :-) (We're fans of XDrip, too!)

[gth001]

Is this feature working for anyone? It's not working for me. I can scrape the IOB from the Omnipod notification using Tasker or using Gluroo, but not with xDrip+. Happy to troubleshoot/test. Just wondering if the feature is supposed to work yet, since the toggle is available.

[bart2]

Lets try to troubleshoot this.

To double check, both "Enable IoB reporting in API" and "Fetch IoB from companion app" toggles are selected in "Inter-app settings" section?

Also, can you open chrome on your phone and go to "127.0.0.1:17580/pebble" and take a screenshot of the output?

[BillShepp]

I'm seeing IOB as part of the response from "127.0.0.1:17580/pebble". Note that I had to turn on "xDrip Web Service" from Inter-app settings.

Is there a way to expose the IOB data as part of the xDrip Complication Provider?

[bart2]

@BillShepp, I'm not familiar with xDrip Complication Provider. Can you explain how are you accessing it?

[gth001]

(Original question poster here)

Yes, I see the iob: number at 127.0.0.1:17580/pebble, and it's correct.

However, I don't see IOB on the xDrip main screen.

What I currently see in xDrip

(notice there's no IOB displayed, no green insulin markers/line, and the purple prediction line isn't taking IOB into account, and the "low predicted" alarm doesn't take IOB into account):

What I expected

(a screenshot when I was using Gluroo to scrape the IOB from Ominpod into xDrip. notice IOB is displayed, there are green insulin markers/line, and the purple prediction line takes IOB into account, and the "low predicted" alarm takes IOB into account):

[BillShepp]

I believe it’s a feature of the xDrip+ codebase (see https://github.com/jamorham/xDrip-plus/blob/master/Documentation/WatchGuide.md). With most watchfaces that allow configuring the complication I can choose “xDrip Complication Provider” under the category “xDrip Prefs” from all the complications available on the watch.

…

On Sep 4, 2023 at 2:00:36 PM, bart2 ***@***.***> wrote: @BillShepp <https://github.com/BillShepp>, I'm not familiar with xDrip Complication Provider. Can you explain how are you accessing it? — Reply to this email directly, view it on GitHub <#2728 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABEC7GKD5KT6DNKJUW4AZHLXYY6PJANCNFSM6AAAAAAVZLWISM> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>

[gitanO0]

Is this working for folks? I just got on an Omnipod 5, have granted the notification access, and enabled the setting but am not seeing any IOB numbers in xdrip.

I'm seeing the correct IOB on my fitbit so I guess the web service number is interacting correctly, just not the main graph? @bart2 ?

[gth001]

No, it never worked. I would like to share my disappointment with you. By that, I mean the feature description isn't at all what most people would interpret it to be. It should honestly be renamed to "standalone omnipod 5 to pebble/fitbit API pipeline" or something. Your Omnipod 5 IOB never actually goes into the multitude of IOB functions and variables in XDrip at all. Its only functionality is to create a new external variable for the Pebble smartwatch endpoint, so a smartwatch developer can pull the value to complications on smartwatches. However, apart from that, there is no functionality for users like you and me.

If you would like to have your IOB actually pulled into xDrip, show up as mini-boluses in your graph, affect your prediction kinematics and soforth, someone DID implement this. It's called the Gluroo app. It will emulate a nightscout instance, send your IOB from the Omnipod 5 notification to it, and then xDrip will slurp that up from said nightscout instance. It works pretty well and hopefully xDrip implements it natively some day. But no rush, Gluroo+xDrip working in tandem works great for now. Super useful to diabetics on Omnipod.

[gitanO0]

will look into this, thx!

[gitanO0]

I've got this sorta kinda working. I have the Gluroo app sending data to my nightsout site and I see bolus info as my IOB but do not see the basal doses or my full IOB (basal + bolus). I'm pretty new to this so maybe I'm not getting the big picture here but I'd like to see in Nightscout the same IOB I'm seeing on the Omnipod 5 app and the Gluroo app.

I also now have that bolus info going back to xdrip+ as well but again, would like to see all the insulin delivery info including the correct IOB and not just the bolus'.

@gth001 is there something I can configure to do that?

Also, the Gluroo app on my Android phone is force closing a lot. I've tried different things to see if I can fix that to no avail.

[gth001]

As for the force closing, I don't know, perhaps try setting the apps battery optimization to "unrestricted" in Android settings. Android might be trying to close it to save battery, but it needs to always run.

As for the IOB, at first it's inaccurate, but after 5+ hours it should start getting pretty close.

The way it works is that it reads the Omnipod 5 notifacation every 5 mintues, IOB:1.25U, IOB:1.2U, IOB:1.15U waiting for it to increase. Then it sees IOB:1.65U. This causes it to log a 0.5U bolus into Nighscout (which xDrip picks up).

[imarotte]

Im interested in connecting my Omnipod5 to xdrip as well but it sounds like it's not actually implemented yet. Are there any plans to add this in the future?

[gdc27health]

Use the GlucoDataHandler app available on the Google play store He reads the xDrip data passes IOB and Acton more

…

On Sun, Sep 15, 2024, 6:02 PM Isaac Marotte ***@***.***> wrote: Im interested in connecting my Omnipod5 to xdrip as well but it sounds like it's not actually implemented yet. Are there any plans to add this in the future? — Reply to this email directly, view it on GitHub <#2728 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A63YKNWCYXTUOEJHVYZ6UOTZWYGZXAVCNFSM6AAAAAAVZLWISOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANRVGQ2DCNQ> . You are receiving this because you were mentioned.Message ID: ***@***.*** .com>

[imarotte]

@gdc27health I appreciate the response, but I don't think this addresses any of the issues in this thread.
The issue is that xDrip does not get the IOB data from omnipod.