Movescount history import is open for all users Spartan/S9/S5

[Egika]

@Dimitrios-Kanellopoulos yes, track is missing after opening. I don’t understand: is this a known big and will be fixed?

And no - no external sync soft. Just automatic import from MC like offered yesterday…

[Dimitrios Kanellopoulos]

@Egika The map missing is a firewall issue with mapbox servers. Adding a picture should resolve this. Mapbox is working on this

[masood]

Dear all I bought suunto 9 baro am totally disappointed because of its problems. Number one it does not count correct daily activity steps number two it can not find gps. It’s expensive but believe me Fitbit charge 3 and versa are best watches suunto is total waste of money plus a nonsense watch

[sartoric]

@masood said in Movescount history import is open for all users Spartan/S9/S5:

Dear all I bought suunto 9 baro am totally disappointed because of its problems. Number one it does not count correct daily activity steps number two it can not find gps. It’s expensive but believe me Fitbit charge 3 and versa are best watches suunto is total waste of money plus a nonsense watch

Good.
Return it.
Farewell.

[Jonathan Newby]

@masood good bye my friend. Good luck with your next watch.

[Fatih Kale]

@masood only one post and it is this one mhmm sounds tricky.

Good luck.

[Luís Pinto]

Second history import concluded at 12/09 and problems identified not solved.

[kostas trogadas]

@Dimitrios-Kanellopoulos γειά. σου εμφανιζει κανονικά χάρτη από δορυφόρο στην εφαρμογή?

[Dimitrios Kanellopoulos]

@kostas-trogadas ναι

[PhilDeFer]

@Dimitrios-Kanellopoulos importation from Movescount done on september this year.

But…

I just discovered last week that a lot of moves were wrong in Ascent / Descent values once imported :

• on Movescount, these moves are fine ;
• on SA, they are wrong.

I think the problem is coming from moves that were on the two platforms (in 2018, i was using the two platforms and synced my activities on the two services) : the Ascent / descent bug on SA wasn’t solved last year and i always get wrong values. So i stayed on Movescount the time to get this bug solved.

I remember reading some information telling us that once the bug solved, all the old moves with incorrect Ascent / descent values will be updated ? Am i wrong ?

What is the solution to have some correct datas for Ascent / Descent which correspond to the right values that are on the Movescount platform ?

I’m trying to ask some assistance from Suunto :

• nobody on French phone assistance ;
• i don’t find any way to contact some mail assistance…

Any idea, suggestion ?