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

there should a timeout period after stopping a sensor session in order for the command to be properly registered by the transmitter #476

Open
sergiu-fintineru opened this issue Nov 27, 2023 · 2 comments

Comments

@sergiu-fintineru
Copy link

I have encountered the following problem.

I stopped a sensor session that was not going well. I waited 5 minutes in order for the transmitter to register the change and I saw the "Session stopped" in the transmitters' details. I initiated a new sensor session, I introduced the calibration code and waited the warm-up period. However the sensor age as shown in the transmitters details was the old one. The blood sugar readings were incorrect since I was using a sensor with a different code than the previous one, somehow the transmitter did not acknowledge the new sensor session or the new code.

@paulplant
Copy link
Collaborator

Dexcom G6? Anubis? One? Are you using the transmitter with "Read from Dexcom App" mode and also using Dexcom app in parallel? Or is the transmitter only connected to xDrip4iOS?

@sergiu-fintineru
Copy link
Author

Anubis transmitter. It is only connected to xDrip4iOS.

It's true that I change sensors fast, but I still think this is an issue.

One should not be permitted to start a new sensor session until the transmitter has registered the stop sensor command.

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