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

mmconnect data has wrong timezone? #32

Closed
Trenar opened this issue Feb 9, 2022 · 1 comment
Closed

mmconnect data has wrong timezone? #32

Trenar opened this issue Feb 9, 2022 · 1 comment

Comments

@Trenar
Copy link

Trenar commented Feb 9, 2022

Hi all,
I just got a new Medtronic Guardian G4 sensor and am now finally also able to easily use Nightscout. I just installed the docker image (version 14.2.5) on a private computer.
Now, that I received the first glucose values via mmconnect, I observe that their time tag is 1hr in the future. Seems like a timezone issue (since I'm in Europe/Berlin or UTC+1). This looks a little weird since the blue-dotted predictions start after the last glucose value (see screenshot)
In my docker-compose I have set TZ: Europe/Berlin and I also chose this TZ in my Nightscout default profile.

Did anybody observe this before or knows how to handle it?

image
Time of screenshot: 16:07 local time. mmconnect data gets time-tagged 1 hr in future.

@Trenar
Copy link
Author

Trenar commented Feb 9, 2022

Duplicate of #30. Sorry guys :)

@Trenar Trenar closed this as completed Feb 9, 2022
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

1 participant