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
{{ message }}
This repository has been archived by the owner on Apr 6, 2024. It is now read-only.
I have the problem that the data from Diasend in Nightscout are shifted by one hour, the CGM values which are sent directly from xDrip (Companion to CamAPS) to Nightscout are correct.
Unless you specify the TZ as only the offset to UTC (e.g. UTC-01:00, the information about daylight saving time (DST) is implicitly known. I.e. don't use GMT+01:00 but use Europe/Berlin instead.
I have the problem that the data from Diasend in Nightscout are shifted by one hour, the CGM values which are sent directly from xDrip (Companion to CamAPS) to Nightscout are correct.
Nightscout runs as a webapp (forked from https://github.com/burnedikt/cgm-remote-monitor) at Northflank with an Atlas Mongo DB. My time zone is Germany (UTC+1 or GMT+1).
I think setting the TZ variable would fix the problem, but unfortunately it doesn't say in the examples what value I have to assign to it.
How does the whole construction actually behave during the daylight saving time changeover?
The text was updated successfully, but these errors were encountered: