@Girts-Gudrits said: what steps I can take to fix it? You could reboot the watch before starting the workout by holding the upper button for ~12 seconds and see if that has an effect on map loading.

Solved (UPDATE!): import old dive logs into the Suunto app (from Subsurface, divelogs.de, or any logbook) Like many here, I had years of dives from an old Suunto HelO2 sitting in Subsurface/divelogs.de and no way to get them into the Suunto app when I bought a new Suunto watch. Every forum thread on this ends the same way: “import to DM5 first, then SuuntoLink” — and then people get stuck, because DM5 only accepts formats nothing else can export, and even when you do get dives into DM5, SuuntoLink imports zero of them. Here’s what we found by reading SuuntoLink’s import code: SuuntoLink never reads DM5 or its database at all. Its “Import dive logs” feature just scans the folder you pick for .sml files — the per-dive log files that Windows DM5 happens to leave behind — parses each one, and uploads it to your Suunto account. No SML files in the folder, no import. That’s the whole mystery. Which means DM5 can be skipped entirely. One script converts a Subsurface logbook straight into SML files that SuuntoLink accepts: https://github.com/974c426jdy-svg/Import-old-dive-logs-into-the-Suunto-app- The pipeline: get your dives into Subsurface (it imports from divelogs.de, UDDF, MacDive, Diving Log, old Suunto SDM files, and dozens of dive computers) → export as Subsurface XML → python3 ssrf2sml.py mydives.ssrf → SuuntoLink → Import dive logs → point at the output folder. Done. Full depth profiles, temperatures, gas mixes, and tank pressures all come through — verified with a 56-dive logbook (2014–2025) now living in the Suunto app. Plain python3, no dependencies, free and open source. Good to know: always test with 1–2 files first (uploads go straight to your live account); re-importing is safe since the server skips duplicates by date+time; imported dives show in your app diary and count toward totals but don’t sync down to the watch (Suunto watches only display dives they recorded themselves — that’s by design, for all imports); and the repo also includes tools for getting dives into desktop DM5 itself, if you use it as a logbook, including a fix for its silently-dropped tank pressures. Tested on macOS; Windows should behave identically since SuuntoLink works the same way there. Would love confirmation from a Windows user. Hope this saves someone the two weeks it cost me.

Could you please provide the Suunto Race 2.39.20 (or late 2024) firmware OTA package? Thank you!

@Nikolai-Simonov I just submitted two screenshand associated SIDs to the support email. 2 recent 5 mile runs are getting truncated shortly after starting. Duration is saved correctly but pace and distance way off. Vertical 1 Ti Solar with current FW and app Suunto App latest beta LiveT app updated. Happened July 8 and today. [image: 1784428310346-img_1837.jpeg] [image: 1784428310392-img_1836.png]

@sky-runner A couple of days ago I successfully used the Live Segments S+ guide on a trail running segment I have never run before (and got a KOM). Watch is Race 2 with the recent Q2 update - 2.56.18 and everything worked as expected. Last month, on the previous SW version, I had 2 unsuccessful attempts for different segments. For the first one the watch did not detect the start of the segment. For the second one it (wrongly) determined that I had went off course and stopped tracking the segment halfway through.

@BadCode-Crew at garmin edge the oposite happens right ?

@Lazar-Dimitrov there has been a test implementation some years ago for this. But it has been abandoned. Suunto has a product management, that is prioritizing all possible features. The developers just do, what is high on the list. It seems, that this one is lower priority than other features. Anyway, I wanted to say that it does not make sense to talk to the developers directly. You want to convince product management

@michael-schwarz da die Messung durch optisch durch Licht funktioniert, ist das Signal für die Vertical 2 nicht gut genug, um als valide zu gelten. Andere Hersteller haben evtl. andere Sensoren und andere Schwellen, was akzeptabel wäre. Und ja, das Problem haben andere auch. in English: the WHR does not work well on a tatooed arm. This is known.

@snow Yes. A known issue for all android users. Recommended bypass is to activate floating keyboard, that will allow you to push the keyboard to the top of the phone screen.

@BokiRun Send a mail to support@suunto.com and share your logs with them. To send the logs, in the suunto app goto your profile, then settings, in that list there is a send logs to suunto option. Send it as quickly after the crash as you can. It’s important to send the mail to support from the same email address that you have configured in the app.

@vinc14 Why? Don’t know. In that case, try to stop navigation from that route and then start a new navigation to another route (instead of switching one route to another). It works for me in such situation.

@lydum, known and fixed in next firmware.

You’re not alone https://forum.suunto.com/post/193526

@leorus have you set the depth for automatic start to the maximum?

@pavel.samokha Thanks. Didn’t intend to sound negative. Suunto’s map update process is a bit of a mystery and must be more complicated than I imagine. As a frequent OSM contributor, I’m probably just more aware of it than others.

You can now use quantified-self.io to import any fit file to Suunto , enable automatic sync from Garmin , coros or wahoo to Suunto and vice versa. Enjoy