Second time this has happened. Changed the alarm time on a previously set alarm (from 6a to 4:30a) Double checked that the setting took in the watch. Next morning, the alarm didn't go off at 4:30a) as it had reverted to the previous setting (6a). The alarm did go off at 6a, but that's not helpful. Beware.
It's a known bug caused by Settings on Garmin Connect overwriting Settings on the watch.
For now the only way to set alarms is to do so via the app NOT the watch.
The Fenix 5 developers say it's an issue that the Connect developers need to fix.
That will keep your alarms, but you will be stuck with alarms that are set to have vibration and sound regardless of what setting you actually want as there's no way to set those options in Connect and if you change them for an alarm on your watch they will revert when your watch syncs again.
2. On the app you can set an alarm to sync with device - there is no option to the alarm notification type and it defaults to vibrate+tone
So there is a slight workaround for this - though it is still very much a bug based on poor implementation.
Here's the issue as I've found it with an F5X:
1. On the device you can set an alarm as well as the alarm notification type - vibrate/tone/vibrate + tone
2. On the app you can set an alarm to sync with device - there is no option to the alarm notification type and it defaults to vibrate+tone
3. If you set an alarm or alter a synced alarm on the device (sync taken from the mobile app), it will be overwritten on next sync with the mobile app (for instance alarm notification to vibrate only - I have a preference to silent alarms).
The order of hierarchy for the way Garmin have implemented syncing is (it's reverse of what one would consider normal functionality):
1. Web UI with Connect IQ on your desktop
2. Mobile Application
3. Actual Device
You can use this to your advantage as a work around. The Web UI allows you to designate 10 alarms (?), as well as alarm notification type (vibrate/tone/vibrate+tone).
If you create a set of alarms in the Web UI in the "off" mode - in my case 3AM weekdays, 4AM weekdays, 7AM weekdays, 8AM weekdays, 7AM weekends, 8AM weekends, and then sync with the device they will transfer across to the device.
These alarms are held the highest in the sync hierarchy. Subsequently, when you sync with the mobile app these will be transferred across (though you won't see the notification type in the app - it will however show up on the device). Now you can turn the alarms on and off on the mobile app and they will hold during user initiated or automatic syncs.
If you activate them on the device, so far they haven't held past a sync, however this should prevent users having to plug the device into a computer every time they want an alarm especially with vibration only or tone only.
It's not pretty and defiantly an extremely POOR implementation of multi-platform settings sync - especially given how embedded the alarm menu is, it would be an act of <insert_deity_here> to accidentally set an alarm on the F5X.
I hope this helps people as a workaround until they sort this mes out.
