@Nandodiver I have the tank POD, i believe the transmitter only works with the older computers like Vyper and the D Range of dive watches. I bought the POD in the beginning of this year and i’m not aware that there is a new version available.

@2b2bff Right, I think in a Race the first 10 minutes are critical. A lot of people get too excited and start too fast. This is where I check the Heartrate very often. Not possible with Zonesense in the first 10 minutes and I am also not sure if it would react fast enough too warn me pushing too hard

@elbee Sent. Thanks.

@Squirrel thank you

@runyx17 said: I’m still experiencing random restarts on my Vertical 2. Yesterday, it happened three times in a single day. Fortunately, not during an activity. I have the latest firmware installed. Question: Should I keep sending the logs, or is the cause of the problem already known? Yes, keep sending logs unit suunto confirms they know the cause. And send an email to support@suunto.com from the same email address as is configured in your suunto profile. That way they connect the logreport with your bugreport in email.

Here we go again. Another completely broken dive log from the Suunto Nautic. The actual dive lasted 1:04:40, with a maximum depth of 12.6 metres and a water temperature of 17°C. The Suunto app even shows these values correctly. But on the Nautic itself, the same dive suddenly shows: 00:00 dive time 0.0 m maximum depth 0.0 m average depth –273°C minimum and maximum temperature a completely useless depth graph missing or obviously corrupted dive data Seriously, Suunto: –273°C? Absolute zero? Was I diving in outer space? This is not a minor cosmetic issue. This is a dive computer that cannot even display its own recorded dive data correctly. The data clearly exists because the app shows it, but the computer itself displays complete nonsense. There have already been numerous posts in this forum about firmware problems, corrupted logs, incorrect calculations and other serious bugs. Yet Suunto continues to remain silent while the support team gives customers the same useless answers and tells them to wait. When will Suunto finally respond to these reports publicly? When will Suunto acknowledge that the Nautic firmware is broken? When will there be an actual fix instead of customers being endlessly passed around by support? This is an expensive dive computer, not an unfinished beta product. Customers should not have to collect screenshots, open support cases and repeatedly prove that the device is malfunctioning. Stop ignoring the reports. Stop hiding behind support tickets. Give Nautic owners a clear statement: Is Suunto aware of these firmware problems? Which bugs have been confirmed? When will corrected firmware be released? [image: 1785620105908-screenshot_20260801_230132_suunto.jpg] [image: 1785620105920-screenshot_20260801_230137_suunto.jpg] [image: 1785620105931-screenshot_20260801_230142_suunto.jpg] [image: 1785620329400-20260801_225902.jpg] [image: 1785620329416-20260801_225917.jpg] [image: 1785620329442-20260801_225926.jpg] [image: 1785620329452-20260801_225931.jpg] [image: 1785620329472-20260801_225936.jpg] [image: 1785620329501-20260801_225942.jpg] [image: 1785620329511-20260801_225948.jpg]

Well, scratches or cracks are permanent, even if the watch is well built. Since it’s a dive watch (close proximity to metal equipment / coral objects), I would rather change protective screen/case than the whole watch in case of an accident Anyways - print is couple of grams of filament and looks better in real life than in close up photo (could be even better if printed on smooth plate). Someone will definately find this useful.

I’ve been having the same problem. It happens while in activities (the activity still saves afterwards but always looses 9.1seconds off the end.) if I have a guide running it restarts about 3 out of 5 times at the end of guide/interval. I’ve tried disabling all suunto + guides, navigation etc it also happens when not inside an activity but while on the normal, day to day watch face also. I’m reverting back to the previous firmware now (April’s version) because I know it didn’t do that then, which is a shame as I was getting used to the map labels.

Its possible to use tank pressure with ascent rate… its one click away [image: 1785601298230-whatsapp-image-2026-08-01-at-17.14.43.jpeg]

@elbee you are funny. Often the car manufacturer will not even give an indication of the needed update We have a couple where we are negotiating for a buy back as they can’t solve a software issue. Life isn’t that hard with Suunto. I do have a wahoo and also have the issue. But I didn’t buy the V2 expecting to be able to broadcast to the bike computer so when I can it will be a bonus.

@Egika the more this is posted the more visible the demand is though