Skip to content

Add Eversense CGM to Trio (open beta, feature-branch)#982

Merged
dnzxy merged 3 commits intonightscout:feat/dev-eversensefrom
bastiaanv:feat/dev-eversense
Feb 21, 2026
Merged

Add Eversense CGM to Trio (open beta, feature-branch)#982
dnzxy merged 3 commits intonightscout:feat/dev-eversensefrom
bastiaanv:feat/dev-eversense

Conversation

@bastiaanv
Copy link
Copy Markdown
Contributor

@bastiaanv bastiaanv commented Feb 20, 2026

Adding EversenseKit as new CGM option for Trio.
And syncing with dev branch

Fresh PR based on feedback from: #978

TODO's:

@bastiaanv
Copy link
Copy Markdown
Contributor Author

@marionbarker Regarding your comment here: #978 (comment)

Maybe this PR helps the Eversense user?
#981

@marionbarker
Copy link
Copy Markdown
Contributor

Test

Started with bastiaanv / Trio branch: feat/eversense
Updated EversenseKit to commit: e870c22c

Add Eversense as CGM

  • Delete CGM
  • Add CGM and select Eversense
  • Works nicely

Copy link
Copy Markdown
Contributor

@marionbarker marionbarker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code review

Some of the updates are to bring dev up to date so the file changes that are strictly due to adding Eversense are mixed with updates to dev.

This would not be my choice but I leave this up to the Trio developers to decide.

I think it would be better to stick with PR #976, make the fixes there and then after merging that, update the feat/dev-eversense branch by merging in dev.

Test

The test using this code plus selecting Eversense commit e870c22c is good to go.

@marionbarker
Copy link
Copy Markdown
Contributor

Alternatively - have someone merge dev into nightscout / Trio branch feat/dev-eversense and then this PR would be just what is needed to add Eversense to Trio.

@bastiaanv
Copy link
Copy Markdown
Contributor Author

@dnzxy or @MikePlante1 Would one of you be able to merge dev into the feature branch?

@MikePlante1
Copy link
Copy Markdown
Contributor

MikePlante1 commented Feb 20, 2026

Okay, latest dev is now merged into the feat/dev-eversense (and feat/dev-medtrum) branch in nightscout/Trio

It looks like AccuChekKit‎ and MedtrumKit snuck their way into your PR'd feature branch, though, @bastiaanv

@bastiaanv
Copy link
Copy Markdown
Contributor Author

Not as clean of a PR as I would have wanted :)
fixed now

Copy link
Copy Markdown
Contributor

@marionbarker marionbarker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for cleaning up the repository branches to provide a clean diff.

My only question (and this can come later) is do we need to add anything to onboarding.

@dnzxy
Copy link
Copy Markdown
Contributor

dnzxy commented Feb 21, 2026

My only question (and this can come later) is do we need to add anything to onboarding.

You do not onboard any device during Trio‘s onboarding. You only select a pump model to get to basal increments via a hard coded enum based list of available increments. So, no, I don’t think so.

Merging this if @bastiaanv is happy and ready, and another Trio dev (@MikePlante1 , @kingst ) approves.

Copy link
Copy Markdown
Contributor

@MikePlante1 MikePlante1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code review looks good.
Browser builds fine.
Xcode builds without linting.
✅ LGTM

@bastiaanv
Copy link
Copy Markdown
Contributor Author

bastiaanv commented Feb 21, 2026

I am happy and ready 😄

@dnzxy dnzxy merged commit 6916c87 into nightscout:feat/dev-eversense Feb 21, 2026
2 checks passed
@sergiu-fintineru
Copy link
Copy Markdown

Maybe it's a dumb question, but can this branch also be used with Loop?
I've seen Marion posted a screenshot from Loop having Eversense as the CGM.

@bastiaanv
Copy link
Copy Markdown
Contributor Author

Hey!
The LoopWorkspace has a branch called feat/eversense. That includes the latest eversense sha

@marionbarker
Copy link
Copy Markdown
Contributor

@sergiu-fintineru

For more information, see LoopDocs.

https://loopkit.github.io/loopdocs/version/development/#table-of-active-branches

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

Successfully merging this pull request may close these issues.

5 participants