Garmin Training Calendar - edit heart rate?

Check the zones on Garmin Connect are the same as the zones you have on your device, if they are the ones you want to use. If not the same, make them the same. That'll clear up any ambiguity.

apparantly there is an error in the plans so they shows default heart rate
but you can enter each workout and edit the heart rate zonez to something different and then back to the right zone and hit enter then it will be correct

This seems to be a bug in the calendar.

See https://forums.garmin.com/showthread.php?371958-Training-Plan-HR-Zones-not-set-to-correct-range

Any solution ?

Have you executed that custom workout on your Garmin wearable device, and through experimentation confirmed whether the watch is actually using the heart rate zones in your user profile to trigger alerts or not?

See https://forums.garmin.com/showthread.php?371958-Training-Plan-HR-Zones-not-set-to-correct-range

Have you executed that custom workout on your Garmin wearable device, and through experimentation confirmed whether the watch is actually using the heart rate zones in your user profile to trigger alerts or not?

Thx. the watch itself (FR235) indeed uses the correct heart rate zones. It's really just the description in the calendar (like is mentionned in the thread you linked too). Seems to be an old bug :(

As mentionned in the other thread; editing the workout step (switching zones back & forth) changes the heart rate to the correct values on the calendar. I just wonder is Garmin aware of this bug ? Are fixes to the connect interface published somewhere / release notes ?

Seems to be an old bug :(

I used to think it was a bug, but I changed my opinion on that.

Heart rate zones are now in device settings (as opposed to Garmin Connect user profile settings irrespective of device). That means a user with, say, a Forerunner 235 and an Edge 520 could have different HRZ settings on the devices. The training plans are added to the Training Calendar, and only after sending the scheduled workouts to a particular registered device can they be executed. However, the Calendar is still going to show the workouts even before you send the workouts to a registered device. Therefore, I don't think it's a bug that the programmers have decided not to check whether the user only has one registered device and then assume that will ultimately be the device to which the workouts are sent.

The zone number as specified in the training plan is correct, it's only the heart rate thresholds in terms of beats of minute that are ‘incorrect’ (because Garmin Connect does not attempt to figure out which device and the HRZ settings on it that the individual user uses, when displaying the training calendar).

I used to think it was a bug, but I changed my opinion on that.

Heart rate zones are now in device settings (as opposed to Garmin Connect user profile settings irrespective of device). That means a user with, say, a Forerunner 235 and an Edge 520 could have different HRZ settings on the devices. The training plans are added to the Training Calendar, and only after sending the scheduled workouts to a particular registered device can they be executed. However, the Calendar is still going to show the workouts even before you send the workouts to a registered device. Therefore, I don't think it's a bug that the programmers have decided not to check whether the user only has one registered device and then assume that will ultimately be the device to which the workouts are sent.

The zone number as specified in the training plan is correct, it's only the heart rate thresholds in terms of beats of minute that are ‘incorrect’ (because Garmin Connect does not attempt to figure out which device and the HRZ settings on it that the individual user uses, when displaying the training calendar).

Allthough I understand your point; the fact that editing the workout (by switching the zone back & forth ) gives the correct absolute heart rate values; contradicts your reasoning (to my opinion).

… editing the workout (by switching the zone back & forth ) gives the correct absolute heart rate values contradicts your reasoning (to my opinion).

I agree to an extent, and here's what I don't understand – and haven't tried testing using two different devices (say, a FR235 and a FR630, being of very similar capabilities and design intent as running watches) both registered to my Garmin Connect account: if I have different HRZ settings for the FR235 and the FR630, and then I edit the zone in a workout which (in the following mutually exclusive scenarios):

• has never been sent to either device;
  
• has only been sent to the FR235;
  
• has only been sent to the FR630;
  
• has been sent to both the FR235 and the FR630
  

then what would the training calendar in Garmin Connect show? Which absolute heart rate values would actually be correct?