Alarm won't set correctly after the clock change. Help please.

I have a 7am alarm. After we turned back the clocks, it now says 6am. I deleted that alarm and set a new one for 7am, guess what, it still says 6am. HELP!!! LOL. I need my sleep.

0 DCeremuga over 5 years ago

Ok, this is once again a GCM problem. the watch says 7am, GCM says 6am, regardless of good sync and connection. Chalk this up to ANOTHER GCM problem.

0 DCeremuga over 5 years ago in reply to DCeremuga

Let me add yet again how utterly crappy support is. I was on the phone and all he said was "If you don't update to the latest versions of firmware/software on the watch, it won't work". Screw that. I'm not breaking another watch with these updates. My ONLY problem is GCM at the moment, not the watch. 3.1 is GREAT.

0 Dr Phil over 5 years ago in reply to DCeremuga

So you don’t believe that fixes to the software on the watch to work with changes to GCM are implemented to work with iOS then, which is where the root of the problem is?

0 DCeremuga over 5 years ago in reply to Dr Phil

NO. Garmin's support is just clueless. Most all problems are GCM, not the watch.

forums.garmin.com/.../since-daylight-saving-triggered-my-alarms-are-set-for-1-hour-behind-fenix-5