Sunrise-sunset widget and data is set on GMT and not local area.

Hi,
i noticed that from some days the time of sunset and sunrise reported in the original widget is wrong. It reports the time alterated by about 2 hour earlier. I try to sync time and to start an activity with active gps, but the results don't changes. Anyone noticed a similar problem?

Top Replies

Former Member over 4 years ago in reply to Former Member +2

FYI... Powering off the watch and turning it back on fixed this little glitch.

All Replies

0 Former Member over 5 years ago

I'm currently GMT +3.5hrs & mine is reporting correct sunrise/sunset timings.

Just checked on Google.

Sunrise for my location is 0444, widget is saying 0444

Sunset for my location is 1856, widget is saying 1856

0 Stefal639 over 5 years ago in reply to Former Member

I am in GMT +2 (italy) and it reports sunrise at 3:36 and sunset at 18:30. The correct one is 5:36 and 20:30.
garmin fenix 6x pro.

0 EyessOnlyy over 5 years ago in reply to Stefal639

I'm in Romania and the sunset/sunrise time seems to be correct.
i have not checked this daily but have not observed such huge differences up to now

0 mcalista over 5 years ago

Perhaps try saving your current location (accessible through the controls by holding the backlight button.

0 Stefal639 over 5 years ago in reply to mcalista

same situation...

0 Stefal639 over 5 years ago

I went to bed yesterday with "sunrise at 3:35" and i woke up today with the correct times of sunrise and sunset.
I don't do nothing on f6 or phone.
Another Garmin mistery.

0 Former Member over 4 years ago in reply to Stefal639

You're not alone on this. I have the Fenix 6S pro and noticed this issue today. I have some watch faces that I've downloaded that show sunrise/sunset times and those are accurate. However, The default Garmin watch faces, and the sunrise/sunset default widget is way off. I'm in southern California, so sunrise right now is just before 6 AM and sunset is just after 8 PM. However, checkout the confusing data my Fenix is showing: drive.google.com/.../view

0 Former Member over 4 years ago in reply to Former Member

FYI... Powering off the watch and turning it back on fixed this little glitch.