@MarkG I agree, a bit of a shame about Zonesense as I was also hoping to be able to use this. I do have the ‘HR Zones Duration” S+ app running, I find it quite a useful extra page to have especially for the long or threshold sessions

Hey guys it happened to me a while ago and I found an easy solution that doesn’t require stopping current activity. After power meter disconnects, go to activity menu (long press bottom button) then go to battery mode and switch to Tour mode. This disables Bluetooth on watch. Wait for a moment, then switch it back to Performance or any other profile. That will reenable watch Blueatooth again and the watch reconnects with power meter

@Egika So unless I’m reading this wrong, Suunto either know that it measures distance a little short, but it was designed to do so…( I can’t understand why this would be the case!) or it’s not significant enough to address in an update. Personally I think it’s disappointing that it won’t be addressed.

@herlas Yes, Suunto shows both average powers, with and without zeros and in Wahoo settings, you can set if you want average power with zeros or without. I have set this to without zeros and I got SMALLER average power without zeros from Suunto than on Wahoo. Never got higher values from Suunto. On last ride, the difference was 3,6%. It’s clear, that algorithm will differ Suunto vs. Wahoo, but I think, this difference is high and this is the reason, that I’m not sure, if Suunto really doesn’t count auto pauses to the average power… With connecting to device which doesn’t support dual sided wattmeter, Assiomas should send the instantaneous power at a given time and it should be the sum of both pedals. EDIT: On ride with “longer” snack pause, the difference was 5,1%. EDIT2: So no, the difference is not because of auto pause🫤. [image: 1776505793278-screenshot_20260418-114309.png] [image: 1776505803202-screenshot_20260418-114248.png]

@maszop it’s still there in the last public version (6.8.13). Do you have another one?

Coming back to this thread, I now see the restriction “while the Walking activity is active.” First, I don’t think this is an important metric for “live” use. The reality is “step count” is a basic metric that is most useful when you don’t have access to other metrics. For example, a cheap pedometer you attach to your shoe can give you steps but likely won’t have GPS to measure actual distance. In almost all cases, your actual distance is more important than number of steps. However, there is a related metric, cadence that can be relevant. This is “steps per minute,” and in running the advice is to typically around 180 spm which is what I tend to go for, although some prefer slightly different values. Search “ideal running cadence” but here’s a starter link: https://us.suunto.com/blogs/blog/tracking-cadence-heart-rate-and-pace-while-running So I’d look to cadence for “how effective are my current steps” and distance instead of total steps.

@Deniska-Rediska Have you tried a reboot? If so, I would try a hard reset. If that does not work you may have a defective watch provided no tattoos or other issues. I assume you tried both watches on both arms to test. OHR for me with any watch from Garmin or Suunto has not been great until Race2 and V2. With this firmware they are near perfect matches to a belt as I tested wearing the watches, one with belt, one OHR and switching watches as well.

@PhilBee said in new Vertical 2 - auto vs manual laps: yes i guess it must mean that coros record auto 1km laps since the previous auto or manual lap - but what’s wrong with that? to me that makes far more sense Nothing wrong. With that. With Suunto’s approach you can have an automatic lap on each km and an manual lap/interval whatever you wanna call it (in German they are called “Runden”) that are connected with some meaning. Especially if you follow a guide you might have something like 5 Minutes warmup 20 Minutes easy pace 1.6km as fast as you can 10km easy open end - run back home Each of these will become an individual “Runde”. This approach makes sense as well, doesn’t it?

@sky-runner said in Race S: Extremely high battery use rate: I suspect this is a software issue so it is likely the same across all models. Indeed as software issue, but maybe connected with the changed HR sensor algorithm? In that case it is a solution solely for the Race S. But who knows… Interested about your results…

@suzzlo said in Downloading map takes a very long time: @muurain said in Downloading map takes a very long time: Suunto’s cloud service that throttles the downloads but… you can download maps for the mobile phone that are much faster… so… if we think, same server is delivering them… this should not be the problem… Anyway, I can live with it You’re right! I didn’t even realize that, even though I did download mobile maps too And yeah this does seem like an understandable constraint of small smart devices. I too am happy to have the convenience of WiFi downloads, even if they are pretty slow compared to bigger devices. My old Garmin Fenix maps downloaded way faster, but it was via USB cable and a PC. But given the analysis here, the original post does now sound like a WiFi issue or a bug. Maybe try downloading maps on some other place or WiFi…? If the download speed is considerably less than 1GB / hour (or ~2Mbps), it should work faster and there are not many broadbands this slow.

@Brainicus 4th degree not needed…I’m neither moderator or suunto related. Even some users here are close to suunto, it’s still supposed to be a help forum between users, not an official suunto support tool. If I had wanted things to be better I guess I would had created my own brand and done everything well since begining and better than garmin, coros, suunto and all the others, and promise a lifetime update support with clear vision of what tech and developpement will be in the futur… I personnaly use SV1, it’s a 3 years old watch, it has already been improved a lot, and I’m confident we will have updates, but also understand hardware can limit update in the (close?) futur. SV1 works like a charm, can for sure be better but is already a best seller on his kind. For ocean my understanding is that it’s a device that must at first be strong on “diving” features and that it can’t suffer about regression bugs on those features. So I guess improvements and testings can’t be nothing else than 100% sure.

@Egika those running metrics are far superior in something like the head than in very moving one arm. It is explained in that video. That is also a reason with PODs exist in other brands or chest straps with POD features. And pod features could also be improved in a future firmware update. An analogy is running with an HR chest strap. It’s better than the wrist sensor and if you are running with the strap, is because you do want the metrics of the strap. It has no sense to have 2 activities in that scenario. Watch’s metrics should be avoided when running with the Spark paired (in my opinion the contrary is clearly a bug once you have both products in the same workout)

@Hashly-Iian but isn’t this an easy to implement Upgrade which would be very heplful! All data and technical basis is already given. Maybe with the step from beta workout plans to the final version…hope so.

@rwmastel0 this should be fixed with an update

Should be fixed in next release, being currently tested.