BLE

Copyright 2017-2024 Moddable Tech, Inc.
Revised: September 10, 2024

This document describes the Moddable SDK Bluetooth Low Energy (BLE) modules. Both client (master) and server (slave) roles are supported on Espressif ESP32, Silicon Labs Blue Gecko, Qualcomm QCA4020, and Nordic nRF52 devices.

Note: A BLE server/slave is also commonly referred to as a BLE peripheral. The terms server, slave and peripheral in this document are used interchangeably.

• Adding BLE to a Project
• Using BLE
• BLE Client
  • Class BLEClient
  • Class Client
  • Class Service
  • Class Characteristic
  • Class Descriptor
  • Class Advertisement
  • Class Bytes
• BLE Server
  • Class BLEServer
  • GATT Services
• BLE Security
  • Class SM
• BLE Whitelisting
  • Class GAPWhitelist
• BLE Apps on ESP32 Platform
• BLE Apps on Blue Gecko Platform
• BLE Example Apps

The BLE client and server are implemented as separate modules to accommodate the limited memory and storage available on embedded devices. BLE applications instantiate a BLE client or BLE server, but never both.

Pre-made manifests are available for the BLE client and BLE server. Add them to the include array of your application's manifest to use them in your project.

To add the BLE client to a project:

"include": [
	/* other includes here */
	"$(MODDABLE)/modules/network/ble/manifest_client.json"
],

To add the BLE server to a project:

"include": [
	/* other includes here */
	"$(MODDABLE)/modules/network/ble/manifest_server.json"
],

BLE applications typically subclass BLEClient or BLEServer and then add device and/or application specific code. The following BLE client example subclasses BLEClient to scan for and discover peripherals:

import BLEClient from "bleclient";

class Scanner extends BLEClient {
	onReady() {
		this.startScanning();
	}
	onDiscovered(device) {
		let scanResponse = device.scanResponse;
		let completeName = scanResponse.completeName;
		if (completeName)
			trace(completeName + "\n");
	}
}

let scanner = new Scanner;

The following BLE server example subclasses BLEServer to advertise the device as a BLE Health Thermometer peripheral:

import BLEServer from "bleserver";
import {uuid} from "btutils";

class HealthThermometerService extends BLEServer {
	onReady() {
		this.startAdvertising({
			advertisingData: {flags: 6, completeName: "Moddable HTM", completeUUID16List: [uuid`1809`, uuid`180F`]}
		});
	}
}

let htm = new HealthThermometerService;

A BLE client can connect to one or more BLE peripherals. The maximum number of concurrent connections is defined at build time and ultimately limited by what the underlying embedded platform supports. To override the default maximum of two connections, override the max_connections value in the manifest defines section:

"defines": {
	"ble": {
		"max_connections": 3
	}
},

A BLE client typically performs the following steps to receive notifications from a BLE peripheral:

1. Start scanning for peripherals
2. Find the peripheral of interest by matching the advertised complete name or UUID(s) in the scan response
3. Establish a connection with the peripheral
4. Discover the primary service(s) of interest
5. Discover the characteristic(s) within the service(s) of interest
6. Enable notifications for characteristic(s) of interest

The following code from the powermate example app shows a typical client flow:

const DEVICE_NAME = 'PowerMate Bluetooth';
const SERVICE_UUID = uuid`25598CF7-4240-40A6-9910-080F19F91EBC`;
const CHARACTERISTIC_UUID = uuid`9CF53570-DDD9-47F3-BA63-09ACEFC60415`;

class PowerMate extends BLEClient {
	onReady() {
		this.startScanning();
	}
	onDiscovered(device) {
		if (DEVICE_NAME == device.scanResponse.completeName) {
			this.stopScanning();
			this.connect(device);
		}
	}
	onConnected(device) {
		device.discoverPrimaryService(SERVICE_UUID);
	}
	onServices(services) {
		let service = services.find(service => service.uuid.equals(SERVICE_UUID));
		if (service)
			service.discoverCharacteristic(CHARACTERISTIC_UUID);
	}
	onCharacteristics(characteristics) {
		let characteristic = characteristics.find(characteristic => characteristic.uuid.equals(CHARACTERISTIC_UUID));
		if (characteristic)
			characteristic.enableNotifications();
	}
	onCharacteristicNotification(characteristic, buffer) {
		let value = new Uint8Array(buffer)[0];
		trace(`value: ${value}\n`);
	}
}

