@Sebastian-Wagner-0 said: NGP, Heat Adapted pace, Wind adapted pace, pace for real effort are all Buggy at the Moment and have the Same Value as the normal pace. The idea is Great. But the implementation should be improved. I am curious how this will pan out. I doubt the idea is great. My stryd at least has a wind sensor, but this in the app just assumes the wind in the weather forecast is correct. But wind is no constant force. There are windguts and the terrain or city could change the wind direction and force. Same for heat. It makes a difference weather you run in the sun or in the shadows, but the forecast cannot tell you that.

@Dimitrios-Kanellopoulos Thanks for answering. I am sure. I did that. Nothing changes.

I’m on 3.12.1 version, I moved to iOS one month ago and I’m surprised not to see some data points that I had on Android (beta), for example heat and wind adjusted pace and especially no ZoneSense data at all (graphs, values). What am I missing?

@isazi Thank you! Just to be clear, the save issue also exists in the Android app - I tried both. Sometimes, when a waypoint is added manually it shows up at multiple matching distances, but that doesn’t work consistently. This specific issue is about importing but it would be great if the same issue is also fixed for manually adding waypoints at the same time.

This is also something that I would like to see fixed. Having my workouts with all the relevant data saved to Apple Health is important to me, so that other iOS apps that I use can read the data directly from Apple Health. Currently to get your Suunto workout data properly synced to Apple Health you need to first sync the workouts through the Suunto API to a 3rd party app, and then use that 3rd party app to sync the data to Apple Health. I’m too using (and paying for) RunGap to sync my Suunto workouts to Apple Health. Having Suunto fix this would save me both money and time.

@Victor-Hugo-Santoyo mine is still not active[image: 1784380649212-img_6446.jpg]

@Dimitrios-Kanellopoulos Thank you for your support in resolving this issue.

@bnft1 said: @elbee said: @bnft1 In the suunto app, under profile, settings there is also a “save to apple health” option you could check. Otherwise, send an email to support@suunto.com Is that what I’ve posted with the first screenshot? Or is there another setting somewhere? I think your screenshot is the health app. I found that setting in the suunto app (and mine is set to enabled) Press the person icon on the bottom left, then settings top right. Scroll a bit down.

@sky-runner I guess you know how to record your runs then!

Thanks for the reply. You’re right that app and watch values often don’t match exactly — but that’s not what’s happening here. In my case the TSS widget works fine and shows correct data. The problem is specific to the Progress widgets (CTL, ATL, TSB), which show 0 both in the app and on the watch. So the distinction is: TSS widget → correct ✓ Progress / CTL / ATL / TSB widgets → 0 everywhere ✗ This makes me think the issue is in how the platform calculates or serves the accumulated training load data (CTL/ATL/TSB), not in the sync between devices. And since it persists after a full factory reset, it’s clearly not a local data problem. [image: 1783353061695-img_8183.jpeg] [image: 1783353068620-img_8182.png] [image: 1783353097619-img_8181.jpeg]

Sascha-Domres said: Average heart rate on laps 1km 5 km 10 km faulty? 1km https://photos.app.goo.gl/hBfVYR8iboVw8cAs7 5 km https://photos.app.goo.gl/3rPG3YmHNwPm4D678 Why are the heart data suddenly missing? I used the Vertical 2 and the Suunto pulse belt But the heart rate was recorded all the time?! Is it because I didn’t drive 80 km but only 77.93? https://photos.app.goo.gl/8reGbmwLFpxzeqws8

Have you tried to remove and reinstall app ? Not sure it would solve, but worth try it ?

@thailon there seem to be an issue with SA at the moment. my activity was synced to strava earlier tonight but I am having multiple problems with SA, too.

Thanks all for your responses. It definitely seems like something is wrong with the way calories are being recorded in the App, and also that it’s not super clear what is referring to what. Hopefully both things can be fixed (or clarified in the laters case) in a future version of the App.