# Bluetooth Start Device Discovery

Starts the discovery of Bluetooth devices.

Action available for the following operating systems:

![](/files/-MGNsZjeYMKt8-HvBB5n)

### Parameters

**Targets**

* **MAC Address** *\<unquoted string> -* The control or variable where the MAC Address of the discovered device will be stored.
* **Name** *\<unquoted string> -* The control or variable where the name of the discovered device will be stored.
* **PairingState** *\<numeric> - T*he control or variable where the pairing state of the discovered device will be stored. It can be:
  * 0 - Not Paired
  * 1 - Paired

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

{% hint style="info" %}
When the discovery process is finished the event **Bluetooth Discovery Finished** will be executed on the top form.
{% endhint %}

{% hint style="info" %}
On Win32 clients, the process is actually synchronous. So this call will be a blocking call and for each device found the event **Bluetooth Device Found** will be executed and at the end the event **Bluetooth Discovery Finished** will be executed.
{% endhint %}

{% hint style="info" %}
On some Windows CE/Mobile devices this function may not be available. It will depend on the actual Bluetooth drivers of the device.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://doc.sysdevmobile.com/kalipso5/developing/form/actions/actions-description/group-communications/bluetooth-start-device-discovery.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.