Hi Dietmar.
I can recommend Shearwater. Their bluetooth is slow and a bit flaky, but they still put the diver first,
Or, if you want a smartwatch that has a decent dive computer built in, go for a Garmin Descent. The drawback is that it requires an USB connection to download dives directly into Subsurface, but on the flip side it does all of the things you'd expect from a smartwatch.
Ngā mihi
Michael Keller
Am 29.11.2025 um 22:22 schrieb Michael Keller <mike...@042.ch>:
--
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/subsurface-divelog/86241db5-71bc-4aeb-ae47-cf95389a1cbd%40042.ch.
Hi Dietmar.
Hi Michael, hi Linus
Thanks for the recommendation, but so far I was quite happy with my Suunto(s). And I have also Pods that work with Suunto and having the same for Shearwater becomes quite expensive.
So, my question remains: what are the plans with the Suunto Nautic: will it be supported and if so, any idea how long will it take?
As Linus stated in his post, from the looks of it the Suunto Nautic is already supported in Subsurface, in a laborious and unreliable way:
And if it does work, we *can* already import the FIT files in the
desktop app, but it's a multi-step process:
(1) sync the dive to the Suunto app - and hope that sync actually
happens, because if it doesn't, you can only see the dive on your dive
computer
(2) on the suunto app, do the "download fit file" thing
(3) move the file from your phone to your laptop (I used google
drive, but any file transfer thing works)
(4) import the FIT file into subsurface
Not sure if this will ever improve - doubt Suunto will have much motivation to open up their watch to app protocol, and reverse engineering is likely going to be a lot more complex than other 'pure' dive computers, as these are smart wartches / sports watches with an added on dive computer mode, rather than devices that are only dive computers.
Ngā mihi
Michael Keller
Hi Michael,
ok, after rcovering from a cold, I was finally able to really use my Suunto Nautic. Looking great so far.
One problem though during import to Subsurface: there is no import of the gas data, no way to see air consumption during the dive. I took a look to the JSON that you can export from the Suunto App and there you can see the data. Not sure if it part oft the .fit file.
It would be a shame if this info cannot be imported to ubsurface – any idea/proposal? How was this managed in the past?
Thanks
Dietmar
--
You received this message because you are subscribed to a topic in the Google Groups "Subsurface Divelog" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/subsurface-divelog/CkeizSm0yXE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to subsurface-dive...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/subsurface-divelog/5a162195-c8df-43a7-8a55-fe73cd29f348%40042.ch.
Hi Dietmar.
ok, after rcovering from a cold, I was finally able to really use my Suunto Nautic. Looking great so far.
Glad to hear you're back to diving. 😃
One problem though during import to Subsurface: there is no import of the gas data, no way to see air consumption during the dive. I took a look to the JSON that you can export from the Suunto App and there you can see the data. Not sure if it part oft the .fit file.
Yeah, I think this is a bit of a systemic issue with the use of FIT files for dive logs. The FIT data format was introduced by Garmin to support logs for fitness activities like running, biking, you name it. As such it has support for a lot of things that are not at all relevant for diving, like lap times, and no native support for diving specific things like tank pressures. When Garmin introduced their 'Descent' dive computer smart watches, they shoehorned support for these things into the FIT format by adding custom extensions.
As it looks now, other manufacturers have jumped onto the bandwagon and started to (ab-)use FIT for dive logs. And from the looks of it, sadly, they have not bothered to implement the same custom extensions that Garmin introduced for dive logs.
So Suunto either does not include tank pressure information in their FIT files, or they do so, but in a different custom format.
It would be a shame if this info cannot be imported to ubsurface – any idea/proposal? How was this managed in the past?
I can see two ways:
- if you supply sample FIT files and accompanying dive logs in a format that can be analysed (can be a profile image showing the gas information), I can have a stab at finding the tank pressure information in it and see if it is possible to add support for it;
- there are other standardised formats that like UDDF that are intended for use for dive log files - does Suunto offer the export in any other format?
Ngā mihi
Michael Keller
Hi all,
please find attached the fit and json from my last dive using the Nautic, including 2 pods for sidemount configuration. The imported fit looks like this in Subsurfacce:
For this dive, I was also using a Garmin including air integration and this looks like this:
I am thinking about creating a python script that converts the json into ssrf format that can be used for import. Do you know if this is already out there or is this something completely new?
Dietmar
--
You received this message because you are subscribed to a topic in the Google Groups "Subsurface Divelog" group.
To unsubscribe from this topic, visit
To unsubscribe from this group and all its topics, send an email to
Hello Dietmar and Alon.
Dietmar: Unfortunately it looks like the attached files did not make it all the way - can you try it again please?
Alon: Thanks for the JSON.
The JSON looks interesting and rich in data. But unfortunately it also looks like Suunto 'invented' a new format instead of leveraging an existing format like UDDF - so it will need a reasonable amount of work to implement a converter / importer for Subsurface.
The mechanism to import proprietary formats into Subsurface that is currently best supported is to convert them into the native Subsurface XML format through an XSLT transformation - see the xslt/ directory in the repository for examples of existing importers / exporters. Adding an importer that is implemented in this way into Subsurface will be straightforward. For a python based importer this might be considerably harder, as it will require to bundle python with Subsurface, or get the Subsurface installer to install python on Windows / macOS / linux...
Ngā mihi
Michael Keller
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/subsurface-divelog/001201dc790f%24ba447070%242ecd5150%24%40gmx.net.
Hi Michael
First of all: Happy New year.
Apologies for the delayed response, I was on a business trip and could not answer earlier. I combined the json and fit in a zip file, hoping that with this, they go through. Please let me know if you need more
Dietmar
To view this discussion visit https://groups.google.com/d/msgid/subsurface-divelog/054f94c9-6445-4aac-858e-508fc0cc8e2d%40042.ch.