Halcyon Symbios Handset log imports.

[Raul]

Seems that the Import option for a computer already shows Halcyon Symbios handset, but I have not been successful on connecting to the device, is there a special trick to do so. Also tried to import the CSV that the computer generates but seems akward and hard to decipher for Subsurface.  Has anyone tried it already ?

[Jef Driesen]

It should work out of the box. Which version of subsurface are you using? Mobile
or desktop? Which operating system?

For the desktop version you need to select the "Choose bluetooth download mode"
and select the correct bluetooth device. You probably need to use "Show all BT
devices" too. And on Windows you need to pair the bluetooth device first using
the Windows control panel.

Jef

[Raul]

I use it mostly on LINUX I have the latest since it updates frequently, but can also try it on WINDOWS. It does show on all the BT devices too, but maybe on Linux need to pair it first to the desktop then run subsurface

[Raul]

Well wierd, can’t seem to make it work , even following your instructions for some reason it doesnt recoginize or download the logs, even  if subsurface connects to the handset, in another note that might be related, seems there is something weird with the current FIRMWARE of the HANDSET that I can’t seem to be able top upgrade maybe that has something to do with the BT connections. Will see. thanks 

[Jef Driesen]

On 2025-08-17 23:49, Raul wrote:
> Well wierd, can't seem to make it work , even following your
> instructions for some reason it doesnt recoginize or download the logs,
> even if subsurface connects to the handset, in another note that might
> be related, seems there is something weird with the current FIRMWARE of
> the HANDSET that I can't seem to be able top upgrade maybe that has
> something to do with the BT connections. Will see. thanks

On Linux you don't need to pair first.

If subsurface is able to connect, enable the "Save libdivecomputer
logfile" checkbox to generate a debug log. If subsurface can't connect,
you need to run it from the command-line and redirect the output to a
file:

subsurface -v -v >debug.log 2>&1

With those debug logs we might be able to tell what goes wrong.

Jef

[Raul Lozano]

Here is the logs, the first one did not produce anything so that means
it did not connect, however I do see on the halcyon handset that the BLE
turns on when subsurface polls it. The Debug log has more details such as :


QLowEnergyControllerPrivateBluezDBus::connectToDevice()
QLowEnergyControllerPrivate setting state to
QLowEnergyController::ConnectingState
###### "org.bluez.Device1" QMap(("Connected", QVariant(bool, true)))
###### "org.bluez.Device1" QMap(("ServicesResolved", QVariant(bool,
true))("UUIDs", QVariant(QStringList,
("00000001-8c3b-4f2c-a59e-8c08224f3253",
"00001800-0000-1000-8000-00805f9b34fb",
"00001801-0000-1000-8000-00805f9b34fb",
"0000180a-0000-1000-8000-00805f9b34fb",
"18424398-7cbc-11e9-8f9e-2a86e4087070"))))
QLowEnergyControllerPrivate setting state to
QLowEnergyController::ConnectedState
QLowEnergyControllerPrivate setting state to
QLowEnergyController::DiscoveringState
QLowEnergyControllerPrivate setting state to
QLowEnergyController::DiscoveredState
INFO:    .. service state changed to 0
INFO: Found service {00000001-8c3b-4f2c-a59e-8c08224f3253} Unknown Service
INFO:    c: {00000101-8c3b-4f2c-a59e-8c08224f3253}
INFO:         d: {00002902-0000-1000-8000-00805f9b34fb}
INFO:         d: {00002901-0000-1000-8000-00805f9b34fb}
INFO:    c: {00000201-8c3b-4f2c-a59e-8c08224f3253}
INFO:         d: {00002902-0000-1000-8000-00805f9b34fb}
INFO:         d: {00002901-0000-1000-8000-00805f9b34fb}
INFO: failed to find suitable service
ERROR: Failed to find suitable BLE GATT service
INFO: Failed to find suitable service on 'CC:8F:FA:DB:4C:D9'
ERROR: Failed to find suitable service on 'CC:8F:FA:DB:4C:D9'
INFO: Deleting BLE object
INFO: INFO: dev_info: Import error: Input/output error
INFO: Finishing download thread: Unable to open LE:CC:8F:FA:DB:4C:D9
Halcyon (Symbios Handset)
INFO: Profile calculation for dive 149 took 9 ms -- calculated ceiling
preference is 0
INFO: Profile calculation for dive 149 took 7 ms -- calculated ceiling
preference is 0
INFO: Profile calculation for dive 149 took 8 ms -- calculated ceiling
preference is 0
INFO: Profile calculation for dive 149 took 8 ms -- calculated ceiling
preference is 0
INFO: Profile calculation for dive 149 took 7 ms -- calculated ceiling
preference is 0
INFO: Profile calculation for dive 149 took 8 ms -- calculated ceiling
preference is 0
INFO: Profile calculation for dive 149 took 8 ms -- calculated ceiling
preference is 0
Wayland does not support QWindow::requestActivate()
Wayland does not support QWindow::requestActivate()
INFO: Profile calculation for dive 149 took 11 ms -- calculated ceiling
preference is 0
Wayland does not support QWindow::requestActivate()
Wayland does not support QWindow::requestActivate()
###### "org.bluez.Device1" QMap(("Modalias", QVariant(QString,
"bluetooth:v00D2p0580d0100")))
###### "org.bluez.Device1" QMap(("Connected", QVariant(bool,
false))("ServicesResolved", QVariant(bool, false)))
QLowEnergyControllerPrivate setting state to
QLowEnergyController::UnconnectedState
Destroying QtBluezDiscoveryManager


