Hi there, I'm new to the forums, so apologies if this has already been identified/discussed. I too have been struggling with the inability to create alarms on the watch that don't either get disabled or deleted by the Connect sync. I finally put a call into Garmin support this morning to provide feedback, and through the troubleshooting (he didn't acknowledge it as a known issue), we did isolate some of the behavior.
From our testing, it seems the issue 100% happens if you create a one time alarm from the watch (meaning no repeats). As soon as you sync after creating that alarm, it disables it. But, if you create an alarm on the watch with a recurring frequency (I used a custom one, only on Tuesdays for example), it seems to keep all the correct settings after the sync. I noticed in the Connect app, there is no concept of a one time alarm -- you *must* set a frequency. I'm wondering if the Connect app is confused by this type of alarm during the sync and disables/deletes it. (Which speaks to the broader issue you guys were mentioning regarding who should be the parent - watch or phone).
So while this still isn't perfect, at least I feel I have a workaround that keeps me from using the phone to set alarms AND I don't have to break the sync with the app.
The tech agreed it's not right and was creating a ticket for engineering. It might be helpful for others to also call in and report this so the tickets stack up -- maybe they'll prioritize fixing it.
Hi there, I'm new to the forums, so apologies if this has already been identified/discussed. I too have been struggling with the inability to create alarms on the watch that don't either get disabled or deleted by the Connect sync. I finally put a call into Garmin support this morning to provide feedback, and through the troubleshooting (he didn't acknowledge it as a known issue), we did isolate some of the behavior.
From our testing, it seems the issue 100% happens if you create a one time alarm from the watch (meaning no repeats). As soon as you sync after creating that alarm, it disables it. But, if you create an alarm on the watch with a recurring frequency (I used a custom one, only on Tuesdays for example), it seems to keep all the correct settings after the sync. I noticed in the Connect app, there is no concept of a one time alarm -- you *must* set a frequency. I'm wondering if the Connect app is confused by this type of alarm during the sync and disables/deletes it. (Which speaks to the broader issue you guys were mentioning regarding who should be the parent - watch or phone).
So while this still isn't perfect, at least I feel I have a workaround that keeps me from using the phone to set alarms AND I don't have to break the sync with the app.
The tech agreed it's not right and was creating a ticket for engineering. It might be helpful for others to also call in and report this so the tickets stack up -- maybe they'll prioritize fixing it.
Have a nice day!
Ryan
Ryan I wouldn't trust any alarm type set on the watch - I've had some that would last for a few days before vanishing. The only sure fire 100% way to ensure your alarm settings stay is to do them via the Connect app or website. I've had my watch for 2 months now so I've had plenty of time to mess about with different scenarios and this is the only one that works.
The support person sounded really helpful, but sadly "known issues" at Garmin rarely make it to the support people. The software engineers know all about it though.
Ryan I wouldn't trust any alarm type set on the watch - I've had some that would last for a few days before vanishing. The only sure fire 100% way to ensure your alarm settings stay is to do them via the Connect app or website. I've had my watch for 2 months now so I've had plenty of time to mess about with different scenarios and this is the only one that works.
The support person sounded really helpful, but sadly "known issues" at Garmin rarely make it to the support people. The software engineers know all about it though.
