Nightscout sync doesn't handle timezones

[LasseLiten15]

I'm not 100% sure if it's timezone related but I think so. This is how it looks in Nightscout:

Green arrow is when I turned off BG sync. Red arrows show the differences. As you can see on the left red arrow it's the same style of the CGM readings, but they have an offset for 1 hour. Maybe that can be fixed automatically by using the phones timezone or at least have an option to say which timezone it should use before sending data to Nightscout.

The alerts where the right arrow is should have been for the low before around 9 PM (21:00).

[jwoglom]

hi @LasseLiten15 , please try the latest release and see if it fixes this issue. ControlX2 previously wasn't explicitly passing your local timezone to nightscout which was likely causing this.

[LasseLiten15]

@jwoglom I saw the latest release and that timezone awareness was implemented. However it wasn't working out of the box. I'm still getting incorrect data. I thought that my Nightscout instance might have incorrect time set in the LXC (Linux Container) but since Dexcom Share sets correct time I don't think so. I can double check that.

[jwoglom]

Thanks for updating me on it still being broken -- I'll look more closely at this later this week. Hope we can resolve it soon!

[LasseLiten15]

I just logged on to my LXC instance which runs Nightscout and saw that I was on UTC which is when I should have been on CET. However, UTC now is 1h before our time and the 0,4E was given like an hour ago but it looks like it was given now:

However, I just made the change on LXC instance to correct timezone and restarted it. I don't think it would help as Dexcom Share send with correct time ven if LXC instance was set to UTC. I will update here if I see any progress on next sync.

[LasseLiten15]

@jwoglom
Nope, it still doesn't give me the correct timezone.

[jwoglom]

@jwoglom Nope, it still doesn't give me the correct timezone.

@LasseLiten15 i'll have a new release of controlx2 out in the next few days. sorry for the back and forth hopefully we get it resolved

[mcurly]

Hello, @jwoglom and @LasseLiten15 and all.

Could #137 be related to this?

Is this issue/bug observable with others?

[LasseLiten15]

Hello, @jwoglom and @LasseLiten15 and all.

Could #137 be related to this?

Is this issue/bug observable with others?

Hmm, the 1h into the future seems related but not the duplication.

[henriquejourdan]

Hello stills happens to me also. What I did to work around in Portugal timezone 1+ hour:
Set all phones to Azores time or 0 GMT and disabled automatic hour update, the set 1+ hour manually. Duplication not solved with this operation.

[LasseLiten15]

@jwoglom
Have you successfully pinned down the issue? Is there anything I can do to help? I'm no Android developer but I can only assume the timezone can be gathered automatically from the phone? If not can we have a setting in the settings page of the app to set it once? Or is Nightscout sync only expecting UTC while uploading?

[jwoglom]

Hey all, sorry for the pain here, this is being worked on. I’ve shipped a lot of things on the ‘dev’ branch but I want to perform more testing before I’m confident in syncing the code over to ‘main’ and making a new release. For better or for worse, this means that the gap keeps widening between the latest official release and the current state of the code, which is why I haven’t released a targeted fix for this quite yet. I hope to get a new release out soon with all these sync bugs fixed. Watch this space!

[LasseLiten15]

@jwoglom
I think that this bug is now solved. I updated today and just checked in Nightscout. At least the two latest entries seems to have correct time set. One was a Bolus and the other was a note saying Sleep mode was started. Both was on the correct time. I will continue testing tomorrow as there will be no more meal boluses today but it looks promising. Thanks for the update! 😊

[jwoglom]

@LasseLiten15 Excellent! Thanks for your patience.

@henriquejourdan @mcurly Please share if once you update to the 20260504 release you are still seeing this issue.

[henriquejourdan]

Hello Sorry for the delay. Yes I installed the update 1 second after you updated :) But after 20 seconds my face :( I tried different androids versions, fresh xdrip, and same issue. I noticed that controlx2 app syncs bolus when initiated in the android app AND when sent to the pump. Thats why it reports 2 bolus in xdrip each time I do a bolus remotely using phone and samsung watch. Direct pump bolus, also 2 bolus records in xdrip https://m.youtube.com/shorts/eJiN0NtWwRw Is it possible to correct the app so that it ONLY syncs in xdrip the bolus initiated by the pump ? About the zone time area & daylight / summer time I'm still trying to understand whats is wrong: 1) glycemia, basal are ok 2) bolus are one hour ahead . Before hour changed in Portugal Mainland, last month, all was good. Of course if I set all the android clocks to 0 GMT time and advance manually one hour.... no problem in xdrip and nightscout with BOLUS hour record. Greetings

…

On Sat, May 9, 2026, 00:57 James Woglom ***@***.***> wrote: *jwoglom* left a comment (jwoglom/controlX2#90) <#90 (comment)> @LasseLiten15 <https://github.com/LasseLiten15> Excellent! Thanks for your patience. @henriquejourdan <https://github.com/henriquejourdan> @mcurly <https://github.com/mcurly> Please share if once you update to the 20260504 release you are still seeing this issue. — Reply to this email directly, view it on GitHub <#90 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANCS25PQOWQZXLVSLWB5NH34ZZ667AVCNFSM6AAAAACWNQGO2SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DIMJQHA3TMNBRGM> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>