@pbanon Different people have different needs. If you ask me, none of what you listed is important to me, and if I wrote a list of top improvements that I want, it would be completely different, and it is likely that you won’t care about what I want. From your list I only care some about the button customization. But with only 3 buttons, there isn’t much that can be done because all of them are used for essential watch functions. But perhaps it could be nice in some situations to disable laps and instead use the bottom button to switch the lower field instead - what we currently do by tapping the screen on the map screen and the elevation profile. That would be equivalent to the “View” button on Ambit and allow to disable the touch completely. I’d use that for ultramarathon running.

@Calando Why is a chest strap necessary? Beat-by-beat data: ZoneSense uses a proprietary physiological algorithm (DDFA) that analyzes Heart Rate Variability (HRV) to determine stress and intensity levels. Optical limitations: Optical sensors (OHR) cannot reliably measure RR intervals (the exact time between heartbeats) while you are in motion. They are only accurate for this metric when you are at complete rest, such as during sleep. When pairing a chest strap, your watch will automatically disable the optical wrist monitor to ensure the data source provides the necessary accuracy for functionality.

@mickywickyftw thanks for the update, I’ll try this week hopefully (on the same road, to compare). One suggestion could be to wait for a few more seconds when the slope reduces before using standard formula (I totally ignore if there are mathematics models behind this, just intuition and probably hard to calibrate). I mean we are still fast for a while when the grade drops from -4% to -2% for example.

@sky-runner For me, ZoneSense matches my breathing quite well. I’ve been using it almost every day for over one years.

@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

@Stefan-T. I now can confirm this behavior. Today, after 13 days with some training and also HR broadcasting, I was down to 2% so I put it in the charging craddle. Some hour(s) ago I checked and the watch was on 100% and I put it on again. I could actually monitor, hot the percentage dropped and no I’m on 97%, which is about 1%/hour. That would give me some 4 days!! I I’ll did the soft reset and was back on 99%. So it’s definitely a software issue, that after charging some “counter” is running nuts So I hope this is fixed in the next FW update…

@Marcelo-Mönch ditto!

@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

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

@duffman19 as someone who works with motors all the time, this is kinda difficult to stay away from magnets.

I have had the Suunto Run since June 2025. It had never happened to me but last week It restarted in the middle of a race, very disconcerting, I hope it won’t happen again…

@SergioB It’s working perfectly again. I guess iOS 27 had a bug. After the latest iOS update, everything is working 100% now.

@DonTomGot Excellent, I think I understand why I’d want to use this now

@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)

@domucki 1- no need to start an actitivy, but you have to be on the start screen, I’m doing dual recording with my watch and HH just because I want those Suunto badges

@Thomxs_ 1: The main widgets menu does not loop, because you enter it through scroll up swipe, or crown rotate. Down enters the Sport modes list. So how would you make it loop without changing the control logic? Other menus, e.g. Settings, are linear as well, but I don’t see that as a problem when you have a digital crown and a touch screen available to quickly navigate the menu structure. One can also argue that looping text menus can be perceived more complex and confusing due to infinite length. 3: Under specific alarm, use Repeat > Customize to select days, then scroll back up and press Select 5: Available in the watch under Progress widget

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).

@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)

@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.

@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?