-
Hi @JohanT, I have the same problem with the IP 11 Pro, Ios 13.7. Cannot synchronize with Ambit 3 via Suunto app v1.51.0. Forced to use serial USB and suuntolink application. Movescount is not updated with this method. Unable to retrieve GPX traces !
Suuto is experiencing planned obsolessance. A shame for a Nordic society claiming to be respectful of the environment … -
Hi all again. I need to validate the following as I am trying to raise your voice to Suunto.
So with iOS:
- Pairing works ok
- Syncing fails for some activities ? Right ?
Syncing with the Suuntolink / cable all activities are synced right ?
-
@Dimitrios-Kanellopoulos yes to all! But I think Suunto has already heard but does not want to hear.
-
@entropia437 I am assigning this to me to help here.
Please install the beta version 8634 1.60.0 (you can find info how to install via the FAQ here).
Here is what we are going todo:
- When an activity sync fails we are going to pull that activity manually out of the watch via a special method and you are going to share it with me and I with the developers.
- They will analyse the issue and fix it.
A few info before that
The ambit / traverse can go into sleep mode if it’s not “shaken”. For example if your hand stays static for some seconds the watch goes to hybernation and thus breaking sync.
So when you try to sync make sure the watch is not in sleep/hybernation mode. Just walk around.If you have tried the above and it still says: 1/x activities not synced etc then:
- Go to debug menu (Tap 7 times next to profile image),
- Select “Save data from watch”, Select “Export raw files”, (switch),
- Then select unsynced workout (toggle above), then press start sync.
- After sync finished you can select “Export” which allows you to send the files via email.
- Use my email ext_dimitrios.kanellopoulos@suunto.com and send me those files.
That should do the trick. It will bypass the app processing.
Does this make sense to you guys ?
-
-
@Dimitrios-Kanellopoulos Hey Dimitrios!
Good news, it worked for me with the beta version!!
I managed to sync two activities
It failed a couple of times but in the end the two activities synced.
I don’t know what did the trick. I tried initializing sync from the watch, then from the « debug » menu you mentioned (save data from watch -> start sync).
I’ll keep you updated as I have more activities to sync.Thank you!
-
@benoitg Ok so basically it was not a “bug” in parsing the data (which I personally suspected), but rather something with the connection…
Just out of couriosity, what will happen if you just keep the phone active when syncing, and the watch (meaning dont let it sleep)
-
@Dimitrios-Kanellopoulos Would love to try it… I don’t see the link to the FAQ?
-
-
@Dimitrios-Kanellopoulos it didn’t seem linked to the activities. In my case the app was showing Syncing with a progress bar progressing very fast and then Sync failed. Every time, for every activities.
It wasn’t a problem with the watch or the phone going in sleep mode, you told us to watch for that and it is explained in the troubleshooting pages too.
With the beta it worked more like in the movescount days: sync failed a few times, app showing « not connected » or sync failed, I turned off and on Bluetooth, start sync from watch, retried the process until it worked
Next activity I’ll try to get you some logs to check. -
@Dimitrios-Kanellopoulos thx. install worked… will do an activity a bit later today, see if it syncs…
-
@benoitg thanks for the explanation. Just making sure.
-
@livia_Gmelin
Hi
Not just the synch the paiting also failed for me A3 peak via iphone se 2020… -
No luck getting this to pair with the beta… nor could I export the workout from the debug menu. It eventually throws a “Failure: Archive or data fetch failed unknownError” message. It does seem to recognize there are three workouts there…
When I just try and sync from debug, I get a “Header Parsing Failure”
-
@runnr_az said in Syncing problems Ambit3 with iPhone11:
No luck getting this to pair with the beta… nor could I export the workout from the debug menu. It eventually throws a “Failure: Archive or data fetch failed unknownError” message. It does seem to recognize there are three workouts there…
When I just try and sync from debug, I get a “Header Parsing Failure”
Thank you
-
@lkovari you cannot pair the watch ?
-
@runnr_az just to get this right. Did you manage to pair the watch ?
-
@Dimitrios-Kanellopoulos yeah… the watch has always paired with my iPhone 11, it always seems to begin sync, but can’t seem to close the deal.
-
Hey guys I need your feedback if we need to get this fixed.
@runnr_az I you have a pm
-
@Dimitrios-Kanellopoulos has anyone tried iOS 14?
