-
Also some S9baro seems to… considering another post.
So it’s not an ambit problem but a Suunto App problem -
@francescobaldi the other user said his/her problem fixed by itself, most probably by syncing with the app.
-
@francescobaldi oh, I thought you meant you had to activate the GPS on the Ambit while syncing to Suunto app.
I don’t think it is a Suunto app problem. My S9 baro changed the time correctly after sync.
I previously owned an Ambit 3 peak and from what I can it also always synced the time right. I never used suunto app however in combination with the Ambit. Always synced it with the moves count app.If I remember correctly you could also sync the time by activating GPS on your ambit and wait for a fix.
-
Actually I’ve activated everything that can be related to time settings but the time is still wrong.
The only other fix is to set the time manually but IMHO it’s a little bit too retro’, i prefer to do -1 in my head…
-
I have an Ambit 2 & Ambit 3 which I synced in the morning via Suuntolink. The time has been set correct.
-
After 20h I’m still waiting for an automatic correction… still showing +1h on the watch after multiple sync with the SA.
-
@francescobaldi said in No automatic seasonal time change:
After 20h I’m still waiting for an automatic correction… still showing +1h on the watch after multiple sync with the SA.
SA wouldn’t do it, use Suuntolink.
-
GPS timekeeping option for Ambits only corrects time to closest 15 minutes, unlike Traverse, it doesn’t adjust to daylight saving time.
Movescount app users can correct me here, but
IIRC time correction for A3 has always been like that - time is corrected only when syncing with cable and BT sync has never adjusted time. -
@margusl Yes. At least my A3P adjusted only when synced, never automatically.
-
My A3P adjusted the hour yesterday when syncing with MC mobile app. Not sure how it would work with SA, as I have not paired it with SA.
-
@Efejota beautiful Suunto app… maybe it’s better also for me to go back to MC app…
