Is BluetoothLowEnergy BLE support still being under development?

Please reply also if not because then I can stop waiting for improvements for my app.

Suggestions:

- Do the pairing to all kind of devices in de device software and make them avalable to the connectIQ apps.

- Implement secure writing and reading (for example a Gopro 9)

- Make the garmin device visible for pairing for connections from other devices (initiate connection from the other device) (GATT Server)

0 jpbusman over 3 years ago

With nRF Connect I could connect and writing succesfull using:
Enable LE Secure Connection Pairing
Enable MITM protection
Enable keypress notifications
Perform Bonding

After pairing I get a Bonded, unauthenticated encrypted link

0 jim_m_58 over 3 years ago

Remember that the BLE interface was never meant to be a full interface providing thins like security.

It was meant to allow adding things like new sensors to activities. It minimizes resourced need, which is why it doesn't include things like BLE security, and why profiles have to be pre-defined. nRfConnect on the other hand is a full blown interface.

I really doubt this will change.

0 jpbusman over 3 years ago in reply to jim_m_58

I got it mainly working with the current SDK, the only thing that fails is the secure write.
I would be really nice to use a Garmin for controlling the Gopro.
How do I know if BLE security write will not be implemented?

Is the connection with the VIRB unsecure?

0 jim_m_58 over 3 years ago in reply to jpbusman

The VIRB is ANT, not BLE if I recall.

I think security was mentioned in the BLE presentation at the summit.

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

I know I read/heard it someplace, and it was early on - right when BLE was announced.

0 jpbusman over 3 years ago in reply to jim_m_58

You are right, they made it basic right now, no security levels, one scan mode and no persistant pairing.

I hope they will add some features in a new SDK version because all is on board in the chip they used.

0 jim_m_58 over 3 years ago in reply to jpbusman

You can persist scan results on devices with CIQ 3.2. Save the scan result in Application.Storage, and after that you can skip scanning.

0 jpbusman over 3 years ago in reply to jim_m_58

that works, thanks.

I did read the wifi is always done on the smartphone using the ble from garmin to phone and connect app. (wifi in the device is not available for the CIQ apps?)

Why is this not done for BLE, then the garmin device can do calls to the phone and from there BLE to the paired devices.
nRF Connect could also do the communication if Garmin Connect is 'connected' to nRF Connect on the phone.

0 jim_m_58 over 3 years ago in reply to jpbusman

BLE (or BT in some cases) to the phone, and from there it can use data wither from wifil or a cell service - That's makeWebRequest.

For CIQ BLE, it wouldn't really make sense to have the phone in the middle, as it should work without a phone.

0 jim_m_58 over 3 years ago in reply to jim_m_58

You could write a companion app for the phone that interfaces to your device and then a ciq app that talks to the companion app.