My instinct is on 6.51 beta right now. I had an alarm set to 5:10 this morning (daylight savings change), but the alarm didn't go off. I was already awake, so I didn't just disable it. The alarm is still set to 5:10, but now it's 5:30. WTH?
My instinct is on 6.51 beta right now. I had an alarm set to 5:10 this morning (daylight savings change), but the alarm didn't go off. I was already awake, so I didn't just disable it. The alarm is still set to 5:10, but now it's 5:30. WTH?
I had the same issue. Set an alarm for this morning, double checked when I went to bed that is was active. Didn't go off.
My watch time changed just fine. Just the alarm failed.
Ah, OK, in that case you better do not sleep at all when there is the change.
BTW, did you change the alarm for the next day, or do you…
Yep, same! I have the latest standard firmware and set an alarm last night for 5:15am, luckily my wife woke me up at 5am anyway :-P The alarm ended up going off an hour later at 6:15am. So the alarm went…
Well, regardless whether it fixed itself alone, or after entering the alarm screen, or after any other manipulation, it would be better reporting it to the beta team <[email protected]>, if nobody did it yet.
I have sent them an email with a link to this forum entry 3 days ago. No response yet, but they have until november to fix fhis problem before the next daylight savings adjustment...
They had until yesterday to fix it without receiving new messages (some countries changed time yesterday). I although the sw has been updated to 6.60.0.0 there is still the same bug this morning (that is I confirm, the hour displayed changed but the alarm fires at the wrong hour).
Come on Garmin! A watch that fails to alarm when set is a critical bug! People expect a watch to do this function reliably!