Imported a GPX to the Suunto App on phone, added my POI’s, and clicked the toggle to sync to watch.
On the watch if I start the Suunto App and select a route, I’ve now got the routes I expect to have, plus an extra duplicate of the latest one, which has a name of “route_in_progress” (not a name I’ve ever given).
I removed all routes from the watch (in the phone app), and that extra “route_in_progress” route remains.
Rebooted Watch, its still there, re-added the routes I want on the Watch by toggling in the phone app, they all arrive, but the “route_in_progess” route remains.
How do I get rid of it?
@nigel-taylor-0 I have exactly the same case!
@nigel-taylor-0 soft reset the watch and it should take care of it.
@brad_olwin How do I do that?
I can only see how to ‘restart’ or ‘reset to factory settings’ (hard-reset?)
‘restart’ hasn’t resolved it.
‘reset to factory settings’ I don’t want to do!
Thanks - logout and login of the phone app did the trick…syncs the ‘route_in_progress’ route across to the phone app, then just untick the saved on watch toggle, and delete the route, and all is good again.
@nigel-taylor-0 I had to do it several times, after having unpaired and then paired at the beginning the sync did not work, but it ended up working …
In this respect I noticed that quite often the synchronization of the routes is a little random, it is often necessary to start again several times …
Did you unpair and repair “only” ? Or logout and login ?
As far as I discovered, logout do unpair AND login will trigger routes from watch properly.
@mff73 I started by “forgetting” the connection on the SA app, dissociating the bluetooth connection and deleting the connection in the watch …
But it took a couple of times for it to work. At the beginning the “route in process” appeared in SA but even by unchecking this route and then synchronizing, it remained present in the watch …
But like I said this is not the first time that I have to go over and over again to delete or add routes in the watch … I find that this bug quite often.
I have the same issue
Anyone has found a permanent fix ? Is Suunto aware of it ?