Anything related to the recent announcement about Suunto’s new Digital services and Movescount Transition
@Prenj said in Nov transition update:
@halajos said in Nov transition update:
@Dimitrios-Kanellopoulos I’m happy to hear that route creation remains on MC, and I wish Suunto opened the API between MC and SA backend for sending over routes.
That’s actually very good one. Suunto opens api for third party services, but not for their own platform LOL
But hey, this service will “continue to evolve”. Is there a word with opposite meaning to word “evolution”? Devolution? That would be more appropriate.
Lol sooo true. That is what I thought as well. Actually this aint bad after what I read here. If for example MC has the “best” (from what people say) for them route creation on the WEB, and SA on mobile, I mean why not? Even better. Make only the MC route creation a new THING/Product/Free and voila. Let people come to Suunto by using this. Sorry this was kinda personal opinion, dont want to “ruin” other people’s feedback.
@Dimitrios-Kanellopoulos importation from Movescount done on september this year.
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 ?