Watch not connecting to wifi for map download

johann.fuehrer

@Wenzudeg that was maybe not the worst idea. I reverted my FW right now and still have the same issue. I now have tried:

2.56.18
2.56.28

Maybe it’s really not the firmware but some connection via WLAN to the Suunto Map download server… then the error message is misleading …

SamppaP

@jjpaz this!
In the Spanish forum it was told that it is a server problem and Suunto is working on it.

Rokelly

@johann.fuehrer Thank you.

What is strange is I’ve been using the same 2.5ghz router for the past 18 months and everything has been okay. II only experienced the issue with the watch not being able to connect to wifi when trying to download a map two days ago. Software 2.50.28 and 2.50.26 may have created this bug ??

Rokelly

@9ppuser Have you tried to downgrade the watch software to see if the problem exists with an older software version?

ninours

@Rokelly yes, but the problem is the same …

johann.fuehrer

@Rokelly it seems that it is a Suunto server issue. no need to downgrade FW (I did - no difference)

Rokelly

@johann.fuehrer How do we open a Suunto Support ticket?

Egika

@Rokelly I have the same.
Have reported it to Suunto

johann.fuehrer

@Rokelly email to support@suunto.com from the email address you are registered at suunto app (not necessarily the same like the forum!)

Wilson75

I was in holidays last week and i was able to download my map without any trouble on my Vertical 1.

dvalob

same issue here on my suunto Race S, using FW2.53.42, but wonder if the issue is not coming from the App update 3.13.1 …

isazi

It is a known issue and already under investigation, it should not require firmware update as far as I can guess.

Thorlap71

@Rokelly Exactly the same for me. Tried many option with no success. I got a replacement watch yesterday and after installing the newest firmware coudn’t download maps to the watch.

9ppuser

Just a quick update: I’ve tried everything—from downgrading to resetting all settings, deleting the app, and reinstalling it—but nothing worked. Unfortunately, all the maps I’d downloaded previously are now gone, too… I hope the Suunto team can find a solution or at least narrow down the problem.

An additional question for the community—is there a way to completely reset the watch? At least in my app, the watch’s memory is shown as not empty, even though the maps are no longer available after the reset. Or is the watch completely back to factory settings and the app is displaying incorrect information?

Thanks and happy training

isazi

@9ppuser as said earlier, the error is known and under investigation, is almost certainly not firmware related, and what you should have done instead of downgrading/resetting/andsoon was to wait that the server side issues are solved…

BrunoH

@isazi Also deleting maps from the watch is stuck. Perhaps these are related problems? It’s been like this for five minutes now.

9ppuser

@isazi Thanks, and yes, you are right, I tried that yesterday, when it wasn’t yet clear that it might be a server issue… I’ll stay patient

isazi

@BrunoH yes, map operations are all dependent on the server

isazi

@9ppuser it should be fixed soon

Johan Mer

I can confirm the same issue on a Suunto Vertical 2 running firmware 2.56.28.

The first offline map downloaded a couple of days ago, no problem. But every attempt today reports “Connection to wireless network failed.” Removing and re-adding the network, rebooting the watch and retrying manually did not help.

I pulled the watch’s system-event logs, they show that the message on the watch is misleading:

Known network: [redacted]
Conn: [redacted] (-49 to -55 dBm)
Https aborted:4
Try resume https (1/10) …
…
Try resume https (10/10)
DL (0%)
DL GET resultCode=500
The watch is therefore successfully associating with the Wi-Fi access point, with a strong signal. The failure occurs afterwards, when starting the HTTPS request.

The same Https aborted:4 error also appears when the watch tries to download ephemeris and weather data. This suggests a general HTTPS/TLS or backend-service problem rather than incorrect Wi-Fi credentials, weak signal, map storage, or a specific map region.

The logs shows the earlier map download completed with HTTP 200 responses on the same network and the same firmware, so the network configuration has previously worked.