@Belli-Sher-Tri @mrkus it is a well known and reported issue of bluetooth sensors dropping connection (power-meters and HR belt monitors) to Vertical/Vertical2/Race/Race2 that Suunto unfortunately (at least officially) continues to refuse to acknowledge. If you search the forum there are multiple instances of this problem reported (and very well documented). ‍️ @brad_olwin @isazi @dimitrios-kanellopoulos @pavel.samokha

Fixed. “modificationTime”: was wrong in the manifest.json.

@Steven-Limmer Hello. I have had a ride yesterday and checked my data as I also had a stop. I stopped for a bit more than 15 minutes, exactly 11 minutes with no power output was recorded. I’m not sure if my Assioma Duo Pro RS did fall asleep, but when I continued, power data and cadence were there immediately. I will monitor this on my next rides (Watch is Vertical 2, latest FW) I have checked the Favero App settings for the PW: standby is set to 5 minutes right now and max. standby time would be 720 minutes with a lot of options in between. Maybe worth a try?

@thanasis For me it’s about 9% per day without training.

@janiroodt I recommend that you read this: https://forum.suunto.com/topic/14710/race-2-accuracy/123 It appears that there is a correction in progress.

@ccrhenrik This is usual behavior for nearly all smartwatches I know (not only Suunto) that they can pair to only one app connection. You need i.e. to disable bluetooth on the other device (or to unpair it in BT, but then you need to pair again) , then it switches to the app on the second device. This is how I have solved it.

Maybe it’s because it is too similar to Ocean and serious divers or active people don’t buy limited version watch. Nautic S falls in that gray zone, where it’s not way cheaper than Ocean, yet looses some functionality and maybe not enough market for that product?

Found out the other day, if there are too many Guides waiting, it will stop syncing as well. I deleted ones for the past and the future in the app and it started syncing again…

@enneo the Chinese suunto account (suunto.cn) are not in the same database as the rest of the world (because china impose that chinese citizen data should be stored exclusivly in China), so your auth credentials won’t work

@bhornz all suunto 22mm straps are compatible with the nautic s

An app like this would be super useful for planning longer ultramarathons on trails where the terrain is always variable. I did a similar plan many times where I try to come up with a target time for each aid station on the race course and then during the race see how I perform against that - whether I am ahead or behind the plan. The main problem is that as long as segments are based on distances, they aren’t going to be accurate and often deviate towards the end of the race. Perhaps for officially measured road races distances are accurate, but for trail races they are usually not. Towards the end of a race, distance that you have on your watch can easy be up to 5% off from the official distance, depending how accurately the official race distance was measured. Often, tace officials just use distance from CalTopo or other online mapping tool, and that is often way too short. It would be super nice if segments were defined by waypoints on the navigation route and if Suunto supported an extension of navigation route that allows including timestamps. That would allow building on the estimated pacing plan right into the navigation route. Garmin does actually have that and the Pace Pro feature utilizes that, and some 3rd part tools like Ultrapacer can generate a plan that can be loaded on a Garmin watch. I think a feature like this should be built-in, or at least have some built-in support - like an ability to load a timed GPX (GPX with relative timestamps) and tell you how much you are ahead of behind when following the route. Then more advanced apps could be built on top of that.

thailon said: @larrybbaker will try, thanks. heya, seems it works! Thanks!

@Ze-Stuart happens to me, too

Setting default works again on iOS.

Thank you for this, this is certainly a step up for strength training experience on Suunto. And good point on N.B. regarding the touchscreen! I had a senior moment and forgot that you need to access custom battery mode for it

@Stefan-T. I guess it depends on the day. On a good day, we can laugh it off and see it as a minor issue. On a bad day, we might look at the watch and wonder, “Seriously? How can such an expensive watch have such a ridiculous bug?” Anyway, let’s hope the next firmware update fixes it — preferably before we all become experts at soft-resetting our watches.

@janir Solved: importing old dive logs into the Suunto app (from Subsurface, divelogs.de, and other logbooks) Like many here, I had years of dives from an old Suunto HelO2 living in Subsurface/divelogs.de, and no way to get them into the Suunto app when I bought a new Suunto watch. The only door into the app is SuuntoLink’s “Import dive logs”, which only reads DM5 — and DM5 only imports SDE/SDP/SML/Suunto-XML, which nothing third-party can export. Every thread I found on this ended unsolved. So we reverse-engineered DM5’s actual SDE dialect (from real DM5 exports and its SQLite database) and wrote two small Python scripts, free and open source: https://github.com/974c426jdy-svg/Import-old-dive-logs-into-the-Suunto-app- subsurface2sde.py — converts a Subsurface logbook to an .sde that DM5 imports: full depth profiles, temps, gas mix, tank pressures, locations, buddies, notes. Since Subsurface can import from divelogs.de, MacDive, Diving Log, old SDM files and dozens of computers, that covers most logbooks. fix_pressures.py — works around a DM5 import bug where tank pressures import correctly but display as 0 (DM5 stores them in bar at dive level but its UI reads the gas-mixture table in millibar). Pipeline: Subsurface → export XML → subsurface2sde.py → DM5 File > Import → fix_pressures.py → SuuntoLink → Import dive logs → Suunto app. The README documents the gotchas (DM5’s silent duplicate-skipping, its hidden database folder, locale decimal separators) plus format notes for other tool authors. Caveats: tested on DM5 1.5.4 on macOS with a Swedish-locale system; there are flags for other date/decimal formats but I’d love confirmation from a Windows user. No dependencies, plain python3. Old dives won’t get the 3D dive view on Ocean/Nautic (that needs data recorded by the watch itself) but they count toward your history and totals. Back up before a big import — the trial-run mode exists for a reason. Hope it saves someone the week it cost me.

The Nautic S now seems to have Trimix. About the Ocean I’m not sure. Does the Oceans Altimeter automatically adapt the dive algorithm for Mountain Lake diving? The Nautic S not if I got the manual right