HR zones different between watch and app
-
There is a discrepancy how the HR zones are defined in the app and the watch. In the app, it is always the lower end of the upper zone (which is also mentioned in the app) while on the watch it is the upper value of the lower zone.
E.g. if I set 157 BPM as the value between zone 4 and 5 on the watch, then the zone pointer during the activity shows at 157 BPM that I am in zone 4 while in the graph in the app it shows that I am in zone 5 at 157 BPM.
Time spent in zones though is the same between app and watch because it uses the calculated zones from the watch.
If found already sooo many bugs where the app doesn’t align with the watch! Also the popular recovery bug is caused by the app. It’s a nice watch but the app is just bad under the pretty surface! Complete opposite from Garmin, where the app structure and visuals are just bad, but at least everything is perfectly in line between watch and app.
Seems as if the suunto developers do not speak at all to one another.
Does it even make sense to report all the bugs here or do developers anyway never check the forum? -
@brave_dave I may be wrong but It doesn’t appear that developers check the forum. There are some people on this forum (some moderators and beta testers) who have an ability to pass information to Suunto team, but that isn’t guaranteed for every issue reported issue.
Also, I have already reported the same issue with Race. The software is the same across all watches, so I bet this applies to other watches as well.
-
@brave_dave said in HR zones different between watch and app:
E.g. if I set 157 BPM as the value between zone 4 and 5 on the watch, then the zone pointer during the activity shows at 157 BPM that I am in zone 4 while in the graph in the app it shows that I am in zone 5 at 157 BPM.
ios or android ?
-
@Dimitrios-Kanellopoulos Android app v6.2.2
-
@sky-runner so I am not the only one who realized it…Was really confused because the time in zones did not align with the graph at all.
Should be a really easy fix in the app though by just defining that the zone values are always the max. of the lower zone
