2.13 (2026-06-27) is live with a small bugfix: Each trend line now scales to its own movement, so a chart looks the same whether you view it in the combined drift view or in its own dedicated view. Fixed the effort direction for speed-based sports (such as hiking): moving faster than your average now correctly reads AHEAD instead of FADE (and correct green/red colors).

New version published: V1.1: Performance improvements through decreased update frequency Modified gauge-colors for improved contrast Gauge extended for improved granularity [image: 1782587403851-2026-06-27_21-05-58.png]

@Kraisun-Tunta said: To verify whether it was a real battery drain or just a reporting issue, I performed a soft reset. After the reboot, the battery level jumped back to 99%. I’ve reported this quite some time ago, as I’m experiencing exactly the same with my Vertical 2. Never got a feedback, so I simply soft reset the watch after every full charge and that’s just it Battery life in general is pretty good though, so nothing to complain in that regard

@sky-runner Funny but that is exactly my own experience with Zonesense for 95% of the times, both aerobic and anaerobic thresholds quite low compared to my 5 traditional zones set after the Anaerobic threshold test (and even my own perception, such as easy breathing, conversational pace, breathing through the nose, etc).

I noticed that there is something wrong in descents. The power is sometimes overestimated. In the screenshot below, I reached 450W ; speed is high, but I was not forcing at all. Note that I have no cadence sensor. I never observed such errors in ascents. [image: 1782578931095-img_4639.png]

@Nelson-Diogo I have been using the watch since last October. And that happened for the first time. I will follow what happens next. But in the time since I’ve had Suunto, I’ve realized that anything can be expected.

@sindavide said: @elbee I largely agree with you. The point is that we pay for those functions, so Ikd expect them to work in an acceptable manner I would rather not pay for functions that perhaps may sound useful but in real life aren’t (either because they don’t work very well, or aren’t how things work or are just marketing bs). But I realize it’s easier to make a watch for people who just want to collect as much data as they can or have fomo, in stead of a watch that is 100% tailored to 1 individual. As long as I can turn things off, I’m make. Manufacturers make the most stupid choices for this. On my previous garmin I could turn off morning report, on my Suunto I cannot. But if I disable sleep tracking, morning report is also disabled. (End result is great, the way to do is is stupid). Garmin added voices alerts to tbt alerts, which couldn’t be turned off. It drove me (and quite a few others on the garmin forum) nuts. Sold my garmin and bought a Suunto. (And my wife noticed I complain less about my watch)

@elbee Could the watch firmware. I never had any issues before the last update. By the way, i got a new suunto smart sensor, and it occasionally dosconnecta - the watch does not show hr - albeit for not long

@Marcelo-Mönch Still, with the same settings, battery lasts some 30/50% less than when i bought the watch. It is not a matter of settings, it’s a mattero of software engineering. Suunto musto solve it! Anyway thanks for the tip about disabling discovery, cheers

@Antoine nope, not really… probably i could explain better in copy 45min tail means, that subscriber who look at you via web will see you current position and 45min trail before. to be honest it was default behaviour whole life of the app. basic idea on start was just economy on ram, when it operates on lower end machine. now legacy behaviour kept the same on free plan. said that, there’s no limit for activity tracking, and whole activity will be saved 3-4 and more hours… it related only for live tail in web view

@dimitrios-kanellopoulos it seems to affect more people. Can you tell if this is indeed a Suunto App bug?

@rémiP Thanks. This seems problematic. Is there any reason for this behavior @suuntopartnerteam?

@raphaelh Will do, and thanks! BR Carl

@Nikolai-Simonov yes I built a custom interval workout because I wanted to use navigation at the same time. If I use the built in intervals I cannot use navigation (this is known Suunto functionality)

@outdoorman, et al. – What I’ve noticed is that… Race 2 unpaired from iPhone & powered down Re-paired, synced, etc. with no sticky notifications Went for run this morning (first activity since re-pairing) and sticky notifications are back, even though no phone with me during run; activity saved post-run before getting in range of phone for sync, notifications, etc. Others’ experiences the same or similar? Debating whether or not to unpair/re-pair with phone as it seems like quite the hassle just to avoid the stickiness. Regardless, I hope Suunto has seen this thread or been otherwise made aware of the issue and has a fix with next update.

@stavrogin - Third party own the data that is displayed on their imported workouts on Suunto, for TP there’s this ER idea to add the step counter, feel free to vote for it. https://peaksware.uservoice.com/forums/106657-trainingpeaks-customer-feedback/suggestions/46005451-interval-counter-on-suunto-s-structured-workouts Adding to my previous post, after disabling the auto lap, you can setup your own screens to see avg numbers for whatever metric you want and it’ll be for that step of the workout. But definitely you cannot see what step you’re on with TP workouts, until TP implements above idea. On your question about undoing a manual lap, it’s not possible, and when doing a manual lap while executing a workout from TP or any other place, it’ll skip the current step. This is by design and cannot be altered. With that said, Training Peaks has the best screen for executing structured works, the only missing piece is the step count in my opinion

@Eric-0 Interesting use case that I had not contemplated in design… ahead/behind in current setup is built on a “Count_Threedigits”-format - which would mean that it allows three digits (also negative). So it will count to -999/999. In simulator it will then display 000 until values goes back in range - assuming the same will be displayed on watch. Reason being that a “normal” display of time would steal to much space and force the use of a smaller font. I also do believe that I had to go with the “Count_Threedigits”-format as all time based formats (duration) seemed not willing to display negative numbers (time). As for your second bullet - I am trying to keep the displayed data to a minimum, prioritizing large fonts in clear contrasts; hence a bit reluctant to add more data fields. But out of curiosity - would you base the expected finish time on the extrapolation of the pace so far OR the planned overall pace?