I have the same issue. Race S, Wahoo HR ticker + 3rd party strap. It often takes ~5 mins from start of activity for HR reading to become accurate (e.g. 150bpm Vs 40-60 BPM shown). The HR strap is definitely connected before I start recording the activity and displays the accurate HR reading until I hit record, which is when it often goes funny. This is pretty frustrating as it makes pacing more difficult and messes up the stats for my runs, so it’s difficult to see any HR trends I may have. I don’t believe it’s a strap or sensor issue as I never have issues with them while using my Wahoo Roam bike computer or any indoor cycling training software. The watch also displays an accurate HR from the strap when not recording an activity, so seems like the issue lies with the watch (particular model or my specific watch perhaps…). Any thoughts? If this continues I’d be tempted to put in a warranty claim, which is a shame because everything else about the watch is fantastic.

Questa è un’attività in montagna di giugno 2025. Un anno fa[image: 1781120433280-1000077770.png] Perfetto… Credo sia un problema di firmware o algoritmo

@Squirrel - thanks for the tip. I rebooted watch and iPhone a couple of times, and the watch faces now show on the store when they didn’t before. Back in business. Phew!

@Egika no, you totally understood my question, and I was hoping the answer would be what you said… Thanks!

@maszop sometimes you realise at the moment to download maps and … Yeah, otherwise this is just a discussion.

@withManish On iOS there is rungap for datamigration. And I use strava and intervals.icu. It collects data from multiple sources (I had different brands in the past). But most importantly, data of 5 or 10 years ago hardly has any relevance. But I’m no hardcore data collector.

@Squirrel thanks!

@sky-runner it does actually. It always starts to connect to the last used, but advances to others it finds. But you can disable each sensor per activity and it will remember this…

@aiv4r Thank you! I’m now looking for AirBnB accommodation for the UTA 22 next year I love this watch but I’m kicking myself for not trying on the Race 2 and the updated bands at the Suunto stand…

after everything you already tested, this really does sound more like a firmware issue on the Suunto Race S after 2.39.20 than a router/network problem. The interesting part is your router logs showing absolutely no connection attempt from the watch. That usually means the WiFi module itself is not initializing correctly after the update, not just failing authentication. I d still try one last simple test: connect it to a very basic 2.4 GHz network without mesh/repeator features, WPA3, band steering, or hidden SSID. Some devices become weirdly picky after updates. But since you already tested multiple routers and hotspots, I honestly doubt your network is the real issue here. Feels like the update broke WiFi handling for some units, especially since the problem started right after the firmware upgrade and before the maps could finish downloading.

@Kajkom Yes, it matches. But that doesn’t seem like it’s connected to the issue. The watch counts correctly all the way up until you save/finish the workout, at which point it discounts it 3.75%.

@Lazyjones said in Charging base: @sindavide Yes it sucks. I’ve bought cheap backup and it works better than original one. Stronger magnets. I read in this forum that the magnet of the original chargers is intentionally weak to not damage the watches

@Thlcd great comparison. I also have noticed that the last update, although full of bugs and battery eating, greatly improved the wrist HR on the Race S. Previously I only used the HR chest strap, but after reading comments here I gave it a chance for walking and body building – for biking the watch is on the handlebar, so I need the strap. Well, after a few tries, I have to say that finally it seems that it works well!

@2b2bff said in Min. Sleep HR too high?: @raven I know it shows the same issue, therefore I picked it… Those Min HR fields are actually buttons that show a line in the graph for the selected data. So, you can see whether the graph is below or above that line. Haha didn’t mean to imply you didn’t know you had the issue; it was just more musing to myself that I’m clearly not alone in this. I did seem to have missed that selecting it as a button turns on a line which is useful and clearly shows a few points in my graphs where the graph is going under the line. Thanks. I guess at this point my questions are more “does it work the way I’d expect it to for anyone or is what we’re seeing a universal truth in Suunto app/devices,” as well as “is there a good reason for this behavior I’m missing.” Have a good weekend!

@Messler I alsomwanted to compare specific sections but it seems it is not possible, as far as i am aware

@SRS2000 you can only have one max HR. It is impossible to have more than one. Even more it doesn’t matter as it is the top of your zone 5 anyways… Suunto Run is a bit different than the rest. With the others you have to set the zones yourself - more control, but a bit more hassle at first.

[image: 1777194333458-img_2053.jpeg] [image: 1777194333470-img_2054.jpeg] Some more helpful info I thought about, I read someone had a similar issue two times at the same distance each time. For me time and distance are different in each case, so I am not sure if it’s related to his issue or not. This is the issue I mentioned https://forum.suunto.com/topic/15116/watch-reboots-mid-activity-at-ca-9km-when-using-gpx-navigation/2 This also seems to be related. https://forum.suunto.com/topic/14527/crashes-in-the-middle-of-an-activity?_=1777194428329

@halajos said in FW 2.53.2 Countdown timer vibration: @sindavide yes, I also experience it on the Race 1. The last beep, which should be longer, gets interrupted, therefore sometimes shorter or not even audible. By the way, having 11 beeps is weird to me, I’d prefer 9 short and one long. Yes, same here. Plus alarm in the morning interrupts without pressing button and no snooze.