OVMS3-idf/docs/api/bluetooth/esp_bt_device.rst

BT DEVICE APIs
===============

Overview
--------

Bluetooth device reference APIs.

`Instructions`_

Application Example
-------------------

`Instructions`_

.. _Instructions: ../template.html


API Reference
-------------

Header Files
^^^^^^^^^^^^

  * :component_file:`bt/bluedroid/api/include/esp_bt_device.h`


Macros
^^^^^^


Type Definitions
^^^^^^^^^^^^^^^^


Enumerations
^^^^^^^^^^^^


Structures
^^^^^^^^^^


Functions
^^^^^^^^^

.. doxygenfunction:: esp_bt_dev_get_address
component/bt : add bt device api 1. add get bd_addr function 2017-01-06 13:19:58 +00:00			`BT DEVICE APIs`
			`===============`

			`Overview`
			`--------`

			`Bluetooth device reference APIs.`

			`Instructions`_

			`Application Example`
			`-------------------`

			`Instructions`_

Updated links to examples in new folders / categories in api documentation 2017-01-16 22:08:36 +00:00			`.. _Instructions: ../template.html`
component/bt : add bt device api 1. add get bd_addr function 2017-01-06 13:19:58 +00:00

			`API Reference`
			`-------------`

			`Header Files`
			`^^^^^^^^^^^^`

docs: use custom roles to generate GitHub links This change replaces direct links to GitHub master branch with auto-generated links using docutils custom roles. These auto-generated links point to the tree or blob for the git commit ID (or tag) of the repository. This is needed to ensure that links don’t become broken when files in master branch are moved around or deleted. The following roles are introduced: - :idf:`path` - points to directory inside ESP-IDF - :idf_blob:`path` - points to file inside ESP-IDF - :idf_raw:`path` - points to raw view of the file inside ESP-IDF - :component:`path` - points to directory inside ESP-IDF components dir - :component_blob:`path` - points to file inside ESP-IDF components dir - :component_raw:`path` - points to raw view of the file inside ESP-IDF components dir - :example:`path` - points to directory inside ESP-IDF examples dir - :example_blob:`path` - points to file inside ESP-IDF examples dir - :example_raw:`path` - points to raw view of the file inside ESP-IDF examples dir A check is added to the CI build script, which searches RST files for presence of hard-coded links (identified by tree/master, blob/master, or raw/master part of the URL). This check can be run manually: cd docs && make gh-linkcheck Additionally, Sphinx linkcheck build type is used to create new CI test, which check for broken links. This test has to be triggered explicitly, because including it in normal build process (when the commit is not yet deployed to Github) will not work. It can be triggered in a regular fashion using a combination of cron and Curl, similar to stress tests. 2017-01-19 08:16:06 +00:00			* :component_file:`bt/bluedroid/api/include/esp_bt_device.h`
component/bt : add bt device api 1. add get bd_addr function 2017-01-06 13:19:58 +00:00

			`Macros`
			`^^^^^^`


			`Type Definitions`
			`^^^^^^^^^^^^^^^^`


			`Enumerations`
			`^^^^^^^^^^^^`


			`Structures`
			`^^^^^^^^^^`


			`Functions`
			`^^^^^^^^^`

			`.. doxygenfunction:: esp_bt_dev_get_address`