@herlas known and reported

https://forum.suunto.com/post/144746 Same issue with my today activity. [image: 1735586221124-screenshot_20241230_201249_chrome.jpg]

@suzzlo should be already fixed in next

@dimitrios-kanellopoulos said in Altitude in app graph differs to movescount: @sebchastang The I am not sure if this so fixable. Moveslink 2 is no longer supported. Suuntolink should be the way to sync as movescount of activity analysis is closing. I did check at your data (you can also follow the link you shared) and they look ok. So this while it looks an app representation issue I am not sure if Suunto can prfioritize this as move-slink is not supported. Hello dimitrios, Just a message to confirm altitude graph is OK in Suunto App now that I have switched to SuuntoLink for moves synchronization Thanks again!

@joaquinxxi yes

I had the same problem and it is solved now, thanks Dimitrios.

@Keelan-Birch hm, do you see any discrepancies in your activities? For me, everything works just perfectly at the moment. HR graphs in SA, Strava and Runalyze are nicely aligned. and even R-R intervalls (ibi) looks pretty good. But the thing is, that I changed the strap for my Smart Sensor. Since I have new strap, everything is just fine. So, just a thought…isn’t your strap starting to misbehave…?

@Dimitrios-Kanellopoulos Cool, yep! Just knowing its up for change is good enough for me, all in time

And today it’s back again.

Maybe true, my point is, times recorded for 1K autolaps in the watch should match times of those 1K laps in the app I’ll give you that the others shown in the app .5KM, 2K and 5K are splits at least this is from running perspective

@Mff73 Ok thanks for this “pre info” I hope everything will go well

I guess it’s known … https://apizone.suunto.com/fit-description

@Dimitrios-Kanellopoulos said in Swimm style missing: @danisius Ok we found the bug. Indeed its our fault Thank You it landed in 4.15.2.

@Davide-Rizzi Ι think that is due to following the Android guidelines. The BT “leaks” location if it’s set on to scanning (other devices can see your BT broadcast). Also this is BLE that scans in the background

@mbartxxx I would ask support for a warrenty repair. The service of Suunto is excellent and they also need to know what’s wrong with few devices. It’s good that this does not happen frequently to more users but Suunto can only fix issues they are aware of.

@Jose-Luis You have to do a factory reset on your watch to re-establish the link to movescount. Reseting the app or just deleting the route won’t fix it.

@Dimitrios-Kanellopoulos said in Ascent missing in old routes: I managed to find the issue. Created a bug for this Good And anyway ascent is wrong. Should be 35m at least I was wrong … In fact the route was drawn from top to the bottom. so calculation is correct considering the direction

@tiberiu-paun my bad before. I confused the threads

@Dimitrios-Kanellopoulos Try now

@surfboomerang said in Duplicated Route: "Route in Progress": bump Got this too now… Same here