@SRS2000 you can only have one max HR. It is impossible to have more than one. Even more it doesn’t matter as it is the top of your zone 5 anyways… Suunto Run is a bit different than the rest. With the others you have to set the zones yourself - more control, but a bit more hassle at first.

@runyx17 said in Several navigation issues (feedback): Just a note: If I create a route in the Suunto app or the Suunto Route Planner, the turns are announced correctly, about 20 meters before the turn. If I create a route in Mapy .com, the turns are announced with a delay, usually exactly at the point of the turn. I dont have Komoot. Guys. This is important. So Mapy seems to have the same issue as Komoot. And, one VERY interesting thing: If I upload my track in Suunto Route Planner, the end is also ok. Look: [image: 1777276764727-11995.jpg] But in Suunto Route Planner, can I upload a GPX (provided by a race organization) and have turn-by-turn directions? Because it seems we can have a fix here for several issues related to TBT and even Climb Guidance. And it’s also very likely that autoreverse can be (just a bit) more reactive once the offset is solved.

Yesterday I restarted the watch before run activity and there was no reboot.

Hello, On the 24th, I conducted some tests, first on a practically straight route, and then on a route in the same area with hills and curves. My hypothesis that the Race 2 is incorrectly processing the recorded points was confirmed. The straight route is marked every 500 meters; it was 4.04 km according to the Race 2 and 4.05 km according to the track, measuring almost exactly during the activity. During the activity with curves, the problem returned, subtracting 80 meters from the total: 4.00 km according to the Race 2 and 4.08 km according to the track. I’ve attached some screenshots that I will send to Suunto support: [image: 1777273901039-captura-de-pantalla-2026-04-27-085958.jpg] [image: 1777274020950-captura-de-pantalla-2026-04-27-090132.jpg] I encourage you to conduct these tests and also send them to Suunto (support@suunto.com). It’s the only way they’ll take the issue seriously. If this problem is widely known, I doubt Suunto will sell another Race 2 at its current price. Regards.

@VoiGAS said in Is there still demand for a modern MIP endurance watch?: But I think AMOLED could completely replace MIP with better adaptive reactions to movement and sunlight. Max brightness is good already on RaceS Amoled will completely replace Mip. Mainly for commercial reasons. They sell way better. There is a small (but loud) group who prefer mips because of readability in direct sunlight, battery usage and/or real always on display without any delays in turning on or needing a wrist gesture. (I’m in this group) Some people find amoled better readable. Most have either had a sapphire mip display or have a gazillion datafields on their watch. For their use they have a valid point. But the biggest group just find mip displays looking old fashioned and prefer a shiny gadget. So they buy an amoled watch

@sartoric ok thanks for the info. I guess it will never be fixed then.

I also have this ‘Raise to Wake’ bug on my V1, however at this stage it does seem to be occasional and quite often seems to turn itself off during the activity which is a good thing. Hopefully it gets fixed in an upcoming update

The issue with the incorrect zoomed in individual climb guidance. In a short period of time I have already experienced it twice. Here you can see that I have transitioned from a descent to a climb as visible at two different zoom levels: [image: 1777224787857-f1b77f1a-e047-41cc-b259-92e28034ec4b-1_all_9057.jpg] [image: 1777224818028-f1b77f1a-e047-41cc-b259-92e28034ec4b-1_all_9056.jpg] But if I zoom all the way in, it shows me at a descent, and that seems to be the previous descent that I’ve just finished: [image: 1777224970549-f1b77f1a-e047-41cc-b259-92e28034ec4b-1_all_9058.jpg] I hope it doesn’t require another year for this to get fixed! Also, as mentioned above, fix the layout so that it actually shows how much climb or descent is remaining and increase the font size for the remaining distance because it is quite difficult to see.

@Egika thanks.

@2b2bff no, 11 different files that I imported from alltrails.

[image: 1777194333458-img_2053.jpeg] [image: 1777194333470-img_2054.jpeg] Some more helpful info I thought about, I read someone had a similar issue two times at the same distance each time. For me time and distance are different in each case, so I am not sure if it’s related to his issue or not. This is the issue I mentioned https://forum.suunto.com/topic/15116/watch-reboots-mid-activity-at-ca-9km-when-using-gpx-navigation/2 This also seems to be related. https://forum.suunto.com/topic/14527/crashes-in-the-middle-of-an-activity?_=1777194428329

A similar issue has been reported on Reddit: https://www.reddit.com/r/Suunto/s/ON5V0wTTNr with more that one user saying they had this issue.

@isazi said in [Race S - 2.50.28] Nap detected during recorded sleep: so report it again if it happens with the new firmware And there I am: Nap accounted to yesterday: [image: 1777121428413-059d473a-6019-4348-bf94-fa20ad027bb8-image.png] And tonights sleep: [image: 1777121473999-6f04e699-6aba-4c5e-bbc2-09d3a18430a6-image.png] Fair enough, I did wakeup because of some noise around 23:55 - as seen by the rising HR. But the sleep tracking didn’t even registered it as wakeup… I think, somebody should look at that code on a higher level as there seems to be something broken in the overall logic…

Thank you very much, I guess I’ll have to solve it that way as well. It would be great if Suunto could pull dive sites from PADI, SSI, or DAN so that you could get suggestions about where the dive took place.

Your watchface looks nice. It is simple and easy to read. Can you modify it to have 3 bottom data fields, same as top row? Could you please share your code?

I am on iOS, I let the issue rest, and it appears like the watch was able to get the weather data. However the following evening the same issue happened again. And again in the morning it had synced. I guess I can update what happens this evening and the following morning as well.

@ashic Hi I am having exactly the same issue! Even Suunto chat could not help me. Waiting for an answer from their tech department. I also did a reset and lost my dive profiles…will try the D5 option…

Just got my new Nautic and this issue was the first problem. I wrote to the Suunto Chat and got below instructions. Haven’t had time to check yet if they are functioning or not. But really strange that device doesn’t match the manual. As there really isn’t a pair a new device. From Suunto Chat: Pairing a heart rate sensor with Suunto Nautic (manual) Go to control panel Press the middle button to open the menu Log in to control panel Open connection Select connection Select Pair new device Select Pair new device Select heart rate belt The watch will show the available sensor types Select heart rate belt Activate sensor Use belt or apply electrodes Hold it close to the watch Select sensor when it appears Select it from the list Confirm pairing Wait for confirmation: Pairing successfulImportant note about manual logic Sensor must be active and transmitting Pairing must be done before starting a dive Only one hour of belt can be actively paired at a time Key point (important for your case) If “Pair new device” is not visible, then according to manual expectation: The watch is not in the correct Connectivity level/menu state Or firmware version/user interface does not match the documented appearance

@Egika thank you too.