@Garmin SDK-Development: Next steps for Blue-Tooth function BLE, what is planned?
For my sports, mountain biking, mountaineering and running, I have had several sports watches from various manufacturers
over the years Time used.
Now I like to use Garmin devices. They work relatively reliably, they have a large one Functionality.
In addition, Garmin's clever idea gives the user personal functionality via CIQ / SDK enable.
That is the best difference to the other manufacturers on the market today.
Now I use the opportunity to expand the functionality of my Forerunner, for example.
The project is add current blood pressure measurements to the daily data.
Good blood pressure monitors have a blue tooth Functionality.
The GATT UUID (0x1810) for the generally accessible service and the characteristic is well known.
A watch app with BLE functionality can be programmed quickly.
And now the problems begin:
BLE is implemented very poorly in the SDK.
Especially the security only knows MODE 1 and LEVEL 1.
The blood pressure devices use MINIMAL MODE 1 and LEVEL 2!
In addition, the transmission is often triggered by INDICATE.
The security level LEVEL2 and the INDICATE function are missing in the current scope of functions of the BLE-API!
I saw the video of the 2019 developer conference. There is the "currently" security only in M1 / L1
is working. That was the case in 2019. And now tree years later?
My question and request to GARMIN is:
will there be an extension of the BLE-API in security to M1 / L2 and an INDICATE function? And when?
I think the hardware for this is available in the Garmin devices.
The message in the forum that sensors do not know any security is no longer true today.
For example the devices from OMRON, some E-BIKE etc. do need M1 / L2.
If someone is planning a similar project, please contact Garmin for support!
Thx
GruGru
Example-View: 
