Warning

This document is not updated for ESP32C6 yet, so some of the content may not be correct.

This warning was automatically inserted due to the source file being in the add_warnings_pages list.

Bluetooth API

[中文]

• BT COMMON
  • Bluetooth DEFINE
  • Bluetooth MAIN
  • Bluetooth DEVICE
• BT LE
  • BLE GAP
  • BLE GATT DEFINE
  • BLE GATT SERVER
  • BLE GATT CLIENT
  • BLE BLUFI
• Controller && VHCI
  • Application Example
  • API Reference
• ESP-BLE-MESH
  • Application Examples and Demos
  • API Reference
  • ESP-BLE-MESH Definitions
  • ESP-BLE-MESH Core API Reference
  • ESP-BLE-MESH Models API Reference
• NimBLE-based host APIs
  • Overview
  • Architecture
  • Threading Model
  • Programming Sequence
  • API Reference

ESP-IDF currently supports two host stacks. The Bluedroid based stack (default) supports classic Bluetooth as well as BLE. On the other hand, Apache NimBLE based stack is BLE only. For users to make a choice:

• For usecases involving classic Bluetooth as well as BLE, Bluedroid should be used.

• For BLE-only usecases, using NimBLE is recommended. It is less demanding in terms of code footprint and runtime memory, making it suitable for such scenarios.

Code examples for this API section are provided in the bluetooth/bluedroid directory of ESP-IDF examples.

The following examples contain detailed walkthroughs:

• GATT Client Example Walkthrough

• GATT Server Service Table Example Walkthrough

• GATT Server Example Walkthrough

• GATT Security Client Example Walkthrough

• GATT Security Server Example Walkthrough

• GATT Client Multi-connection Example Walkthrough

Provide feedback about this document