@Brad_Olwin The comparisons I’ve seen on here are usually against the Vertical 1 (which seems to report accurate distances). I’m wondering if you’re not seeing much difference because you’re comparing with the Vertical 2- perhaps this watch uses the same algorithm as the Race 2? I don’t mind if the distances are a little bit off as nothing is going to be perfect, but if I have my forerunner 265 on one wrist that says 12k and it’s still 11.8k or less on the Suunto, then that will bug me!

@cumbrian-runner OHR is highly dependent on the individual. For me Race2 OHR works well with steady runs and poorly on intervals. I almost always use a belt because I want better HR data. I often wear Race2 on one wrist and Vertical on the other. I get nearly identical distances and altitude gains/losses with both. I can share many instances of data if you wish.

Today first run no downhil metrics, after rebooting worked well till the end.

As soon as I completed an interval exercise and marked it as very good, from feel perspective. The recovery status went from 31 to 51.

Hello, Have the same problem, HR stuck at 110 BPM during the first 20 minutes of running, then suddenly goes up to 165 bpm which is the correct reading. It was working better before the last firmware.

I would like to see a sum of descents (total vertical) on weekly, monthly, and yearly summary. So far, I can only see the distance, which in downhill skiing is pretty irrelevant

@gipfelkind I found the cause: the Morning Report is triggered by arm movement while I’m still in bed. If I don’t see it and leave it undismissed for an hour, it vanishes and cannot be accessed again that day.

[image: 1771754828727-img20260222100401.jpg] Suunto – built for the grind.(Nix für Träumer ;o))

@kristofkmety said in Suunto Race 2 General Discussion: Anyone heard of something they planning to integrate more datas to apple health or bevel? maybe? If you want Bevel to access Suunto data Bevel needs to initiate this. Suunto has an API that Bevel can have access to. I do not know the limits on the API or what data streams Suunto allows access to. This is not something that Suunto would initiate from their end.

@Fabii85 yes, I have the same Problem. After Sleep! I think its the „DND“ Mode?

@Dieter1960 is it iOS you are using with Apple Health? maybe other devide saves data into Apple Health and then Suunto takes those data out from there?

I have been experimenting with wearing a different watch to see if it’s a common issue, but this rash is keep coming back after switching back to SR2. At this point I am starting to think it’s an allergic reaction to some material on the watch itself.

@Manuel-Extreme it is, because the Elite Misuro is a Bluetooth device. Also the Ambit3 is a Bluetooth device and it works with the old watch. The issue is known and reported since months. Just not fixed https://forum.suunto.com/post/181171

@peegee said in Comparing workouts: How is this done? Same as before. In workout, scroll down to Comparisons section, under graph/zones and then select another one to compare to.

For those with similar problems, there are some general posts related to the Vertical 2 model which discuss potential solutions. I’ll will update if they do work. Vertical 2 posts

@Fabii85 I still experience it. It’s only the recovery that is affected. At some point they align more at some it is more obvious with the watch being more ‘strict’. So I follow the watch suggestion and it aligns with how I feel.

@Dieter1960 said in Subject: Feedback on Zone Sense accuracy: Short intervals and Zone 2 threshold shifts: Analyzed the data through a specialized AI model to identify physiological breakpoints I’d be curious to know which model you used. If you ask an LLM to interpret your R-R data it generally uses the same (or similar) model that DFA-alpha1 is based on, but you can then tweak the prompt to ask it to compute the data using an “adaptive” model that should be more similar to what Suunto uses. At least this is something I tried long time ago, and eventually the computation was too heavy for the model to produce a result. AI models have evolved enormously since then. Nevertheless, I no longer look at ZoneSense data during my runs, simply because it just seems to “adapt” to my intensity. If I run at my typical aerobic effort, the shift between green and yellow is very likely where I expect it to occur, but if I run something more demanding (trail, tempo, race, etc.) it puts me in the aerobic zone when I actually have ±10 bpm above my aerobic runs.

Morning report appears reliably, but I can’t find the setting to disable it.;o) Btw I am getting error 503 quite often. The same here. Cheers