Strava issues fixes

someguythatruns

For what it’s worth, both runs have transferred over correctly, HR moved over great with HR belt data. Using iOS, 9 baro and Suunto HR belt.

stromdiddily

Looking closer at my lap display issues in Strava web…

Seems that if you pause an activity Suunto/Strava is counting that as a lap. Activity with manual laps shown below. At .22 miles I paused waiting to cross the street. There were no other activity pauses and the remaining laps are accurate based on the workout.

S9 baro, Android beta

Dimitrios Kanellopoulos

Hi please dont get confused about the graphs.

The graphs in SA are based on time and the time is not linear (known issue) and on strava it’s by distance. It’s like comparing apples with bananas as far as I understand

fleshymutant

This time without the Stryd but with my H10, HR values look good for the beginning then back to flatline:
https://www.strava.com/activities/2015585935

Here it is in SA and everything looks fine with HR:

PNG image.png

Brad_Olwin

@fleshymutant I am transferring from Strava to TP using RunGap. As long as there are no stops/slowdown it is working but not optimal. So I am still trying to transfer from MC as well. My HR and laps are fixed now.
Screen Shot 2018-12-12 at 8.46.11 AM.png

stromdiddily

Suunto 9, Wahoo Tickr Fit, Android, hiking sport…heart rates in Strava look good.

Testing a run with the Wahoo later today. Would be strange if the problem is specific to the Polar strap

cosme.costa

@stromdiddily said in Strava issues fixes:

Suunto 9, Wahoo Tickr Fit, Android, hiking sport…heart rates in Strava look good.

Testing a run with the Wahoo later today. Would be strange if the problem is specific to the Polar strap

Sorry to disagree here. The problem is not in the Polar or any belt if the values are ok in SA (or MC). If the heart rate is OK in SA or MC and then it isn’t in Strava, the problem has happened in the transference or in the way Strava reads the values.

Dimitrios Kanellopoulos

we have found an additional issue with the HR + Belts

Here is the deal if you need some insight.

A belt can record both IBI and HR. When the processing is not good enough (from the belt module) the belt can send HR instead of IBI.

The above means that in a move you can have both IBI and HR samples.

This is a quirck again. We were parsing HR if we found HR and sending HR only to strava.

So if the belt has mainly IBI those few HR samples were only sent to strava.

We changed the logic to send IBI if IBI is there disregarding those “faulty” HR samples.

This change is not yet live but will be next week.

Thanks a lot for all the posts and the “suffering”, I am with you guys, I also have these issues.

stromdiddily

@Dimitrios-Kanellopoulos great troubleshooting! Makes sense then why sometimes it works for some and not others

Anssi Auvinen

Activities synced to strava & training peaks show the time without pauses.
For example swimming in app the time is 1h 4min and in strava & TP 1h 7min. I had 3 minutes toilet break and I paused my suunto 9. This worked the right way when used movescont and the time matched.