A BLE client is fundamentally asynchronous and results are always delivered to the BLEClient class callback methods, e.g. onReady, onConnected, etc. above. The following sections describe the BLE client classes, properties, and callbacks.

The BLEClient class provides access to the BLE client features.

import BLEClient from "bleclient";

Applications must wait for the onReady callback before calling other BLEClient functions:

class Client extends BLEClient {
	onReady() {
		/* stack is ready to use */
	}
}
let client = new BLEClient;

The params object contains the following properties:

The filterPolicy parameter can be one of the following:

The startScanning function enables scanning for nearby peripherals.

If no params argument is provided, the default scan properties are used:

class Scanner extends BLEClient {
	onReady() {
		this.startScanning();
	}
	onDiscovered(device) {
		trace("device discovered\n");
	}
}

Passing in a params object overrides the defaults. This example uses passive scanning at a 70ms interval:

class Scanner extends BLEClient {
	onReady() {
		this.startScanning({ active:false, interval:0x70 });
	}
	onDiscovered(device) {
		trace("device discovered\n");
	}
}

The onDiscovered callback function is called one or more times for each peripheral device discovered.

To connect to a device named "Brian" from the onDiscovered callback:

onDiscovered(device) {
	if ("Brian" == device.scanResponse.completeName) {
		this.connect(device);
	}
}

The stopScanning function disables scanning for nearby peripherals.

The connect function initiates a connection request between the BLEClient and a target peripheral device.

onDiscovered(device) {
	this.connect(device);
}
onConnected(device) {
	trace("Connected to device\n");
}

The onConnected callback function is called when the client connects to a target peripheral device.

The onDisconnected callback is called when the connection is closed.

BLE clients can optionally request link-layer security to protect data transferred between devices. The securityParameters property accessor function is used to configure the device security requirements and I/O capabilities.

To request MITM protection with encryption for a display-only device. The device will display a passkey when requested:

import {IOCapability} from "sm";

onReady() {
	this.securityParameters = { mitm:true, ioCapability:IOCapability.DisplayOnly };
}

To request MITM protection with encryption and bonding for a device with both a display and keyboard. The device will request a passkey to be entered and encryption keys will be saved:

import {IOCapability} from "sm";

onReady() {
	this.securityParameters = { mitm:true, bonding:true, ioCapability:IOCapability.KeyboardDisplay };
}

Note: The BLEClient object hosts all callbacks for classes used with BLEClient.

An instance of the Client class is instantiated by BLEClient and provided to the host app in the BLEClient onDiscovered and onConnected callbacks. While applications never instantiate a Client class instance directly, applications do call Client class functions to perform GATT service/characteristic discovery, negotiate a higher MTU and close the peripheral connection.

Use the exchangeMTU function to request a higher MTU once the peripheral connection has been established.

The onMTUExchanged callback function is called when the MTU exchange procedure has been completed.

To request an increased MTU size of 250:

onConnected(device) {
	device.exchangeMTU(250);
}
onMTUExchanged(device, mtu) {
	trace(`MTU size is now ${mtu}\n`);
	device.discoverAllPrimaryServices();
}

Use the readRSSI function to read the connected peripheral's signal strength.

The onRSSI callback function is called when the peripheral signal strength is read.

To read the signal strength of the connected device:

onConnected(device) {
	device.readRSSI();
}
onRSSI(device, rssi) {
	trace(`signal strength is ${rssi}\n`);
}

Use the discoverAllPrimaryServices function to discover all the peripheral's GATT primary services. Discovered services are returned to the onServices callback.

Use the discoverPrimaryService function to discover a single GATT primary service by UUID.

The findServiceByUUID function finds and returns the service identified by uuid. This function searches the services property array.

The onServices callback function is called when service discovery completes. If findServiceByUUID was called to find a single service, the services array contains the single service found.

To discover all primary services:

onConnected(device) {
	device.discoverAllPrimaryServices();
}
onServices(services) {
	trace(`${services.length} services found\n`);
}

To discover a single primary service:

const SERVICE_UUID = uuid`0xFF00`;

onConnected(device) {
	device.discoverPrimaryService(SERVICE_UUID);
}
onServices(services) {
	if (services.length)
		trace("found service\n");
}

Note: The uuid tagged template allows applications to represent UUID values as strings. Refer to the Bytes class section for details.

The close function terminates the peripheral connection.

