Import logs from two dive computers

[laurie_...@yahoo.co.uk]

Greetings,

I currently dive with a Shearwater Perdix AI and a Suunto D4i for backup.

I am in the habit of importing the dive logs for the Perdix first and the Suunto second.

When I choose to download the dive logs for the Perdix both devices are presented in the download window with the Suunto showing as it was the last downloaded from.  If I select the Perdix a Bluetooth window appears and a search for the Bluetooth address for the Perdix is performed even though it has been used before.  It seems that the address for the Perdix is not remembered in the same way as the port the Suunto uses is.

Is this a bug or the only way that Bluetooth devices can be addressed?

Thanks in advance for clarification.

Cheers,

Laurie Miller

[Dirk Hohndel]

You aren't telling us which OS you are doing this on.
Different OSs behave differently. Currently on macOS, for example, we need to re-pair with the Shearwater dive computers every time - at least the macOS documentation tells us that the UUID used for a BLE device is not supposed to be stable between connections, so you shouldn't be able to reuse it. Oddly, I see other software that appears to do so and it appears to work, but I'm not sure whether that's indeed what they are doing or if they are just better at hiding the re-scanning.

Anyway, yes, that's a known "feature".

/D

[Jim E]

I use 2 different Scubapro G2s with bluetooth connections on macOS and the connections are remembered and reused.
I think this was address in https://github.com/Subsurface/subsurface/pull/4120, but maybe I’m missing something here.

best,
Jim

> --
> 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/B1F8CAEF-C267-4025-8706-94668ED0F82E%40hohndel.org.

[Laurie Miller]

Hello Dirk,

My apologies.  I am running Subsurface version 6.0.5504 on a MacBook Pro, Apple M1 Pro chip and macOS Tahoe version 26.2.

Based on what you say, the fact that I also link a Suunto to Subsurface is irrelevant, and caused me to misinterpret the problem.

Thank you for your feedback and in the future I shall be frustrated by the shortcomings of macOS and its Bluetooth implementation and not Subsurface.

Just for information I have been a keen user of Subsurface from the very early days when Linus Torvalds was heavily involved in its development.  I have dives recorded on Subsurface dating back to November 2011 which I have integrated into the revised data format now used.

Thanks for all of your, and all the other volunteer developers, hard work in producing such a great piece of software.

Laurie Miller

--
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/eFB3g_zOOzE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to subsurface-dive...@googlegroups.com.

[Dirk Hohndel]

Hi Laurie

As you may have seen from Jim's response, the answer may be more complex than I remembered.

The thing is, I, too, have a number of Shearwater dive computers, and those I have to re-pair every time I try to download from them on my Mac. It's interesting that apparently that is no longer the case for some other dive computers (I have never owned a G2, so I have no first hand experience with this). But that means that it still COULD be a bug in Subsurface that is only triggered for some of the dive computers? Not sure, honestly.

Thanks for being around for 14+ years. Linus is still lurking and getting involved now and then - but certainly nowhere near the way he was in 2011/2012.

/D

[Laurie Miller]

Hi Dirk,

As a side note to this I also upload my Perdix dive data to Shearwater Cloud on the same laptop and I have observed how the Shearwater Cloud app connects to the Perdix.  It appears to be able to identify that the dive computer is a Shearwater device and automatically link to it without my intervention.

The Subsurface dialogue to download dive data has the dive computer it is to connect to already identified so why can't Subsurface follow a similar procedure to Shearwater Cloud and look for, in this example, the Perdix - it's identified in the Bluetooth device list - and automatically connect to it without the user confirming the Bluetooth divice?

Just a thought?

Cheers

Laurie Miller

--
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/eFB3g_zOOzE/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/09FC4D2D-3BFE-474B-A51F-7725C5DB743B%40hohndel.org

.

[Michael Keller]

Hi Laurie.

On 1/02/26 10:50, 'Laurie Miller' via Subsurface Divelog wrote:

As a side note to this I also upload my Perdix dive data to Shearwater Cloud on the same laptop and I have observed how the Shearwater Cloud app connects to the Perdix.  It appears to be able to identify that the dive computer is a Shearwater device and automatically link to it without my intervention.

The Subsurface dialogue to download dive data has the dive computer it is to connect to already identified so why can't Subsurface follow a similar procedure to Shearwater Cloud and look for, in this example, the Perdix - it's identified in the Bluetooth device list - and automatically connect to it without the user confirming the Bluetooth divice?

The difference here is the order of magnitude - for Shearwater this is relatively simple, all they have to do is recognise one particular family of devices and support their particular bugs and quirks in the Bluetooth implementation. And they get paid for it, by users buying their devices and considering app support a part of the feature set making them desirable.

Subsurface on the other hand is supporting a couple of 100 dive computers from a couple of dozen manufacturers. Even if we wanted, we would not have the manpower to put as much effort into supporting all of the quirks in each the protocol implementations used by all of the devices that we support.

And they are quirky indeed - as Dirk said, for Shearwater this means that you'll have to re-pair way more often than with a normal Bluetooth device, unless you are using the Shearwater app which uses a deliberately modified Bluetooth implementation to circumvent this problem...

Ngā mihi

  Michael Keller