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

Introduce proper wear-only mode for wearos4 and dexcom g6 #3719

Draft
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

t0st
Copy link

@t0st t0st commented Oct 16, 2024

Implements #3676:

  • fix direct-connect from wearos4 to dexcom g6
  • implement nightscout upload from wearos4 lte
  • prevent data transfer to mobile if only_ever_use_wear is active

@thepartisan
Copy link

@t0st I am using this PR as basis for an attempt to add G7 support. Could you maybe quickly describe the pairing process for G6 for me here? After porting some more shortId-related things from app to wear I still struggle a bit here.

  • As you are using the phone slot, will you pair G6 autonomously without prior phone pairing?
  • Which name does G6 advertise?

@thepartisan
Copy link

@Navid200 , reaching out to you because I saw you commit quite a bit in the wear section...
Do you have any resource that describes how the pairing of app vs wear is supposed to work (design-wise)?
Do I pair the sensors completely new with wear app? I've started an attempt to integrate G7, but I am stuck at the initialization of pairing now and saw that for app there is "the plugin" feature. Do you know if this is this something I would need for G7 or should it theoretically also work based on the existing code?

Is there any interest/place for technical discussions?

@Navid200
Copy link
Collaborator

@thepartisan Please limit posts in a PR to what is specifically related to that particular PR.
For everything else, please use Discussions.

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.

3 participants