onConnected(device) {
	trace("connected to device\n");
	device.close();
}
onDisconnected() {
	trace("connection closed\n");
}

The Service class provides access to a single peripheral GATT service.

Use the discoverAllCharacteristics() function to discover all the service characteristics. Discovered characteristics are returned to the onCharacteristics callback.

Use the discoverCharacteristic function to discover a single service characteristic by UUID.

The findCharacteristicByUUID function finds and returns the characteristic identified by uuid. This function searches the characteristics property array.

The onCharacteristics callback function is called when characteristic discovery completes. If findCharacteristicByUUID was called to find a single characteristic, the characteristics array contains the single characteristic found.

To discover all the characteristics in the Device Information service:

const DEVICE_INFORMATION_SERVICE_UUID = uuid`180A`;

onServices(services) {
	let service = services.find(service => service.uuid.equals(DEVICE_INFORMATION_SERVICE_UUID));
	if (service)
		service.discoverAllCharacteristics();
}
onCharacteristics(characteristics) {
	trace(`${characteristics.length} characteristics found\n`);
}

To find the Heart Rate Measurement characteristic in the Heart Rate service:

const HEART_RATE_SERVICE_UUID = uuid`180A`;
const HEART_RATE_MEASUREMENT_UUID = uuid`2A37`;

onConnected(device) {
	device.discoverPrimaryService(HEART_RATE_SERVICE_UUID);
}
onServices(services) {
	if (services.length)
		services[0].discoverCharacteristic(HEART_RATE_MEASUREMENT_UUID);
}
onCharacteristics(characteristics) {
	if (characteristics.length)
		trace(`found heart rate measurement characteristic\n`);
}

The Characteristic class provides access to a single service characteristic.

Use the discoverAllDescriptors function to discover all the characteristic's descriptors. Discovered descriptors are returned to the onDescriptors callback.

The onDescriptors callback function is called when descriptor discovery completes.

To discover the Characteristic Presentation Format Descriptor for a characteristic with UUID 0xFF00:

const CHARACTERISTIC_UUID = uuid`FF00`;
const PRESENTATION_FORMAT_UUID = uuid`2904`;

onCharacteristics(characteristics) {
	let characteristic = characteristics.find(characteristic => characteristic.uuid.equals(CHARACTERISTIC_UUID));
	if (characteristic)
		characteristic.discoverAllDescriptors();
}
onDescriptors(descriptors) {
	let descriptor = descriptors.find(descriptor => descriptor.uuid.equals(PRESENTATION_FORMAT_UUID));
	if (descriptor)
		trace("found characteristic presentation format descriptor\n");
}

Use the enableNotifications function to enable characteristic value change notifications.

The onCharacteristicNotificationEnabled callback function is called when notifications have been enabled for the characteristic.

Use the disableNotifications function to disable characteristic value change notifications.

The onCharacteristicNotificationDisabled callback function is called when notifications have been disabled for the characteristic.

The onCharacteristicNotification callback function is called when notifications are enabled and the peripheral notifies the characteristic value.

To enable and receive characteristic value change notifications for the Battery Level characteristic in the Battery Service:

const BATTERY_SERVICE_UUID = uuid`180F`;
const BATTERY_LEVEL_UUID = uuid`2A19`;

onConnected(device) {
	device.discoverPrimaryService(BATTERY_SERVICE_UUID);
}
onServices(services) {
	if (services.length)
		services[0].discoverCharacteristic(BATTERY_LEVEL_UUID);
}
onCharacteristics(characteristics) {
	if (characteristics.length)
		characteristics[0].enableNotifications();
}
onCharacteristicNotification(characteristic, value) {
	let level = new Uint8Array(value)[0];
	trace(`battery level: ${level}%\n`);
}

Use the readValue function to read a characteristic value on demand.

The Authorization object contains the following properties:

The onCharacteristicValue callback function is called when a characteristic is read by the readValue function.

To read the Device Name from the Generic Access Service:

const GENERIC_ACCESS_SERVICE_UUID = uuid`1800`;
const DEVICE_NAME_UUID = uuid`2A00`;

onConnected(device) {
	device.discoverPrimaryService(GENERIC_ACCESS_SERVICE_UUID);
}
onServices(services) {
	if (services.length)
		services[0].discoverCharacteristic(DEVICE_NAME_UUID);
}
onCharacteristics(characteristics) {
	if (characteristics.length)
		characteristics[0].readValue();
}
onCharacteristicValue(characteristic, value) {
	let name = String.fromArrayBuffer(value);
	trace(`device name: ${name}\n`);
}

