@Klaas Can you upload the dives log file (json) to Claude AI and ask Claude the simple question why the algorithm deviation occurred? Can you let us know the response?

@GiPFELKiND said: @johann.fuehrer thank you! I will try this ️ I always clean my Suunto watches like every week with normal soap, old hand brush. Daily just with water only after training. Looks like new

@Egika said: I ever wondered why anyone would like to know their step count. It must have been some good marketing from whoever came up with this… I looked into the history of “step count” and asking some people I know who use that metric, and I think a few things came together to make it popular. First was the “10000 steps” idea made by a Japanese marketing firm years ago which I think people liked as being an easy number to remember, and it was promoted as a universal thing (compare with tracking active calories, where people of different weights like need different targets). https://www.nuhs.edu/debunking-the-10000-step-myth-figuring-out-what-actually-matters/ It also resonates with some people as some of their “natural activity counts” towards it, so walking around the house, etc. gets one somewhat toward the goal then they just need to “finish their steps.” I still see it ideally as more of a “training wheels” metric and think at least tracking active calories is better (so other activities like cycling and yoga “count better” despite not having many steps, as opposed to Polar’s system that assigns “step equivalents” to encourage non-walking activity). And Suunto puts steps and calories on the same Daily Health page so I can see someone new to fitness and Suunto thinking “need steps” eventually learning to use calories instead.

I had written a similar request before. It might even be related to sunrise-sunset settings. For example, “turn off 30 minutes after sunset” or “turn on at sunrise”.

@snow Thanks, but that still requires you to sign up for API access, and based on Suunto’s own disclaimer, you can’t do this unless you’re a company.

@Łukasz-Szmigiel ok @isazi for the follow up just in case

snow said: That said, I’m curious to know if and when features related to running dynamics and the like will be available. The data is already available, and I’ve finally figured out how to retrieve it. Select “Suunto Spark” in SA, choose the only available activity—namely, “Running”—and then start the session. When you’re done, stop the session, and it will be saved. [image: 1787162605447-whatsapp-image-2026-08-19-at-20.01.03.jpeg] The data doesn’t make sense: I was walking while I was testing it…

@leo250461 you can customize the widget order and enable/disable them in the Suunto App. It is easy to have alarm on top of the list

@pg1999 thanks, I forwarded this to Suunto.

I was wrong ! but please Suunto, communicate, communicate !

@jussim said: First of all, did no one Finnish speaking take a look at this? Those translations are laughable and frankly embarrassing for a Finnish company. I guess that’s the new reality in the AI era

@Stanislav-Kuzmin this has been implemented in April already. https://www.suunto.com/en-nl/Support/Software-updates/Release-notes/suunto-race-software-updates/

Since my latest findings, im starting to get a conclusion based on what I’ve observed (some of you might not be on the same opinion) Nautic - No dropouts > No issues (air consumption or alerts) Nautic - With dropouts > issues air consumption & alerts Nautic S - No dropouts (sidemount ) NO ISSUES watch & transmitter are close by Nautic S - with dropouts (backmount ) ISSUES since the watch is opposite side of transmitter [image: 1786960733625-captura-de-ecr%C3%A3-2026-08-17-%C3%A0s-10.28.32.png] [image: 1786960755202-captura-de-ecr%C3%A3-2026-08-17-%C3%A0s-10.36.56.png]

Here the behaviour was the same Nautic - No dropouts no issues (right arm + transmitter side) Nautic S - dropouts and issues calculating consumption (left arm + opposite transmitter) [image: 1786959131833-captura-de-ecr%C3%A3-2026-08-17-%C3%A0s-10.28.32.png]

@Art-C hi when you clear the alarm you should see the bar’s in the tank pressure window again!!

@Art-C I’m not sure for the full 100% but it seems Suunto is wotking on an update that makes the screen views more flexible. It was written in the forum somewhere but Suunto has never been confirmed. So let us hope by putting post to the forum thry pickup and do what the Nautic users want. Indeed the screen is awesome, just like the compass and Battery usage !!!

@David-Jakobsson well, advanced running zones are only for running based sports, not paragliding I will report the original issue for you.

@Ldive It’s a matter of respect for those who bought a Nautic and placed their trust in Suunto. Unfortunately, I shouldn’t have

@hhouter I also lean towards Ocean/Nautic firmware optimizations (pod/watch position is also important). Received back POD from service, still having hard time connecting before dive (previous firmware version worked way better: turn on gas, watch connects and you don’t have to worry again). Now I constantly need to bring back watch close to POD before dive or connection is lost. Underwater looks like transmission is OK, mainly drop outs occur out of water. ps. My suspicion is with this new feature in newest firmware, probably it brought some additional complexity and stability issues: “Possibility to link two tank pods to same gas If two tank pods are linked to same gas, the tank pressure field will show two tank pressures during dive”

Follow-up: I ran the test, and I can answer my own question 5. The eviction path does not release the app’s JS context, and the shared heap is exhausted inside a single four-minute exercise. Method: fresh reboot, one exercise, three apps enabled, triggering the eviction repeatedly by switching screens and opening/closing the map. After each eviction I re-enabled my app from the SuuntoPlus menu without ending the exercise. Four evictions in four minutes # time how long my app survived after being enabled 1 14:48:40 118 s 2 14:49:07 14 s 3 14:49:57 33 s 4 14:50:27 15 s 118 s the first time, 21 s on average afterwards — an 87% collapse. The heap is at 99.5% Two lines from the firmware itself, 16 seconds before the first eviction: 14:48:24 : WRN UI_FRAMEWORK : JsTotMem 129980/133120 (97.6%) 14:48:29 : WRN UI_FRAMEWORK : JsTotMem 132412/133120 (99.5%) This is the only figure the system has ever given me about its own limits, and it is not documented anywhere. An earlier report on this forum (topic 15490) describes the watch freezing at essentially this same level. Nothing is ever released None of the four evictions is followed by JS discard. The first and only one in the whole session appears at 14:50:35, when I stop the exercise. So every Disable → Load script → Enable cycle instantiates the module scope again while the previous one is still held. That also reframes the “three apps” case. It is not that a third app is too big — my own footprint is 12.4 KB, resident main.js plus the single mounted template. It is that three apps cycling through evictions exhaust a shared pool that nothing empties until the exercise ends. One caveat on reading this The intervals between evictions look almost constant (27, 50, 30 s). That number measures how fast I re-enabled the app by hand, not the watch. Survival time is the honest metric. And the last three survival times being similar does not mean it stabilised — it means the pool was already full before I started measuring. At 99.5%, any re-enable trips the release callback almost immediately. So, concretely Is Zapp X:Disable without a following JS discard expected to leak the module scope? If yes, a firmware eviction is not a recoverable event — it permanently consumes shared heap, and the watch degrades within a single session. Is there a supported way to make an app release its context on eviction, or to be re-enabled cleanly within the same exercise? What is the intended budget per app against the 133 120 B shared heap when three apps are enabled, which is the configuration FW 2.50.26 added? I have the full logs and the built blob available if that helps, and I am happy to run any test you would like measured.