This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

wore garmin 235 and fitbit hr during a run

I wore my garmin and my Fitbit charge hr during a 4 mile run today. Not something i usually do. My average heart rate was 15 beats per minute higher on the Garmin than Fitbit. Garmin also said I needed 3.5 days to recover. It didn't even say that after my half marathon 2 weeks ago. Anyone seen this?
  • Can you post the two HR graphs? Sounds like one or the other was incorrectly reading a lot higher than the other for part of the run.

    As for recovery, if the Garmin was reading too that won't have helped. How often do you normally run and how did the pace compare to your normal pace.
  • Both heart rate graphs




    Normally I run 3 days a week. Distance has been a little less and slower because I'm recovering from plantar fasciitis. Overall pace was 20-30 seconds faster than last few runs (was supposed to be a slow run but it started raining halfway through). It was still a full minute slower than my half 2 weeks ago though.
  • Not entirely clear from last graphs which is correct. Presume you think the Garmin is wrong? Might have had some cadence lock as the two metrics look fairly well correlated.
  • IMO you are seeing the result of a "Cadence Lock"

    IMO one clue for this is to look at your stride rate and the heart rate reported by your 235, they are very very close. As for why your 235 did this and the Fitbit didn't, compare the weight difference between the two. Quite simply because the 235 is heavier it's much more likely to move on your wrist with each stride. For me the solution to cadence lock issues is to use a chest monitor for activities when I want good heart rate data. BTW, took the dog for a gentle walk today at a 16:15 pace and didn't want to bother with the chest monitor so I just snugged my watch up two holes on the watch band so it was good and snug. While it doesn't seem possible looking at the heart rate trace for that walk at one point shows a near instantaneous spike from a heart rate of 102 to 118 and a following drop back to 102 that only took 2 seconds. I believe that particular spike was caused by my stepping off or on to a curb, probably stepping up because at one higher than normal curb I sort of jog onto that curb.

    Solution One. Use a chest monitor. Really, they aren't at all uncomfortable once you become used to wearing one.

    Solution Two. Snug that watch band up to the point where it's mildly uncomfortable, not making your hand numb tight but just below that point. If you have hair on your arm then I would also suggest shaving the area of your wrist when the watch is placed. BTW, don't consider the hair comment in any way a comment on grooming or sex because it's not meant that way. I am simply pointing out that hair could potentially interfere with the wrist monitor.
  • Former Member
    0 Former Member over 8 years ago
    I wore my garmin and my Fitbit charge hr during a 4 mile run today. Not something i usually do. My average heart rate was 15 beats per minute higher on the Garmin than Fitbit. Garmin also said I needed 3.5 days to recover. It didn't even say that after my half marathon 2 weeks ago. Anyone seen this?


    I have both the fitbit blaze and garmin 235. I run with both at the same time and fitbit always underreports HR during my runs. I can be sprinting and fitbit never shows above 160. I believe it's a known issues with fitbit and don't feel blame lies with Garmin. Cadence lock or not.
  • Thanks

    It could have been a cadence lock. I didn't think about that. I remember reading about it months ago but never experienced myself it to my knowledge. I'm running again tomorrow so I'll try wearing both again and see if I have results that make more sense.
  • Wore both today and HR was close

    Saturday must have been a fluke. I wore both today and the HR were only 2 beats per minute apart. Heart rate made more sense for how I felt during today's run too. Good enough for me!