@johann.fuehrer Yeh, It’s a mess. I have several issues now and no way to reference one. But I guess most of them aren’t actively handled by Suunto for my race s.

@sloppysloper said: Only very recently with iOS 27 did Apple Health get support for HRV in the RMSSD format, so maybe writing HRV to Apple Health is now possible for iOS 27+ users. Yes, Apple calls this “Recovery HRV” and is a separate category in Apple Health from the original HRV. I already have seen some apps update to ask for read permission for this metric.

Is it under my impression of the bluetooth sync from ambit 3 with latest betas are slow? like minutes for a 3km run. the watch seems to "cut " the bluetooth since it is so long. yesterday to sync 3 small 3km activities it was there a couple minutes and even failled on the third.

@Dimitrios-Kanellopoulos 3 things. I tried the party that asked for permission in the first place. Revoking from their site doesn’t work. Yes that’s a mess. Suunto support directs you to a place in the suunto app. But either suunto support doesn’t know how it works, or the place they redirect you to doesn’t work. The party that grants permission should have a function to revoke that again. I know of no system that doesn’t provide this. (be it, google, git or anyone else). Suunto doesn’t provide this function, so it seems. The 3rd is the most important. Of course the party that grants access should be able to revoke that access again. I don’t understand why someone would think otherwise. It’s a security and privacy risk if this function doesn’t exist. You cannot rely on the party who asks permission to give up that permission. One has only control over the party that grants the permission.

I think I found a hint to the second issue. Looking at a run in Runalyze shows a different view: [image: 1789738980334-207c307b-2611-4e38-8f82-697a43571638-image.jpeg] So, instead of 259/435 = 0.596 you have to calculate 259/90 = 2.88 what makes more sense, but seems a bit harsh… Especially if you look at the individual metrics there is still something missing in the puzzle… GCT: 259 is “good” FT: 90 is right in the “Jogging” part of 80-120.

Bug found… The Nautic does not measure GPS when the device is under 1,5m of water (common for dive-computers). As GPS is new to dive computers… the Nautic should especially update the GPS location when it is above 1,5m of depth. Here there are actually a chance of getting a gps-fix, as gps else does not work under water! Therefore the Nautic device reports: null’s in the route. But, the gps-chip inside the device actually properly has a measurement ready for the point inside…

@OutdoorMan I found the same, and looks like certain metrics are not compatible with all sports.

It would also be really cool if new badges appeared on the watch when you earned them. Other watch brands are pretty good at this. I know not everyone likes the idea (so it should be possible to turn it off), but some of us are easily motivated by certificates, badges and medals, no matter how cheesy it may be [image: 1789373955230-watch-badges-small.png]

Ha, 3.14.0 update came through these minutes. And it is fixed.

I’ve dug a little deeper and discovered that most of these issues are rooted in OpenStreetMaps. the crazy idea to include Stephansplatz subway station with routable paths is actually already implemented in OpenStreetMaps completely unbeknownst to me there’s a long distance trekking route called “Sultan’s Trail” (kind of a knockoff of Camino de Santiago) that apparently runs from Vienna to Istanbul. Somehow this trail has made it into OpenStreetMaps with a really high routing weight, so all routing apps seem to follow it, and it doesn’t run straight through Kärntnerstraße, but takes the detour shown over Neuer Markt. Doesn’t make the routing in the Suunto app any better, but at least Suunto is not alone to blame here.

@darrepac just pressing a button does not stop sleep tracking. I do this regularly.

@GratefulDeadpan @GratefulDeadpan I’m on Android latest beta and don’t have that option. Don’t know if it appears when connecting a Suunto Run

So I started looking into it a little. Suunto app doesn’t enrich activities after upload, but Strava and Garmin does. Worth knowing before. So I don’t know how to do it in a place without a cell phone signal. That’s really bad. I tried ran with a Suunto Vertical and a Garmin Enduro 3 at the same time from no phone signal location. The Garmin activity came out with weather conditions and a place name attached; the Suunto one had neither. My first assumption was that the Vertical hadn’t got a GPS fix at the start. But it looks the difference is entirely server-side, after upload: Weather. Garmin Connect and Strava both take the activity’s coordinates and start time and pull historical conditions from a weather API. Suunto doesn’t do this. The only weather-ish data in my FIT is the watch’s own temperature sensor, which mostly measures your wrist. Place name. Same story - Garmin reverse-geocodes the start coordinates and names the activity after the location. Suunto leaves it as the sport type. One separate thing that caught me out: the forecast widget in the Suunto app takes its location from your phone, not the watch.

I’d try restarting the app and checking for an update first. If the share button still does nothing, reporting the iOS and Suunto app versions might help them reproduce it.

@peegee heat strain score

@Marcelo-Mönch I’m talking about the widget… Mmmh, I wanted to take a screenshot right now, but now it is 2D? Strange…