Use the writeWithoutResponse function to write a characteristic value on demand.

To write the URI characteristic value in the HTTP Proxy service:

const HTTP_PROXY_SERVICE_UUID = uuid`1823`;
const URI_UUID = uuid`2AB6`;

onConnected(device) {
	device.discoverPrimaryService(HTTP_PROXY_SERVICE_UUID);
}
onServices(services) {
	if (services.length)
		services[0].discoverCharacteristic(URI_UUID);
}
onCharacteristics(characteristics) {
	if (characteristics.length)
		characteristics[0].writeWithoutResponse(ArrayBuffer.fromString("http://moddable.tech"));
}

The Descriptor class provides access to a single characteristic descriptor.

Use the readValue function to read a descriptor value on demand.

The Authorization object contains the following properties:

The onDescriptorValue callback function is called when a descriptor is read by the readValue function.

To read a descriptor with unauthenticated encryption:

import {SM, IOCapability, Authorization} from "sm";

const REPORT_REFERENCE_DESCRIPTOR_UUID = uuid`2908`;

onDescriptors(descriptors) {
	let descriptor = descriptors.find(descriptor => descriptor.uuid.equals(REPORT_REFERENCE_DESCRIPTOR_UUID));
	if (descriptor)
		descriptor.readValue(Authorization.NoMITM);
}
onDescriptorValue(descriptor, value) {
	let report = new Uint8Array(value);
}

Use the writeValue function to write a descriptor value.

To enable characteristic value change notifications by writing 0x0001 to the Client Characteristic Configuration descriptor:

const CCCD_UUID = uuid`2902`;

onDescriptors(descriptors) {
	let descriptor = descriptors.find(descriptor => descriptor.uuid.equals(CCCD_UUID));
	if (descriptor) {
		let value = Uint8Array.of(0x01, 0x00);	// little endian
		descriptor.writeValue(value.buffer);
	}
}

Note: The Characteristic enableNotifications convenience function is typically used for this purpose, though writing the CCCD descriptor directly provides the same net result.

The Advertisement class provides accessor functions to read common advertisement and scan response data types as JavaScript properties. The class is primarily used to parse the scanResponseData provided to BLE clients via the onDiscovered callback function's device parameter. The accessor functions return undefined if the associated data type is not available in the scanResponseData.

Use the findIndex function to find the index of a specific advertisement data type in the raw advertisement data bytes.

To identify an advertised device with the complete name "Zip":

onDiscovered(device) {
	let completeName = device.scanResponse.completeName;
	if (completeName == "ZIP") {
		trace("Found ZIP device\n");
	}
}

To identify a Blue Maestro Environment Monitor and read the temperature from the manufacturer specific data:

onDiscovered(device) {
	let manufacturerSpecific = device.scanResponse.manufacturerSpecific;
	const TempoManufacturerID = 307;

	// If this is a Tempo device...
	if (manufacturerSpecific && (TempoManufacturerID == manufacturerSpecific.identifier)) {
		let data = manufacturerSpecific.data;
		if (data[0] == 0 || data[0] == 1) {	// ...and product model T30 or THP
			let temperature = (data[3] | (data[4] << 8)) / 10;
			trace(`Temperature: ${temperature} ˚C\n`);
		}
	}
}

To search for the "TX Power Level" advertisement data type in the scan response data:

onDiscovered(device) {
	let scanResponse = device.scanResponse;
	let index = scanResponse.findIndex(GAP.ADType.TX_POWER_LEVEL);
	if (-1 !== index) {
		trace(`Found advertisement tx power level data at index ${index}\n`);
		const bytes = new Uint8Array(scanResponse.buffer);
		const txPowerLevel = bytes[index + 2];
	}
}

The private Bytes class extends ArrayBuffer. Applications typically use the provided uuid and address tagged templates to create a Bytes instance from hex strings.

The address tagged template is used to convert a Bluetooth address expressed as a hex string to a Bytes instance.

import {address} from "btutils";

const DEVICE_ADDRESS = address`66:55:44:33:22:11`;

The uuid tagged template is used to convert a Bluetooth UUID expressed as a hex string to a Bytes instance.

import {uuid} from "btutils";

const HTM_SERVICE = uuid`1809`;
const CHARACTERISTIC_RX_UUID = uuid`6E400002-B5A3-F393-E0A9-E50E24DCCA9E`;

