@Nelson-Diogo said: @aiv4r yes but you don’t have a way to plan them outside of the app or watch. That’s not enough. With any other suunto watch and entry level watches from other brands you can plan and send them to the watch from outside plataforms like Runna, Intervals or TP. Except for TP—since it’s unclear what will happen now that it belongs to Garmin. Even so, the future of all training platforms is quite uncertain given the rise of AI.

@Nelson-Diogo sorry i missed this part. I have the Race.

@Egika The strange reaction from suunto support I get from multiple bug reports. As if they have no interest in “older” devices.

@isazi No. I forgot to write that I restart when I wear them on my hands and the activity record is not running.

@isazi yes, the watch was updated (I think last week) and I experienced it again during the last rides with the newest firmware. If it helps, I can provide the data. I logged three rides, Dropout during resupply (supermarket) approx. 8h into the ride. Reported 0W for the rest Ferry approx. 1h into the ride. Approx 10 minutes waiting time and 10 minutes on the ferry. I was close to the bike the whole time but the powermeter disconnected. Same scenario as 1.) If I remember correctly, during the first ride with the newest firmware, the power was recorded for the full ride despite a supermarket stop. This was the shortest (<5 minutes) but I went definitely out of range of the Bluetooth signal. As I said, if I can do anything to help you fix the issue please don’t hesitate to ask.

@ccrhenrik Correct. Two computers connected to same Tank POD. The EON Core does not give me the error, the Nautic does. See screenshots of same dive in post above. The tank pressure graph in both computers are equal and do not indicate any loss of pressure, see screenprints below. So my conclusion is that it is not a tank pod error or inteference of a flashlight as the EON didn’t give me the error and functioned correctly. There should be a bug in the Nautic as it indicates the 5 Minutes Mandatory gas time alarm with full tank in certain situations in the beginning of the dive. See both logs; [image: 1785136766242-screenshot_20260727_101822_suunto.jpg] [image: 1785136766287-screenshot_20260727_101750_suunto.jpg]

@VoiGAS said: The Run is the weight king (queen?) It should as it is one of its selling points…

I’m still experiencing random restarts on my Vertical 2. Yesterday, it happened three times in a single day. Fortunately, not during an activity. I have the latest firmware installed. Question: Should I keep sending the logs, or is the cause of the problem already known?

Hello, I have a question about the S+ aerobic decoupling. Suunto excludes the first 10 minutes and uses the following 10 minutes for calibration. During the run AD values ranged from 3% to 8%. At the end, the calculated AD was 16%. I’ve tried doing the same calculation myself and got the following results: entire interval: Pw:Hr 8.49% Pa:Hr 8.37% excluding the warm-up (10 minutes): Pw:Hr 4.35% Pa:Hr 4.45% Pa:Hr -> EF (Efficiency Factor) = average speed (m/s) / average heart rate (bpm) Pw:Hr -> EF_power = average power (Watts) / average heart rate (bpm) % AD = (EF_1st_half − EF_2nd_half) / EF_1st_half × 100 In both cases AD is far from 16%. Some hint?

@VoiGAS, I purchased the Nautic end of Dec 2025 when it became available in Netherlands. Due to the fact that I missed the flexibility which my Suunto EON had to dive with two algorithms (RGBM & Buhlmann), I was comparing the Nautic Bulmann table vs RGBM because my buddies were using RGBM on their EON’s and Vypers. My old computer was the EON Core and I used them on the same POD in my dives to do the comparison. Let me be clear, I am a recreational diver with a good level of experience and I’m diving mainly in Netherlands, I do single dives on Sunday mornings so I didn’t compare situations like repetative diving and situations where RGBM locks out for omitting deco stops and Buhlmann takes this into account for next dives. I mainly was interested to have a comperable setting on the Nautic which was close to the RGBM P0 setting. We had some deep dives planned and we needed to have all computers reach Deco -1 at +/- the same time as this indicated the start of our ascent to the surface. The RGBM Default value P0 was less conservative then the Buhlmann default value - 40/85 (Medium) so for the next dive I changed the Nautic to the 45/95 (Low) value. This seemed to work quite wel and yes behaviour of the buhlmann is a bit different but in general this setting matched RGBM P0. I’m confident that the RGBM P0 which I dived on my Cobra’s, Vypers and EON’s was matching 45/95. So this is the setting on my Nautic I am using until today. My EON core remains as backup on P0.

I do occasionally nighttrails. Never have any problem with seeing the map at night. Since headlights are required during nighttrails (I participate in), staying as dark as possible isn’t an issue.

@Michele-Sella which file or files do I need to install or place to have executed in the Suunto app, and how can this be installed? I found an ESP-WROOM-32 module and an acrylic housing to use.

@Sunday really? This is available on Suunto Run. Really starting to feel like the Run has the superior amount of qol compared to every other Suunto watch.

It at least seems that the last update helped at least the first tests with a COROS armbelt worked I tested some starts and stops during the ride, no signal loss till now

Tide widget started working again today. Watch hasn’t left the house in the last 48 hours so I’m not sure what has changed. Perhaps Suunto has been working behind the scenes to fix it? Still not sure where they are getting their tide data from as it differs a bit from the tide tables of both my nearest ports. High and low tide times are out by between 10 and roughly 20 minutes on the widget. Still gives my location as Scotland, UK.