@maszop First few weeks with the vertical 2 it didn’t work as well. That’s when I knew what I had bought. Still like it, but sometimes I wished it worked. It only works a few times

@Elvis-Tavarez Hi I’m trying some plannings with the coach AI , and I have the same trouble that you. Suunto Coah it’s very simple, most of the plans don’t specify the intervals, recoveries, warm up time etc. in the calendar. So then in the Race watch is worst, you need to plan manually. I think that Suunto need more work over trainning plans, competence like Garmin or Coros plan you the series including rythm based on your goals etc , and you don’t need to do anything on the watch. Albert

@yoora Came here looking for a solution to a similar question. I recently ran a race that is a short 5K (the actual distance is closer to 4.68 km). However, my watch reported that I ran 5.18 km, a full 0.5 km farther than the actual course length with a significantly faster average pace than I actually held. When I navigate to Settings -> Connectivity -> Paired Devices -> Stryd X on my watch, it shows “SPEED & CADENCE, POWER”. I’m assuming these are the metrics the watch is sourcing from the pod. Does this mean that distance is coming from GPS? This was a downtown race, but there is only one “tall” building that is 17 floors, the second tallest is 8 floor, and the rest are 4 floors or shorter. It was a clear sky, and the street is very wide. The watch has very good view of the sky. So I don’t think buildings would cause poor GPS signals. I ran this race with other friends, and all their watches recorded 4.5-4.7 km. I’m the only outlier with 5.18 km. None of them have Suunto though, but as I understand it, I have multiband GPS, so it should not have been a problem anyway. So what is sourcing pace and distance? The watch or the pod? Or is pace coming from the pod and distance from the watch?

I wonder if it’s gotten worse with updates. When I first got the watch I was impressed—the OHR was way better than my old Garmin 745. But the last few weeks/months it’s gotten really bad. 80bpm while sitting down tying my shoelaces (should be ~40bpm). Today on a short 20‑min easy run it spiked to 163bpm (my max HR is in the 150s). At first it would shoot high for the first 10 minutes then settle, but now even long runs have random spikes mid‑run. I tried tightening the strap, but after a few runs I now have a rash on my arm from the watch!!! Usually taking the watch off for 30 seconds helps, but lately even that doesn’t work—I have to repeat it multiple times. Today’s run it just kept spiking again.

Speaking for me - Crowns and AMOLED keep me away from upgrading. AMOLED would be okay but only with maximum battery life. Most of the time I forget that there is touch too. Maybe because you always have to push a button before starting to use touch.

@Reino-von-Wielligh Suunto service repairs have been looking at this issue for 20 weeks, and there is no resolution yet. I handed in my watch on 03 July 2025 at Ultimo Service center in South Africa, who sent the watch to Finland. Does any user have the same problem with the Race S?

Nope, the issue is still there. I charged my Stryd last evening and today I had to repair it to use it. Another ‘dead’ entry showed up in the paired devices list.

@Ian-Beveridge Instead of replacing the Polar strap I decided to buy the CooSpo HZ9 rechargeable chest sensor combined with a new strap. Total cost including postage 22€. This strap gives 0.14 KOhm for both electrodes and for the month I’ve been using it there has been only one single glitch when the strap had worked itself a little bit loose. Otherwise it works really well for HRV data at high intensity workout levels. Unlike the previous CooSpo strap it wont allow me to swap the sensor for the Polar one so I’ve dumped the Polar and will be returning it to Polar for repair or replacement. I don’t think this CooSpo model can be used for swimming (not sure) - but I’m not interested in swimming for at least the time being.

thanks - I know an external HR belt is an option, but my race s is very accurate for all other sports. It just fails entirely for the indoor cycling app. Hoping someone has some suggestions for that.

Charged last Thursday to 100%. Had my usual one and a half hour club training Thursday eve. (My stryd was connected, my polar chest strap refused to connect) Had a 10k trail on friday of about 1 hour (used navigation, no connected devices) Had a 30k trail on saterday of about 3 hours(also with navigating, no connected devices) Gps setting is on the highest (because of some stupid design decisions of suunto you cannot turn down gps accuracy without loosing maps). I don’t use aod. Now on sunday, 3 days after charging, battery is down to 39%. It’s okayish. My previous watch (forerunner 965) did worse. Watch before that (forerunner 935) did way better, but had a mip screen, which is better for sport, and didn’t have maps, only breadcrumb navigation.

@valeR This sounds like two different things. What I saw on my watch was not a safe mode with limited functionality, it reported that it was restoring the watch to a safe state after encountering an error (1403, whatever that means, in my case). It had no functionality other than the progress bar showing the restore progress. No time, etc.

@Steven-Hambleton I bought Barton spring bars that somebody else recommended for Race S. They are a bit thicker and fit perfectly - not loose at all. Also, I compared them to spring bars that came with Suunto nylon band.

@pilleus hi there. Thanks for this. How far back should I go? Or do you know which firmware version I should jump to for the suunto race S. Much appreciated

@ChrisA it is Runalyze… yeah, possibly it’s a me problem

@laufbursche7 I think you should wait - official 26.1 probably will be released tomorrow. I couldn’t stand iP 17 BT issues and installed Beta 4 (not RC) and everything is perfect now. Just as I suspected, battery drain in watch and phone is over - unstable connection was draining watch and phone 24/7. Hope they don’t break something new in the stable release.

@Sixeela29 en tout cas ce n’est pas Suunto qui bloque puisque les segments strava sont une fonctionnalité strava. Je n’utilise pas strava. les infos pour mettre en œuvre sont dans le manuel.

@sartoric actually if I check the activity on the watch, I see HR for the whole run. [image: 1761392386169-img_4023.jpeg]