Strava issues fixes

jumalca · 12 Dec 2018, 15:08

Maybe my band is broken, but all the values are different.

jumalca · 12 Dec 2018, 15:15

These are the graphs about the pace.

fleshymutant · 12 Dec 2018, 15:19

So here are some testing I’ll run today.

External HR with Stryd
External HR without Stryd
Internal HR with Stryd
Internal HR without Stryd

What am I missing?

Brad_Olwin · 12 Dec 2018, 18:40

@fleshymutant I am getting only avg power on the mobile site and no power data on the website. Not much use for Stryd+Strava.

stromdiddily · 12 Dec 2018, 18:44

Same HR problem with this morning’s run. FWIW - I have never had lap data work in Strava, manual or auto.

Android
S9
Polar H7

A Former User · 12 Dec 2018, 18:48

Second test for HR wrist S9 wHR.
HR is transferred.
However, something funky happened at the end. I made a long pause there. The graphs start to divert

fleshymutant · 12 Dec 2018, 19:21

@Brad_Olwin true but it’s more than a few months ago Regardless I use TrainingPeaks which is not yet supported by SA so I’m going to have to keep using MC for that.

TrainingPeaks can source from Strava but if the data isn’t right in Strava then I suspect it won’t be right in TP either…just trying to think down the road here.

fleshymutant · 12 Dec 2018, 19:27

@fleshymutant said in Strava issues fixes:

External HR with Stryd - https://www.strava.com/activities/2013797790
External HR without Stryd - https://www.strava.com/activities/2013797770
Internal HR with Stryd - https://www.strava.com/activities/2013797816
Internal HR without Stryd - https://www.strava.com/activities/2013797766

So these look fine but…

I did my actual workout for the day and the HR problem was back. Good news is that the lap info is working now and I can do the workout analysis This was done using the run interval Suunto preset with my H10 and Stryd.

https://www.strava.com/activities/2013994621

someguythatruns · 12 Dec 2018, 21:36

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 · 12 Dec 2018, 23:53

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 · 13 Dec 2018, 09:41

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 · 13 Dec 2018, 19:25

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:

Brad_Olwin · 13 Dec 2018, 19:41

@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.

stromdiddily · 14 Dec 2018, 18:11

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 · 15 Dec 2018, 07:46

@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 · 15 Dec 2018, 10:13

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 · 15 Dec 2018, 13:41

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

Anssi Auvinen · 31 Jan 2019, 09:20

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.