Over the years, people reported bugs on their Suunto watches in this forum [1]. This is useful because there are some Suunto employees in this forum, and also some external field testers that have access to the bug reporting system. In this way your issue can be forwarded in an easy way to Suunto.
In this post I wanted to share some tips that will make your bug reporting easier, and that will also make the reporting easier. So, let’s start.
Search the forum
First of all, I would suggest that when you have a problem, you search in this same forum if the issue is already known and reported. If there is an open topic, comment on that and report your experience, especially if there is something different in the way the issue affects you that has not been already discussed.
Report your bug
If the bug that is affecting you has not been reported and/or discussed in the forum, then it is time to open a new topic in this same category, or the specific category for your watch. Indeed instead of commenting on some general, or even unrelated, topic, just open a new one with a good title. A good title could be something like “[WATCH MODEL - FIRMWARE VERSION] Few words description of the bug”, such as “[Vertical - 2.50.28] Deleted sport mode after firmware update”. A good title makes it easier for other users to find your post, and makes the reporting easier too.
Once we have a good title, there are two main use cases that we can address.
Reproducible bug
In case you have a way to (consistently) reproduce your issue, the best way to share the problem is to describe the steps to reproduce it. This way developers can rapidly investigate the issue, without having to spend time trying to reproduce your conditions.
You can, for example, provide a list of steps, such as:
Long press the middle button to access the settings menu
Scroll down to Alarms
Enable the storm alarm
And then specify what is the result, and what would be the expected result instead, such as:
Expected result: the storm alarm is enabled
Actual result: the sunset alarm is enabled, the storm alarm is not enabled
Crash, or non reproducible bug
If your watch crashes, or you cannot find a way to reproduce your issue, or simply the issue does not happen often, you can simply share your experience, describe what were you doing when the issue occurred, and try to provide as many details as possible, such as the S+ apps you were using during that activity, or the watch face name where the complication is misbehaving, and so on. More details is always better than less details when reporting an issue, because someone will need to try and reproduce it.
In case the issue is related to some specific activity, share a link to said activity from the Suunto App, or add the FIT file to the report. In case you are navigating, you can also provide the GPX file you were using.
Moreover, because your issue cannot be easily reproduced, the two following sections will be even more important for you.
Pictures and videos
When words are not enough, provide pictures of your misbehaving watch, or even a video that shows your interaction with the watch and the issue happening.
Logs
After all this, end your report with the logs. To send logs go to the settings in Suunto App, and click on “Send logs to Suunto”, and then stay on that screen until you get a confirmation that logs were sent. You can then end your report with something similar to “Logs DATE AND TIME (TIMEZONE)”, such as “Logs 2026-04-01 19:37 (Finland)”. The email associated with the Suunto App account you are sending the logs from will also be necessary, but don’t put it in your public report. If someone from this forum is going to forward the issue to Suunto, they will ask you in private for the email. You know who such people are in this forum.
Privacy concerns
Like for email, if you do not feel like sharing pictures, videos, activity or navigation files in public, just state that they are available and wait to be contacted by the person forwarding your issue to Suunto.
Conclusions
The goal of my post is to make life easier for everyone involved in this process, these are not official instructions in any way, just some tips taken from the way I have been reporting bugs to Suunto for a few years now. Having some structure, and knowing some of these tips, can make your reporting easier, ease some of the frustration, and also make it easier for the people here that spend some of their time forwarding all the information to Suunto.
Please comment on this post if you have some additions, need clarification, or whatever. I may have forgotten something, even if I spent writing this topic more time that I expected.
[1] This even when the forum was only monitored for Suunto App related bugs and issues, and you were not supposed to discuss watch bugs here!
