• Zonesense Activity Tracker

    1
    1
    -1 Votes
    1 Posts
    58 Views
    No one has replied
  • SuuntoPlus App: Stifa - a few questions

    3
    1 Votes
    3 Posts
    697 Views
    W
    @MarkG @francesco-pagano Had a few really good runs with the Stifa app here’s my 10 mile effort up into Lyme Park which is a hilly National trust park in the UK : [image: image.jpeg] The “warm-up” to get the park is continuously up and felt like it held me at a comfortable-hard pace, then hit the lap button to reset the calculations once I was in the park itself where there is a steeper road going into the park and all the the way up to a high point where I turned around hitting the lap button again. I have a 10-mile race coming up soon and this feels like the ideal prep. For training I’m using 175 bpm as my max heart rate which results in optimal zone usage but thinking about raising to 180 so the Stifa app can auto-scale the workout so it’s something near race pace - could be a winning plan The “Stifa Snitt” score shown here: [image: image.jpeg] …which is the total elevation gain ( in m ) / total distance ( in km ) : [image: image.jpeg] [image: image.jpeg] How do other people use the app - especially when to hit the lap button? Martin
  • 8 Votes
    11 Posts
    784 Views
    B
    @tvial said: Let me know how HR reads on your SV1. Not really good. The number is actually very small. It does not met the “corner of the eye” requirement. Same for the pace target + pace window. I would say that most of the time, the information is not relevant. I mean, I know it (I configured it in the app), and the half-bottom line repeats part of it. Exceptions are: I just changed it with long press and/or negative split (the value changes over time). The blue/green distinction is also not easy. Having a blue marker on the left of the main pace when too slow, and a red marker on the right when too fast would help (so both color and location of marker are meaningful). Could be a simple circle, or the delta (“-5s” or “+10s” for example, but I am not sure there is enough room there). Note that my run was right before the night, with decreasing amount of light. Probably not ideal when looking for details. In a race perspective, I am missing the number of seconds ahead/behind the objective as well. But that’s maybe too many requirements for a single app.
  • Live location S+ app

    357
    59 Votes
    357 Posts
    150k Views
    C
    @Nikolai-Simonov Hi Nikolai, I’m developing GEO LINK, a SuuntoPlus radar app for the Race S. Our radar already works on the physical watch, but we want to receive friends’ live GPS coordinates from an iPhone. I saw that Live.τ supports bidirectional communication between iOS and SuuntoPlus, including messages sent to the watch. Could you share some technical guidance on how your SuuntoPlus app exposes or accesses BLE GATT services during an activity? Specifically, is this possible with a normal .fea Sports App, without requiring a .dev device connection app and the watch’s pre-activity sensor search? We’re not asking for your proprietary source code, just guidance on the supported API or connection architecture. Thank you!
  • Gustin is now available in the Suunto app

    38
    1
    37 Votes
    38 Posts
    5k Views
    Marcelo MönchM
    @Łukasz-Szmigiel muito obrigado pelo retorno.
  • Constantin: monitor effort drift against your session average

    65
    3
    25 Votes
    65 Posts
    8k Views
    Łukasz SzmigielŁ
    Constantin 3.13 is out (Carduelis release) This update is about memory on the watch when you run route navigation or a second SuuntoPlus app at the same time. Constantin uses less memory. Its screen needs about a fifth less memory when it opens, for example when you switch to it from navigation. That’s the moment the watch could close it before. Views, chart and buttons work as before. If the watch still closes Constantin mid-workout, please tell me your watch model, which apps were running, and whether navigation was on.
  • Race Pacing app - Using Grade adjusted Pace according to GPX

    2
    3 Votes
    2 Posts
    916 Views
    M
    A useful starting point is the average pace needed for the distance and goal time, with that pace then adjusted for the hills on the course. I check the basic numbers here: https://milepacecalculator.com
  • oCycler - FTMS bike link: power & cadence

    29
    1
    8 Votes
    29 Posts
    3k Views
    O
    @Wilson75 I usually have the opposite problem with my trainer, if I use the FTMS - be it oCycler, myWhoosh, TrainingPeaks virtual or Kinomap the connection to the device remains active on the bike, therefore (be it a watch, tablet or macbook) I need to soft reset my bike to connect to something else. That’s the nuance of the protocol I got used to.
  • oSpotter - Gym workout tracker

    27
    4
    5 Votes
    27 Posts
    3k Views
    O
    @2b2bff Yeah, It was sad to see that too, who’s gonna make the quarterly videos for their youtube channel now? I love those lecture series. But seems like he managed to secure the C-level role in some AI startup, so I’m happy for him and wish all the best
  • Cycling Power Estimator

    52
    11 Votes
    52 Posts
    7k Views
    mickywickyftwM
    @SergioB …aaand that is why it crashed I knew about the limit but couldn’t find a reference to it anymore yestwrday, so tried anyway. TBH TSS is less useful than the other metrics. Maybe I’ll give the user a choice of metrics to: Display at the bottom of the power estimator screen (currently it’s duration) to write in the summary output
  • S+ Race pacer

    61
    1
    6 Votes
    61 Posts
    21k Views
    B
    @false I know, two years later I tested the application today and it worked fine. I fully agree with @false comments. In addition: I lack a “target pace” field, to know what is expected (especially when using a negative split, I cannot retain X values). An easy-to-catch-when-running marker could help as well (green when within a 10s/km range for example, red otherwise - could be configurable). maybe finer grain on % of splits Is this application still under development, or is this a message in a bottle thrown to the sea?
  • STRENGTH TRACKER

    6
    1
    25 Votes
    6 Posts
    2k Views
    J
    @mich-heller Agreed on algo. It got me more reps on initial release but after the latest update, I too have been getting no reps at all on some movements.
  • Aerobic Decoupling

    8
    0 Votes
    8 Posts
    886 Views
    S
    @isazi yep I meant that, support@
  • Sleep HRV vs workout HRV

    4
    0 Votes
    4 Posts
    317 Views
    E
    Hrv on a consumer device just isn’t that accurate. When a person lay still (sleeping), there might be reasonable results, but the slightest move influences the measurement. https://www.researchgate.net/publication/400515012_Right_Place_Right_Time_Validation_of_a_Consumer-Grade_Wearable_for_Heart_Rate_and_Heart_Rate_Variability_Across_Sleep-Wake_Cycles_Physical_Activity_and_Postures_in_an_Ambulatory_Study_Preprint And the gadgetblogger version: https://the5krunner.com/2026/02/18/garmin-hrv-accuracy/ (And no, suunto is not magical better in measuring hrv)
  • oTicker - Checklist app

    1
    1
    2 Votes
    1 Posts
    216 Views
    No one has replied
  • livetracking

    7
    0 Votes
    7 Posts
    732 Views
    Tomas5T
    @Majula contact suunto directly using chat in app. They will tell you if this is known bug or if you need replacement for watch etc.
  • 3 Votes
    3 Posts
    380 Views
    R
    Thank you. Your description matches everything I have measured from inside a SuuntoPlus feature, and it explains the one result I could not account for. Here is what I can add, measured rather than guessed, in case it is useful to you or to anyone else reading. The trigger really is the direct distance A feature can read /Navigation/Poi/Active/Distance. While a route is being navigated, that is the direct distance to the next named waypoint, and it is accurate to about a meter: I logged it once a second for a whole walk and checked all 495 samples against the route’s GPX, and the best match is the expected waypoint every time, to within 1m. /Navigation/Poi/Active/Name gives that waypoint’s name and switches at the passage. So the concept you describe from the outside is visible from the inside too, and it is the only usable thing a feature is given about a waypoint. There is no resource for a waypoint’s coordinates, and none for a bearing to it. Off route it all stops, exactly as you say On one walk I left the route deliberately. For 178 seconds Poi/Active/Distance, /Name, /Coordinates, /Bearing and Routes/NavigatedRoute/DistanceToDestination all went silent together. ClosestPoint and Position kept answering. Coming back on route brought everything back. This is the part I find hardest to accept as a design. Being off track is the moment you most need the watch to tell you where the next waypoint is, because that is the information you need to get back on the route at all. On the line, where everything still works, you can already see where you are going. The data is withheld exactly where it becomes necessary, and for a pilot or a skipper pushed off track by wind or current that is not a rare corner case, it is a normal part of the trip. Your point about reversing explains a result I had left open I walked a short loop whose start and end sit 26m apart. The very first sample, before a step was taken, read Position 1.000 and 50 m to the destination, and the watch never ran waypoint navigation at all for that walk. Position then went negative for the rest of it. I could not explain it and left it unexplained. Your description of the navigation reversing on an out and back, and then listing the waypoints back to the start, fits it exactly. What I did about the missing bearing Since the distance to the next waypoint is exposed and its position is not, the position can be recovered from the distance alone. Each measurement says the waypoint lies on a circle of known radius around a known position, and circles taken from a moving observer meet at one point. Solving that over a leg puts the waypoint within a few meters of where the GPX says it is, and from then on the bearing is computed locally, so it survives the watch going quiet. It works, but only for the waypoint the watch is currently offering. Once off route there is no new waypoint to learn, so it carries the current leg and no further. The question I am left with Is there any resource, documented or not, that gives a feature the coordinates of a route’s waypoints? I have tried about twenty spellings across Routes/NavigatedRoute and found none, and after your answer I understand why: if the list is recomputed rather than stored, there is nothing to read. If that is so, then the only stored thing with coordinates that a feature can reach is the POI library, through /Navigation/Poi/Count and /Navigation/Poi/<index>/Coordinates, which do answer. Is that a supported way to read them, and is it expected to keep working?
  • 1 year Live.τ 🎉

    13
    28 Votes
    13 Posts
    2k Views
    UjcoCZU
    @herlas Well, that would be great. Or at least it could better support the developers’ efforts, since it already provides them with the Suunto Plus platform.
  • The best race pacing app for a 10k?

    10
    0 Votes
    10 Posts
    760 Views
    G
    @Steven-Hambleton I ran a half marathon recently with my Suunto Run and used Marathon Mode as well as Ghost Runner. Worked great for me and I got a new PB Very happy to have had those tools.
  • Suunto ZoneSense

    1k
    2 Votes
    1k Posts
    672k Views
    ravenR
    @Francesco-Pagano said: @raven I appreciate how confidently you can say what I didn’t do. If you look at my graph you will see 40 minutes of steady pace / effort. I am not even skeptical about the AeT value reported - that would still have little value to ny training - but rather about the fact that ZS shows I’m still doing aerobic training when my effort increases (also shown in the graph). Right, that steady pace at the start looks to be around 5:50/km and you reported you go above your aerobic threshold these days at 6:00/km Quoting you: “ My aerobic runs used to be around 5:30 min/km below 145 bpm, now I’m well above that heart rate at 6:00 min/km. Today after 40 minutes of another miserably slow run with elevated HR” Given your own reporting, that chart and info didn’t look like an easy warm up effort to me but instead an effort over threshold. ZoneSense requires a lighter effort in the first ten minutes. However, I admit may have read the chart wrong though or misunderstood you. If aerobic threshold (AeT) = 162 bpm, and Anaerobic threshold (AnT) typically sits 10–20 bpm higher than AeT, then an estimate of that would be: 172–182 bpm. Then max HR is higher than that. If all if that sounds right, then perhaps ZoneSense is correct. However, note an effort below AeT typically should pass a “talk test,” being able to speak whole sentences comfortably, without gasping for breath.

Suunto Terms | Privacy Policy