@elbee I agree, there should be a simple toggle for morning report without doing anything about sleep tracking.

@duffman19 said in Min. Sleep HR too high?: @raven This has been discussed before and, if I recall, the reason for the discrepancy is that the minimum sleep HR is actually the lowest average HR over a given time period (I think 10 minutes? not sure, though). This can obviously differ from the absolute lowest specific HR reading. Appreciate the context. Given that info, I still feel there’s an issue here. As one can see from what I presented, I think it’s easy to think there’s a conflict between “Min Sleep HR” and the lowest point of the graph. It may be there needs to be a different label, something like “low sleep trend” that indicates the value isn’t the lowest recorded, but whatever it’s meant to represent. As it is, it just looks like the system is “lying” to me when it tells me my low sleep HR was X but it’s always actually X-2, or X-4, etc.

Any cheststrap is accurate. Price or brand doesn’t matter. Main difference is comfort and additional functions. Some can buffer heart rate readings. Nice for swimming (connection to watch doesn’t work under water) or when you are not allowed or it is inconvenient to wear a sport watch (some fighting activities prohibit watches, or free climbers don’t like to wear a watch) Some measure running dynamics. I had one and it’s kinda meh. You look at the numbers once or twice but you’r not going to change anything based on those numbers. So save yourself the money. Basically, choose one that is comfortable to wear.

@Travis-Kinney said in Watch set to Imperial but I'm getting Kilometer splits: gives me is kilometer splits Choose exercise, before start scroll down to Exercise options > Autolap > Distance Choose the distance and unit, either Miles or Kilometers. Edit: Not sure if this applies to Suunto Run though.

@Dimitrios-Kanellopoulos I wanted to mention that I had one crash a a few weeks ago, for which I had uploaded the logs, and the crash was then reported into the system with help of @Egika . In my case it was a vanilla Run sport with nothing special about it and me not doing anything with the watch at the time of the crash. The only special thing was, perhaps, is that I used the Run sport for the first time on the watch, but previously I did a number of activities with a customized Trail Run sport. If that helps, I can send you the details (crash time, etc) again in the chat.

@JebClydeNC I went under bluetooth settings on my phone and clicked ‘forget this device’ and had my phone refind the device and that worked!

I did make some mistakes, but without any impact (wrong signature for getUserInterface, …) The actual real reason I did get the “Maximum SuuntoPlus Apps reached” is because I was using regex in main.js … This is not documented, so warning for all the other devs: do not use regex as this will work with the simulator but not with your watch!

@Egika I mean DND during the sleep schedule. Currently way too bright during the night.

After 10 days, I have the answer provided by Komoot Hello there, Thanks for your message. What you’re seeing is related to how komoot processes imported GPX files, and I’m happy to explain what’s happening and what you can try. When you import a GPX file as a planned route, komoot doesn’t display the track exactly as it is. Instead, it processes it through its routing system. During this step, you’re usually given two options: Stick to original route: keeps the track as it is, though some sections may appear as straight (off-grid) lines if they don’t match known paths. Navigation can be less precise in those parts. Match route to known ways: adjusts the route to follow mapped paths, which can slightly change the original track but often improves navigation guidance. For round trips where the route overlaps itself (for example, going out and back along the same path), this processing can sometimes lead to unexpected results. You might see gaps, shifted endpoints, or the route not finishing exactly where it should. This can also lead to “off route” notifications on your watch. Regarding turn-by-turn instructions, komoot provides guidance slightly before the actual turn to allow time to react. On connected devices like Suunto watches, this can feel more noticeable due to how the data is transferred, so a small offset is expected. Larger differences are often linked to how the route was interpreted during import. Here are a few things you can try: Re-import the GPX file on the komoot website and choose Stick to original route, then review the route carefully before saving If the route is quite long and you’re using Premium, try importing it as a multi-day Tour with the same option After saving, open the route in the planner and check that the endpoint and path look correct before syncing it to your device If the route still doesn’t appear correctly after this, it falls into a known area where GPX imports can behave differently than expected. At the moment, there isn’t a way to fully prevent komoot from processing the file through its routing system. If you have any other questions or need assistance in the future, don’t hesitate to reach out. We’re here to help! Have a great day! komoot Support Team They basically confirm: GAPs and missing parts which can lead to “out of the route” notifications (and wrong Climb Guidance ones). Delays with turn-by-turn indications So those both navigation issues Suunto watches have, are basically caused by Komoot, as I was pretty sure. I’ll continue with the support explaining other things like several turns in quick succession (and considering the delays), but this is a dead end.