The equals function returns true if the instance ArrayBuffer data equals the data contained in buffer.

import {uuid} from "btutils";

const HTM_SERVICE = uuid`1809`;
onServices(services) {
	let found = services[0].uuid.equals(HTM_SERVICE);
	if (found)
		trace("found HTM service\n");
}

The toString helper function returns a printable hex string of the Bytes contents. The string is formatted in big endian order with separators.

onDiscovered(device) {
	trace(`Found device with address ${device.address}\n`);
}
onServices(services) {
	if (services.length) {
		trace(`Found service with UUID ${services[0].uuid}\n`);
	}
}

A BLE server/peripheral can connect to one BLE client and typically performs the following steps to send notifications to a BLE client:

1. Start advertising so that clients can discover the peripheral
2. Establish a connection with a client
3. Accept characteristic value change notification request(s)
4. Notify characteristic value changes.

The following abbreviated code from the heart-rate-server example app shows a typical server flow:

onReady() {
	this.bpm = [0, 60]; // flags, beats per minute
	this.startAdvertising({
		advertisingData: {flags: 6, completeName: "Moddable HRS", completeUUID16List: [uuid`180D`, uuid`180F`]}
	});
}
onConnected() {
	this.stopAdvertising();
}
onCharacteristicNotifyEnabled(characteristic) {
	this.startMeasurements(characteristic);
}
startMeasurements(characteristic) {
	this.bump = +1;
	this.timer = Timer.repeat(id => {
		this.notifyValue(characteristic, this.bpm);
		this.bpm[1] += this.bump;
		if (this.bpm[1] == 65) {
			this.bump = -1;
			this.bpm[1] == 64;
		}
		else if (this.bpm[1] == 55) {
			this.bump = +1;
			this.bpm[1] == 56;
		}
	}, 1000);
}

GATT services are automatically deployed by the BLE server when launched. A BLE server is fundamentally asynchronous and results are always delivered to the BLEServer class callback methods, e.g. onReady, onConnected, etc. above. The following sections describe the BLEServer class, properties, and callbacks.

The BLEServer class provides access to the BLE server features.

import BLEServer from "bleserver";

The BLEServer constructor takes a single argument, an optional dictionary of initialization parameters.

Applications must wait for the onReady callback before calling other BLEServer functions:

class Server extends BLEServer {
	onReady() {
		/* stack is ready to use */
	}
}
let server = new BLEServer;

The deviceName property accessor function is used to set/get the Bluetooth peripheral device name.

class Advertiser extends BLEServer {
	onReady() {
		this.deviceName = "My BLE Device";
		trace(`My device is named ${this.deviceName}\n`);
	}
}
let advertiser = new BLEServer;

The read-only localAddress property accessor function returns the Bluetooth peripheral's local address as a Bytes object.

class Advertiser extends BLEServer {
	onReady() {
		trace(`device address: ${(new Uint8Array(this.localAddress)).toHex()}\n`);
	}
}

BLE servers can optionally request link-layer security to protect data transferred between devices. The securityParameters property accessor function is used to configure the device security requirements and I/O capabilities.

To request MITM protection with encryption for a display-only device. The device will display a passkey when requested:

import {IOCapability} from "sm";

onReady() {
	this.securityParameters = { mitm:true, ioCapability:IOCapability.DisplayOnly };
}

To request MITM protection with encryption and bonding for a device with both a display and keyboard. The device will request a passkey to be entered and encryption keys will be saved:

import {IOCapability} from "sm";

onReady() {
	this.securityParameters = { mitm:true, bonding:true, ioCapability:IOCapability.KeyboardDisplay };
}

The params object contains the following properties:

Note: The notify property is only implemented for nRF52 devices.

The filterPolicy property can be one of the following:

The startAdvertising function starts broadcasting advertisement and scan response packets. The function is also used to configure discoverable and connectable modes.

The advertisingData and scanResponseData contain one or more properties corresponding to the Bluetooth Advertisement Data Types:

To advertise a Health Thermometer Sensor BLE-only connectable device with the complete local name "Thermometer" and one service with UUID 0x1809:

import {uuid} from "btutils";

this.startAdvertising({
	advertisingData: {flags: 6, completeName: "Thermometer", completeUUID16List: [uuid`1809`]}
});

To advertise a Heart Rate Sensor BLE-only connectable device with the complete local name "Moddable HRS" and two services with UUIDs 0x180D and 0x180F:

