g7 experimental #25
Closed
g7 experimental #25
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
Trend is not decided yet either. |
Contributor
Author
codebymini
pushed a commit
to codebymini/LoopWorkspace
that referenced
this pull request
Sep 2, 2025
Add Dexcom One+ to allowed prefix
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an experimental version of Dexcom G7 integration for Loop. You should be able to add the CGMManager, and it will auto-connect to your G7, as long as you have the native G7 app running and paired to a sensor. To switch sensors (like when pairing a new one), for now you will need to remove the cgm manager, and re-add it, which is just a few clicks. It will be more reliable if you do this after you pair your new sensor in the G7 app. Eventually it should auto-follow, but that's not done yet.
Since this is fresh reverse-engineering of a new protocol, it's still possible that dangerous errors in decoding are still present. Generally the data matches what is shown in the Dexcom app, and I believe calibrations are detected properly, but there are probably error states that aren't handled correctly, and those could be parsed as incorrect BG readings, leading Loop to deliver incorrect/unsafe dosing. Because of that, I'd recommend that testing be done only with the simulator pump, and not a real insulin delivery device.
The UI is very rudimentary, and will change quite a bit, so no need for feedback on that yet.