|Check Bluetooth Permission||Checks whether the user has granted permission to use Bluetooth on this device. If permission has not been granted, the Bluetooth Permissions dialog with be displayed. No BLE actions can be run until permission has been granted.|
|Clear BLE State||Clear a BLE Component to an empty state.|
|Connect to Bluetooth Device||Connects to a BLE device identified by ID. The ID should be obtained from discovery, as it may change over time and between different phones.|
|Enable Bluetooth||Ensures Bluetooth is enabled on the device.|
|Set BLE Characteristic||Set a characteristic value on a connected BLE device. The following parameters are required:|
- Services are used to break data up into logic entities, and contain specific chunks of data called characteristics. A service can have one or more characteristics, and each service distinguishes itself from other services by means of a unique numeric ID called a UUID, which can be either 16-bit (for officially adopted BLE Services) or 128-bit (for custom services).
- Characteristics are containers for data. A Characteristic encapsulates a single data point and distinguishes itself via a pre-defined 16-bit or 128-bit UUID. Can use the standard characteristics as listed on the link below to ensure interoperability across and BLE-enabled Hardware/Software or define your own custom characteristics which only your peripheral and Software understands. Characteristics can have either read only or write privileges.
- Value is the value attribute that contains the actual user data that the client can read from and write to for practical information exchanges. It has a specific UUIDs that can refer to a sensor’s reading or a keypress on a keyboard. It can contain any type of data imaginable, from temperatures in celsius to key scan codes to display strings to speeds in miles per hour—anything that can be usefully transmitted over two BLE devices can fill in the contents of that value.
|Set BLE Frequency|
Start BLE discovery (scanning). The “frequency” sets the time in milliseconds for continuous scanning. After this time a short delay will occur then the scan will start again. We suggest 10000.
Call this action with frequency 0 to stop scanning.
While discovery or scanning is running, device discovered events will fire on a BLE component.