import {uuid} from "btutils";

this.startAdvertising({
	advertisingData: {flags: 6, completeName: "Moddable HRS", completeUUID16List: completeUUID16List: [uuid`180D`, uuid`180F`]}
});

To advertise a BLE-only non-connectable and limited discoverable device with the complete local name "Moddable HRS" and the short name "Moddable" and random target address 00:11:22:33:44:55 provided in the scan response:

import {address} from "btutils";

this.startAdvertising({
	connectable: false,
	advertisingData: {flags: 5, completeName: "Moddable HRS"},
	scanResponseData: {shortName: "Moddable", randomAddress: address`00:11:22:33:44:55`}
});

To receive a notification callback after each advertising data packet sent:

onReady() {
	this.startAdvertising({
		notify: true,
		advertisingData: {flags: GAP.ADFlag.NO_BR_EDR, completeName: "Advertiser"}
	});
}
onAdvertisementSent() {
	trace("advertisement sent\n");
}

Call the stopAdvertising function to stop broadcasting Bluetooth advertisements.

import {uuid} from "btutils";

onReady() {
	this.startAdvertising({
		advertisingData: {flags: 6, completeName: "Thermometer Example", completeUUID16List: [uuid`1809`]}
	});
}
onConnected(device) {
	this.stopAdvertising();
}

Call the notifyValue function to send a characteristic value change notification to the connected client.

To notify a characteristic with the string "hello" every 250 ms:

onCharacteristicNotifyEnabled(characteristic) {
	this.startNotifications(characteristic);
}
startNotifications(characteristic) {
	this.timer = Timer.repeat(id => {
		this.notifyValue(characteristic, ArrayBuffer.fromString("hello"));
	}, 250);
}

The onAdvertisementSent callback function is called after each advertising data packet sent, when a server enables advertisement notifications from the startAdvertising() function.

Note: The onAdvertisementSent callback is only implemented for nRF52 devices.

The onCharacteristicNotifyEnabled callback function is called when a client enables notifications on the characteristic.

The characteristic object contains the following properties:

The onCharacteristicWritten callback is called when a client writes a service characteristic value on demand. The BLEServer application is responsible for handling the write request.

The following abbreviated example from the wifi-connection-server example shows how characteristic write requests are handled. The SSID and password characteristics are strings and the control characteristic is a numeric value. When the BLE client writes the value 1 to the control characteristic, the app closes the client connection and initiates a WiFi connection:

onCharacteristicWritten(characteristic, value) {
	if ("SSID" == characteristic.name)
		this.ssid = value;
	else if ("password" == characteristic.name)
		this.password = value;
	else if ("control" == characteristic.name) {
		if ((1 == value) && this.ssid) {
			this.close();
			this.connectToWiFiNetwork(this.ssid, this.password);
		}
	}
}

The characteristic object contains the following properties:

The onCharacteristicRead callback is called when a client reads a service characteristic value on demand. The BLEServer application is responsible for handling the read request.

To respond to a read request corresponding to a numeric "status" characteristic:

onReady() {
	this.status = 10;
}
onCharacteristicRead(characteristic) {
	if ("status" == characteristic.name)
		return this.status;
}

Use the disconnect function to terminate the BLE client connection.

import {address} from "btutils";

onReady() {
	this.allowed = address`11:22:33:44:55:66`;
}
onConnected(device) {
	this.stopAdvertising();
	if (!device.address.equals(this.allowed))
		this.disconnect();
}
onDisconnected(device) {
	trace("device disconnected\n");
}

The onConnected callback function is called when a client connects to the BLEServer.

The onDisconnected callback function is called when the client connection is closed.

Use the close function to terminate any BLE client connection and release all BLE resources.

onDisconnected(device) {
	this.close();
}

GATT services are defined by JSON files located in a BLE server or client project's bleservices directory. The JSON files are optional for BLE clients. Each JSON file defines a single service with one or more characteristics. The JSON is automatically converted to platform-specific native code by the Moddable mcconfig command line tool and the compiled object code is linked to the app.

The JSON file for a service consists of an object with a single service property. The service property is an object that includes the following top-level properties:

Each item in the characteristics object contains the following properties. Note that only the uuid and type properties are required for BLE client applications that include GATT services JSON files:

Characteristics that include a value property are considered static. The BLEServer class automatically responds to read requests for static characteristic values, further reducing the script code required to host a GATT service.

