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
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?
The text was updated successfully, but these errors were encountered:
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?
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?
The text was updated successfully, but these errors were encountered: