@GiPFELKiND I think that is a catch up update for Android. I am not seeing anything in the US for iOS.

@Adrian.S not realy discribe it here - https://forum.suunto.com/post/193011

@enneo the Chinese suunto account (suunto.cn) are not in the same database as the rest of the world (because china impose that chinese citizen data should be stored exclusivly in China), so your auth credentials won’t work

@bhornz all suunto 22mm straps are compatible with the nautic s

@Marcelo-Mönch said: When pairing a chest strap, your watch will automatically disable the optical wrist monitor to ensure the data source provides the necessary accuracy for functionality. It will disable the optical sensor of the watch, but not for the reasons you stated. Suunto just can’t work with multiple sources. On the plus side the disabled sensor will save you a bit of battery…

@freeheeler said: @Jose-Luis-Merino-Parra it is under improvement and further development. I am giving frequent feedback and also wish we can soon benefit from it Where do you send feedback please, is there a specific thread or something in the app? Im currently trying a 10 week trail plan but the sessions don’t seem to correlate to my age and performance, which I thought the AI would take in to account setting it up based on previous training. For example my Z2 pace is about 8m/km (OK I’m old and slow but Suunto knows this) but just as an example one session this week was an easy Z2 run of 10k in 1 hour - for me that’s definitely not Z2! I realise it’s still under development but I’d like to feed that back to the right place. Also does anyone know if the plan adapts or updates itself based on performance during the sessions?

I, again, reported an occurrence of my watch loosing connection to my heart rate sensor and asked if suunto is able to find the problem. Here is their reply: Regarding the three questions you raised, we are currently unable to determine whether this is a software defect or an occasional hardware issue. We need to clarify that we have not yet received any batch feedback on this issue, therefore we cannot currently guarantee that it is “fixed” or “will be fixed in a future version.” So, don’t get your hopes on a fix in the next firmware update.

Ok, I see… Thanks for the explanation.

@snow after a backlash on reddit, yes.