Zonesense readings
-
I’ve spent hours studying all the videos and used this system for a while - but ZoneSense still seems to defy commonsense to a large and very fuzzy degree.
Starting with the chart from Dragan showing the intervals - HR goes up and ZoneSense plummets - obviously not working. Nobody can explain however how to interpret how the algorithm fails in terms of HRV and associated lactate levels.
It’s clear also that running/cycling at a relatively steady pace the line traced by DDFA index is still WILD to the degree that most of the time it’s impossible to tell what’s due to “not working” or very strange metabolic behaviour.
Why is the DDFA Index line spiking all over the shop? What does it mean when the aerobic zone bounces like a yoyo to the bottom of the chart?
(Using here a Polar H10+ chest strap with slightly salted water applied to the strap and skin for good contact. The aerobic threshold was calculated to be 154 bpm by ZoneSense. Was “barefoot” running with a stride cadence of 180.) -
@Max-Melchior Well said! I think the aggressive/dismissive attitude is because they really aren’t very confident. ZoneSense is a bold move by Suunto but it needs more detailed clarification due to its instability. So far I’ve found the ZoneSense watch face itself appears practical when working out but the phone app graphics are scary.
-
@Ian-Beveridge there is no point in looking at the graph, what matters is just the zone you are in
Watch: Suunto Vertical Ti
Blog: isazi's home
-
@isazi Thank you for the clarification and simplification.
So…
New thresholds are calculated for each workout and the 3 zones are all that counts. The scales and graphs are meaningless.
Today on my two hour bike ride there was no measurement of ZoneSense thresholds in terms of heart rate. I’ve only seen this difference shown for aerobic threshold - never anaerobic threshold. Tying the two systems together like this is also very useful - when it happens - if it happens.
-
@Ian-Beveridge to be honest, also the thresholds do not matter if you are just using ZoneSense
Watch: Suunto Vertical Ti
Blog: isazi's home
-
Ieri sera al dal 16 km in poi stranamente la mia fascia cardio ha smesso di funzionare
-
Hi sorry for posting this here as well but there are no answer in others treads. I and others here in the forum do not get any ZoneSence data at all after the latest firmware update. Nothing on my side have change and it does not work on my Vertical och Race 2. Before the latest update work as it should. In the watch app it only states waiting for data, on iPhone app (latest beta version) it does not show up at all.
-
@isazi Okay! But don’t the ZoneSense thresholds and their shifting values inform us of anything? …or am I still stuck in an out-of-date paradigm?
-
There’s a bug with ZoneSense - in real time on the watch (Race S) it just randomly stops tracking while behind the scene it’s correctly logging changes and proper data (as viewed on the phone app). Once it stops displaying proper data it doesn’t recover during the workout.
The following screengrab shows data collected for an hour - but the watch stopped displaying the data changing from before half way through. There were calculations for both thresholds. This is the fourth time the live tracking has failed for me.
-
The ZoneSense bug - to which nobody has replied - is manifesting itself in two ways so far.
When tracking cycling the ZoneSense in real time on the watchface just stops (as reported ) but behind the scene data is still being collected and displayed in the Suunto phone app. The bug usually appears about half and hour into the workout. (one hour session)
When tracking running the ZoneSense real time data is displayed without problem over the entire one hour session. Then when accessing the data in the Suunto phone app there is absolutely no data for ZoneSense.
It’s a mess!
