@Sportsfreund I understand what you are saying, but there is a difference between seeking advice or help vs complaining. But I agree which what you are saying partly. I would not agree that “Nobody goes to a forum if everything is great.” I came here and I think others have as well to lend support and celebrate Suunto.

@TED77 But generally, the number itself doesn’t matter, nor do these types of comparisons. If the trend or graph is more or less the same in both tools, the difference in numerical values ​​can simply be ignored.

@ChrisA And how did you find out? Have you tried it yourself or you just trust Olaf?

For the record, I think the Race 2 and Vertical 2 faces are very good, I’d like to see more development in terms of options for those two. For example being able to configure the Race 2 graph to show us sleep over time, or HRV, or CTL, or cycle through all three if you tap on it. The same with the Vertical 2, make the bottom complication configurable too! Oh and larger complication fonts

@MdzOtt Thanks for the tip. Is the first thing I do when something doesn’t work But it didn’t help

@gkaempfer So, your watch seems fine? You’ve inspired me to create a model. What is your reason you drain it till 7%? I assume it’s not good for the battery life (long term) to drain it that low, isn’t it? My charging strategy is this: drain it till 20%, do a run and charge it when I do have the time. I’m on my second non-obsessive battery cycle. I’m on day 12 and have about 5,75 hours of GPS-activity (running). My battery right now: 30%, prediction is 31,78%. Model: daily-drain: 0,21 %/h Model: training-drain: 1,54 %/h Things that increased the battery drain: Use of flashlight a few times a day Use of maps around 50% of the time running. I’ve used around one day (18 h) AOD with an analog watch face Fiddeling around with Maps and compass. Also use of thermometer in a swimming pool and measuring depths of the swimming pool Things that decreased battery drain: Turned on the Flight Mode (10 h) because I thought the drain was too high. I didn’t use the HR-belt. I don’t like resetting my watch all the time. I’ll wait for the next update. So, I think I’m fine as well regarding the specifications! And I do lose my charging cable all the time. I don’t know where it is right now, haha

@Stavrogin it already happened once

@VoiGAS I assume that the issue is something like that. However, under the assumption that GPS is accurate, especially multi band which I used and is supposed to be very accurate, I would think that step count could probably be corrected by a better algorithm (assuming occasional measurements would miss a step, measure double air time or some other artifact).

@sartoric @Brad_Olwin thank you guys, I’ll go for support. I’ll make you know the end of the story, just in case it could be useful to someone else.

@ze230877 Let’s hope… Basically, I am happy with the watch.

@Ecki-D. I think your guess is correct, it probably won’t work technically. It’s kind of a shame because you have to consider navigation or live trekking… Thanks for your feedback

Tested today, thanks for the advice to both of you, it works well on routes without crossings. Great.

I would like times for high and low water plus heights based on the nearest reference port and a tide graph. For example I know I can navigate a particular channel when the depth of water at Mallaig is 3.3m or more. The channel isn’t at Mallaig but that’s the reference port I use for this location and the depth at a particular time is more useful than the actual time of HW (or the time of HW locally because a neap tide may not reach the required height, even at HW) If I have times and depths of high and low water I can work it out manually from that but a graph makes life easier. I’m a sea kayaker as well as a runner and this information would be helpful. However in a situation without phone coverage such as on a multi day trip I’m not sure if the software could load or store and display advance predictions and if there was coverage it might be more efficient to view it from actual tide tables or on a smart phone. Or simply write it down in advance on a bit of paper! There’s a lot more to it than just high and low water times but they are a starting point from which other calculations can be made using other data (which I’m pretty sure couldn’t be on a watch) and are useful locally for planning launch and recovery.

@Brad_Olwin good news - looking forward for the next release

Since the last update, with the 9PP I’ve had some lap go uncounted up to 4 out of 10 times, and recently with the Race S it’s happened 1 out of 4 times. It’s not terrible behavior, but it’s certainly not on the side of excellence. Also, the timer for automatic intervals isn’t working.

@Brainicus ok I will test but am not convinced distance is from Stryd. I always get more distance with Suunto than any Garmin users. With Stryd previously witn auto calibration off distance was the same. I ran a 5km with three friends recently (post bluetooth change) and got 100m more using Stryd and Suunto. The next day we ran and I accidentally had gps off on my watch so 100% Stryd and our distances were identical. But I will test like you suggest with both on a straight route. I do not know why Suunto gives more distance than Garmin.

@GiPFELKiND said in Bug: power meter loses connection in activity: @Olaf-Gottschalk same Problem with Bluetooth heart rate Sensor… Suddenly breaks and lost for the whole Session I am convinced it is a bug in Suunto’s BT algorithm combined with how some sensors enter a sleep mode or something like this. For my HR sensor (Wahoo) it never had an issue like my Wahoo SpeedPlay power pedals have. But yes, I can see the exact same problem happening with any kind of sensor. Suunto’s BT software is kind of unforgiving once it loses connection. Will never return, never recover, and does not give the user a feedback and option to reconnect in the session. That is the problem. Plus: it was NOT an issue prior to Suunto changing the complete BT stack!

Update from Stryd Support. They are working on a fix, expecting in soon.