Fenix 5 - Workout heart rate alerts (beep & notif) bug?

Former Member over 8 years ago

I have a problem with the heart rate zone based workouts generated on GC, my Fenix 5 doesn't alert when I'm out of the desired zone. On my previous watch Fenix 3 this was working correctly with sound and "notification".

Is this a bug, or am I missing something in here?

Reproduce the behavior:

Plan on GC:

Heart rate zones are wrong on GC but watch still shows these correctly (based on my preferences). This training plan bug has been on GC like forever.

0 Former Member over 8 years ago

Fenix 5: not fit for custom workouts due to lack of effecient alerts?

I'm still having issues with the way the Fenix 5 gives alerts in custom workout:

for some reason the alerts-vibration when not in in the correct zone (f.ex. when HR was programmed between 163 - 169, and the current HR is 160 or 170) only come after 30 seconds not being in the zone AND no alert-vibration is given when actually entering the zone.

With my 920xt alerts were given
- after 15 sec when not yet in the zone (HR to low, pace to slow),
- instantly/immediately when entering in the zone
- instantly/immediately when leaving the zone (HR to high, pace to fast)

As I train in specific HR-zones (based on lactate tests), and my interval session include often blocks which are shorter then 30sec, the lack of instant-alerts and belated alerts, make the functionallity of programming custom workouts, kind a useless, unless you are constantly looking at your watch?!?

as for the new "feauture" to end the workout, useless. I always leave the end of my workouts open by "Stop by pressing lap", this way you have always control on when ending the workout...

0 Former Member over 8 years ago

After an update, I guess to 2.90, notifications and alerts in customer workouts started working as they did in the 920xt.

I think the only difference is that the signal when not in the zone (HR to high, tempo to fast, depending on the workout) is only given once or twice, while in the 920xt this was repeated more often. Perhaps this could be corrected in a future update?