Overall HR measurements vs training measurement

[wedzir]

Noticed something strange this morning.. I included both screenshots.. 

Getting readings in the extreme zones when doing something like walking.. And besides that turning on a workout and comparing that to the overall hr usage eg comparing the ionic with itself shows also strange data.. 

Picture 1 shows my activity from the moment I got up.. around 5 am.. walking for about 90 minutes.. HR high (not correct) but not so high as it sometimes gets. Then from 7 am to 8 am a workout including running. HR lets say around 120 average..

whole day picturemorning training session

Now have a look at the second picture.. That is the IONIC workout.. You would think the same data, the same graph..but the average hr is higher and there is a peak in there of around 176. Mind you. I ran during the first 15 minutes of the workout and the other part was strength. So everything is still in a development fase I would say..

Moderator edit: format

[WavyDavey]

Hi @wedzir,

I believe that has to do with how fitbit manages heart rate average.

Your first screenshot is the daily graph, which is a five--minute average.

The second is from the activity log, which is a one-minute average.

On the daily graph, peaks and valleys often get smoothed out due to the averaging. This is normal behavior, and I get similar results.

[bbarrera]

---

@wedzir wrote:

Getting readings in the extreme zones when doing something like walking.. And besides that turning on a workout and comparing that to the overall hr usage eg comparing the ionic with itself shows also strange data.. 

---

Getting extreme HR during walking sounds like either an accuracy problem, or you need to adjust Ionic on your wrist. If adjusting doesn't change, its an Ionic problem. There are plenty of people reporting 180bpm HR in beginning of run, then it settles down and is accurate, so Fitbit certainly has some work to do.

The daily graph shows 5 min averages - and that shows trends instead of precise measurements.