> For the complete documentation index, see [llms.txt](https://doc.sysdevmobile.com/kalipso5/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.sysdevmobile.com/kalipso5/developing/form/actions/actions-description/group-communications/bluetooth-le-start-scanning.md).

# Bluetooth LE Start Scanning

Starts the discovery of Bluetooth Low Energy (BLE) devices.

Action available for the following operating systems:

![](/files/kfMeq0OanEe5OOx5RmUn)

### Parameters

*Targets*

* **Target for Address** *\<unquoted string> -* The control or variable where the MAC Address of the discovered device will be stored.
* **Target for Name** *\<unquoted string>* - The control or variable where the name of the discovered device will be stored.

{% hint style="warning" %}
Many Bluetooth LE devices do not return this value
{% endhint %}

* **Target for RSSI** *\<unquoted string>* - Value for the radio signal strength.
* **Target for Advertisement Element Count** *\<unquoted string>* - Number of data elements in advertisement.
* **Target for Advertisement Element Type List** *\<unquoted string>* - List of data element types in hexadecimal

{% hint style="info" %}
The possible types values are listed in the Bluetooth SIG website: <https://www.bluetooth.com/specifications/assigned-numbers/generic-access-profile>
{% endhint %}

* **Target for Advertisement Element Data List** *\<unquoted string>* - Element Data in Hexadecimal
* **Separator** *\<string>* - Element separator
* **Filter Address List** *\<string>*
* **Filter Service UUID List** *\<string>*

{% hint style="info" %}
This action starts the discovery process. When a Bluetooth device is discovered the event **Bluetooth LE Device Found** will be executed on the top form.
{% endhint %}

{% hint style="info" %}
On iOS, it is not possible to obtain the raw advertisement data, so the returned advertisement data is emulated to try to make it compatible with the data returned on Android and Win10. The following mapping was done between iOS types and Bluetooth specification for the **Element Type List** and **Element Data List** parameters:

* CBAdvertisementDataLocalNameKey -> Type(09): the data is returned as Hexadecimal representation of the UTF8 for the string
* CBAdvertisementDataManufacturerDataKey -> Type(FF): the data is returned as Hexadecimal representation of the byte values
* CBAdvertisementDataServiceDataKey -> Type(16): the data is returned as concatenated Hexadecimal representation of each UUID concatenated with the Hexadecimal representation of the service data
* CBAdvertisementDataServiceUUIDsKey-> Type(07): the data is returned as concatenated Hexadecimal representation of the UUIDs
* CBAdvertisementDataOverflowServiceUUIDsKey-> Type(06): the value is returned as concatenated Hexadecimal representation of the UUIDs
* CBAdvertisementDataTxPowerLevelKey-> Type(0A): the data is returned as the Hexadecimal value of the RSSI
* CBAdvertisementDataIsConnectable-> Type(01): the data is returned as the Hexadecimal value of the flag
* CBAdvertisementDataSolicitedServiceUUIDsKey-> Type(15): the data is returned as concatenated Hexadecimal representation of the UUIDs
  {% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.sysdevmobile.com/kalipso5/developing/form/actions/actions-description/group-communications/bluetooth-le-start-scanning.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.