Categories

  • Suunto mobile apps and platform feedback, questions, feature suggestions and issues

    5k Topics
    50k Posts
    2
    With the resources graphs when you swipe through the days the top line won’t stay the same. Depending on the day it might be 120 or only 80. It should be 100 all the time, so you have the same visual scale everytime and it is comparable…

  • Suunto Sports and Outdoor Watches

    6k Topics
    85k Posts
    sky-runnerS
    @OutdoorMan May it is because I have pace at the top and HR at the bottom. I’ll try to modify it and see if is different. It works correctly for one time after the watch is restarted, which I guess resets some internal state. But it consistently looks like this on the majority of runs. The “flatline” is always at a different HR - sometimes at a high HR like in the above example and sometimes at a low HR. Also, to make it clear the “flatline” represents the time before the beginning of a run. In the above example I have been running for 22 minutes but the graph shows about 40 last minutes.

  • Suunto dive computers

    264 Topics
    2k Posts
    R
    @trianst Thanks yeah that make sens to me. Especially with my 5 minute surface interval before the dive is ended the deviation gets even bigger. I would also love suunto to fix this in their app. Especially that the dive time and all other stats are the same.

  • Discussions about S+ Store

    214 Topics
    3k Posts
    sky-runnerS
    @brave_dave said in Suunto ZoneSense: For me personally, when I know that on average, even under perfect conditions, the ZS estimated threshold is off by 8-10 BPMs in either direction, it is not usable for me It is way worse for me. I’ve seen example of ZS suggesting anaerobic threshold that is even below my aerobic threshold - that is almost 30 BPM below what it should be. These are laughably inaccurate estimates. Let’s look at another example where I actually had a steady threshold effort for a long time that was a good indicator of my anaerobic threshold. ZoneSense still managed to detect my anaerobic threshold at 148 even though I ran for 20 minutes in the 160-165 range. By the way, that closely matches multiple of Garmin’s LTHR estimates that all detected my LTHR at 162-163. How ZoneSense managed to detect that at 148 is beyond my understanding. I can’t seriously trust that at all.

  • 94 Topics
    859 Posts
    M
    Has anyone replaced the belt only & then found the sensor to be at fault ? Since I posted above I’ve got rubbish results using the new belt pretty much every time I use it (regardless if I wear a vest or not)… On each of the runs below I wore a different T shirt so I don’t think its down to the fabric causing friction (I’ve read that that can also cause problems). [image: 1762283260864-647a5ed2-dcc6-4c7c-b65c-ab1c207c13d8-image.png] [image: 1762283294093-c640df00-d760-438c-afd2-3bd0a782f6ea-image.png] [image: 1762283359755-80251775-a7bd-4ab3-a025-826d862b9c60-image.png] [image: 1762283409424-5a2ddb5e-2962-4c63-a6ae-b53dd0f3a8d6-image.png] [image: 1762283442997-60fa9ee7-1159-439b-bf75-d011b3537c44-image.png]

  • Anything not related & off topic

    1k Topics
    28k Posts
    No new posts.

  • Sports Tracker apps feedback, questions, feature suggestions and issues

    24 Topics
    112 Posts
    Brad_OlwinB
    @gernophil This is working without issue for me. As Pavel stated check your Health permissions on the phone and watch for SportsTracker.

  • Forum scope and expectations.

    96 Topics
    434 Posts
    C
    While some people still spend time in vain comparing OHR accuracy on their watch and that of their friends, other people let their earbuds measure it for them. With HR belt accuracy.

  • Anything related to the recent announcement about Suunto’s new Digital services and Movescount Transition

    338 Topics
    4k Posts
    Marin LeroyM
    Hi i am trying to code an interval training in time, i am able to activate the light but not the beep, do you guys have an idea ? /*header*/ /*entrainement intervalle*/ counter=0; warmup_time=1500; speed_up_1=900; speed_up_2=600; speed_up_3=600; recovery_time=100; factor=300; wsu=0; /*end header*/ /*decompte en bip*/ if(SUUNTO_DURATION==1497){Suunto.alarmBeep();} if(SUUNTO_DURATION==1498){Suunto.alarmBeep();} if(SUUNTO_DURATION==1499){Suunto.alarmBeep();} if(SUUNTO_DURATION==warmup_time){ Suunto.alarmBeep(); Suunto.light(); wsu=warmup_time+speed_up_1; counter=counter+1; } /*decompte changement allure*/ if(SUUNTO_DURATION==wsu-3){Suunto.alarmBeep();} if(SUUNTO_DURATION==wsu-2){Suunto.alarmBeep();} if(SUUNTO_DURATION==wsu-1){Suunto.alarmBeep();} /*temps de repos*/ if((SUUNTO_DURATION==wsu) && (counter==1 || counter==3) ){ Suunto.alarmBeep(); Suunto.light(); wsu=wsu+recovery_time; counter=counter+1; } /*2eme accel*/ if((SUUNTO_DURATION==wsu) && (counter==2)){ Suunto.alarmBeep(); Suunto.light(); wsu=wsu+speed_up_2; counter=counter+1; } /*3eme accel*/ if((SUUNTO_DURATION==wsu) && (counter==4)){ Suunto.alarmBeep(); Suunto.light(); wsu=wsu+speed_up_3; counter=counter+1; } postfix="min/km"; RESULT=SUUNTO_PACE;

Suunto Terms | Privacy Policy