This repo holds a very basic PoC of the Web BLE APIs.
Since the APIs work only in trusted environments you need to create your own certificates before running the example code.
Create TSL certificates with:
openssl req -nodes -new -x509 -keyout server.key -out server.cert
then allow chrome to accept self-signed certificates from localhost with:
chrome://flags/#allow-insecure-localhost
Other Chrome flags to enable to run the code are:
enable-experimental-web-platform-featuresto use thegetDevices()andwatchAdvertisements()APIsenable-web-bluetooth-new-permissions-backendto enable first-time only explicit user permission to connect with a particular device. Subsequent requests to connect to the same device will not require the explicit user permission.
You can use a BLE Device Simulator App to simulate a BLE device for experimenting:
https://github.com/WebBluetoothCG/ble-test-peripheral-android
-
Web BLE API is in experimental status for most functionality: not yet suited for production
-
STWIN Fw is not compatible out-of-the-box with current API to receive notifications: Client Characteristic Configuration Descriptors need to be developed (need to check this)
Trying to enable characteristic's notifications on an STWIN raises the following error:
It seems that this error is raised because of missing Client Characteristic Configuration Descriptor:
WebBluetoothCG/ble-test-peripheral-android#59 https://bugs.chromium.org/p/chromium/issues/detail?id=578811
-
Some APIs (for example
getDevices()andwatchAdvertisements()) are behind thechrome://flags/#enable-experimental-web-platform-featuresflag -
The Persistent Device Permissions feature is behind the
chrome://flags/#enable-web-bluetooth-new-permissions-backendflag