Suunto ZoneSense
-
@Dareo I have already told you this before:
The same thing happens to me, inconsistencies everywhere. The live data from the watch never matches what is later indicated in the app. When it is indicated, of course, because sometimes that data appears and other times it doesn’t. I have uninstalled, re-installed, reset, etc. and everything remains the same. I still don’t know how I haven’t given up on the effort… it seems I’m a masochist.
-
@enriqueescoms Enrique (¿o Quique?) - Yes, I remember you telling me, but I thought it was just growing pains for the app. Now that there have been a couple app and watch updates I figured that issue would be worked out, but that doesn’t seem to be the case. This is why I’ve thrown the question out there again, thinking that my brain is somehow incapable of properly interpreting the data.
-
@Dareo looking at your heart rate graph, your metabolism was not in a steady state, HR was continuously rising. Pace is not visible. Was this run supposed to be an accelerating or a steady-state run?
-
@halajos The intention was to gradually pick up the pace without over exerting myself. I admittedly have some accumulated fatigue from the previous 3 days training sessions. This is the analysis of exact same route the last time I ran it 2 weeks ago:
The duration was pretty much the same. Today’s was a little longer because I don’t run with my phone so the activity continued recording until I got into the house to take a picture of the watch.
It’s evident that I was less fatigued 2 weeks ago, but it still doesn’t explain the inconsistency from what’s displayed real-time on the watch. Again, that inconsistency repeats itself time-after-time which is why I pretty much don’t pay attention to the real-time display despite really wanting it to jive with the app.
-
@Dareo Mine match up much better than yours. What belt are you using? Is it possible the data coming from the belt affects real time? I agree that this is an issue. I assume you have a 10 minute aerobic warm up?
-
@Brad_Olwin I’m using a Polar H10 with my S9PP and haven’t had any issues in the past with the belt. As far as the 10 minute warm up, on both graphs you can see an initial rise of my HR at the beginning of the session followed by a drop in the HR before things start to get a little more stable. That’s because on this specific route I have a short uphill after leaving the house then an easy downhill run until I get to the boardwalk.
-
@Dareo Yes, exactly. That’s what I thought. But no, inconsistency is still the norm. And consequently it is not a reliable tool for me. (Enrique, yes
) -
@Dareo you can confirm R-R intervals data quality with Runalyze.
-
@halajos Would be great to have such a functionality in the App. Maybe just a quality metric, like Good, Medium and Bad. Then I we would have a hint why it doesn’t work like expected and could e.g. replace the belt to get better results
Edit: And maybe the possibility to do the warmup as a separate activity or multisport activity. I don’t want the warmup to have influence to my running statistics
. And so you could have Zonesense from the beginning of the run -
Yesterday I attended my first pilates class since xmas (and could feel it!) and then went on a 30mins easy run. I also admit to prob. not hydrating enough after the class. What I noted was that my HR was well above where I’d expect for an easy run (160 rather than 140) but using ZoneSense I was able to confirm the easy run was indeed still easy on my body because it still showed I was working aerobically despite the higher HR
I assume what I experienced here was basically a form of aerobic decoupling where dehydration and an hour of previous activity pushed my HR up rather than it rising due to increased effort. This is a recognised problem with zone 2 HR training and longer runs and it’s cool that ZoneSense appears to be ‘immune’ to it - I assume because the R-R interval properties of the heart change with stress, not heart rate
