Re: Connecting Peregrine to SS

[JB2Cool]

Subsurface (Please don't use the double-S abbreviation) can't see the Peregrine at all or it can see it but somehow can't download from it?

Jason

On Tue, 6 Feb 2024 at 14:43, 'Ed Jacobs' via Subsurface Divelog <subsurfac...@googlegroups.com> wrote:

Hi,

I can't successfully sync my Peregrine to SS  on either my laptop (SS v6.0.5091; Apple M1 running 14.2.1) or my Galaxy S9+ (Android 10; SS 6.0.5091).

In general settings, credentials are verified, am logged on to cloud.

SS doesn't find Peregrine.  Advice?

TIA

--
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 on the web visit https://groups.google.com/d/msgid/subsurface-divelog/6e6a026d-9592-4f22-a176-9fad78632e7bn%40googlegroups.com.

[Gachoud Philippe]

got a Peregrine, the only way I get it to be done is by the android app

1. start bluetooth on your android device (not sure for iphone)
2. start bluetooth sync connection on your peregrine
3. open subsurface app and go to sync
4. works, accept the newly created dives
5. maually sync to cloud
6. open from cloud in subsurface desktop
   

[Ed Jacobs]

Subsurface doesn't seem to see the Peregrine--that is, no connection is made to the Peregrine.  

Bluetooth on on Android device, and have started the bluetooth sync on the Peregrine.  the 3' connection time elapses with no connection made.

[Martin Swanston]

Are you turning on Bluetooth in the phone settings and trying to connect there? If so, with Bluetooth switched on on the phone, try opening the Subsurface app and connecting by tapping the middle ‘button’ at the bottom of the screen and either selecting the correct dive computer.

HTH

On 6 Feb 2024, at 16:25, 'Ed Jacobs' via Subsurface Divelog <subsurfac...@googlegroups.com> wrote:

Subsurface doesn't seem to see the Peregrine--that is, no connection is made to the Peregrine.  

To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/5b18c699-a6e4-45d5-b52f-f49e4e504cb4n%40googlegroups.com.

[Martin Swanston]

So when you tap the connection button in subsurface, do you see your computer litsted? If not, go back to settings (still in Subsurface) then advanced and switch on the option ‘Temporarily show all Bluetooth devices…’ and try again. You should only be connecting from within subsurface. 

On 6 Feb 2024, at 16:45, 'Ed Jacobs' via Subsurface Divelog <subsurfac...@googlegroups.com> wrote:

Yes, phone's BT is on.  

BT on Peregrine is "Wait PC" awaiting Subsurface's connection via BT.

I've tried it with "force downloading" checked and unchecked.

To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/45f8f069-fc6d-49db-ae84-6437367afe6fn%40googlegroups.com.

<Screenshot20240206-114130Subsurface-mobile.jpg>

[Ed Jacobs]

Yes, the Peregrine is listed (see attached screenshot).

[Dirk Hohndel]

"S1" is a very unusual device name for a Peregrine. Are you sure you are connecting to the correct Bluetooth device?

[Martin Swanston]

just to confirm - when you tap the ‘Shearwater - Peregrine’ under ‘previously used dive computers’, does that provide the same result?

On 6 Feb 2024, at 16:52, Martin Swanston <martin....@gmail.com> wrote:



[Ed Jacobs]

Yes, I click 'Shearwater - Peregrine' then retry; same result.  (thanks for all of your time in troubleshooting this--much appreciated!)

[Ed Jacobs]

I gather you're referring to the "Connection", which begins S1.

That is the only choice that appears in the connection's drop-down menu.

Thank you.

[Dirk Hohndel]

But that is almost certainly not your Peregrine. That is some other device. Your Peregrine should identify itself as "Peregrine"

So my guess is that your phone isn't actually connecting to your dive computer. One odd thing that Shearwater dive computers do is that if they think they are connected to a computer, they stop advertising. So do you have Shearwater Cloud running on a different device / computer which is talking to the Peregrine?

/D

--
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 on the web visit https://groups.google.com/d/msgid/subsurface-divelog/0af90573-5edb-4ae0-9001-98a498d8169bn%40googlegroups.com.

[Dirk Hohndel]

Let's please keep this on the forum so others can find the conversation later.

You are mixing two things. The second line "Dive Computer:" shows what you are telling Subsurface-mobile to expect the device it talks to to be.

The third line "Connection:" is where you tell Subsurface-mobile which BLE device to talk to.

Unless THAT line shows a connection to a Peregrine (and that usually identifies itself as "Peregrine xx:xx:xx:xx:xx:xx"), you aren't talking to your dive computer.

In my experience (and I have a lot of Shearwater dive computers, thanks to their support for this project) the first connection is the hardest. Turning the Peregrine off and back on again, starting a tool like nRF Connect on your phone to scan for BLE devices, and then turning the Peregrine into Bluetooth mode often helps to create this initial connection. Once that is established, the rest will work.

But that's the part that you are currently not achieving.

/D

On Feb 6, 2024, at 09:53, Ed Jacobs wrote:

As you see on the attached, it is TRYING to connect to the Peregrine.

And, as you say, the phone isn't connect to the Peregrine--that's the nature of my inquiry here.

I do not have any other device beyond the Peregrine and my Samsung phone (running Android) in the area.

Thanks

<Screenshot20240206-114130Subsurface-mobile.jpg>

[Ed Jacobs]

ok, so I'm likely only understanding _some_ of what you're saying.  

I have restarted the Peregrine, and when I tell my phone to scan for BT devices, then Peregrine appears just fine.  When I choose it, though, I get "An app is needed to use this device."

When I go back to Subsurface, click the Shearwater-Peregrine under previously used devices, then retry...nothing connects.

So I'm NOT doing something you are suggesting, but I'm not sure what that is, to be honest.  

Thanks for your patience,

Dirk Hohndel

unread,

1:02 PM (6 minutes ago) 

to Subsurface User Forum

Let's please keep this on the forum so others can find the conversation later.

You are mixing two things. The second line "Dive Computer:" shows what you are telling Subsurface-mobile to expect the device it talks to to be.

The third line "Connection:" is where you tell Subsurface-mobile which BLE device to talk to.

Unless THAT line shows a connection to a Peregrine (and that usually identifies itself as "Peregrine xx:xx:xx:xx:xx:xx"), you aren't talking to your dive computer.

In my experience (and I have a lot of Shearwater dive computers, thanks to their support for this project) the first connection is the hardest. Turning the Peregrine off and back on again, starting a tool like nRF Connect on your phone to scan for BLE devices, and then turning the Peregrine into Bluetooth mode often helps to create this initial connection. Once that is established, the rest will work.

[Dirk Hohndel]

You're close.

When you go back to Subsurface, click on the connection drop-down. Do this right after you get the "an app is needed to use this device" message in the Bluetooth center.

So the sequence should be

- enter Bluetooth mode on the Peregrine

- look for the Peregrine by having your phone scan for BT (actually BLE) devices

- once the phone shows the Peregrine in that list, open Subsurface, go to download, do NOT pick the previously used devices but manually select the Peregrine from the drop down in the connection entry.

- once that has happened, you should be fine.

If the Peregrine is still not offered in that connection drop down (and I'm serious - the order and sequence of steps above matters), then please send a support request from within the app (it's in the menu under Help) right then, e.g. after you tapped on the connection drop down. That will send me the log files. And right after you do that, go back to the Bluetooth screen of your phone and send me a screenshot that shows your Peregrine being seen by the phone (that will give me the BLE address to look for in the Subsurface-mobile logs.

Thanks

/D

To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/e3df8011-a01c-4bcd-99ba-f516052196cfn%40googlegroups.com.

[Ed Jacobs]

I've just now followed your instructions--and sent the log files and screenshot, as the connection still isn't happening.

Thanks,

[Dirk Hohndel]

> On Feb 6, 2024, at 13:25, 'Ed Jacobs' wrote:
>
> I've just now followed your instructions--and sent the log files and screenshot, as the connection still isn't happening

My apologies - due to a stupid mistake on my part that email got lost (I had to make some changes to the Subsurface email backend).
Would you please resend it?

Thanks

/D

[Ed Jacobs]

sent again, hopefully it provides the data you think will help!

[Dirk Hohndel]

On Feb 7, 2024, at 06:41, Ed Jacobs  wrote:

sent again, hopefully it provides the data you think will help!

Yes, I think it did tell me more than I knew before.

So let's try this the hard way (sorry).

Please look in the Google Play store for an app called nRF Connect. It's made by Nordic Semiconductor ASA - the manufacturer of many of the BLE chips in use in BLE enabled devices.

Start the app, go through the quick intro, and tap on Scan in the top right corner. Android will ask you to give the app location permission (such as weird way of doing things) - please allow it because without it the app can't scan for BLE devices.

When you are done giving permissions, in my case the app forgot that I was going to scan for BLE devices, so I had to tap on that button again - it will show "STOP SCANNING" in the same place when it is working. The list on the screen should populate with the BLE devices that it can find. Put your Peregrine into Bluetooth mode and wait for it to show up (you may have to tap "SCAN" one more time if that takes to long and the app stopped scanning already). Now tap on the CONNECT button next to the Peregrine.

That should get you to a screen that tells you all kind of odd technical things - don't mind them, switch to Subsurface-mobile, go to the Download screen and check if you can see the Peregrine now.

I reproduced this process here after making my phone and my Subsurface-mobile forget that it had talked to my Peregrine before, and it allowed Subsurface-mobile to re-connect with it.

I know this is a bit awkward and weird, but it should work.

/D

[Dirk Hohndel]

Oh. Here's a thought. Is it possible that you have not given Subsurface-mobile "location access" permission when it asked?

Because that would create exactly the situation that you describe. I can't believe I didn't think to ask about that earlier.

/D

[Ed Jacobs]

Using nRF to connect, this DID work--using a connection Subsurface id'd as Peregrine (rather than Shearwater).  It is downloading dives now, albeit painfully slowly.

So I gather this is the process I should continue to use, yes?

Thanks so much for hanging in there with me!

[Ed Jacobs]

just to reply to this as well...Subsurface-mobile doesn't ask for location access when opened.

[Dirk Hohndel]

On Feb 7, 2024, at 12:02, Ed Jacobs  wrote:

Using nRF to connect, this DID work--using a connection Subsurface id'd as Peregrine (rather than Shearwater).  It is downloading dives now, albeit painfully slowly.

So I gather this is the process I should continue to use, yes?

Thanks so much for hanging in there with me!

Of course. I'm glad we got it working.

And yes. PAINFULLY SLOW is unfortunately a very common phenomenon there...

> On Feb 7, 2024, at 12:02, Ed Jacobs  wrote:

> 

> just to reply to this as well...Subsurface-mobile doesn't ask for location access when opened.

Yeah, once you say no, it won't ask again.

If you go to Android Settings, Apps, find Subsurface-mobile and tap on it, it should tell you its permissions.

It needs both "Location" and "Nearby devices" in order to find the Peregrine without the help from nRF Connect.

/D

[Ed Jacobs]

Greetings,  A problem once solved, now re-emerging.

Running Subsurface mobile 6.0.5264 on my Galaxy S9+ running Android version 10

Per Dirk, using nRF to connect to my Peregrine (successfully), then starting Subsurface.  But Subsurface doesn't find the Peregrine.

Process was never very consistent, but since last successful connection about a month ago, no luck in about 10 tries.

Thanks for any assistance,

Eddie

[Dirk Hohndel]

<<side note... as a person of German descent I absolutely despise the abbreviation for the German Nazi Schutzstaffel being used for Subsurface... and current politics all over the world has made my revulsion towards that even stronger -- if the word Subsurface really has too many letters and is too hard to type, use SSRF>>

> On Sep 24, 2024, at 08:41, 'Ed Jacobs' wrote:
>
> Greetings, A problem once solved, now re-emerging.
> Running Subsurface mobile 6.0.5264 on my Galaxy S9+ running Android version 10
>
> Per Dirk, using nRF to connect to my Peregrine (successfully), then starting Subsurface. But Subsurface doesn't find the Peregrine.
> Process was never very consistent, but since last successful connection about a month ago, no luck in about 10 tries.

Generally once you connected using nRFconnect once, you shouldn't be needing it again on an Android device unless some other device connected to the Shearwater dive computer in the meantime. E.g., I download from my Perdix 2 all the time and only need to redo this connection if I tested said download from a different device in the meantime.

That aside, the way this should work is:

- exit Subsurface-mobile
- on the Peregrine, start Bluetooth mode (the countdown will start)
- start nRFconnect
-- tap on scan
-- once the Peregrine shows up, connect to it and bond with it
- start Subsurface-mobile
-- tap on Download from dive computer, select Shearwater and Peregrine - the connection should be auto-populated

if that last step fails, check that (a) the Peregrine still shows the countdown and (b) that nRFconnect still shows the device as bonded.

I have never seen this fail if those two conditions are true. If it does, then create a support request from within the app right then (that way the logs should contain the most relevant info) and send that to me (the in-app-support address is just an alias for me)

/D

[Gmail im Auftrag von Martin Gröger]

and - at last - don't forget to turn on the location service at your android device.
my peregrine refuses any connection without the location service

keep on howling

grey

--
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 on the web visit https://groups.google.com/d/msgid/subsurface-divelog/1EF8F826-397B-43FA-9AC2-C189B9B8A794%40hohndel.org.

[Dirk Hohndel]

Oh yes, how could I forget this brilliantly logical Android "feature". In order to be able to talk to BLE devices, you MUST have location permissions.

And to make this better, if you don't use Subsurface-mobile for a while, Android helpfully removes that permission from the app... 🤦🏻‍♂️

/D

[Chris DMV]

Dirk Hohndel wrote:

Is it possible that you have not given Subsurface-mobile "location access" permission when it asked?

 

I was having similar issues with my Mac not detecting any dive computers over Bluetooth, and wanted to share that this comment was the solution. I don't recall if it had prompted me for access whenever I first installed Subsurface, but I did have to go into System Settings -> Privacy & Security, and manually toggle Bluetooth access to allow it to see my computers today. (I had previously been using USB cables to sync.)