Suunto ZoneSense
-
@Egika said in Suunto ZoneSense:
@pilleus said in Suunto ZoneSense:
If this is the case and the baseline recalculated after the activity on Suunto servers is not synchronized into the watch, then the live display on the watch would be pointless for me …
actually this is what is supposed to happen: the baseline is synced back to the watch.
Synced back to all watches? I use the Vertical and the 9PP with ZoneSense …
-
@pilleus I would expect the ZS baseline to be updated as part of the SuuntoPlus sync step whenever you do a sync - assuming the ZS SuuntoPlus app is installed on the watch being sync’d.
-
Walking on a 13 % incline and running on a 3 % incline ️on the treadmill.
Intervals of 2 minutes walking and running. ZS also shows me a conclusive graph here.
-
Is there a way to increase the font size a bit? After a certain amount of time, I have trouble reading the values while running.
-
@iterumtenta no font size is adjustable in any Suunto screen, I’d like to see changes but we don’t know if it’s being considered unfortunately.
-
Hi friends, after some weeks of testing, I can’t find the connection between ZS in watch and app. On the watch it seems to work most of the time. APP shows nonsense 100% of time. I don’t catch this. If this should show us “real time effort”, what it does most of the time, why in app is not only the mirror what was measured by the watch. I saw here something about recalculating on the suunto servers but… really? How can be real time effort recalculated on the server? Then it can’t be real time… or? I don’t know guys, I think that this is very poorly explained.
If I don’t want to use it anymore, is there any possibility in the app to turn this thing off? It is always as default in the graph. I need to use strap for 100% activities if I don’t want to have absolutely random HR data, so in every activity I have this nonsense graph as default. In the watch it is easy, just don’t use S+ app.
Below example, it is like this 100% of time. In the watch there are some times measured in zones, in app 100% Z1. It definitely wasn’t
It is good idea by design, but does not work yet, it should be presented as beta I think.
-
I use ZS too. For me there is a minimal difference between watch and app, but only in the summary of the times in different zones.
I have never seen such straight horizontal lines between two points as in your graph. I think that data are missing or bad in these areas?
-
@pilleus said in Suunto ZoneSense:
I think that data are missing or bad in these areas?
I also think that may be the reason. @AntoniusGaius you can check your data quality in Runalyze (requires free account).
-
@halajos OK, I did, but I can’t interpret it:
In Runalyze it says that max HR during exercise was 149 vs. SA says 155 (much more possible) It looks weird because this and SA data are not matching. I would appreciate to turn this thing off instead digging in inconsistent and unreliable data.
Strap is Suunto smart sensor - I have two of them - reliability is not high. I did half marathon last month an whole race I had no HR data at all. I had to re-pair sensor and since this it works +/- well. Frustrated again. I miss old good days with Ambit and Movescount.
Anyway thanks for help. Appreciate this. -
@AntoniusGaius this clearly shows bad quality data. It should look like a narrow line, instead of scattered points all over like this. There are some sections of good data, where you see a line in your chart. Your HR belt is very likely worn out. Check if this is a recurring pattern in your workout history. If you don’t have any arrhythmias, then you should see a (wavy, if your HR fluctuates) line in this chart.
-
@AntoniusGaius
What about the battery ? -
@halajos I will try to upload more sessions to see some differences. Thank you for your help.
I will buy H10 instead suunto smart sensor. I had problems with them early after start using them. Maybe there is some upgrade on Suunto side planned? This thing needs redesign as other HR measurement stuff in suuntio universe. -
@sartoric New one.
-
-
@AntoniusGaius I also switched to polar H10, because I can get replacement belts for it on ebay for the fraction of the price of a new Suunto belt.
-
@sartoric Of course Heavily. I checked other activities in runalyze back to September and I found one export from 24.9.2023 and it was corrupted too. Strap has to be definitely bad…
-
I’ve tested zonesense for a few sessions and the results seems sometimes strange to me.
Today the watch didn’t show red zone and the suunto app shows it. Well why not but the 2nd threshold seems quite low (lower than my lab tested 1st threshold…) On top of that zonesense dropped backed to green zone when I finish my effort and my HR was going near my “normal” 2nd threshold and what I know I can sustain for ~1hour racing.
2 days ago the 1st threshold was at 116bpm.
The difference in measurements seems huge doesn’t it ? I’m not sure if there is anything I can interpret based on that
-
@tomtom73
before any interpretation, you would check first the quality of the RR data registered for such activity. Runalyze provide such information (search the forum for little more detail on this).
Without good quality of RR intervals, i would assume that ZS could not tell any real “truth”.
i would be really great if Suunto could provide such data quality indicator, at least, user would have this information before any analysis. Or even ZS indicate like a level of trust, or something like this… -
@Mff73 Thanks !
Runalyze shows ~1% anomalies with a polar h10 strap. Is this bad data quality ? -
Had my first run with the new HR belt. Really like the idea of Zonesense, tested it on a mid week slow run, after being inactive for a couple of weeks due to sickness (man-flu…). Made a point of not really keeping an eye on HR but after the 10min initial window I followed the Zonesense and tried to stick in the green aerobic zone. After the hour loop was up the on watch (vertical) app showed I had about 75/25 aerobic/anaerobic, however, after syncing to the phone (android) the app say’s 98% aerobic. Seems to be a big disconnect between the two.
Is this a bug or a feature?