@cosme.costa Having Suunto OHR armband would be cool. Sorry being offtopic

@fondueaufromage For the buttons, you might try to clean them (like put watch in gentle warm water, with few soap and brush gently). Maybe not the pb, but worth trying. After, if soft or hard reset didn’t change anything, it is looking like an internal issue. Is it doing the same for all menus?

@Dimitrios-Kanellopoulos Sorry to say it, but if Reliability and Battery efficiency would be the focus for Multisport watches we wouldn’t have the current problems with Crashes, not working Bluetooth sensors and Battery drain. For Dive products this might be. Had two Zoops, both died with depth sensor problems. So it wasn’t software…

@shamilt1 IMO The Race 2 is shy a few meters than other devices yes, but I think the other devices are more ‘generous’. What I found is that the Race 2 is very much like AWU2/3 when it comes to distance and represents the real distance. I might get the Vertical 2 now that the Vertical Week is upon us and will be able to compare them side by side. The weirdest thing I experienced on my Race 2 is that when you are navigating a route or snap to route the distance is literally the same as the AWU3, when having it on free (breadcrumbs) it is shy few tens of meters. Nevertheless the GPS track is great and smooth and its one of the most beautiful/light watches I own (the Ocean is still the best looking )

@Egika ja stimmt. Aber ich hätte Suunto das zu getraut. Gregor schrieb mir aber, das es für alle neuen Watches kommt. Daher kollektives Aufatmen

@Ries22 Feeling is taken into account in recovery value. If you have put your latest activities with less feeling, it might impact.

@carloscolaro hey, did you solve this problem? i have same watch and i have same problem.

@ruNSuunto I cannot find the peaks with the same type of equipment as you. Can you check the firmware numbers of your equipment: Suunto Run and Coros Heart Rate Monitor?

Hello, Have the same problem, HR stuck at 110 BPM during the first 20 minutes of running, then suddenly goes up to 165 bpm which is the correct reading. It was working better before the last firmware.