When Ambit 3 Peak will transition to Suunto APP?
-
@dkoor You can make changes on Movescount web, then sync with the Android Movescount app. That will work too. That’s what I do 99% of time. I never sync with the cable.
-
@silentvoyager
I wonder if the connection from a MC app apk (?) backup will remain to work with the evolutionary MC web…?! -
@TELE-HO said in When Ambit 3 Peak will transition to Suunto APP?:
@silentvoyager
I wonder if the connection from a MC app apk (?) backup will remain to work with the evolutionary MC web…?! -
I have migrated and come to a grinding halt. App does not sync or randomly syncs parts of old activities from a month or two ago. The App looks good but so far for me is style over substance as is bloody useless. Annoyingly I have just read that the transfer from Movescount to the App by linking is once only so I can’t go back to Movescount and then resync. Contacted support this morning and they went through the usual try this, try that but all failed so waiting for a level2 response in the next 48 hours. Yes my Ambit3 Peak is old but it just does exactly what I need it to do.
-
@Cookiemonster said in When Ambit 3 Peak will transition to Suunto APP?:
App does not sync or randomly syncs parts of old activities from a month or two ago.
Andoid? Did you get it pass though initial full sync? First sync from A3 can be painfully slow, it can take over an hour if watch logbook is full. And during first full sync the process seems to be quite easily interrupted - watch goes into standby, general power saving mode of the phone is too aggressive (on my Galaxy S9 I’ve had numerous anomalies even with medium power saving settings), power settings for the app are too restrictive (optimized battery usage and allowing background activity in Samsung terms), probably something else as well. During those first syncs I’ve just kept watch on wrist so it would not fall into standby and have tried to keep Suunto App active.
I’d just start from the very beginning - turning off all power saving settings on phone; unpairing watch from the app, checking that it’s also gone from phone’s bluetooth device list; unpairing Mobile App from watch menu; and starting over with pairing and syncing. Well, a way to dramatically speed up that first sync is just to clear the watch logbook by forcing FW update though Moveslink2, but that of course might mean some data loss. Forcing FW update has has also cured some strange connectivity anomalies I’ve had in a past and as I’ve started having them again (for no apparent reason SA wants to pair with the watch again) , I might need to go through it myself as well.
I also have a Movescount app installed on the same phone and while I personally haven’t noticed any Suunto App issues due that (SA background process has always kicked MC out of the way), it might be different for others.
Once all previous logbook entries are transferred, syncing A3P with Suunto App is faster and more reliable than it was with Movescount app, at least in my experience and with my setup. While Suunto App doesn’t do much for A3 / Traverse users, syncing itself works quite well.
-
@silentvoyager said in When Ambit 3 Peak will transition to Suunto APP?:
@dkoor You can make changes on Movescount web, then sync with the Android Movescount app. That will work too. That’s what I do 99% of time. I never sync with the cable.
So far I have never synced with the cable. syncing worked good thru MovesCount android app.
I had more time to look at the watch/internet Movescount service and I have to say that I’m pleasantly surprised, and more with all the possibilities. I can arrange myself a route, metrics, warnings and stuff each time I got for a new activity.
And once fully familiarized with this process, it’ll go as easy as it gets. -
@margusl thanks for your reply, I am on iOS and have tried everything including a hard reset of the Ambit3P to clear out all the old logs that were causing many issues but that made no difference. Awaiting support to get back to me after a long discussion with them this morning. I really want to get this sorted otherwise it will be goodbye Suunto (except for diving).
-
@Cookiemonster said in When Ambit 3 Peak will transition to Suunto APP?:
@margusl thanks for your reply, I am on iOS and have tried everything including a hard reset of the Ambit3P to clear out all the old logs that were causing many issues but that made no difference. Awaiting support to get back to me after a long discussion with them this morning. I really want to get this sorted otherwise it will be goodbye Suunto (except for diving).
Any updates ?
-
@LudovicTheRunner Yes, they could not get anything to work and said to send the watch in for repair. Speakimng to another Ambit3 user with iPhone 11 they have the same problem so it is clearly not the Ambit 3. I have decided to use my back-up phone (iPhone
with teh Suunto App for syncing which works OK but truncates the routes on the map. Bizarrely though it transfers all the data to Strava that displays the route correctly so that has to be a Suunto App bug. -
@Cookiemonster nice to find another DB paddler here!!
And we also are new owners of A3P!
Hope it will be a great experience… -
So, in the end, was someone in this thread able to move to Suunto APP using his A3P with all the moves correctly synchronized ?
-
@LudovicTheRunner , I went through the transfer about a week ago, wanted to get over with it before May as they seem to plan some Movescount data handling change:
Moves that have been deleted in Movescount after May 2019 will be transferred to Suunto app and may still appear in the Diary. If this is the case, we kindly ask you to manually delete them in Suunto app.
https://www.suunto.com/Support/faq-articles/movescount/how-do-i-transfer-my-move-history-from-suunto-movescount-to-suunto-app/I had synced Ambit3P to both MC & SA since Oct. 2018, maybe just missed some activities in MC, also had few deletes sometimes from both services, sometimes only from one. So the content wasn’t quite 1:1 and there was a great potential to double nearly everything I had done during 2019, but after transfer it turned out quite OK:
2019 Movescount 439 moves 411:37 hours 4344 km 2019 Sports-tracker 456 workouts 425 hours 4457 km 2019 Suunto App 461 activities 425:23 hours 4457.49 kmAfter transfer I did remove some activities through sports-tracker as I discovered that feed view in ST dashboard was basically a live status view of transfer progress and once the activities from overlapping time frame started to appear there, those were mostly some super-short test activities that I had once already deleted from SA.
Though note that during the time I synced to both services, I made only few changes to those activities in MC and SA - so almost no tags, comments nor manual duration changes, this probably helped as well.
It’s actually quite easy to get a list of activities from both Movescount and sports-tracker to track down those differences, but so far I haven’t really bothered with this. Diff between Suunto App and ST activity number comes probably from some kind of SA caching.
Before transfer I disconnected all my 3rd party services to avoid duplicates there and reconnected once finished. And also exported & backed up all Movescount data (http://www.movescount.com/settings#export) ; also all summary data with all tags & notes that are not included in export (http://www.movescount.com/Move/MoveList , it’s json and needs some processing to be useful, also works only if you are logged in to Movescount )
-
-
Finally, after one week one synchronization to get all my moves from movescount to be inserted into Suunto link, I can now fully rely on Suunto link app.
