@far-blue Yes, got the same problem. I reported it to Suunto support who told me they will report it to development.

Charged last Thursday to 100%. Had my usual one and a half hour club training Thursday eve. (My stryd was connected, my polar chest strap refused to connect) Had a 10k trail on friday of about 1 hour (used navigation, no connected devices) Had a 30k trail on saterday of about 3 hours(also with navigating, no connected devices) Gps setting is on the highest (because of some stupid design decisions of suunto you cannot turn down gps accuracy without loosing maps). I don’t use aod. Now on sunday, 3 days after charging, battery is down to 39%. It’s okayish. My previous watch (forerunner 965) did worse. Watch before that (forerunner 935) did way better, but had a mip screen, which is better for sport, and didn’t have maps, only breadcrumb navigation.

@valeR This sounds like two different things. What I saw on my watch was not a safe mode with limited functionality, it reported that it was restoring the watch to a safe state after encountering an error (1403, whatever that means, in my case). It had no functionality other than the progress bar showing the restore progress. No time, etc.

@Steven-Hambleton I bought Barton spring bars that somebody else recommended for Race S. They are a bit thicker and fit perfectly - not loose at all. Also, I compared them to spring bars that came with Suunto nylon band.

@pilleus hi there. Thanks for this. How far back should I go? Or do you know which firmware version I should jump to for the suunto race S. Much appreciated

@ChrisA it is Runalyze… yeah, possibly it’s a me problem

@laufbursche7 I think you should wait - official 26.1 probably will be released tomorrow. I couldn’t stand iP 17 BT issues and installed Beta 4 (not RC) and everything is perfect now. Just as I suspected, battery drain in watch and phone is over - unstable connection was draining watch and phone 24/7. Hope they don’t break something new in the stable release.

I’ve had similar chronic issues with the heart rate on my Race S. Not registering an accurate heart rate until a mile or two into a ride or run, dropping heart rate during an activity, reading overly high during a ride or run. On some activities like cross training, I’ll never get a reasonable heart rate reading. I tried posting a review on Suunto’s website describing this and other issues I’ve had with the Race S and Suunto refused to publish the review saying my feedback “is not a common issue.” I contacted customer support hoping for some resolution since they apparently regard my experience as abnormal. Instead of a resolution, I got a bunch of excuses as to why I can’t really expect the watch to perform any better. All in all, my experience with this watch has been a disaster. I’ll never buy another Suunto product. Going back to Garmin.

@Sixeela29 en tout cas ce n’est pas Suunto qui bloque puisque les segments strava sont une fonctionnalité strava. Je n’utilise pas strava. les infos pour mettre en œuvre sont dans le manuel.

@sartoric actually if I check the activity on the watch, I see HR for the whole run. [image: 1761392386169-img_4023.jpeg]

@Stefano-M64 bummer, doesn’t seem like it’s widespread enough to get attention or maybe people don’t realize it.

This is insane. I remember 9PP had an issue measuring HR when off the wrist, then it was fixed in 2024. And now they are back to square 1. Most likely they could’t reuse any of the OHR sensor code from 9PP due to different hardware and are writing it from scratch making the same mistakes. ‍️

@tailwind_mrs it does start from 0 as soon as you start swimming again.

@rawmtb keep me updated. Hard reset didn’t help for me.

@LGoSo It actually worked! Unbelievable! The low resistance (dirt cheap CooSpo) belt - when combined with all the other measures I’ve taken worked 100%. It’s also changed the heart rate upper level and stabilised it at Zone 4 instead of VO2max - despite today being a minute faster over a 6k run than yesterday when my HR jumped for a sustained period in VO2max (H10+ belt). It’s the first time since I started posting here that anything has made sense. The H10+ strap is simply not working properly - and that appears to include BPM as well as HRV. I did need to shave the part of my torso where the strap goes, dry brush the skin and use a proper conductive gel - but the result is solid. When I had previously tried using the low resistance CooSpo strap with a hairy chest and just water the result was messy. Clearly, individual skin conductivity is involved in determining the limitations of the higher resistant straps. Looks like bad quality control in production - though this probably works for most people.

@fritzbt2013 said in Custom Sports Modes disappearing after each firmware update: @gizmo two updates ago I lost everything like you. Last update (the hotfix) I only lost one custom sport mode. The later has been my typical experience with updates since I got the watch. What I have learned is to add a custom sport mode that I do not use such a stretching and make sure it is the least used. When I get the update that will be the one I lost. I did that as well a couple of times. Now I always have, not a least used custom mode, but a least used standard mode (not customized). And never had any more any mode deleted. Coincidence? Marboutism? Nothing scientific for sure .