Why Bluetooth profiles have to be registered first?

2056951 over 2 years ago

Hello,

I wonder from where comes the requirement to register Bluetooth profiles in order to discover them? And why it's possible to register only 3? Usually nothing like this is required in BT clients, and this limits usability of BT, as for example GoPro apparently requires to receive discover on all profiles in order to be successfully paired (not saying it's ok, but well, that's how it works, and the Garmin API is an unusual limitation here).

Is there any chance this will change in future releases of SDK?

jim_m_58 over 2 years ago

You don't need to register them to see them in a scan or to pair to them. My BleScan app tells you everything it sees and you can try to pair with each one

https://apps.garmin.com/en-US/apps/9bcc8b66-8385-4afb-b93e-f69e01422284

As far as 3 profiles, I asked the guy that implemented this for CIQ when it was introduced, The watch itself has a very limited number, and they need to reserve enough for native devices that use BLE

Here's the presentation on CIQ BLE. It's a minimal implementation.

https://forums.garmin.com/developer/connect-iq/b/news-announcements/posts/adding-bluetooth-connectivity-to-your-connect-iq-projects

There's other things to think about, like the max bytes CIQ can get from the seonsor. It's 20-22.

Three profiles is not an SDK thing. It's a device thing, and I can't see it changing.

2056951 over 2 years ago in reply to jim_m_58

The problem is that I need to discover the available profiles after pairing, not discover devices which advertise something. Otherwise GoPro won't finish pairing and go out of the connection screen. Yes, that's also an issue on GoPro side I believe.

It's interesting that the number of profiles is limited, but the number of characteristics in them it's not I believe (at least officially). And basically it shouldn't be required to register anything in order to just see what other device provides.

jim_m_58 over 2 years ago in reply to 2056951

With CIQ BLE you must define everything you want when you register the profile. There is no discovery. It's a minimal implementation in CIQ. Watch the presentation I posted a link to.

CYBERMAN54 over 2 years ago in reply to jim_m_58

The quality of the linked video looks and sound like from the 80s... no chance to gather the information from it. Is there a source to download the shown slides from?

CYBERMAN54 over 2 years ago in reply to CYBERMAN54

Ok, had to switch quality on youtube to 720p manually. No i can read it. Thanks for the link.

jim_m_58 over 2 years ago in reply to CYBERMAN54

Some of what is on the slides is what you can see in the SDK samples. There are other things where the Profile for the thingy52 helps you understand things.

/ https://nordicsemiconductor.github.io/Nordic-Thingy52-FW/documentation/firmware_architecture.html

You may also pick up some stuff from a blog post I did about using CIQ BLE with a raspberry pi

https://forums.garmin.com/developer/connect-iq/b/news-announcements/posts/would-you-like-some-raspberry-pi-with-your-connect-iq