Thanks for the info, Rick! Did you tried to download the dives after you paired the devices manually (using bluetoothctl)?
Currently the QtBluetooth library doesn't have an agent which can be used to set a custom PIN code on pairing step [1]. I don't know when they will implement it. The pairing step must be done only once when you connect a new device to the computer. Therefore we decided to postpone the implementation of a custom agent. The only way to test if the pairing command was triggered from our widget is to open a default agent in the background and see if the PIN code request is raised. One solution is to use the bluetoothctl tool: > agent KeyboardOnly > default-agent Unfortunately I don't know why some devices need a pairing code and others don't need one. As I said before, I assume that they are smarter and they try some basic PIN codes on the authentication step. Claudiu [1] - https://bugreports.qt.io/browse/QTBUG-42740
_______________________________________________ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
