Suunto ZoneSense
-
I did a Steady State Interval run yesterday. 3x10 min SSR with 5 min Recovery. ZS worked very well on a Vertical. Rare that my zones match up this well so I was not fatigued. And yes, I bit too hard for steady state…should have stayed in the yellow but I was running by RPE and did not have live ZS running.
-
@Brad_Olwin Aye, it’ll come down to aerobic as expected but the lines are horizontal like it’s missing data?
I’ve shown a run from Wednesday (graph as expected) which was actually the same workout - I’m pretty unfit at the minute, had surgery recently so easing back - my fitness has fallen off a cliff
-
@andrewjknox I was not looking carefully enough! The flat lines are either lost HR data or some bizarre HR lock…Make sure the belt is wet, it should not record the data if data are poor. Maybe the app did a bizarre calculation, you could try force quitting the app.
-
@Brad_Olwin I initially thought that too but it was recording heart rate data? That’s the background comparison graph in my image. Assume the HRV is just a separate stream of data from the belt that didn’t get picked up?
-
@andrewjknox I’ve never seen this!
-
The topic may have been asked but I did not find a reference, although there is a reference to determining heart rate zons.
The question is this - at the end of the workout, the zonesense data on the watch is not the same as the data in the app.
I am attaching two pictures - I would be happy to receive assistance in understanding the topic.
Thank you to anyone who helps.
-
It’s a much-talked-about problem; in my opinion, many do not trust zone sense because of this. I intuitively believe that the APP data is accurate and the watch data is not. Others, the reverse. The value proposition for Zone Sense is the real-time watch data so they need to fix this for product credibility.
-
@Brad_Olwin I’m going to put this down to the fault of the chest-strap so bad data in, bad data out. I’ve included screenshots of the R-R intervals under HRV in Runalyze:
Bad data:
Good data:
Thanks for having a look!
-
@Stephen-Kenny I find that really weird because, in my case, the values on the watch and in the app are exactly the same.
-
@andrewjknox Now I know that you can flat line ZS with bad data. The fabric part of HR belts does not last forever. Mine give up after a year or a bit more.
-
@andrewjknox Dear Andrew,
I observed such results too. After lots of trials I came to the following conclusion: ZoneSense allways works proper with my Suunto vertical. BUT: Suunto app shows ZoneSense data correct if HR-data is above 120 bpm during exercise. Maybe you have the same topic?
Have an nice sunday ! -
@Brad_Olwin Nice, hopefully others will find it useful when they see chest-straps can generate bad data when the materials start to fail and the ZS graph can look “funky”. I knew there was a risk of the internals getting compromised once you change the battery and damage the rubber ring/seal/gasket (which has happened to me (twice) - the battery life then takes a nosedive, you then start changing batteries more and more often).
Went for the same run this morning and it was okay oddly.
But I’ve ordered the Garmin HRM 200 - mainly because of the battery indicator
I’d like to have a bit more heads-up when the battery is dying without having to check in-app (Suunto watches don’t have a sensor battery warning do they?) -
Had another try with Zonesense today with a new belt, for for me its just random
Heartrate vs Power looks good
Zonesense vs Power looks… hmm
Calculated Zone is also far off in my opinion
Data Quality is good, I checked it in Runalyze. Could it be that Zonesense results differ with the individuals physiology? For me it just doesn’t work, but Heartrate works very well. From belt and also OHR
-
@VoiGAS I see similar results & have posted about it above.
As the workload increases significantly ZS often suggests the complete opposite.
Someone will be along shortly to tell you that you need to read ALL the literature & watch ALL the videos before you can make any sense of it… (but won’t actually provide any answers)
All I’ve gleaned so far is that we may be running on the wrong type of trail or the hills we’re running up aren’t long enough
-
@Mattg576 Right, I also think it works just in special circumstances. I watched a lot of the videos and I understand it reacts slowly. But how long am I supposed to run in the red zone.
But maybe it will improve and maybe I also find a usecase for it -
@VoiGAS Janne said there is a lag of about 2 minutes that ZoneSense needs to react to something. So you need a prolonged effort of those two or three minutes to make any sense of ZoneSense. It is nothing for short periods. Also it is said that the actual curve doesn’t matter, only the color…
If you match that with your workout, you see that the increased effort beginning at your 30 minute mark pushed it in the yellow Zone about 10 minutes later.ZoneSense works best, if you have longer intervals with constant effort.
Personally I think the tool is interesting, but it doesn’t fit every job. And it is still in the early stages. When Suunto can bring down that 2 minute lag it would be even more helpful…
-
@2b2bff I know, but its not like there was no effort between the peaks. I just did them to reach the red zone. If I would have done it in a race it would have been over for me, but Zonesense signals ‘Everything is ok’.
So if it only works if I control my effort right, then I have no idea what the usecase is.Don’t get me wrong, I really love new technology like this. But how it can be a benefit I just don’t understand
-
@VoiGAS said in Suunto ZoneSense:
If I would have done it in a race it would have been over for me, but Zonesense signals ‘Everything is ok’.
I don’t doubt, your evaluation about failing in a race, but are you’re sure? Ever tried it in a race (or in racelike conditions - like tapering your load before, having enough sleep, etc.) ? That would be an interesting thing to know, if the majority of the racing people actually benefit from Zonesense in those races
? -
@Mattg576
IANAHD (I Am Not A Heart Surgeon), but…these charts almost make more sense if you consider DDFA to be HRV (which I appreciate, it isn’t really), with the bottom of the chart being high HRV (relaxed/low intensity), and the top of the chart being low HRV (stressed/high intensity).
because i would expect sharp HRV increases (the dips on the chart above) to occur when we’re moving from high effort to low effort, as the heart rate is increasing beat-to-beat. and then i would expect it to then sharply snap back to a lower HRV (the subsequent peaks in the chart) as we hit and maintain the high-effort heart rate.
i’m theory-crafting here, but we can see the dips in the DDFA chart for the high effort parts. it fees a bit like the data is telling us the story, but the zones/colour-grading isn’t being applied in a useful way. at least not for this kind of activity. over longer activities without quick and short effort changes i guess it’s more useful, but it feels like with some tweaking it could understand both scenarios.
-
@VoiGAS As I did a slightly hilly race for the first time last week, I know it is a totally different thing to a traditional race on a flat surface. Possibly I tried to be conservative with my resources I didn’t reach heart rates I usually reach when running on a flat course. As it was 6 round running up and down a smaller hill, each round about 10 minutes, I don’t think ZoneSense could have made much sense of it either. But I haven’t had a Suunto watch with me to prove it.
Long story short, my point is: possibly trail running isn’t steady enough for ZoneSense to make sense…