@alp1n3 said: Switching to Garmin since Suunto has had over a year to fix the auto-update bug, but can’t manage that. You are of course free to switch brands when ever you like and I think it is interesting to see the approach of others. However… if you switch brands in the expectation to find a bug free watch with great battery life, you will be disappointed. I switched from a very expensive forerunner 965 to my current race s. For me, battery life is about the same (garmin charge every 3 or 4 days, suunto every 4 days) but the amount of bugs I experienced on that garmin is incredible.

Hopefully they’re able to fix it soon. It feels like with every update they just introduce more problems. Currently still experiencing the auto-update bug (can’t disable it essentially), and now the battery bug has gotten even worse.

@bartolomeo6 I have an HRM DUAL and didn’t have any problems with it. Are you sure the belt is connected and used in the activity? The heart symbol with little “wings” on the side? If yes, sync the activity to Runalyze and look at the r-r graph at the bottom. It might give some insights…

@krad801 there is no way to set the watch for GPS altitude only. If you find such a setting in the app, it is used for activities recorded with the app directly. Otherwise with the watch on a bike, there sometimes can be wind affecting the barometric sensor. Maybe this was the case for you.

@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…

@SamuelP I once had a problem installing watch faces, so I reset the settings. Now I’ve decided not to wait for the watch update after all, but to reset the settings instead. Of course, it’s a shame that I have to set everything up again, download maps, and wait for the HRV and ZoneSense ranges to be calculated. I’m curious to see how Suunto will resolve this issue—will the new software version help, or is the problem somewhere else entirely, meaning I’ll have to reset the settings anyway?

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

@Nelson-Diogo I agree. Hopefully they are aware and working on it. It seems wierd selling products that are supposed to be used together and they arent =).

@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

@isazi said in [Race S - 2.50.28] Nap detected during recorded sleep: so report it again if it happens with the new firmware And there I am: Nap accounted to yesterday: [image: 1777121428413-059d473a-6019-4348-bf94-fa20ad027bb8-image.png] And tonights sleep: [image: 1777121473999-6f04e699-6aba-4c5e-bbc2-09d3a18430a6-image.png] Fair enough, I did wakeup because of some noise around 23:55 - as seen by the rising HR. But the sleep tracking didn’t even registered it as wakeup… I think, somebody should look at that code on a higher level as there seems to be something broken in the overall logic…

@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.