@jjpaz I am really impressed with the work you have done. I had posted in Reddit thread about the conservative distance race 2 is giving, ie I am also getting about 80-130m distance shorter for a 10km run compared to coros pace pro and apex 4. I used to have both race S and Race and both actually have very similar distances logged and are longer by about 80-130m compared to Race 2 (for a 10km run). While I am not disputing that Race 2 could be more accurate in distance, I do think that there could be a smoothing effect in logging of distance . It’s not a big deal but it does bug me quite abit. Sure hope a software update will help resolve this .

I am having the same issue on my Race S. Has anybody found a way to fix this?

@gipfelkind Totally agree, ZoneSense seems to be buggy. I’m going to run without it for a while and see. Thanks for confirming!

After the download the update need to be confirmed/activated at the device settings. [image: 1769210370727-whatsapp-image-2026-01-23-at-23.16.47.jpeg]

@sky-runner said in In-activity time in HR zones data screen seems broken - times in zones are incorrect: Doesn’t Suunto team have an intern of someone like that to get on these bugs? They could start with fixing translations - an even lower hanging fruit…

@Brad_Olwin said in Subject: Feedback on Zone Sense accuracy: Short intervals and Zone 2 threshold shifts: ZS is primarily intended for live values and its ability to detect zones will depend on how recovered you are In that case ZS shouldn’t be used to detect zones but that is exactly what Suunto does. It remembers the last detected thresholds and tells me about them later. For example, a few seconds ago I looked at my watch and it showed me that my Lactate Threshold is 145, which is nonsense because that is just one or two beats above of where my AT is based on multiple years of observation. I can still mostly breathe through the nose at that effort.

Hello. Is anyone experiencing an issue on their Vertical 2 with the advanced heart rate zones for different sports? When they modify the maximum heart rate for cycling (since it’s lower in this sport), it ends up affecting the maximum heart rate for other sports (default, running, etc.), even without selecting the option to update maximum heart rate after the suggestion message appears. I’ve looked in the manual, but it explains what it’s supposed to do, but it doesn’t work. I don’t know if this has been reported… I’m using version SFTW 2.50.26; I didn’t notice this issue in any previous versions after modifying the thresholds. EDIT: For now… I’m not modifying the maximum heart rate while cycling, so it doesn’t alter the other zone programs.

@dimachad Thanks for your reply! Unfortunately that does not work in my case. I’ve reached out to Suunto over IG…

@jjpaz I will try this next time. During activity turning it off/on didn’t change anything.

Some very loud statements here. Unless you were counting all your steps in your head throughout the day. Which I highly doubt.

@Egika. Yes i have seen some queries. But nothing in 2026 so I push it again :).

@MatthiasKlug said in getting too much ascent / descent on flat routes: @Dimitrios-Kanellopoulos … (edit: my first thought was that this behaviour is somehow temperature related (the bigger the temperature drop the higher the ascent) i just wanted to mention this, we will see if the outer temps get warmer and closer to the changing room, so there is less temperature drop) From my experience with the altimeter, it actually is not 100% temperature compensated. I found this when climbing indoor without GPS. I did 3 consecutive climbs in the second half of the recording. I might have gotten warm and the altitude is shifting downwards: [image: 1769164260259-db9acb8d-d9fb-4dbb-bcb9-684c6825ed4f-image.png]

So I added 10+ dives, and ~20 other activities (yoga, hiking, skiing). For diving with 5mm wetsuit: thought of an extra soft cord to help with watch strap. After a while, no problem straping watch onto suit with last hole. Wearing watch on the right hand and POD on the right side solved disconnect issues. Not a single disconnect during dives. No decompression time with default gradient was on par with other diving computers in a group. Default non removable alerts are a bit annoying, but can be excussed for safety. For non diving activities: GPS works well, even under a coat. Problems: Diving map (3D) is not recorded correctly if you do not wait for GPS signal before the dive. Scrolling between maps in an updated android app - crashes it or makes app unresponsive. Can not end a dive manually. Tried to extend auto dive end (dove in cenotes, which means some surface time in a cavern), with default 5min, got my dive split into 2 parts. Set it to 10mins and did not find a way to stop the dive manually, which means POD alerts already dissasembling the gear outside the dive time (other computers also split the dive and probably everybody needs to live with this). Battery is not a full week lasting (not gonna try to dive with less than 30%) if using for diving and smart phone features, so would not go on a journey without a charger (not an issue, but a thing to know). ps. Brightness was almost always on lowest setting, except for AOD autobrightness.

@egika unfortunately, yes. however, as a workaround, the latest version (still in appstore review) adds a restore session feature. so briefly you will be able to turn off live.τ for a minute, sync with the suunto app (to update a route or something), and then turn live.τ back on, the app will let you continue your session without interruption. it’s kinda hacky and not ux friendly solution, but it could works for non frequent things like an route update.

@jason.scrivens Hi, it was the watch firmware update, therefore FW 2.50.26 on Suunto Race watch. I think that SA (android or apple) has nothing to do with this functionality. So, after the watch firmware update, it really works for me. I am in the pool at least two times per week and so far so good. There is another topic, which is maybe more for feature suggestion, but I would welcome if the swim rest time is not a cummulative time from all rest times between the laps/intervals, but the actual rest time after actual interval. so it should start from zero after each interval. But as I said, that is different topic.

@mrkus Если у тебя iOS , то попробуй отключи часы от самого приложения , переустанови его, потом в настройках приложения выставь время сна и снова подключи часы и синхронизируй . Мне помогло