@louispar in the app - watch settings - wireless networks -> is the WiFi successfully added? Can you maybe try with a mobile hotspot just to rule out some firewall settings?

@hhouter I did it yesterday on a dive - one POD shared between Nautic and EON it worked perfectly In the case where I saw problems were in none-dive mode on land.

Re software 2.50.26: During last week’s Spine Challenger North I found that, after maybe a day of continuous tracking, when I had the navigation screen showing the backlight would turn on, often at high intensity, if I apparently raised my wrist - but I had disabled this function under General Settings and confirmed this post-event. Wrist raises occurred often because of the terrain so the backlight kept turning on. This caused me great concern because of the obvious effect on battery life and the need for good navigation at night up on the mountains in bad weather. I also note that if I select ‘endurance’ gps accuracy (that is, ‘good’ rather than ‘best’) only breadcrumb navigation is now available, whereas in the previous software version I could select outdoor mapping for navigation for ‘good’ gps (that, I found, is perfectly adequate for navigation in open countryside). Was this change a bug fix or was it to remove an apparently better battery life than the Vertical 2 in the good/endurance gps mode?

@Nikolai-Simonov Thank you for this update! I believe the messenger functionality is potentially rather useful. I tried testing it, but I could not get it to work - in my tests the web UI says that the message is sent successfully, however nothing shows up on my watch. Watch: Race 2 with FW v2.50.26 SuuntoPlus app v: Live.τ 1.6 R3 iOS app v: 1.0.13 (70) Beta iOS v: 18.7.2

@Tieutieu what activity do you use?

@Dimitrios-Kanellopoulos said in Race 2: wrong cadence/step calculated during activities: Did you pause? No, no pause at all. Continuous activity.

Bug detected: Race 2: wrong cadence/step calculated during activities

@Nigel-Taylor-0 said in Sleep monitoring is far from reality: This morning my wake time is a minute before I started running…a little better, except I’m pretty sure I wasn’t asleep for the previous 50mins of breakfast etc and a 15-20minute drive! Hopefully not…

@Néstor it’s also there as far as I can see.

@sky-runner said in Race 2: GPS and distance accuracy vs previous Suunto models: @jjpaz No comment about the distance, but when I first moved to Race S from Garmin Fenix 7X I noticed that it reported noticeably fewer steps than Garmin. Later Race / Race S step accuracy when running was improved but my impression was that it still remained too low, so perhaps Race 2 counts steps more accurately. Here is an example from a recent 14 mile run on trails. The number of steps is 23886. Historically, when running on flat road I did about 1600 steps per mile and on technical trails - closer to 2000 steps per mile. When walking - also about 2000 steps per mile. This trail run was more runnable but still with a decent amount of ascent, some stairs and some walking sections, etc. 1700 steps per mile feels a bit short. About steps/cadence: in all my activities during these 2 weeks, Race 2 have measured less steps and higher cadence than Vertical and Race S and I think there’s something wrong. Both watches in same arm. For example, yestarday’s activity: Race 2: 9,02km. 8736 steps. 87rpm. Race S: 9,08km. 8743 steps. 86rpm. Saturday’s activity: Race 2: 11,21km. 10639 steps. 87rpm. 1h02’38". Vertical: 11,26km. 10647 steps. 85rpm. 1h02’37". So, taking this into account, with same distance and duration, how can I take less steps and faster (higher cadence)? I have asked Gemini about this inconsistency: "The data recorded by the Suunto Race 2 during the 62:38 session shows a critical mathematical inconsistency between ‘Total Strides’ and ‘Average Cadence’. The device recorded a total of 10,639 steps. Mathematically, over a duration of 62.63 minutes, this results in an actual cadence of 169.8 spm (84.9 rpm). However, the watch reported an Average Cadence of 87 rpm (174 spm). For this average to be correct, the device should have registered approximately 10,900 steps, which is not the case. This proves that the Suunto Race 2 is not deriving its ‘Average Cadence’ from the ‘Total Strides’ counter. Instead, it is using incorrectly averaged instantaneous values. This ‘ghost cadence’ (87 rpm vs. the real 85 rpm) directly misleads the FusedSpeed algorithm: the watch ‘believes’ the runner is taking more steps than they actually are, assumes a much shorter stride length, and consequently applies an artificial reduction to the total distance (11.21 km vs. the 11.26 km recorded by the Suunto Vertical)." WOW

I had problems before with intermittent disconnects with the Suunto smart sensor and Polar Varity sense, but it wasn’t to bad or long. On saturday I had my first total failure. Started the activity, on the startup screen it picked up the Polar Varity sense and connected to it. When the activity started the watch lost connection to it, and didn’t connect to it for the whole duration of activity (8 h). The sensor was on and broadcasting over bluetooth. This is a really bad bug. The OHR is not good enough for accurate tracking, and now the external sensors wont’ work.

@cheetah694 fair enought, but with ski resort activity, one could expect that 99,9% of time you take the ski lift ; otherwise, in the cases you mention, I would rather use another ski sport mode.

Still unsolved seems to be a reason to get unsatisfied

@manuel.machado U is not the same, meaning there is no style, and the distance covered is incorrect. From the very beginning, there have been errors in the distance and style, a known problem at Suunto, but they haven’t done anything about it. I use a Suunto 7.

@Mff73 Thanks for Info. I saw that coming.

@zadow I have the Suunto Race and this feature for me, pool lap splits, with a pause manual or auto laps top right button was working fine til October 2025. When you state a firmware update resolved is that the Watch v2.50.26 or the App v3.7.1 (i.e. Apple Phone) a week ago?