Attached the files.

[Raul]

So I have another device running UBUNTU, this an old macbook air, but runs ubuntu and I have subsurface there too, well there I was able to pair with the HALCYON HANDSET and download the dives, the only difference is that on that imac as soon as it connect to the halcyon computer, it asked me for the BT pair code that the halcyon computer has, and on my main UBUNTU machine is not asking me for anything, so apparently is not connecting. 

[Jef Driesen]

On 19/08/2025 22:32, Raul Lozano wrote:
> INFO: Found service {00000001-8c3b-4f2c-a59e-8c08224f3253} Unknown Service
> INFO:    c: {00000101-8c3b-4f2c-a59e-8c08224f3253}
> INFO:         d: {00002902-0000-1000-8000-00805f9b34fb}
> INFO:         d: {00002901-0000-1000-8000-00805f9b34fb}
> INFO:    c: {00000201-8c3b-4f2c-a59e-8c08224f3253}
> INFO:         d: {00002902-0000-1000-8000-00805f9b34fb}
> INFO:         d: {00002901-0000-1000-8000-00805f9b34fb}
> INFO: failed to find suitable service
> ERROR: Failed to find suitable BLE GATT service
> INFO: Failed to find suitable service on 'CC:8F:FA:DB:4C:D9'
> ERROR: Failed to find suitable service on 'CC:8F:FA:DB:4C:D9'
> INFO: Deleting BLE object
> INFO: INFO: dev_info: Import error: Input/output error
> INFO: Finishing download thread: Unable to open LE:CC:8F:FA:DB:4C:D9
> Halcyon (Symbios Handset)

For some reason, subsurface fails to find the correct service, but it's right
there. At first I thought you were running an older build, that is missing the
commit to detect the Halcyon service and characteristics:

https://github.com/subsurface/subsurface/commit/b46b3f5a7912658f62a8f2ab72892cbab3e640b4

But you appear to be running a recent version that should include this commit:

> Subsurface v6.0.5424-CICD-release

So I'm not sure why this fails for you.

> built with libdivecomputer v0.9.0-devel-Subsurface-NG (4e4f1f7ac59c8827d2cdd58cbb2ec78f92d038b2)

Your libdivecomputer version is missing some of the latest Halcyon improvements,
but those are only relevant *after* the connection is established.

Jef

[Raul]

Yes it is weird, well the good thing, I have another UBUNTU machine as I said on a MACBOOK AIR, that one is working it connects and downloads the logs, as I mentioned before, on the machine that is failing, is not even asking for the BTCODE Handset has, so I do not think is pairing correctly.