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
-
@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.
-
@olson917 The ramp test should have worked but the hill climb is probably too short. Depends on warm up too. Suunto has S+ apps to test AT and two that test LT. One is a Cooper test and one an LT ramp test. You could try one of those when rested. All of my exercise for serious HR is running so that may differ too. Your LT still seems low. If you can do a 10 min ramp at the HR you state then 148 is wrong. I would look at the ramp test and hill climb but maybe set your LT nearer to 155. Maybe we’ll bump into each other sometime.
Again for training with ZS you don’t need to know your HR zones, but you do need them to set up the watch. You can train in green for recovery/low aerobic; green/yellow for endurance; solid yellow for Tempo; ZS is not good for all out intervals, it takes about 2 min or so for ZS to react appropriately and ZS needs a solid easy aerobic warm up of 10 min. -
Now get Zonesense to work like expected with new belt, new battery, 10 minute rampup. It now responds to my efforts.
Still some topics:
It responds, but slower than Power, HR and Personal feeling
If I (and I see it at other users too) increase effort it goes down before rising up
It needs perfect conditions like descibed above
Its hard to reach red. Maybe because of the slow response
I don’t have the problems with HR and Power, so I will stick to them. I am sure someone will bring a scientific proove that Zonesense is much better, but for me its just not
Race S
Ambit3 Vertical -
@VoiGAS Nothing wrong with sticking with an approach that works for you
I’d suggest 2 ways ZoneSense could still benefit you even if you don’t use it as a primary metric.-
It can help you set your HR zones more accurately. If you check the ZoneSense suggestion a few times to get a general idea of when it suggests your zone2->3 and zone 4->5 transitions should be you can adjust to match and you will have your LT1 and LT2 points aligned with the HR you are used to training with (accepting that recovery, illness, temperature etc. will mean these are not perfectly accurate).
-
On longer efforts or races (or long races!) stress and fatigue can change your LT1 and LT2 points significantly so keeping an eye on this using the S+ app by checking every half an hour or so can help you adjust the HR range you are aiming for. As an example, you might be running a HM an will start with an aim to be in the middle of zone 4 (“tempo” pace) but 60 mins in you notice ZS is showing you are dipping into ‘vo2max’ quite a lot so you could dial back to the top of zone 3 to make sure you aren’t overcooking things. Obviously the same applies if you are more focused on power. In the same way, if you know you can sustain a zone 5 pace for about 20mins and ZS has indicated you’ve mostly stayed out of ‘vo2max’ for your race so far you know you could prob. push the last 15mins up a gear.
-
-
@VoiGAS ZoneSense is essentially a representation of RPE. Traditional metrics will always respond faster since heart rate, pace, or power react before fatigue fully sets in. No special context is needed. That said, you’re absolutely right — the best metrics are the ones that make you feel good, grounded, and in sync with yourself.
-
@far-blue Good ideas, thank you!
-
