Different ascent value between Suunto App and Strava

[jjpaz]

@Cédric-Dodrimont
Same here, my yesterday’s run:

Suunto Vertical: 189m
Strava: 184m

Altitude correction feature is missing in Strava for that activity. Does Strava think that Suunto Vertical doen’t have Baro?

I have verified monday’s run and ‘altitude correction’ is there, so something has chenged from monday to tuesday in Suunto-Strava integration.

[Cédric Dodrimont]

Altitude correction is not available for the activity in strava, but it was when activities were uploaded from my S9.

5 meter difference doesn’t matter, but 200m is quite high.

So, I’m juste wondering if there’s an issue during export from SA to strava.

[nseslija]

@Cédric-Dodrimont I just checked on Strava. Different ascent values are on mine last to activities, since Strava start to identify the watch as Suunto Vertical… On Runalyze everything is ok…

[trailcafe]

Same here, since Strava identifies Suunto Vertical as “Suunto Vertical” and not only as “Suunto” the button for altitude correction disappeared and a discrepancy between SA elevation und Strava elevation appeared.

[pilleus]

Write to Strava to add the Vertical to the library with watches which have a berometer and the option to correct the elevation is available.

[Cédric Dodrimont]

@pilleus Maybe it’s the solution, this activity with wrong ascent value is the only one where “suunto vertical” device name appears. For other activities, ascent value match SA value and the device name is just “Suunto”.

[isazi]

I’ll ask people at Suunto to tell Strava, but please fill a bug report with them too.

[valdis830]

@Cédric-Dodrimont
Apparently this bug has emerged from day 19. It is when Strava has changed <<SUUNTO>> for <<SUUNTO VERTICAL>> Something has been overlooked. I have opened a ticket in strava support.

[pavel.samokha]

It should be fixed now (older workouts will likely to stay as it is, with corrected ascent)

[Egika]

@pavel-samokha that was quick

[jjpaz]

@pavel-samokha Not fixed, I’ve just uploaded an activity and elevation is based on Strava data and not in barometer info.

[pavel.samokha]

@jjpaz OK, we’ll try to contact Strava again

[Dimitrios Kanellopoulos]

@pavel-samokha same here was ok yesterday though

[valdis830]

@Dimitrios-Kanellopoulos
I didn’t realize it before but it’s been wrong since the 20th

[Dimitrios Kanellopoulos]

For me it was ok today

[pilleus]

It’s working.

[MiniForklift]

My run yesterday was quite different between Strava and my SV…

Compared to Strava…

I’m obviously going with the SV but that’s a hefty difference don’t you think?

[freeheeler]

@MiniForklift
that’s possible depending how hard it rained. I try to protect the baro sensor during heavy rain.

[Ollipolli]

Same problem here 🫣

[lessthanmore]

@Ollipolli Do you have screenshots of the/ your activities that show different values?
It’s supposed to be fixed weeks ago and for me the values match/ are identical between SA and Strava.