"Bluetooth Smart" device missing Toybox::BluetoothLowEnergy

It appears that Fenix 5 device, which features a "Bluetooth Smart" interface, does not make available the BluetoothLowEnergy API. Is this expected?

jim_m_58 over 5 years ago

Yes it's expected. While CIQ 3.1 supports BLE, not all devices with CIQ 3.1 support it.

See this post: https://forums.garmin.com/developer/connect-iq/b/news-announcements/posts/connect-iq-3-1-connects-you-to-the-world

There are newer devices that support it that aren't on the list.

You can also check https://developer.garmin.com/connect-iq/compatible-devices/, and click on the blue circle with the "I" and look for

Generic Bluetooth Low Energy Channel

You'll see it on the f5+ and not the f5 for example

zmullett over 5 years ago in reply to jim_m_58

Thanks jim_m_58. Nice clear answer.

<thinking out aloud> I wonder if that functionality will be providable through a software update, or whether the device simply cannot support it?

jim_m_58 over 5 years ago in reply to zmullett

You'll notice it's older devices that aren't supported, and things like the 645m supports it while the 645 (non music) doesn't. Looks like a HW limitation.

MobileDriveway over 4 years ago

Hi, I hit the same problem on some devices, most notably on a brand new Venu SQ. The Music version of it supports BluetoothLowEnergy API, but standard doesn't! Why would a brand new device not support it?!

Also, there is another problem with SDK. When I select Permission BluetoothLowEnergy in manifest, it disables most Build Targets that supposedly not support the BLE API. However, Fenix 5 and Venu SQ are still available and let you build an app for them. Is it an SDK bug?

Thanks!

jim_m_58 over 4 years ago in reply to MobileDriveway

The Venu SQ is a low end device, so I'm guessing that the non music version just doesn't have the HW to support CIQ BLE.

As far as the permission, I fon't think it disabled targets that don't support BLE. Maybe just targets that don't support CIQ 3.1 at all. I've never noticed it, as I just set targets that I know support BLE.

By using something like Jungles or "has", you can write apps that will use BLE if it's available, but not required.

jim_m_58 over 4 years ago in reply to jim_m_58

Here's my BleScan app in the sim for a non music Venu SQ and a Venu Sq Music showing how an app can make the determination.

For this app, stating that when it's run on a non supported device reduces requests to add a device that's not supported.

MobileDriveway over 4 years ago in reply to jim_m_58

Thanks! I guess it makes more sense now - 3.1 with optional BLE support.

Core functionality of the app I developed (https://apps.garmin.com/en-NL/apps/53d9c500-614e-4e3a-88b6-9f65bc6a144a) depends on BLE, so I don't want it to even be available on devices that don't support BLE. It is a real bummer about Venu SQ - no BLE for a brand new device. The watch talks to a phone over BLE, so I can't imagine any extra hardware that it misses. And SDK doesn't make it easy to select compatible devices, I have to try every single one in a simulator...

By the way, I used your BT app sample - it is the only thing that makes sense on how to use BLE API. Thank you very much for posting it Jim!