You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
Time of screenshot: 16:07 local time. mmconnect data gets time-tagged 1 hr in future.
The text was updated successfully, but these errors were encountered:
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?
Time of screenshot: 16:07 local time. mmconnect data gets time-tagged 1 hr in future.
The text was updated successfully, but these errors were encountered: