May Transition Update
-
I was able to import all my moves from Movescount to Suunto (with a lot of duplicates to delete manually) and my Ambit 3 Peak is now synchronized with th Suunto Link (which is far better than movescount). BUT, now why match says “please synchronize your moves” and I see the memory percentage occupied increasing (now 70%). I don’t absolutely get why…and I’m afraid the memory will be saturated soon. Can anyone help ? Thanks !
-
@LudovicTheRunner from what I read your memory will be automatically recycled, i.e. old activities will be deleted when necessary. So I don’t think you need to worry. Please Ambit users correct me if I’m wrong.
-
@isazi said in May Transition Update:
@LudovicTheRunner from what I read your memory will be automatically recycled, i.e. old activities will be deleted when necessary. So I don’t think you need to worry. Please Ambit users correct me if I’m wrong.
So you think it has nothing to do with the transition from MovesLink to Suunto App ?
-
@LudovicTheRunner no it’s that because atm there are 2 services (movescount is still running) it wont mark as synced all the activities on the watch and remove them. That is for now.
You might want to delete the “synced ones” manually, that’s ok, but also the watch will 'recycle" as @isazi said the activities. However, sync can be slower if you are keeping a big log book
-
@Dimitrios-Kanellopoulos said in May Transition Update:
@LudovicTheRunner no it’s that because atm there are 2 services (movescount is still running) it wont mark as synced all the activities on the watch and remove them. That is for now.
You might want to delete the “synced ones” manually, that’s ok, but also the watch will 'recycle" as @isazi said the activities. However, sync can be slower if you are keeping a big log book
ok, thanks. I don’t care to delete them, I just have a lot of activities (210)…I can’t imagine to delete them one by one…
-
@LudovicTheRunner , as long as your activities are synced, you can ignore that warning. @isazi is correct - Ambit memory is circular, once it gets filled, old activities are overwritten by new ones. Actually you should not see that reminder when successfully syncing with Suuntolink …
@Dimitrios-Kanellopoulos , there is no way to delete individual activities from Ambit, only way to clear logbook is forcing FW update. And Suuntolink does set a sync flag , meaning it will already break syncing to Movescount.
-
@margusl
roger that. Thanks I ll check this with the teamMaybe its a generic flag
I think Suuntolink can be reseted ? -
@Dimitrios-Kanellopoulos said in May Transition Update:
@margusl
roger that. Thanks I ll check this with the teamMaybe its a generic flag
I think Suuntolink can be reseted ?There’s no problem “resetting” Suuntolink as it doesn’t care about previous sync flag values stored in the Ambit logbook, it’s happy to sync everything it doesn’t have a record of in its local suuntolink_data.json . Meaning that it also tries to re-sync all activities stored in watch logbook when you switch computers or user accounts. But after every sync it also sets sync flags in Ambit logbook, locking out all other (official) Movescount sync agents that will now ignore those activities.
Not quite sure whats a generic flag, but there are tools for getting and resetting sync flag states directly from Ambit logbook, so there’s no guesswork involved, just plain observation:
- Suuntolink (v3+) - writes flags / reads everything, keeps it’s own record
- Suunto App - does not write flags (for now) / reads everything, keeps it’s own record
- Movescount mobile - writes flags / ignores all flagged activities
- Moveslink2 - writes flags / ignores all flagged activities
-
Why is this information not send by mail?
Just a small number of customers will be at this forum and read this.
Last year I received 2 mails about the transition and beside that a lot of markering shit.
This kind of information howto migrate your data, the new Suuntolink tool etc etc is the kind of information we want to receive.
You get a lot of complaining customers if at one point their data can’t be synced etc.
Your communication about this needs to improve a lot! -
@awinkel all those were at your email, inside the app and everywhere .
-
@Dimitrios-Kanellopoulos said in May Transition Update:
@awinkel all those were at your email, inside the app and everywhere .
Well… not quite. I don’t think I know anyone who knows anyone who has received transition update mails after December 2019.
-
@margusl not sure what you mean. This is a may 2019 update and your emails talk about dec.
Last update was there, and provided the details about the movesoucnt closing in summer 2020 no? And we passed this date
-
@Dimitrios-Kanellopoulos said in May Transition Update:
@margusl not sure what you mean. This is a may 2019 update and your emails talk about dec.
Last update was there, and provided the details about the movesoucnt closing in summer 2020 no? And we passed this date
Last update at https://www.suunto.com/transition was April 2020.
-
@margusl this is A MAY THREAD
The April update is a short paragraph
Dear Suunto Community members,
As a part of our digital service transition, and aligned with our prior communication we will continue the process of ramping down movescount.com in the coming months. As such, there will be changes to the website and some features will be removed. The future end-state of what is currently movescount.com will be where Ambit and Traverse watch owners will manage key watch functionality like settings, customization of sport modes and planning routes.
We will continue to update the community as we go forward.
And iterates over what it has been said as a statement and clustered all to FAQS etc
-
@Dimitrios-Kanellopoulos said in May Transition Update:
@margusl this is A MAY THREAD
@Dimitrios-Kanellopoulos , this is also the latest pinned thread about transition.
That’s why people are coming here to complain about lack of communication. -
@margusl Ok but that is how the forum did it with shorting. The Last APRIL post here is in my email. Sorry but what are talking about here?
-
@Dimitrios-Kanellopoulos said in May Transition Update:
Sorry but what are talking about here?
What about updates in January 2020, April 2020?
(I don’t get the point for April 2019 update/mail, I have it listed too… but that’s OK)Transition update mails stopped in December 2019. Most targeted people have no idea that Suunto has quietly published few more updates in 2020 and that they should now reach out for this information themselves even though those previous mails promised to, quoting the Important Digital Service Update :
We will keep you updated on these coming changes
All the “read more” etc links in those mails are also expired by now (“This link has expired. Please contact the sender of the email for more information”)
Notifications in Movescount mobile app are visible only for Ambit3/Traverse/Vertical users and it’s just a vague reminder to move to Suunto App, not mentioning anything about Suuntolink nor the role of movescount.com after next few(?) months. Well… maybe there’s some super-informative content popping up in Moveslink2 when Ambit/Ambit2 are connected to the cable, but for some reason current Moveslink2+movescount-com users seem to be clueless about switching to Suuntolink+SuuntoApp+Movescount-com combo. When running Moveslink2 without connecting a watch there’s no information about already effective nor upcoming changes.
-
@margusl
there is definitely room for a FAQ on the Suunto Website regarding the transisition. Even more so since A3P is still actively sold. -
Thanks to the automatic link creation for .coms, I was quite excited to see that there were now two websites devoted to the subject. Possibly @margusl’s own creations. Apparently not. Damn.
-
@margusl said in May Transition Update:
What about updates in January 2020, April 2020?
(I don’t get the point for April 2019 update/mail, I have it listed too… but that’s OK)Exactly.
We can move this to a new thread if that is the case. More important, also Suunto decided not to support anymore the forum as the prime source of feedback about the transition. That is why also further updates are not listed here as no user feedback was needed (decisions taken)