The following is an example of JSON corresponding to a Bluetooth Battery Service:

{
	"service": {
		"uuid": "180F",
		"characteristics": {
			"battery": {
				"uuid": "2A19",
				"maxBytes": 1,
				"type": "Uint8",
				"permissions": "read",
				"properties": "read",
				"value": 85
			},
		}
	}
}

The service is defined as follows:

• The service UUID is 0x180F
• The service contains a single characteristic named "battery"
  • The characteristic UUID is 0x2A19
  • The characteristic represents an unsigned 8-bit value
  • The characteristic value is 85 and clients only have permission to read the characteristic

BLE clients and servers use the securityParameters property accessor to optionally request link-layer security to protect data transferred between devices. Passkey pairing requires both devices to exchange and confirm the code before establishing a connection. Once the pairing process is complete, the connection and data transferred is encrypted. The BLE Security Manager (SM) defines the methods and protocols for pairing and key distribution.

The SM class provides objects used to configure BLE client and server security requirements and device capabilities. The SM class is available to both BLEClient and BLEServer classes. The security callback functions defined here are hosted by the BLEClient and BLEServer classes.

The IOCapability object contains the following properties:

To request MITM protection with encryption on a keyboard device:

import {IOCapability} from "sm";

onReady() {
	this.securityParameters = { mitm:true, ioCapability:IOCapability.KeyboardOnly };
}

Call the deleteBonding function to delete stored bonding information for the peer device with the provided address and addressType. The onBondingDeleted callback is called once the bond has been deleted. The onBondingDeleted callback is supported by both the BLEClient and BLEServer classes.

To delete bonding information after disconnecting from the peer device:

onDisconnected(device) {
	SM.deleteBonding(device.address, device.addressType);
}
onBondingDeleted(params) {
	trace(`device ${params.address} bond deleted\n`);
}

Use the deleteAllBondings function to delete all bonding information and encryption keys from persistent storage:

onReady() {
	SM.deleteAllBondings();
}

Call the passkeyInput function from the onPasskeyInput callback function to provide an input passkey value:

onPasskeyInput(params) {
	let passkeyValue = 123456;
	this.passkeyInput(params.address, passkeyValue);
}

Call the passkeyReply function from the onPasskeyConfirm callback function to confirm the passkey displayed by the peer device:

onPasskeyConfirm(params) {
	// passkey is valid
	this.passkeyReply(params.address, true);
}

The onSecurityParameters callback is called after the device security requirements and I/O capabilities have been set.

import {IOCapability} from "sm";

onReady() {
	this.securityParameters = { mitm:true, ioCapability:IOCapability.NoInputNoOutput };
}
onSecurityParameters() {
	this.startScanning();
}

The params object contains the following properties:

The onAuthenticated callback is called when an authentication procedure successfully completes, i.e. after successful device pairing or bonding. The onAuthenticated callback is supported by the BLEClient and BLEServer classes.

onAuthenticated(params) {
	trace(`authentication success, bonded = ${params.bonded}\n`);
}

The params object contains the following properties:

The onPasskeyConfirm callback is called when the user needs to confirm a passkey value displayed on a peer device. The callback calls passkeyReply passing true or false to confirm the passkey value.

onPasskeyConfirm(params) {
	trace(`confirm passkey: ${params.passkey}\n`);

	// passkey is valid
	this.passkeyReply(params.address, true);
}

The params object contains the following properties:

The onPasskeyDisplay callback is called when the device needs to display a passkey.

onPasskeyDisplay(params) {
	// display passkey on screen
	trace(`display passkey: ${params.passkey}\n`);
}

The params object contains the following properties:

The onPasskeyInput callback is called when the device needs to input the passkey displayed by the peer device. The inputPasskey function is called to return the input passkey value.

onPasskeyInput(params) {
	// display keyboard to enter passkey displayed by peer
	//let passkey = 123456;
	this.passkeyInput(params.address, passkey);
}

The params object contains the following properties:

The onPasskeyRequested callback is called when the device needs to request a passkey entry. The callback returns a numeric passkey value between 0 and 999,999.

onPasskeyRequested(params) {
	// display keyboard to enter passkey
	let passkey = Math.round(Math.random() * 999999);
	return passkey;
}

Note: Passkey values are integers, but must always include six digits. The host application is responsible for padding with leading zeros for display.

