@2b2bff Danke dir 🤌

I have noticed that using a chest strap, the average heart rate per lap is always lower than the real average that is displayed on Strava. This doesn’t happen using the watch’s optical heart rate sensor. ZoneSense works fine for these activities… I believe that this is a bug that has been present for several years. I reported it many months ago through Suunto App and am disappointed that it still has not been fixed. Another member once mentioned that maybe the cause is that the lowest heart rate per lap is logged as zero in Suunto App.

There is already another thread about that: https://forum.suunto.com/topic/13517/how-comes-this-run-is-classified-in-suunto-app-as-anaerobic I did set up pace zones a couple of months ago, did not update as 9PP didn’t get it till now. Calclulation in App is TSS ( r ) already, don’t know if this changes as soon as you setup pace zones. So I am curious what happens to my pace zones with the update. Did take them form runalyze but I am sure they are just a guess. So far as I found out, you can change TSS for all by selecting a workout and change it there and you will be asked to change it for all future sessions of that workout type.

@Guy-Arbez It gives notification that you are off route when you go off rout for 100m I think

@Edward630 with the last firmware update you should be able to connect multiple sensors of the same kind…

@VoiGAS I also agree that a new activity is warranted, but perhaps also a new feature for the existing hiking activity where you can specify the weight of the load carried. This makes a big difference in power output as you stated. And one rarely (?) hikes without some sort of load being carried. I hike with a weighed vest in late winter and spring each year to prepare for an annual pack carry test (firefighting) each May. In Strava I just note the weight being carried but the estimated power and TSS are all wrong for my body weight.

@sky-runner you don’t want to see my estimation for mtb and what actually happens ‍️

It is also this one enable.

@Squirrel thx for pointing me in this direction. Frustration turned into positive anxiety.

@sky-runner it’s investigated. Known aka. It can also be due to the latch mechanism if you remember what we are talking about.

Same problem here. The belt is easily paired with the watch but when I start activity, it connects only once for 2-3 sec per couple minutes. Then disconnects… and over and over again. The battery change was the first thing I did when noticed unstable connection, but it didn’t help at all. The belt has worked fine with Garmin Fenix 5 and Wahoo Bolt v2 for the last year. I also tested it positively with my wife’s Garmin Forerunner 45s, so definitely the belt is not the issue here.

@VoiGAS grass is always greener

Did anyone find a solution for this? Even the current user manual for the Race S says that it should be possible to change the view: Altitude navigation: bottom: remaining ascent or descent (tap screen to change views)

@Dimitrios-Kanellopoulos This could be something useful.

@sky-runner sorry I’ve missed that thread. I’ve read it now and I can confirm many of the issue you have described! Thanks also for the magnetic declination tip

@Mff73 said in And it crashes mid run: @Kenneth-De-Cocker Besides software problems, you might have an hardware one which is happening in rare situations and causing the crash (es). You should maybe contact support while your watch is still under warranty. I contacted support they also said to return it, just a small problem I have a big trainings weekend coming up and also I participating in a race half September. They said if I send the watch it could take up to 14 business days … so yeah not ideal for the moment so perhaps I’ll send it off after that race. Also gonna take zero risk on race day and use a second watch an old polar but it has no gpx function which is mandatory for the race so yeah better hope is stays alive during that 100km.