@soisan Look at the graphs - the HR data from the belt is rock solid for the first two examples - that’s downloaded to the app from the watch. Why is the graph stored on the watch completely different from the graph correctly displayed on the phone app? It’s amazing that nobody can see this. The detailed phone app graph shows a completely consistent (and stable) HR recording. Yesterday I went for a walk with just using the optical HR and the two graphs (watch/app) were identical - ZoneSense was activated but there was no data available after syncing. Basically - the software/firmware is a mess. It was the same with the counter being blocked in real time ZoneSense - first admission that there was a problem was the recent firmware update with this error being listed as having been corrected. I’m not going to be using ZoneSense at all now. I’ll see if by getting rid of ZoneSense also removes the problems with the stored graphs being different on watch and app. So far I’ve identified 3 different problems - one has been fixed with the latest firmware update.

@soisan After watching the videos I think Suunto does mention shortcomings, in the app the wording is very careful about whether or not you should change your zones. I agree that the short marketing videos are just that, marketing videos.

@GiPFELKiND said in I have zero confidence in Suunto route navigation!: @sky-runner wow thats incredible inacceptable. But that is no new Problem. In complex routes its necessary to show at the Phone. This didnt work Like exspected. At no time you can navigate a Special route with your Suunto. I navigate“Special” Routes all the time, most of them off trail. For example, a four day fastpack in the wilderness with nearly 3 days fully off trail and no issues. However, I do admit there are issues. The auto-reverse can cause issues and I have had an issue @sky-runner describes but long ago with the 9baro before maps. I will ask around some and see if other testers have encountered this.

@pavel.samokha thanks for the info. I will have a closer look at this. Just one question: for uploading to the Vector I still need the App on the iPhone? Or can it be loaded directly to the watch from the web application (PC)?

@Hari-Seldon said in 3.21.14 Rolling out: The notification experience after waking up in the morning has been optimized HRV is missing from the report

@Audaxjoe yes, I can also confirm the warranty, even for the new replacement product, ends as soon as the original warranty is over. It is only the service center good will to prolong it.

@Florentin 26.0.1 released, so far so good. Sync is continuous and complete.

@Yves_ I was normally asking. I don’t know about this feature. Maybe it runs on background. I used this with Garmin, but that was clearly visible - timeout after finishing the workout and the HR drop value stored in activity.

@Tomas5 with almost every Suunto watch I had bad OHR readings when riding my bike. Usually it would eventually just fall into the lower 80s and stay there. Race 2 was the first watch to ever got OHR in cycling right for me!

For me, on a Race 1, the battery drain actually seems quite a bit worse after the update. “For what it’s worth”.

@Mouse-Cruiser ahahaahahahah

@WlodiPawel-87 thank you. Reported. Should be fixed quickly.

@Squirrel not sure how Suunto does numbering here. But logic says that 2.46 should be ahead of 2.44. But who knows And user manual refers to wheel size calibration in settings, but it is not there at least for my Suunto Bike Sensor.

@gogapo I had a couple of those naps while sleeping with my Race S as well. Usually it works fine for me, though. At least for overall sleep duration. But don’t look too close at the stages. Interestingly the last two nights that my watch woke me up with vibration in the morning, it detected my awakening two minutes before the alarm.

@owend thank you for the answer

@OutdoorMan ah!!! You guys are so good!!! Got it back, thank you so much!

@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