Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hints on usage of iob: Insulin-on-board? #86

Open
bjornoleh opened this issue Oct 14, 2023 · 2 comments
Open

Hints on usage of iob: Insulin-on-board? #86

bjornoleh opened this issue Oct 14, 2023 · 2 comments

Comments

@bjornoleh
Copy link

I did read the manual about the limitations of IOB data added as an “activity”. Still wondering if it’s ok to ask about how people have made use of this. Perhaps someone come up with a hack to get it displayed in NS somehow?

Thanks!

@jwoglom
Copy link
Owner

jwoglom commented Oct 14, 2023

@bjornoleh I don't think it's currently possible to get the IOB amount to show in the Nightscout UI, however you can get the value from the API by making a request to NIGHTSCOUT_URL/api/v1/activity.json?find[activityType]=tconnect_iob, which returns, e.g.:


[
  {
    "_id": "62d85a6d25fef6066b28ac6f",
    "activityType": "tconnect_iob",
    "iob": 14.42,
    "created_at": "2022-07-20 15:30:28-04:00",
    "enteredBy": "Pump (tconnectsync)"
  },
  ...
}

It's probably possible to patch Nightscout to show this, but I haven't looked into it heavily.

@bjornoleh
Copy link
Author

Thanks!

I also wonder if it would be possible to write IOB data as devicestatus instead? Perhaps as a Loop or OpenAPS devicestatus? Then I imagine it could be displayed in one of those pills, and the data would hopefully also be propagated to the IOB pill. Surely I could be missing something here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants