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

Rewinding time breaks graphs #20

Open
saercnap opened this issue Dec 9, 2014 · 4 comments
Open

Rewinding time breaks graphs #20

saercnap opened this issue Dec 9, 2014 · 4 comments

Comments

@saercnap
Copy link
Contributor

saercnap commented Dec 9, 2014

I traveled backwards in timezones recently but just fixed the clock.

The time on the dexcom was ~8pm but local time was ~1pm. After fixing the clock and downloading the graph display goes to 8pm with a large gap in display. New (clock change forward) entries don't seem to be rendered properly.

Can the receiver time be used with a runtime-gathered offset rather than relying on displaytime?

@altintx
Copy link
Contributor

altintx commented Dec 10, 2014

Planning an upgrade to Dexcom driver at some point in the future that will bring this. I don't feel like it's imminent, though. Are you able to compensate at present?

@saercnap
Copy link
Contributor Author

Sounds fine provided too many don't get caught in the same position as the android-uploader timezone problems. I'll manage for now

@altintx
Copy link
Contributor

altintx commented Dec 22, 2014

It's now posting with system tz to Mongolab. Internally it's still relying on an integer timestamp. Small steps.

@altintx
Copy link
Contributor

altintx commented Jan 22, 2015

0f26ed1 will keep this from being as big a problem too.

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