A dedicated divelog app would be better than what we have now. But what we really need is an API or something so LIBDIVECOMPUTER can support the Ocean, Nautic and Nautic S. That way all the divelog apps (subsurface, submersion, divelog, etc.) can import the data. I’m not trusting a manufaterer with my divelog. (due to maintaining software suppport) Open source is the way to go.

@Nandodiver you can easily test this above water as compasses next to eachother will pull the compass off.

@Ldive No, only with the Suunto belt as far as I know. Only works with the same brand (Suunto-Suunto, Polar-Polar, Garmin-Garmin, )

@Migsey wrll, my dive this morning was with the new firmware and I noticed that after a minute the SAC value started high and graduately leveled around 12 / 13. But you have seen the tank pressure, so it simply cannot have anything to do with the POD as it only transmit. The Nautic picks up the signal and applies it’s magic with tank sizes and internal calculations. Did you check the tank size and dive mode like single multi gas in the settings? [image: 1787495145871-screenshot_20260823_125600_suunto.jpg]

I haven’t check if gas display is working below 30Bar But recently couple minutes after end the of the dive, i start to change tank for the second dive and the Suunto gave me brief alert of 3 bar remaining when i took off the regulator.

Keeping both computers on same wrist & in the same side of the dive transmitter seems to fix the dropouts and alerts… this dive even the air consumption was very similar. [image: 1787436006641-captura-de-ecr%C3%A3-2026-08-22-%C3%A0s-22.47.22.png]

@MRHblue doesn’t a new sync restore the deleted dives?

@VoiGAS thanks for your reply. I think that this is a bug… I did a dive today , went into deco and the computer states a mandatory stop at 6 m and, at the end of this stop, a safety stop at the same depth. No mention of safety stop at 3 m at any time …

@hhouter Compass takes up two data fields. Tank pressure definitely cannot be seen along side with compass.

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

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

@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?

I agree with the points above, the app is absolutely useless at this point. There should be a dedicated app for Suunto diving products.

@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”

Hi Same for me … I dive in salt water but I rinse the Nautic in fresh water after each dive

@BlackRabbit I do export from sunto app and import to Subsurface. Just use JSON file export. (still waiting for second POD to arrive from distributor but the one I have is there) [image: 1786209427565-zrzut-ekranu-2026-08-8-o-19.16.44.png]