Same issue, and yes, syncing from SportTracker…

@Dimitrios-Kanellopoulos Awesome 😉

@Bulkan this is actually the cycle part of a triathlon…

@sartoric Sorry.

Sadly can confirm the same… Hadn’t really noticed it hadn’t… do as Danisius suggests seems the only way to get it working… Would suggests its a bug it has aquired in last up date to Suunto app…

Now going back fully to MC app and will occassionaly give Suunto app a go… Just far too much wrong with Suunto app now.

https://app.suunto.com/move/johan6504/5d2624d517683ac68a309a9e?imageId=5d2627fda6957b25e75fe9a2

I have had a similar problem.
Followed all proposals (delete from phone, unpair on watch, restart phone, etc.)
Watch is found - all good - until the watch returns to the time screen. Connection is automatically lost and the phone and watch have to be reset and paired again. Most annoying!

Any suggestions please.

Hi,

This post is created in iOS bugs, but it should be moved to Feature Suggestions… BTW, there are different post talking about zones, please vote there (so votes are aggregated)

https://forum.suunto.com/topic/58/customisable-heart-rate-zones

BR

I hope they will stay in the other screens, where they seems to work. Stroke rate is a very useful metric for swimming. I would say that it is much more useful in swimming than in running.

suunto 9
software 2.8.24

I think this is fixed already for the next staged update.

In theory you should not have any data loss

Try a soft reset first

@Dimitrios-Kanellopoulos 😂😂😂😂

SA uninstall / install solved this problem, too!

@Egika no pause, it stopped whilst I was on my bike but continued recording the HR data and the route as all the route appeared on Strava. I have the latest version of the app 1.13.0 (7675) which is the latest version on the Appstore

@Paul-Nier
Have you tried via cable with the new SL version ?

Today after trying multiple times I could enter. I cannot mention any specific reason why it now worked as I did nothing else… But still information for Suunto to take a look at this.

@Stefan-Kersting It is a fix for an old bug.