Suunto ZoneSense
-
@Kramble @duffman19
I have been seeing the exact same thing up until yesterday (ZS dropping into low aerobic as I start climbing & increasing effort, basically reverse of what I’d expect to see).This was my first time out since ZS updated on Friday & it worked perfectly (ignore the 2 drops at around 1hr.12mins, I was skiving off work & had to take 2 phone calls whilst on the trail)
So from what I saw yesterday the update has worked has worked a treat.
Incidentally I uploaded a run on Friday around the time ZS updated & it totally screwed the results…
-
@Mattg576 said in Suunto ZoneSense:
@Kramble @duffman19
I have been seeing the exact same thing up until yesterday (ZS dropping into low aerobic as I start climbing & increasing effort, basically reverse of what I’d expect to see).This was my first time out since ZS updated on Friday & it worked perfectly (ignore the 2 drops at around 1hr.12mins, I was skiving off work & had to take 2 phone calls whilst on the trail)
So from what I saw yesterday the update has worked has worked a treat.
Wow never seen such coherent graph !
I thought I did the update, hard to be sure… -
@Kramble you can remove it and reinstall to be sure.
-
@iterumtenta said in Suunto ZoneSense:
@Kramble you can remove it and reinstall to be sure.
Thanks, but I already did, is there a way to check it ?
-
@Kramble Since the release is the updated version, reinstalling should work fine. I couldn’t find a way to check the exact version installed on the watch either.
-
@Łukasz-Szmigiel said in Suunto ZoneSense:
A tiny-tiny bug that I’ve found.
When using Aerobic Decoupling and ZoneSense with ZoneSense displayed, an event (alert) from Aerobic Decoupling resets ZoneSense view to a default that contains time in each zone. So when a different value were cycled by the top button, it’s back to default view.
This bug applies for all alerts unfortunately
-
I have been using Zonesense for a few weeks now and am struggling to interpret the results. In general Zonesense seems to underestimate the effort.
For example this 50 min bike session with a few very hard intervals ending in an all out effort: https://ibb.co/km0XgKx
It is interpreted by Zonesense as a mostly aerobic effort: https://ibb.co/WxwjhgM
(The all out end is even a low aerobic effort.)Suggestions on how to interpret this are welcome. I use a Suunto Race S with a Polar H9 HR belt.
-
Today, for the first time, the evaluation in the app did not match the display on the vertical.
I was on the road for 2:19 hours, of which 1:23 hours were in the green zone, 0:41 hours in the yellow zone and 0:15 hours in the red zone. That’s what the Vertical showed at the end of the training session.
The hand in the outer circle also showed this correctly on the watch. The app corrected the percentage twice after I selected the ZoneSense display. First, it showed 1:05 minutes in the red zone (VO2max), then no VO2max zone at all.
The activity was tagged as “Anaerobic - hard”, but I activated the S+ app “aerobic decoupling” for the first time today, which only showed a “%” sign in the center of the display after 15 minutes (without any number), with “High” in red letters underneath. This did not change during the entire training session. I often switched back and forth between ZoneSense and aerobic decoupling.
Perhaps there is an “incompatibility” between the two S+ apps, as I have always had conclusive ZoneSense results so far?
-
@Jan-Van-de-Velde not sure if you missed it but ZS is not going to be able to represent efforts on short intervals, this was stated since day 1 as a limitation. Sustained efforts are more what ZS will work best with. I don’t bike but in running, I’ve noted that it takes ZS up to 4 mins on a hard interval to start represent real effort, so have that in mind. Also when you do sudden high changes in pace, ZS will go to green, sounds odd, but remember this isn’t HR, this is based on HRV data so it’s a different concept, we have to adjust to that.
-
@herlas said in Suunto ZoneSense:
@Jan-Van-de-Velde not sure if you missed it but ZS is not going to be able to represent efforts on short intervals, this was stated since day 1 as a limitation. Sustained efforts are more what ZS will work best with. I don’t bike but in running, I’ve noted that it takes ZS up to 4 mins on a hard interval to start represent real effort, so have that in mind. Also when you do sudden changes in pace, ZS will go to green, sounds odd, but remember this isn’t HR, this is based on HRV data so it’s a different concept, we have to adjust to that.
The end of his graph, something clearly went wrong
-
4 minutes seems about right from my experience today doing a fartlek run - although the one long (7:30) interval I did I was suffering at the end and it dipped a little. Else you can see fatigue at the end when I skip back in not as fast but ZS shows I’m suffering.
-
@pilleus I’ve seen similar behavior with app differing a bit from ZS summary on watch. ZS data gets analyzed in the cloud after you synced your activity to the app, so sometimes there can be small delays while that happens.
Also it has been mentioned some S+ app have issues when using along size ZS app, climb app was mentioned and now the one you said might be another. Due to how important ZS is for Suunto, I’d bet they’re already looking at it .