Suunto ZoneSense
-
@VoiGAS have you done “calibration” runs?
I noticed a huge improvement with zonesense when i did 3 super easy 30-45 min runs under aerobic threshold.After doing this my app and watch shows the same time spent in green yellow and red. Before those runs the data between watch and app was way off.
I did those runs after watching suuntos videos about zonesense. He explained to do a few low intensity runs to calibrate the watch.
Worked for me🥳
-
@halajos data in Runalyze looks pretty good - just the first 10 minutes are a mess…
-
@Samuel-Pirttikangas interesting, I will try with the next recovery runs
-
@VoiGAS if the R-R data in first 10 minutes is bad, then it messes up ZoneSense calibration. Does the R-R data continue to be bad if you continue to run with the same pace as during warmup? Does the R-R plot become better if you increase effort? Might that indicate some kind of arythmia? Do you wet the HR strap before putting on? Do you use the Suunto smart sensor? You might try a Polar H10, is known for reliable measurements.
-
@halajos After 10 minutes the data gets better all the time - like magic. Suunto Smart belt, I always wetten it. But you could be right, I thought the bad data is the reason Suunto skips the first 10 minutes…
-
@VoiGAS no, ZoneSense uses the first 10 minutes (should be low effort) to calibrate your baseline, that’s why it’s excluded.
-
My graph looks like this:
If the anomalies are more than 1 %, something is really wrong in my opinion (low battery, old belt…).
-
@Mitch9 Oh, that looks different! My battery is at about 20% - is this already to low?
Belt is brandnew - bought it extra for Zonesense… -
I just realized that the ZoneSense app was updated on March 20th. Just a heads-up.
-
@Ghost New version for everyone and a new battery for me
. Lets give it another try -
Tried today with a short workup recorded with the Android App - but the HRV data transfer and Zonesense both seem not to work
-
@VoiGAS said in Suunto ZoneSense:
Tried today with a short workup recorded with the Android App - but the HRV data transfer and Zonesense both seem not to work
Consider SA recording as an external app (not a Suunto watch) and activity recording from it is “like” imported into the cloud as like a fit file --> no HRV, no zone sense, no custom HZ zones.
-
@Mff73 Yeah, I had to learn that the hard way. Currently on a Business Trip without access to my watch. Should have taken it with me…
And also eliminates my plans to use the suunto app as a bike computer -
After several months of trying, I still have yet to get ZoneSense to detect my Anaerobic Threshold. Not once. It routinely detects Aerobic Threshold, and within 1 or 2 BPM of where I have it set (132BPM) . But no matter how hard I push or for how long, it will not detect Anaerobic. I have it set at 148, I can do 10 minutes in the mid 160’s and still not get it to detect. I’m a pretty fit 60 year old, but far from a trained athlete. Max HR is 178-180.
I have naturally low HRV with a normal range between 20-24 as detected on the Race S. My assumption is that my naturally low HRV doesn’t give ZoneSense enough variation to work with. Has anyone else experience this or can someone confirm if this assumption is correct?
Thanks.
-
@olson917 What is your setup? In my case, the anaerobic threshold is always detected, but only when I’m running in the mountains and really pushing hard. Otherwise, it’s never calculated because my heart rate doesn’t go high enough. I’m using a Suunto Vertical with a Suunto Smart Sensor belt.
-
@Ghost Race S Titanium with a Polar H9. Oh, and I’m not running, most of my high intensity stuff is on the bicycle smart trainer. the 148 BPM Anaerobic threshold is determined by my Garmin. I believe it to be fairly accurate also, as that’s about the point when I start to fatigue quickly. I routinely go into the mid 160’s for several minutes, no go. I did an FTP test a month ago, and steadily climbed to 178 before failure, and it still did not detect. But again, my HRV is really low, it may just be a limitation of the algorithm.
-
Oh, one other thing. I live and train at elevation 5,300 ft or about 1,610m. My understanding is that can lower HRV on its own. I certainly get higher numbers when I’m down at sea level.
-
@olson917 Personally, my lactate threshold is at 186 bpm, and I’ve never managed to get it detected while cycling either. From what you described, someone with more experience (@Brad_Olwin) might offer better insight, but my guess is that your actual lactate threshold is higher than you think, which could explain why ZoneSense isn’t detecting it. For me, it only works when I push really hard during vertical runs, with my heart rate climbing to 190 bpm or more.
-
@olson917 said in Suunto ZoneSense:
Oh, one other thing. I live and train at elevation 5,300 ft or about 1,610m. My understanding is that can lower HRV on its own. I certainly get higher numbers when I’m down at sea level.
Where are you? I am near Boulder, CO and I am 68. I live at about the same elevation, max HR is ~180, my LT is ~164 and only had ZS identify it a couple of times. Short hill intervals at max effort where I hit HR of 177 does not give me an LT estimate. These are 2 min hill intervals. You will need sustained anaerobic effort to get ZS to provide a good estimate of your LT. To me, it seems your LT is likely to low but I don’t know your fitness. For reference, my AT is ~140 and LT ~ 164. The beauty of ZS is you don’t need to know those, just exercise in the appropriate zone for the effort.
-
@Brad_Olwin I’m in Denver. My fitness is not what yours is, I do mostly lower intensity stuff, with 1 HIIT workout a week and one longer intense workout a week. Garmin says my AT is 132 and LT is 148. ZoneSense tracks the 132 AT perfectly, often to within 1 BPM. Last Sunday I did a 10 minute climb and varied from 156 to 160 BPM, no go. I about barfed! A few weeks ago I did a FTP ramp test, 15 minutes of steadily increasing HR until I blew at 178. Still no go. But again, my normal HRV range is really low, 20-24. That’s not much for the algorithm to work with.