Whitelisting provides filtering of peer devices by Bluetooth address. A BLE client can use the whitelist to only receive peripheral scan responses and hence subsequent connections to devices in the whitelist. A BLE peripheral can use the whitelist to filter BLE client scans and connections. Whitelist filtering provides enhanced security by limiting communication to known and trusted BLE devices.

There is one BLE whitelist used by both the BLE client and server. The maximum number of whitelist entries allowed is platform-specific.

Note: Whitelisting is not currently supported on the Blue Gecko platform.

The GAPWhitelist class provides functions for manipulating the BLE whitelist.

import GAPWhitelist from "gapwhitelist";

Use the add function to add a peer device to the whitelist.

To add a Bluetooth address to the whitelist and receive only scan responses from devices in the whitelist:

onReady() {
	GAPWhitelist.add("B4:99:4C:34:D7:A7");
	this.startScanning({ filterPolicy:GAP.ScanFilterPolicy.WHITELIST });
}

To add a Bluetooth address to the whitelist and limit scan requests and connections to devices in the whitelist using a filter policy:

onReady() {
	this.deviceName = "Moddable HRM";
	GAPWhitelist.add("8C:10:21:79:C9:F3");
	this.onDisconnected();
}
onDisconnected() {
	this.stopMeasurements();
	this.startAdvertising({
		filterPolicy: GAP.AdvFilterPolicy.WHITELIST_SCANS_CONNECTIONS,
		advertisingData: {flags: 6, completeName: this.deviceName, completeUUID16List: [HEART_RATE_SERVIE_UUID, BATTERY_SERVICE_UUID]
	});
}

Use the remove function to remove a peer device from the whitelist.

Use the clear function to remove all peer devices from the whitelist.

The mcconfig command line tool automatically configures the ESP-IDF sdkconfig.defaults BLE options required by the host app. The ESP-IDF supports both the Apache NimBLE Bluetooth LE 5.1-certified open-source host and the dual-mode Bluedroid stack. NimBLE provides several benefits over Bluedroid, including smaller Flash/RAM footprint, fewer buffer copies, and faster builds. NimBLE is enabled by default by the Moddable SDK in ESP32 builds.

Note: BLE options can be further customized by the host app, if necessary, by providing a pathname to a directory containing custom sdkconfig defaults entries in the application manifest. Refer to the manifest documentation for details. For example, the CONFIG_BT_NIMBLE_MAX_CONNECTIONS value can be increased to support more than one BLE client connection. This value should match the max_connections value in the application manifest.

To build BLE apps using the legacy Bluedroid implementation, set the ESP32_BLUEDROID build environment variable to 1. This environment variable can be set on the mcconfig command line for convenience:

cd $MODDABLE/examples/network/ble/scanner
ESP32_BLUEDROID=1 mcconfig -d -m -p esp32

Building and deploying BLE apps on Blue Gecko follow the same workflow outlined in our Gecko developer documentation. For BLE apps, we recommend starting from the soc-ibeacon Simplicity Studio example project.

The make.blue.mk makefile includes variables that define the Gecko target platform, kit and part. The makefile is configured by default to build apps for the Blue Gecko EFR32BG13P632F512GM48 Bluetooth low energy chip mounted on the BRD4104A 2.4 GHz 10 dBm Radio Board. To configure the build for a different Blue Gecko target, change the makefile GECKO_BOARD, GECKO_PART, HWKIT and HWINC variables accordingly.

To build the scanner BLE app xs_gecko.a archive for Blue Gecko:

cd $MODDABLE/examples/network/ble/scanner
mcconfig -d -m -p gecko/blue

After building the BLE archive, the archive is linked to the native app hosted in Simplicity Studio. The main() native code function for a basic BLE client/server app can be reduced to the following:

void main(void)
{
	initMcu();
	initBoard();
	initApp();

	xs_setup();

	while (1) {
		xs_loop();
	}
}

BLE apps require additional stack and heap. We've been able to run the Moddable BLE example apps using the following values:

__STACK_SIZE=0x2000
__HEAP_SIZE=0xA000

Simplicity Studio includes a BLE GATT Configurator to define BLE services. Moddable apps define BLE services in JSON files and hence don't use the gatt_db.c and gatt_db.h files generated by the configurator tool. These two files must be removed from the Simplicity Studio project.

The Moddable SDK includes many BLE client and server example apps to build from. We recommend starting from an example app, since the apps demonstrate how to implement common use cases: