Incorrect lengths counted when swimming

[EmmaP89]

I've been swimming twice with my new sense and both times it's completely inaccurate with my lengths. I've tried the 'fixes' and various different things but it's still completely wrong!

My versa counted perfectly and I've changed nothing about the pool or the way I swim.

This morning it varied my 100m laps from taking 0.59 seconds to 2.05 minutes (my average with the versa based on 5 weeks of swimming is about 2.41 minutes for 4 lengths of 25m)

It's the main feature I use so it's incredibly frustrating

[GrantMark]

It’s the same for me. I always swim an EVEN number of laps for the same length of time everyday at virtually the same speed. 

My fitbit charge 4 always records an ODD number of lengths and the rate per 100m can vary by up to 20 seconds. It’s not good enough. Not to mention it calculates that I’ve climbed up to 30 floors a day when I live in a very flat area in a single storey property. So disappointing.

[GrantMark]

I’m so fed up with inaccuracies when swimming, I count the lengths I swim and use the digital timer at the end of the pool to get meaningful stats.  Add to this to the fact that my Fitbit charge 4 is no longer recording my sleep data, I might just as well throw it in the bin.

Complete waste of money. #FitBitRipOff

[Jools13]

Me too. Also fed up of All the things going wrong with this expensive watch.

I have updated the length of the pool in my watch to 20m. Yet it is still over calculating a lot. Example I swam 6 lengths and my watch recorded 8 lengths. Which is a huge difference over 50 - 75 lengths.

Now I just look at the clock and swim for 45 minutes instead.

Very sad. 😞

[Gr4ndp4]

Hi, @EmmaP89, @Jools13, & @GrantMark I'm assuming you are not using the auto-recognize feature but starting your swim exercise>swim>start arrow. I have the pool length set to 25metres, laps off, auto count unchecked. The number of lengths is in the large (middle) display (my eyesight is not that good) There is always 1 length discrepancy on a turn, I check my lap count every 20 lengths at the shallow end where I start so an even number is expected. After 20 lengths I see 19 when I flick my wrist but if I flick my wrist a second time before resuming my swim I get 20 (the last length end had now been detected)

By and large, I'm not experiencing any lap count problems though I occasionally miscount.

You may find this article helpful How do I track my swims with my Fitbit device? 

I hope this is helpful but if you are still stuck please post here again.

Cheers

[GrantMark]

Thank you for taking the time to reply. Much appreciated.

[Jools13]

Hiya Gr4ndp4, and everyone,

Yes, I have my device set at 20 metres as that is the pool I swim in. And I manually enter that I'm about to swim, instead of auto recognition.

Today I swam my normal 50 lengths, or 1000 metres. I know as I manually counted. My sense registered 1380 metres!!!!!  That is a ridiculous discrepancy.  

I swam only freestyle ( even though I like to mix up my strokes sometimes) and I apart from adjusting my googles/hat, I didn't take too much time between laps. 

I am so fed up with this, and all the other things going wrong.

Does anyone know how, or if we even can, change the default swim stroke from freestyle. 

TiA

[Gr4ndp4]

Hi, @Jools13, It's a pity you are having a problem with your lap count. I too pause for a few seconds from time to time to let faster swimmers overtake at an end or adjust my goggles, I do not see the discrepancies you report.

One of the links I posted earlier might have a bearing on your problem -

"Inconsistencies in your swim data may be caused by any of the following:

• You completed only a few laps
• You stopped to rest multiple times or in the middle of the pool
• You stopped to rest for longer than 60 seconds after completing a pool length
• You changed your stroke type midway through a length
• You swam with a kickboard or without using your arms
• You swam less than the minimum duration needed for your swim to be automatically recognized"

My theory is that our devices detect a pause/disturbance in the stroke rhythm and record it as a length end, as there is no GPS or it would appear a time template this might be at the root of your problem. Of course, only you know if this might be happening. You might make progress by talking to "Customer Support" here, use the chat facility or the phone for a prompt response.

I hope this helps.

Cheers

[Alexbuxton]

This looks like it's a very common problem. I'm having it myself Fitbit product support don't help at all (you have to call through the Fitbit app and that cuts out, live chat is a boy, and the actual people just give you the same list of things that don't apply). Steer well clear.