Strava issues fixes
-
@Yannis-Belouris said in Strava issues fixes:
@suzzlo Yes. Yesterday evening, well after Dimitrios post.
Was with polar H10 and Android. Will try now just on run of 700m with wrist HR and report back.
EDIT: On my test run with wristHR all is well on Strava. Maybe the fix was not 100% up yesterday?
Will make on with polar again in a few hoursMy run from this morning with Polar H10 is correct (values and graph) in Strava. Anyway I do not see why the brand of the belt could affect this issue, eventually is the watch who send the info to SA -> Strava and the info is in SA.
-
@cosmecosta correct
-
Maybe my band is broken, but all the values are different.
-
These are the graphs about the pace. -
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?
-
@fleshymutant I am getting only avg power on the mobile site and no power data on the website. Not much use for Stryd+Strava.
-
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
-
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
-
@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.
Suunto 9 Baro Titanium
iOS 13.1 -
@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/2013797766So 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. -
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.
-
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
-
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
-
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/2015585935Here it is in SA and everything looks fine with HR:
-
@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.
-
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
-
@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.
-
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.
Community Manager / Admin @Suunto
Creator of Quantified-Self.io
youtube.com/c/dimitrioskanellopoulos
https://instagram.com/dimitrioskanellopoulos
https://www.strava.com/athletes/7586105 -
@Dimitrios-Kanellopoulos great troubleshooting! Makes sense then why sometimes it works for some and not others
-
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.
