03-31-2016 04:31
03-31-2016 04:31
I've had my surge for 10 weeks or so - on the whole it seems to work well. The heart rate monitor seems accurate enough - I've checked it when I've been sitting down and it tallies well with a manual reading - not sure if it's right when running etc. but it is consistent from one run to another so I assume it to be correct. However, there is a problem when I cycle - I haven't used it for cycling much, but I noticed it gave low calorie output and low HR so I imagined that maybe I just take it really easy when I'm cycling and don't realise it. However, I went for a two hour ride the day before yesterday and was pleased to see that my average HR was 140 or so - which is equivalent to a jog for me - I did the same route today and it averages 65 - however I stopped to check my pulse a couple of times and it was easily twice that. It seems to give a continous reading - so it's picking up something - though clearly not my pulse. I tried rebooting it -no change - I tried turning off cycle mode but it gave similar readings for HR - and, as an aside, it didn't autodetect that I was cycling. Any ideas?
03-31-2016 07:06
03-31-2016 07:06
Have you tried wearing it a little tighter and higher up on your wrist during cycling?
03-31-2016 09:44
03-31-2016 09:44
@SunsetRunner agree with Patruns - try changing position:
However as Fitbit was originally optimized for walking, and later running, its not uncommon to have poor accuracy while cycling or spinning. So you may or may not achieve good accuracy while cycling.
Aria, Fitbit MobileTrack on iOS. Previous: Flex, Force, Surge, Blaze