The thing is that the OHR sensors (watch and armbands) can measure R-R doing estimations as they can measure the HR. They do not measure directly the electric pulses as the chest straps. Is for that that that they do not work with Zonesense.

Tested today with the Coros HR armband, everything seems fine - firmware du Coros : V1.22.0 [image: 1771852447633-img_0483.jpeg]

@Brad_Olwin “My Plan” is Suunto’s own approach of a training plan, or is it called differently now? I use the iOS app in German translation, what is still a bit lacking…

@SirMcKey @sportsfreund @brad_olwin Thank you! I’m slowly getting back into online things…

@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.

@Dima-Pursanov Let’s hope so. It would make the watch a better tool.

@Ray-de-Jager In practice, you cannot upload any other base maps with underwater details (bathymetry, depth contours, etc.) to your Suunto Nautic other than those provided by Suunto, and there is no documented “unofficial” solution for importing Navionics, CMAP, Openseamap or other maps. The only option is to import GPX/KML tracks from external nautical tools, which the watch will display as routes on top of its own base maps.

Hello; I got almost the same problem but here i get a phantom call, nothing on my phone butt always on my wristh : unknow number. I now use even a call blocker but stil : missed call notification. on the latest software butt very annoying. Greetings

Still crashing: this app doesn’t like when I follow a route I have created. It struggles a bit to lock my position on the route. On this example my real position (red) and my route (blue): app is stuck 383 m from my real position (blue dots) because there was a small detour and it can’t process it. Eventually it crashes because distance is too far… [image: 1771769469318-img_9555.jpg]

@cumbrian-runner Welcome to the club --> Thread

A week on & I’ve done a good mix of walks & runs, some hilly & some flat (48 miles with 5111ft ascent). The Race has reported spot on ascent values throughout so the cleaning process above definitely works

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

Hello, I was just skiing 6 days and alpine ski mode worked perfectly. I did two sessions per day, one in the morning an second on the afternoon. I did not needed to do reboots or anything else. Watch is Race 2 with latest fw.

@ADidier said in Third-party training: @Brad_Olwin, I understand that the old operating system of the Race 2, Vertical 2 requires an addition in the form of additional applications, it was designed like this. I just hope that with this new software platform, Suunto will be able to communicate with third parties such as other watch brands (Garmin, Coros) that do not use Suunto+. In the meantime, I hand transpose my Runna plans into interval training. At the moment, there’s no sign the new OS used for the Run will be continued to be used. The Race 2 and Vertical 2 use the older OS and those watches were released after the Run. The Run OS was described as “an experiment” not as a direct successor.

One year later this issue still exists. I did a 50K trail race today that consisted of 3 laps. The arrows were absolutely invisible behind several tracks from multiple laps. There were at least a couple of tricky 4 way trail junctions on the race course where the arrows would be helpful, if they were visible. I didn’t have time to take a picture of my watch because I was racing but here are fragments from the recorded activity: [image: 1771720463549-screenshot-2026-02-21-at-4.33.38-pm.png] [image: 1771720472616-screenshot-2026-02-21-at-4.34.05-pm.png] Please give this simple fix a priority!

@SuperFlo75, @gipfelkind, Thanks for the answers!

I have similar issues on my Race S several months ago an apparently fixed a couple of firmware update ago. In recent weeks I realized the problems popped up intermittently. I had been diligently sync-ing and exporting Stryd-only data for my runs and compare them to Suunto’s data. About half the time, the power numbers matched well, while the others will be off by 5 to 10w. And when the data got merged into Power Center, the Suunto’s numbers persisted, “compromising” the overall data quality. This is really frustrating.