@jannis That’s a pretty generalised view you’re posting about the Suunto. As I mentioned above, it works for me – just as accurately as it did with my Garmin Epix back then. And I ask myself: what’s wrong with resources rising again during the day, even if I don’t take a nap? When I’m sitting relaxed on the sofa, it’s definitely restorative.

@Sportsfreund Yeah! I think this is known by Suunto. I have the problem as well. There was a problem with the 9 Peak Pro. It just erased all the watch faces. Suunto fixed that in a few days, but since then the watchfaces are not shown in the app. On the watch I don’t have problems

@Steven-Hambleton from a few posts I read here I can see your initial enthusiasm about Suunto faded very quickly. What happened? Sorry for the off-topic. Well done @Nikolai-Simonov !

@2b2bff Thank you

Hi, I’m having issues again with HR data not being recorded in the last part of the activity. There have now been consecutive updates all at the same time, so it is difficult to understand why the problem has occurred again. I’ve updated the Polar H10 to latest fw, 4.1.10 I’ve updated SA to 6.5.7 (Android) I’ve updated the Run to 3.22.24 [image: 1765211731887-run.png]

@mich-heller that’s definitely not good. Weird. So far I haven’t had any issues except a bit of difficulty initially updating the h10 software. Let us know if u work out what it was.

@2b2bff I’d be surprised to see a tilted rectangular display But I agree on the QC part.

@vinc14 in my case, rebooting my phone helps, at least for a while, see also here Obviously that’s not a solution.

And again on my Vertical all watch faces disappeared. I don’t sync my 9PP now to avoid this. [image: 1765286317513-21361.jpg] [image: 1765286317527-21362.jpg]

@Brad_Olwin As I said in my original post this wasn’t the issue. This issue fixed itself and I am now able to see zonesense data on the watch and in the app, and I am not sure but believe one of the 2 following things fixed it: HRM 200 version updated to 5.40 Looking at the HRM 200 manual (Manual) I realized the device have 2 connection types: secure and open. Secure is when the device blinks green twice and open when it blinks green three times. I am not sure what was the connection type when I originally tried to make it work, but when trying again after opening this thread I made sure to use the open connection state. My hypothesis is that one of the two fixed my issue. Leaving this for future reference and future google searches, as when I searched this I didn’t find anything related.

My Suunto Race 2 stopped measuring blood oxygen after updating to version 2.48.16. Manual measurements don’t work at all, and the nighttime readings are inaccurate. A soft reset didn’t help.

@leehikes said in Watch mode during activity recording: I see the time is on the info page that gives you your heart rate distance and time taken but I need my glasses to see it as it is so small. You can disable Music controls if you don’t use it. For bigger time, customize your sport mode and add/use Time of day as one of the data fields on any of the data pages. In case you don’t want to waste S+ slot for Big numbers S+ app, or don’t want to have one more additional S+ page.

@VoiGAS No because complications are not very readable. There is no accessibility options to increase text size.

@el2thek thank you for your reply. I actually still haven’t received any update. I made some other tests this morning, one of which being installing the Suunto app on an iPhone and this way, the synchronisation worked. But as my own Smartphone is an Android, this doesn’t help me a lot. I suspect you’re on Android as well? If so, what Android version are you on and what is the version number of the Suunto app you last installed?

Posting my experience here too. I continue to monitor in my next charging cycle. I have a feeling that the slight drainage increase that I experienced in the last day or so of the previous cycle continues but too early to tell for sure. Here is my recent battery experience with my Vertical 2. Over the past 14 days (and a bit) I managed to do 19.5 GPS+HR activities and drain 91% of my battery. I built a simple prediction model for battery drainage rate assuming that there are three different drainage rates: During GPS+HR activity (running and cycling in my case), during sleep (DND) and while idle (with notifications and raise to wake variations). Under these assumptions I tried to approximate the drainage model as close as possible to the battery levels and activity times I recorded during the day and came up with the following numbers (they imply slightly less than 5% per day without activities and more than the spec 65 GPS hours): Sleep tracking rate: 0.11%/h Non activity rate: 0.25%/h GPS Activity rate: 1.16%/h Flashlight rate: 20%/h The above model worked very well during most of the two weeks until the last day or so when the battery got to about 20%. From that point it seems to drain faster than my model allowed. In fact, until that point, the model showed about 1.07% drainage per GPS hour which I updated to the higher number above to compensate for the end. Settings: AOD OFF Raise to wake: Display only 247 HRM Notifications ON No external BT connections except Android Suunto App (6.4.7) Wireless OFF BT discovery OFF Brightness LOW DND from 22:00-5:40 Sleep tracking on with HRM but without SPO2 NO USE OF FLASHLIGHT [image: 1765122476069-pasted-image.png]

@Jaxxdu I did just post in the iOS 3.6.0 thread there is something wrong with the sync too and I can see HR sensor failures almost every night. Like this: [image: 1765188757075-img_5051.png] I am no longer sure if I would go for Suunto device for diving. I always loved Suunto products, compasses, watches but seems like modern software and qa for that is just still in its childhood. This isn’t only a Suunto problem it’s true for other smartwatch, device and even car manufacturers. So I guess we shouldn’t rely on it unless it’s bare analog metal.

@Mff73 only one phone

@Highlands No issues with my V1 at the moment. Try again after 24 hrs. I’ve seen similar behavior with just one watchface. According to the app it was installed, but the watch never showed me. The day after, suddenly the installed watchface was shown in the app.