Interval timer settings mismatch

A Former User

@amidas hi,
yep I confirm this but it happens only with some value (e.g. try to set low 5 and high 11 and it’s ok).
I do not think it will be fixed…

isazi

Okay so you mean that the two parameters are inverted?

amidas

@_giovanni nope it does not depend on values. I’ve just set low = 15 and high = 20, but I see high = 15 in my Ambit. I also tried your values (5 and 11), but the results is the same.

amidas

@isazi yeah, precisely.

isazi

@amidas I will fill in a bug with Suunto, using your screenshots.

amidas

@isazi Just for the information. I have the latest version of SuuntoLink – 4.1.6

isazi

@amidas done, will let you know if I hear something.

A Former User

@amidas
nope it does not depend on values. I’ve just set low = 15 and high = 20, but I see high = 15 in my Ambit. I also tried your values (5 and 11), but the results is the same.

yup, funny for me it’s ok

A Former User

I didn’t notice this as recently I didn’t use this feature, but now I’ve just tried it with different combinations (even set time based for one and distance based for other, repetition set to a value or to infinite) and my results were the same as for @amidas.
It’s funny though how it’s ok for @_giovanni, if the same version of SuuntoLink is used. Maybe it is related to other setting from the sport mode.

isazi

@andrasveres I can say that Suunto received the report and they are working on fixing this.

amidas

@andrasveres, I wonder if this issue applicable for Ambit series or for others devices too? I guess owners of non-Ambit devices would also noticed the bug, but so far they didn’t.

A Former User

@amidas I’m afraid Ambit and Traverse users are the only ones to be able to notice this as SuuntoLink is used with newer watches only to keep firmware up to date. See my post here.