HRM does not look good

Well.. my HRM is screwed up too...

Well I was really liking my 235 until todays run. I ran an easy 6 at 9:34 pace (never looking at my watch the duration of the run) normally my HR would be 135-145 average max. Well it says my average was 168 (?! that's like normally my AVG HR in a 5k or 10K race). Here is the activity.

https://connect.garmin.com/modern/activity/972903903

This was a run a week ago where I ran approximately the same pace and just a mile more.

https://connect.garmin.com/modern/activity/966796238


Anybody? What are your thoughts?

Well I was really liking my 235 until todays run. I ran an easy 6 at 9:34 pace (never looking at my watch the duration of the run) normally my HR would be 135-145 average max. Well it says my average was 168 (?! that's like normally my AVG HR in a 5k or 10K race). Here is the activity.
https://connect.garmin.com/modern/activity/972903903
This was a run a week ago where I ran approximately the same pace and just a mile more.
https://connect.garmin.com/modern/activity/966796238
Anybody? What are your thoughts?

the same here. I'm happy with the device for how beautiful it is, but at the same time very disappointed for the data recorded. HR is absolutely wrong, especially during interval trainings. A bit better during easy runs, but still far from the value showed from the HRM chest strap with the FR620 unit. One of the main reasons I decided to buy the 235 was the activity monitor included, that let me take off the Vivosmart.

Strange that also the pace graph will show better values on Strava or Sporttracks than on Garmin Connect.

Three runs done...first pretty ok..but last two really disappointing...180/185bpm for a long time during easy pace...then jumping up/down during intervals..really bad I would say..running on latest beta FW with tight wear... hope they are going to improve shortly this FW.

I get similar readings occasionally. The heart rate will be around 130-140, which is normal, but then drop out or spike up and then recapture my rate.

I'm tempted to buy a heart rate strap to remedy this but I'm not sure if it's worth the additional cost or the discomfort (never worn one before).

Exchanging 235 for 230 Due to HRM

After several runs on trails and road, my experiences with the 235, firmware 3.10, are:

1. Takes 1-2 miles of ‘warmup’ to get stable and realistic readings.
2. Doesn’t really track quick changes in HR due to sprints/intervals. It actually showed a declining HR during a 1 min sprint on flat trail.
3. Doesn’t work well in the cold; the colder the temp, the longer the warmup.
4. Seems to work better for steady run on pavement, without drastic HR changes due to hills, etc.
5. VO2 Max and Race Predictor never changed after the 1st run (tempo, on asphalt) perhaps because HR was so dysfunctional on trails/hills/intervals.

An HR strap is uncomfortable but has been much more reliable for me.

So far I didn't had THAT bad issues with the HRM in the 235. I will however continue to test and compare it to my Polar H7 cheststrap.

I post my results here: https://forums.garmin.com/showthread.php?336443-FR235-HRM-and-Sleep-Data-Comparison

Personally, I don't have much discomfort issues with the chest strap. However I don't know if those from Polar might be more comfy than the Garmin ones?

If it should turn out that I get Issues with the HRM or that I am just not happy with it I will consider returning it and downgrading to a 230 with cheststrap. Because otherwise I kind of like the watch, though it's my first from Garmin and can't compare to previous models.

I was also considering the Polar V800 or M400, but those seem really big for my rather small wrists. The FR235 fits well though.

phil

I've had bad experience with the 235 with the first runs, especially during interval trainings.
Two recent recordings:
10x400m rec.200m https://connect.garmin.com/modern/activity/966271624
12x300m rec.200m https://connect.garmin.com/modern/activity/972772991
in both of them:
-the pace graph shows top speeds that are much slower than the real; note that the same recordings on Sporttracks and Strava look better, with realistic paces
-the HR graph shows spikes (high and low) that aren't real
-the HR during recovery is higher than the HR during the fast phases (!)
-the "best pace" in the details is slower than the "average pace" (!)
I ran once with both the 235 with wrist sensor and the 620 with HRM chest strap. This is the HR comparison: https://www.dropbox.com/s/jleyn9myap8qak2/Schermata%202015-12-02%20alle%2022.21.07.jpg?dl=0
The lines are similar, apart from some minor spikes on the 235 graph. I will do the same with another IT run to show the big differences.

I have the same issues, i 'll copy them here again:

-the pace graph shows top speeds that are much slower than the real;
-the HR graph shows spikes (high and low) that aren't real
-the "best pace" in the details is slower than the "average pace" (!)

Concerning the HR during recovery. It can be normal if you are doing high intensity intervals till 400m (for example ) with recovery phases shorter. I noticed that also on the TomTom cardio and on some friends graphs.

Here is a run with the observed issues : https://connect.garmin.com/modern/activity/972570514

Those issues are definitely bugs. @Moderator, can you confirm that you are aware of those issues (thanks to these posts) and if they will be reported to developpers ?

Thanks

I have now had 4 runs with my 235. The HRM is definitely a bit off on my runs. However, I have not updated to the Beta yet either (assuming from the description of the update that no improvement was made to HR). I did find one thing that seemed to help. Maybe it is like when you stand on one foot and hop twice and your car magically starts. For what it's worth, though....

When I notice my HR data starts coming in far below what is expected in the middle of a 12-miler (98-110ish vs. 130-135ish), I sort of jiggle the watch face side to side on my wrist. That somehow seems to bring the HR monitoring to life. It usually spikes at first and then settles back in to a normal range. The trouble is that I have to keep a pretty good eye on it to ensure there are no dips. I did that about 4 times during my run, which was on flat terrain at a pace between 8:15-8:30. Still, there was one mile where I missed it and my HR was 112 while the rest were in the 130s and low 140s.

For tomorrow's run, I am going to try looking at "Lap HR" (in which my laps are set to a mile) instead of HR (which I believe is "instant HR"). I'm hoping that will make me see less spikes and give smoother feedback while I run. I'll report my results in case anyone is interested.

I have 4 runs now, and all of them have these crazy spikes in HR. I have looked closer into when it happens, and I have found that 95% of these spikes happen when a big change in pace happens. For example when starting to walk after running, staring to run after walking etc. I can't see the logic why the accuracy of HR should be affectedby the pace changes? But this is absolutely something that Garmin should look into!