Conflicting reading on same screen

[SatishHV]

The dashboard reads 1.88 kms, the activity reads 13 kms and I changed to cycle but still shows walking. 

 

[eezeepee]

I believe the Today distance is only walking distance. I'll see if I can find the thread saying this. Since your exercise was a cycling (weird glitch it still says walking), it doesn't count towards that distance.

Update:

Here's the thread I was talking about above.

https://community.fitbit.com/t5/Sense/my-sense-does-not-add-the-miles-traveled-during-the-exercise/m... 

[SatishHV]

Thanks. I get that. It explains the issue but that still    doesn’t make it right  
I had walked only 100 steps probably. So data overlap by recognising walking of 1 kM and GPS reading of 13 kms! So it’s not  synchronised between applications and is an issue. Especially when we track an exercise- that  application seems autonomous!

[t.parker]

If this was cycling then probably lots of steps are picked up just by bumps on uneven surfaces (Fitbit detects steps during cycling).  In general, cycling distance doesn't count towards the daily distance goal but there is lots of inconsistent behaviour which may play a significant role in the issue you experienced. The bogus steps may count toward a daily distance of 1.86km. Check what is real steps impact your activity, cycling gives me usually plenty. Looking at pace and distance you must have been cycling 42-45min this will give you plenty of steps, hence distance.

Here's the proof from my own log:

As you can see, I wear the watch ONLY during activities so there are no other steps than those when I decided to track something (manually, I don't use auto recognition). Outside activities I didn't wear the watch. You can see spikes of steps during two rides. There's only one step based activity which is 1.88km and the remaining distance is added through detecting "fake" steps during cycling. In the mobile app, if you look at the impact of cycling activity, you will notice that steps don't appear anymore but Fitbit cheated users by just hiding the metric rather than turning off the whole steps detection.