Cancellare itinerari

freeheeler

@_giovanni
@Gianfry
I’ve requested this in many surveys.
I guess it is either more complex than we think or lower priority as it is not a task that we have to do frequently… normal or ideal case is to setup the watch once and then use it 5 years

@Gianfry hello, same problem here…
it always worked fine, the only different thing I did was to directly delete on SA the route without disabling it first and while I was doing that the watch was offline… I don’t know if there is an unknown bug in this procedure

@freeheeler said in Cancellare itinerari:

it’s annoying, I know, but with screenshots, as I suggested, it can be done during a lazy rainy evening

Ok, tomorrow it’s gonna rain

@gi0vanni it’s happened again… now I’ve two routes on the watch

Anybody else? I hope Suunto takes care of this

@Gianfry unfortunately this problem keeps going on… pretty annoying

@me
I contacted support and explained the issue.
It seems that the problem stems from the fact that I delete the route from SA instead of disabling it and then synchronizing it with the watch. They told me if I delete the route from SA it is then not possible to remove it from the watch anymore

A bit odd in my opinion because it is perfectly legitimate to delete it… but ok, got it.

Spree

@gi0vanni Deleting should definitely be enough. This sounds like a bug rather than a feature to me; I’ll double check what happens if I do the same.

isazi

@Spree it will happen the same, unfortunately at the moment you need to first remove from watch, and then delete.

@Spree

isazi

To work it would have to force you to have your watch connected before delete, and do remove from watch and then delete automatically, or have a routine that removes routes front the watch if they are not in the app anymore, similar to what happens with ghost notifications.

Spree

@isazi said in Cancellare itinerari:

or have a routine that removes routes front the watch if they are not in the app anymore, similar to what happens with ghost notifications.

Yes, that’s what I would have assumed. Sort of a permanent check/sync for routes. But it might be more complicated than think to implement.