Open e9henrik opened 9 years ago
I have the same issue with running activities since a few weeks (always Endomondo -> Runkeeper). There are always lots of incorrect pauses inserted in the runkeeper activity. I've tried disabling the "simulate auto-pause" setting in Tapiriik but it doesn't seem to change anything.
Seems to be related to pulse data.
I ran on Saturday without pulse sensor, and the activity was synced without issues. Todays run was done with pulse sensor, and the duration is off by almost 30% (with lots of incorrect pauses inserted).
I observe the same problem for running. It seems to also be connected to the issue I referenced above. In that issue we did a change to the way tapiriik handles Endomondo workouts to fix the pace times for import in Strava. If you experience it since few weeks, it's a good chance that the change that we made broke it.
If you want to dig into the code: this line is the place to start I guess. That's where @cpfair added the pauses to address the Endomondo -> Strava syncing issues.
Edit: although this does not fit nicely with what @e9henrik suggests with the pulse sensor...
Nothing new regarding this issue? I have a fresh example from a run I did earlier this month with Endomondo. Looks REALLY weird in Runkeeper...
Still no solution to this problem? Manually exporting and importing from Endomondo to Runkeeper works well, but through Tapiriik it inserts lots of pauses.
In endomondo Distance: 14.5 km Duration: 43m:51s
Strava Distance: 14.3 km Duration: 43m:51s
Runkeeper Distance: 12 km Duration: 18:59
This happened to the last two out of three cycling activities. When it's bugging, there seem to be a lot of spurious pauses during the ride. Removing them doesn't cause runkeeper to recalculate correct distances nor durations however.