ANSWERED
Accepted Solutions
@Sensenotasgood I did a number of activities with Sense and both HR and GPS are simply not fit for purpose. I had two devices (the second one I still have). First, I bought it myself and send it back for a full refund. The second device I borrowed from a friend who doesn't mind me keeping it for now so sometimes I give it a go just to see whether anything changed. Getting into zones is particularly important when you based your exercising on that. For such a purpose Sense is no go and I don't think there is anything that can fix it. Before, I assumed that steady-state activity may produce better results but one of my runs proved it's really random. Here it is:
My target training zone is zone 2. The orange graph is the chest strap connected to the Garmin watch (the chest strap is very accurate, it responds to changes in the heart rate instantly). The blue graph is Fitbit Sense. The only place they both agree is a dip near 9km which is me waiting at the level crossing to open. I never during this particular run went above tempo zone (green). It was a slow base/recovery 10km run, no way I could reach HR at the anaerobic zone (5). The Sense HR is inflated and pretty much rubbish. Using it during the run to make sure that I stay within a range of the desired zone is not possible. When I assume I want to spend 1hr in zone 2 (easy low-aerobic) then I need accuracy. This is the accuracy:
Fitbit Sense is nowhere near that and I doubt it will ever be. Sorry but numbers don't lie.
Best Answer
Bronze Community Members are highly active users who have shared their knowledge for the betterment of Fitbit products and services. Learn more
Best Answer
Bronze Community Members are highly active users who have shared their knowledge for the betterment of Fitbit products and services. Learn more
Best Answer@Sensenotasgood I did a number of activities with Sense and both HR and GPS are simply not fit for purpose. I had two devices (the second one I still have). First, I bought it myself and send it back for a full refund. The second device I borrowed from a friend who doesn't mind me keeping it for now so sometimes I give it a go just to see whether anything changed. Getting into zones is particularly important when you based your exercising on that. For such a purpose Sense is no go and I don't think there is anything that can fix it. Before, I assumed that steady-state activity may produce better results but one of my runs proved it's really random. Here it is:
My target training zone is zone 2. The orange graph is the chest strap connected to the Garmin watch (the chest strap is very accurate, it responds to changes in the heart rate instantly). The blue graph is Fitbit Sense. The only place they both agree is a dip near 9km which is me waiting at the level crossing to open. I never during this particular run went above tempo zone (green). It was a slow base/recovery 10km run, no way I could reach HR at the anaerobic zone (5). The Sense HR is inflated and pretty much rubbish. Using it during the run to make sure that I stay within a range of the desired zone is not possible. When I assume I want to spend 1hr in zone 2 (easy low-aerobic) then I need accuracy. This is the accuracy:
Fitbit Sense is nowhere near that and I doubt it will ever be. Sorry but numbers don't lie.
Best AnswerI think I got the worst HR results up to date! Same as before, a steady-state run in the low-aerobic zone. Targetting 1 hour in low-aerobic. This is interesting as usually, Fitbit lowers HR comparing to the chest strap but this time it's the opposite.
Orange - PolarhH10 + Garmin Fenix 6 Pro, Blue - Fitbit Sense
The result is absolute garbage. I restart the device before each sync (otherwise it just doesn't sync) but also I restart before each run. Usually, at least average is not far off but this is... I can't find words 🙂 An interesting thing that in the beginning my HR shoots up to 180 and stayed there. It may be a coincidence but my cadence was 180spm for most of the time. It is a known issue of many wrist-based HR monitors that the running cadence interferes with sensor readings and the point is, the algorithm has to recognize that and filter out. Otherwise, it will take steps for heartbeats. I know that Fitbit devices don't support cadence as a running parameter so I would assume, the cadence isn't taken into account by the algorithm. That could fix issues with running/walking/jogging.
Best Answer
