前面第 11~13 章,我們已經使用 ESP32 的 Wi-Fi 功能完成:
- Wi-Fi 無線網路連線
- ESP32 Web Server
- 手機網頁控制 LED / Relay
- DHT11 / DHT22 溫溼度監控
- JSON Sensor API
- AJAX / Fetch Web Dashboard
這些專案都有一個共同點:
手機與 ESP32 主要透過 Wi-Fi Router 進行通訊。
但 ESP32 還有另一項非常重要的無線能力:
Bluetooth
ESP32 可以讓手機不經過 Wi-Fi Router,直接利用 Bluetooth 與 ESP32 通訊。
例如:
手機
│
│ Bluetooth
▼
ESP32
│
├── LED
├── Relay
├── Sensor
├── Motor
└── Servo
因此非常適合:
- 手機遙控器
- 智慧燈
- 電子鎖
- 機器人控制
- 設備設定
- 感測器讀取
- 工業設備近距離維護
- Wi-Fi SSID / Password 初始設定
- 不需要 Router 的離線控制
本章將完整介紹:
- Bluetooth Classic
- BLE
- Bluetooth Serial
- SPP
- BLE Server
- BLE Client
- UUID
- Service
- Characteristic
- Notification
- UART Bluetooth
- 手機控制
最後實作:
手機 Bluetooth 控制 ESP32 LED / Relay
而且會提供兩套方式:
- Bluetooth Classic Serial 控制
- BLE UART 控制
其中 BLE 會作為本章較推薦的手機控制方式。
一、ESP32 有哪兩種 Bluetooth?
ESP32 Bluetooth 最重要的兩種技術是:
Bluetooth Classic
以及:
Bluetooth Low Energy
BLE
兩者雖然都叫 Bluetooth,但設計目的並不完全一樣。
Espressif 將 Bluetooth Classic 定位於連續、較高吞吐量的資料傳輸,而 Bluetooth LE 則針對低功耗、間歇式資料傳輸設計。原始 ESP32 支援 Classic Bluetooth 與 BLE 雙模。
二、Bluetooth Classic 與 BLE 差異
| 項目 | Bluetooth Classic | BLE |
|---|---|---|
| 全名 | Bluetooth Classic | Bluetooth Low Energy |
| 功耗 | 較高 | 較低 |
| 連續資料傳輸 | 很適合 | 可以,但架構不同 |
| Serial 模式 | SPP | 通常以 Characteristic 模擬 |
| 手機相容性 | Android 較方便 | Android / iPhone 都很適合 |
| Sensor | 可用 | 非常適合 |
| IoT | 可用 | 非常適合 |
| Wearable | 較少 | 很適合 |
| ESP32 原版 | 支援 | 支援 |
| ESP32-C3 | 不支援 Classic | 支援 BLE |
| ESP32-S3 | 不支援 Classic | 支援 BLE |
如果只是想快速建立:
手機 Terminal
↓
ESP32
Bluetooth Classic SPP 很容易理解。
但是如果考慮:
- Android
- iPhone
- ESP32-C3
- ESP32-S3
- IoT
- 低功耗裝置
則:
BLE 更值得優先學習。
三、非常重要:不是所有 ESP32 都支援 Bluetooth Classic
這是 ESP32 Bluetooth 教學中最容易踩到的問題之一。
目前 Espressif 官方能力表指出:
| ESP32 系列 | Bluetooth Classic | BLE |
|---|---|---|
| ESP32 | ✓ | ✓ |
| ESP32-S2 | ✗ | ✗ |
| ESP32-S3 | ✗ | ✓ |
| ESP32-C2 | ✗ | ✓ |
| ESP32-C3 | ✗ | ✓ |
| ESP32-C5 | ✗ | ✓ |
| ESP32-C6 | ✗ | ✓ |
| ESP32-H2 | ✗ | ✓ |
也就是:
傳統 ESP32 / ESP32-WROOM-32 可以使用 Bluetooth Classic + BLE。
但是:
ESP32-C3、ESP32-S3 等新型號只能使用 BLE,不能使用 Classic SPP。
Espressif 最新文件明確列出原始 ESP32 支援 Bluetooth Classic BR/EDR 與 BLE,而 S3、C3、C6、H2 等系列不支援 Classic,只支援 BLE。
因此本章的:
#include <BluetoothSerial.h>
Bluetooth Classic 程式主要適用於:
ESP32
ESP32-WROOM-32
ESP32 Dev Module
如果是:
ESP32-C3
ESP32-S3
請直接使用本章後面的:
BLE 實作。
四、Bluetooth Classic 是什麼?
Bluetooth Classic 是傳統藍牙。
常見應用包括:
- Bluetooth Audio
- Speaker
- Keyboard
- Game Controller
- Serial Communication
- 車用設備
在 ESP32 Arduino 開發環境中,一個非常方便的功能就是:
Bluetooth SPP
SPP:
Serial Port Profile
可以把 Bluetooth 想像成:
一條無線 Serial Cable。
五、什麼是 Bluetooth Serial?
Arduino UNO 平常使用:
Serial.begin(9600);
再透過 USB Serial 傳資料。
Bluetooth Classic 則可以使用:
BluetoothSerial SerialBT;
然後:
SerialBT.begin("ESP32-BT");
手機就能搜尋:
ESP32-BT
並像 Serial Terminal 一樣與 ESP32 交換文字。
Espressif Arduino-ESP32 官方仍提供 BluetoothSerial 函式庫,透過 Bluetooth Classic SPP 建立類似 Serial 的資料通道;官方同時指出 SPP 僅適用於原始 ESP32 晶片。
六、Bluetooth Serial 基本架構
Android Phone
│
│ Bluetooth Classic
│ SPP
▼
ESP32 BluetoothSerial
│
▼
SerialBT.read()
│
▼
Arduino Program
│
▼
GPIO
例如手機送:
1
ESP32:
if (command == '1') {
digitalWrite(LED_PIN, HIGH);
}
LED 就會亮。
七、Bluetooth UART 是什麼?
很多教學會稱:
Bluetooth UART
其實要分成兩種概念。
Bluetooth Classic UART
Bluetooth Classic 可以透過:
SPP
提供非常接近 UART / Serial Stream 的使用方式。
例如:
SerialBT.available();
SerialBT.read();
SerialBT.print();
BLE UART
BLE 並沒有一個和 Classic SPP 完全相同的通用 Serial Port Profile。
BLE 通常使用:
Service
+
Characteristic
建立:
RX Characteristic
TX Characteristic
模擬:
UART RX
UART TX
因此常稱:
BLE UART Service
八、先實作 Bluetooth Classic 手機控制
本章先從容易理解的 Classic Serial 開始。
使用硬體:
| 元件 | 數量 |
|---|---|
| ESP32-WROOM-32 / ESP32 DevKit | 1 |
| LED | 1 |
| 220Ω~330Ω | 1 |
| Relay Module | 1 |
| Android 手機 | 1 |
本範例:
LED → GPIO 2
Relay → GPIO 26
九、LED 接線
ESP32 GPIO 2
│
220Ω
│
▼
LED +
LED -
│
▼
GND
程式:
#define LED_PIN 2
十、Relay 接線
ESP32 Relay
───── ─────
GPIO 26 ──────► IN
GND ──────────► GND
電源 ─────────► VCC
仍假設使用:
Active LOW Relay
所以:
#define RELAY_ON LOW
#define RELAY_OFF HIGH
十一、Bluetooth Classic 控制指令
我們定義五組命令:
| 手機傳送 | 功能 |
|---|---|
| 1 | LED ON |
| 0 | LED OFF |
| R | Relay ON |
| r | Relay OFF |
| S | 顯示 Status |
例如手機送:
1
ESP32 回傳:
LED ON
送:
R
回傳:
Relay ON
十二、Bluetooth Classic 完整程式
/*
* =====================================================
* 第 14 章
* ESP32 Bluetooth Classic
*
* 手機 Bluetooth 控制 LED / Relay
* =====================================================
*
* 適用:
* ESP32 / ESP32-WROOM-32
*
* 不適用:
* ESP32-C3 / ESP32-S3
*
* 指令:
*
* 1 = LED ON
* 0 = LED OFF
* R = Relay ON
* r = Relay OFF
* S = Status
* =====================================================
*/
#include <Arduino.h>
#include "BluetoothSerial.h"
// =====================================================
// Bluetooth Classic Support Check
// =====================================================
#if !defined(CONFIG_BT_ENABLED) || \
!defined(CONFIG_BLUEDROID_ENABLED)
#error Bluetooth is not enabled.
#endif
#if !defined(CONFIG_BT_SPP_ENABLED)
#error Bluetooth SPP is only available on supported ESP32 chips.
#endif
// =====================================================
// GPIO
// =====================================================
#define LED_PIN 2
#define RELAY_PIN 26
// =====================================================
// Relay Logic
// =====================================================
#define RELAY_ON LOW
#define RELAY_OFF HIGH
// =====================================================
// Bluetooth
// =====================================================
BluetoothSerial SerialBT;
const char* BT_NAME =
"ESP32-BT-Control";
// =====================================================
// Status
// =====================================================
bool ledState = false;
bool relayState = false;
// =====================================================
// Send Status
// =====================================================
void sendStatus() {
SerialBT.println();
SerialBT.println(
"===================="
);
SerialBT.println(
"ESP32 Status"
);
SerialBT.println(
"===================="
);
SerialBT.print(
"LED : "
);
SerialBT.println(
ledState ? "ON" : "OFF"
);
SerialBT.print(
"Relay : "
);
SerialBT.println(
relayState ? "ON" : "OFF"
);
SerialBT.println(
"===================="
);
}
// =====================================================
// Process Command
// =====================================================
void processCommand(char command) {
switch (command) {
// -------------------------------------------------
// LED ON
// -------------------------------------------------
case '1':
digitalWrite(
LED_PIN,
HIGH
);
ledState =
true;
Serial.println(
"LED ON"
);
SerialBT.println(
"LED ON"
);
break;
// -------------------------------------------------
// LED OFF
// -------------------------------------------------
case '0':
digitalWrite(
LED_PIN,
LOW
);
ledState =
false;
Serial.println(
"LED OFF"
);
SerialBT.println(
"LED OFF"
);
break;
// -------------------------------------------------
// Relay ON
// -------------------------------------------------
case 'R':
digitalWrite(
RELAY_PIN,
RELAY_ON
);
relayState =
true;
Serial.println(
"Relay ON"
);
SerialBT.println(
"Relay ON"
);
break;
// -------------------------------------------------
// Relay OFF
// -------------------------------------------------
case 'r':
digitalWrite(
RELAY_PIN,
RELAY_OFF
);
relayState =
false;
Serial.println(
"Relay OFF"
);
SerialBT.println(
"Relay OFF"
);
break;
// -------------------------------------------------
// Status
// -------------------------------------------------
case 'S':
case 's':
sendStatus();
break;
// -------------------------------------------------
// Ignore CR / LF
// -------------------------------------------------
case '\r':
case '\n':
break;
// -------------------------------------------------
// Unknown
// -------------------------------------------------
default:
SerialBT.print(
"Unknown command: "
);
SerialBT.println(
command
);
break;
}
}
// =====================================================
// Setup
// =====================================================
void setup() {
Serial.begin(
115200
);
// ---------------------------------------------------
// GPIO
// ---------------------------------------------------
pinMode(
LED_PIN,
OUTPUT
);
pinMode(
RELAY_PIN,
OUTPUT
);
digitalWrite(
LED_PIN,
LOW
);
digitalWrite(
RELAY_PIN,
RELAY_OFF
);
ledState =
false;
relayState =
false;
// ---------------------------------------------------
// Bluetooth
// ---------------------------------------------------
SerialBT.begin(
BT_NAME
);
Serial.println();
Serial.println(
"ESP32 Bluetooth Control"
);
Serial.print(
"Bluetooth Name: "
);
Serial.println(
BT_NAME
);
Serial.println(
"Waiting for Bluetooth connection..."
);
}
// =====================================================
// Loop
// =====================================================
void loop() {
// ---------------------------------------------------
// Bluetooth → ESP32
// ---------------------------------------------------
while (
SerialBT.available()
) {
char command =
SerialBT.read();
processCommand(
command
);
}
// ---------------------------------------------------
// USB Serial → Bluetooth
// Optional Debug Bridge
// ---------------------------------------------------
while (
Serial.available()
) {
SerialBT.write(
Serial.read()
);
}
delay(
5
);
}
十三、Bluetooth Classic 操作流程
程式上傳完成後:
ESP32 開機
│
▼
SerialBT.begin()
│
▼
Bluetooth Name
ESP32-BT-Control
│
▼
手機搜尋裝置
│
▼
Pair / Connect
│
▼
Bluetooth Terminal
接著輸入:
1
LED ON。
輸入:
0
LED OFF。
輸入:
R
Relay ON。
輸入:
r
Relay OFF。
輸入:
S
看到:
====================
ESP32 Status
====================
LED : ON
Relay : OFF
====================
十四、為什麼 Bluetooth Serial 很容易學?
因為:
BluetoothSerial SerialBT;
使用方法很像:
HardwareSerial Serial;
例如:
SerialBT.available();
檢查資料。
SerialBT.read();
讀取資料。
SerialBT.print();
傳送資料。
所以如果已經會:
Arduino Serial
就很容易理解:
ESP32 Bluetooth Serial
十五、Bluetooth Classic 與 iPhone 要注意
如果目標是:
Android
Bluetooth Classic SPP 很方便。
但是如果希望同一套專案容易支援:
iPhone
+
Android
更建議使用:
BLE。
Apple 的 Core Bluetooth Framework 主要提供 App 與 BLE 裝置通訊;需要透過 Classic Bluetooth 與自訂配件通訊時,通常涉及 External Accessory / MFi 的配件架構。Apple 也將 BLE 列為一般 App 與低功耗 Bluetooth 配件互動的主要方式。
因此對一般 ESP32 教學專案而言:
Android only
→ Classic SPP 很方便
Android + iPhone
→ BLE 更推薦
十六、什麼是 BLE?
BLE:
Bluetooth Low Energy
也就是:
低功耗藍牙。
它不像 Bluetooth Classic SPP 單純提供一條 Serial Stream。
BLE 使用的是比較結構化的:
GATT
架構。
常見結構:
BLE Device
│
▼
Service
│
├── Characteristic
│
├── Characteristic
│
└── Characteristic
十七、BLE Server 與 BLE Client
BLE 通訊最重要的兩個角色是:
Server
Client
本章設計:
ESP32
=
BLE Server
而:
Phone
=
BLE Client
完整流程:
ESP32 BLE Server
│
│ Advertising
▼
Smartphone
BLE Client
│
│ Connect
▼
Discover Services
│
▼
Discover Characteristics
│
▼
Read / Write / Notify
十八、BLE Server 是什麼?
BLE Server 負責提供:
- Service
- Characteristic
- Sensor Data
- Control Interface
ESP32 非常適合當:
BLE Server
例如:
ESP32
│
├── LED Control Service
│
├── Relay Control
│
└── Sensor Data
Espressif Arduino-ESP32 官方 BLE Server 範例就是使用 BLEDevice::createServer() 建立 Server,再建立 Service 與可讀寫的 Characteristic。
十九、BLE Client 是什麼?
BLE Client 是主動尋找並存取 Server 資料的一方。
在本章:
手機
就是 Client。
手機執行:
Scan
↓
找到 ESP32
↓
Connect
↓
Find Service
↓
Find Characteristic
↓
Write Command
所以手機寫入:
1
ESP32 就可以讓 LED ON。
二十、ESP32 也可以當 BLE Client 嗎?
可以。
例如:
BLE Temperature Sensor
│
▼
ESP32
BLE Client
ESP32 主動連接別的 BLE Sensor。
因此:
ESP32 BLE Server
和:
ESP32 BLE Client
都是可能的。
本章實作主要採用:
ESP32 = BLE Server
二十一、什麼是 GATT?
BLE 裡經常看到:
GATT
全名:
Generic Attribute Profile
可以簡單理解為:
規範 BLE 資料如何由 Service 與 Characteristic 組織及存取。
架構:
BLE Server
│
▼
Service
│
▼
Characteristic
│
├── Read
├── Write
└── Notify
二十二、什麼是 BLE Service?
Service 可以理解為:
一組相關功能的集合。
例如:
Environmental Service
裡面可能包含:
Temperature Characteristic
Humidity Characteristic
本章則建立:
UART Service
其中有:
RX Characteristic
TX Characteristic
二十三、什麼是 Characteristic?
Characteristic 是 BLE 真正交換資料的重要單位。
例如:
Temperature Characteristic
裡面可能存:
27.5
Relay Characteristic:
ON
或者 UART RX:
1
Characteristic 可以具有不同屬性:
READ
WRITE
NOTIFY
INDICATE
二十四、READ 是什麼?
如果 Characteristic 有:
BLECharacteristic::PROPERTY_READ
Client 可以主動讀取資料。
例如:
Phone
│
│ READ
▼
ESP32
│
▼
LED=ON
二十五、WRITE 是什麼?
WRITE 代表 Client 可以把資料送給 ESP32。
例如:
Phone
│
│ WRITE "R"
▼
ESP32
│
▼
Relay ON
本章手機控制最重要的就是:
WRITE Characteristic
二十六、NOTIFY 是什麼?
Notify 則是:
ESP32 主動把資料送給已訂閱的 Client。
例如 Relay 改變後:
ESP32
│
│ Notification
▼
Phone
│
▼
LED=ON,RELAY=OFF
不需要手機一直:
Read
Read
Read
Read
這對即時狀態更新非常有用。
二十七、什麼是 UUID?
BLE 會大量使用:
UUID
全名:
Universally Unique Identifier
例如:
6E400001-B5A3-F393-E0A9-E50E24DCCA9E
這是一個:
Service UUID
另外:
6E400002-B5A3-F393-E0A9-E50E24DCCA9E
可以作為:
RX Characteristic UUID
再用:
6E400003-B5A3-F393-E0A9-E50E24DCCA9E
作為:
TX Characteristic UUID
二十八、為什麼需要 UUID?
假設手機找到 ESP32。
ESP32 內可能有:
10 個 Service
50 個 Characteristic
手機如何知道哪一個是:
Relay Control
答案就是:
UUID
因此可以理解:
UUID
=
BLE 功能的識別碼
二十九、本章 BLE UART 架構
我們建立:
ESP32 BLE Server
│
▼
UART Service
│
├── RX Characteristic
│ │
│ └── Phone → ESP32
│
└── TX Characteristic
│
└── ESP32 → Phone
三十、BLE UART 資料方向
從 ESP32 的角度:
RX
Phone
│
│ command
▼
ESP32 RX
例如:
1
R
S
TX
ESP32 TX
│
│ Notify
▼
Phone
例如:
LED=ON,RELAY=OFF
三十一、本章 BLE 指令
BLE 版本仍然沿用:
| 指令 | 功能 |
|---|---|
| 1 | LED ON |
| 0 | LED OFF |
| R | Relay ON |
| r | Relay OFF |
| S | Status |
這樣 Classic 與 BLE 兩個版本可以使用相同通訊協定。
三十二、實作:BLE 手機控制 ESP32 LED / Relay
本章 BLE 版本架構:
Smartphone
BLE Client
│
│ WRITE
▼
RX Characteristic
│
▼
ESP32
│
├── GPIO 2
│ └── LED
│
└── GPIO 26
└── Relay
狀態回傳:
ESP32
│
▼
TX Characteristic
│
│ NOTIFY
▼
Phone
三十三、ESP32 BLE UART 完整程式
以下程式以:
ESP32-WROOM-32
ESP32 Dev Module
為教材基準。
如果使用 ESP32-C3 / ESP32-S3,BLE 原理仍適用,但 GPIO 腳位必須依實際開發板 Pinout 重新選擇,尤其 ESP32-C3 並沒有與 ESP32-WROOM-32 完全相同的 GPIO 配置。
/*
* =====================================================
* 第 14 章
* ESP32 BLE UART
*
* 手機 BLE 控制 LED / Relay
* =====================================================
*
* ESP32 = BLE Server
* Phone = BLE Client
*
* Command:
*
* 1 = LED ON
* 0 = LED OFF
* R = Relay ON
* r = Relay OFF
* S = Status
*
* GPIO:
*
* LED = GPIO 2
* Relay = GPIO 26
*
* Relay:
*
* Active LOW
* =====================================================
*/
#include <Arduino.h>
#include <BLEDevice.h>
#include <BLEServer.h>
#include <BLEUtils.h>
#include <BLE2902.h>
// =====================================================
// GPIO
// =====================================================
#define LED_PIN 2
#define RELAY_PIN 26
// =====================================================
// Relay Logic
// =====================================================
#define RELAY_ON LOW
#define RELAY_OFF HIGH
// =====================================================
// BLE Name
// =====================================================
#define BLE_DEVICE_NAME \
"ESP32-BLE-Control"
// =====================================================
// BLE UART UUID
// =====================================================
#define SERVICE_UUID \
"6E400001-B5A3-F393-E0A9-E50E24DCCA9E"
#define CHARACTERISTIC_UUID_RX \
"6E400002-B5A3-F393-E0A9-E50E24DCCA9E"
#define CHARACTERISTIC_UUID_TX \
"6E400003-B5A3-F393-E0A9-E50E24DCCA9E"
// =====================================================
// BLE Objects
// =====================================================
BLEServer*
pServer = nullptr;
BLECharacteristic*
pTxCharacteristic = nullptr;
// =====================================================
// Connection State
// =====================================================
bool deviceConnected =
false;
bool oldDeviceConnected =
false;
// =====================================================
// GPIO State
// =====================================================
bool ledState =
false;
bool relayState =
false;
// =====================================================
// Pending BLE Command
// =====================================================
volatile char pendingCommand =
0;
// =====================================================
// Server Callbacks
// =====================================================
class ServerCallbacks :
public BLEServerCallbacks {
void onConnect(
BLEServer* pServer
) override {
deviceConnected =
true;
Serial.println(
"BLE Client Connected"
);
}
void onDisconnect(
BLEServer* pServer
) override {
deviceConnected =
false;
Serial.println(
"BLE Client Disconnected"
);
}
};
// =====================================================
// RX Characteristic Callback
// =====================================================
class RxCallbacks :
public BLECharacteristicCallbacks {
void onWrite(
BLECharacteristic*
pCharacteristic
) override {
String value =
pCharacteristic
->getValue();
if (
value.length() > 0
) {
// Callback 中只記錄命令
// 真正控制動作交給 loop()
pendingCommand =
value[0];
}
}
};
// =====================================================
// Create Status String
// =====================================================
String createStatus() {
String status;
status.reserve(
64
);
status +=
"LED=";
status +=
ledState
? "ON"
: "OFF";
status +=
",RELAY=";
status +=
relayState
? "ON"
: "OFF";
return status;
}
// =====================================================
// Send BLE Notification
// =====================================================
void sendStatus() {
if (
pTxCharacteristic ==
nullptr
) {
return;
}
String status =
createStatus();
pTxCharacteristic
->setValue(
status.c_str()
);
Serial.print(
"Status: "
);
Serial.println(
status
);
if (
deviceConnected
) {
pTxCharacteristic
->notify();
}
}
// =====================================================
// Process Command
// =====================================================
void processCommand(
char command
) {
Serial.print(
"BLE Command: "
);
Serial.println(
command
);
switch (
command
) {
// -------------------------------------------------
// LED ON
// -------------------------------------------------
case '1':
digitalWrite(
LED_PIN,
HIGH
);
ledState =
true;
break;
// -------------------------------------------------
// LED OFF
// -------------------------------------------------
case '0':
digitalWrite(
LED_PIN,
LOW
);
ledState =
false;
break;
// -------------------------------------------------
// Relay ON
// -------------------------------------------------
case 'R':
digitalWrite(
RELAY_PIN,
RELAY_ON
);
relayState =
true;
break;
// -------------------------------------------------
// Relay OFF
// -------------------------------------------------
case 'r':
digitalWrite(
RELAY_PIN,
RELAY_OFF
);
relayState =
false;
break;
// -------------------------------------------------
// Status
// -------------------------------------------------
case 'S':
case 's':
break;
// -------------------------------------------------
// Unknown
// -------------------------------------------------
default:
Serial.println(
"Unknown BLE Command"
);
return;
}
// 更新 TX Characteristic
// 並通知 Client
sendStatus();
}
// =====================================================
// Setup
// =====================================================
void setup() {
Serial.begin(
115200
);
delay(
500
);
// ---------------------------------------------------
// GPIO
// ---------------------------------------------------
pinMode(
LED_PIN,
OUTPUT
);
pinMode(
RELAY_PIN,
OUTPUT
);
digitalWrite(
LED_PIN,
LOW
);
digitalWrite(
RELAY_PIN,
RELAY_OFF
);
ledState =
false;
relayState =
false;
// ---------------------------------------------------
// BLE Device
// ---------------------------------------------------
BLEDevice::init(
BLE_DEVICE_NAME
);
// ---------------------------------------------------
// Create BLE Server
// ---------------------------------------------------
pServer =
BLEDevice::createServer();
pServer->setCallbacks(
new ServerCallbacks()
);
// ---------------------------------------------------
// Create BLE Service
// ---------------------------------------------------
BLEService* pService =
pServer->createService(
SERVICE_UUID
);
// ---------------------------------------------------
// TX Characteristic
//
// ESP32 → Phone
// ---------------------------------------------------
pTxCharacteristic =
pService
->createCharacteristic(
CHARACTERISTIC_UUID_TX,
BLECharacteristic::
PROPERTY_READ |
BLECharacteristic::
PROPERTY_NOTIFY
);
pTxCharacteristic
->addDescriptor(
new BLE2902()
);
// ---------------------------------------------------
// RX Characteristic
//
// Phone → ESP32
// ---------------------------------------------------
BLECharacteristic*
pRxCharacteristic =
pService
->createCharacteristic(
CHARACTERISTIC_UUID_RX,
BLECharacteristic::
PROPERTY_WRITE
);
pRxCharacteristic
->setCallbacks(
new RxCallbacks()
);
// ---------------------------------------------------
// Initial Status
// ---------------------------------------------------
String initialStatus =
createStatus();
pTxCharacteristic
->setValue(
initialStatus.c_str()
);
// ---------------------------------------------------
// Start Service
// ---------------------------------------------------
pService->start();
// ---------------------------------------------------
// Advertising
// ---------------------------------------------------
BLEAdvertising*
pAdvertising =
BLEDevice::getAdvertising();
pAdvertising
->addServiceUUID(
SERVICE_UUID
);
pAdvertising
->setScanResponse(
true
);
BLEDevice
::startAdvertising();
// ---------------------------------------------------
// Serial Message
// ---------------------------------------------------
Serial.println();
Serial.println(
"ESP32 BLE Control Started"
);
Serial.print(
"BLE Name: "
);
Serial.println(
BLE_DEVICE_NAME
);
Serial.println(
"Waiting for BLE Client..."
);
}
// =====================================================
// Loop
// =====================================================
void loop() {
// ---------------------------------------------------
// Process BLE Command
// ---------------------------------------------------
if (
pendingCommand != 0
) {
char command =
pendingCommand;
pendingCommand =
0;
processCommand(
command
);
}
// ---------------------------------------------------
// BLE Disconnect
// Restart Advertising
// ---------------------------------------------------
if (
!deviceConnected &&
oldDeviceConnected
) {
delay(
500
);
pServer
->startAdvertising();
Serial.println(
"BLE Advertising Restarted"
);
oldDeviceConnected =
false;
}
// ---------------------------------------------------
// New Connection
// ---------------------------------------------------
if (
deviceConnected &&
!oldDeviceConnected
) {
oldDeviceConnected =
true;
sendStatus();
}
delay(
5
);
}
Arduino-ESP32 官方目前也提供 BLE UART 範例,使用 BLE Server、RX Write Characteristic 與 TX Notify Characteristic 建立雙向資料交換;官方範例同樣在 Client 斷線後重新啟動 Advertising。
三十四、為什麼 BLE Callback 不直接做很多事情?
在:
onWrite()
中,我們沒有放大量:
delay()
Sensor Reading
Network Request
Long Calculation
而只是:
pendingCommand = value[0];
然後:
loop()
再處理。
這是一個比較好的嵌入式設計習慣。
目前 Arduino-ESP32 BLE 實作的 Write Callback 會直接影響 ATT Write 回應時間,因此官方原始碼也建議 onWrite() 保持快速且非阻塞,較長的工作應移交其他 Task 或 Queue。
三十五、手機如何控制 BLE ESP32?
流程:
ESP32 開機
│
▼
BLEDevice::init()
│
▼
建立 BLE Server
│
▼
建立 UART Service
│
▼
建立 RX / TX
│
▼
Advertising
│
▼
手機 Scan
手機使用 BLE Scanner / BLE Client App 搜尋:
ESP32-BLE-Control
三十六、連線後會看到什麼?
手機連線 ESP32 後,可以看到:
Service
6E400001-B5A3-F393-E0A9-E50E24DCCA9E
裡面兩個 Characteristic。
RX:
6E400002-B5A3-F393-E0A9-E50E24DCCA9E
用途:
WRITE
Phone → ESP32
TX:
6E400003-B5A3-F393-E0A9-E50E24DCCA9E
用途:
READ
NOTIFY
ESP32 → Phone
三十七、手機控制 LED
在 RX Characteristic 寫入 ASCII:
1
ESP32:
digitalWrite(
LED_PIN,
HIGH
);
手機訂閱 TX Notification 後會收到:
LED=ON,RELAY=OFF
三十八、LED OFF
寫入:
0
ESP32:
digitalWrite(
LED_PIN,
LOW
);
Notification:
LED=OFF,RELAY=OFF
三十九、Relay ON
寫入:
R
ESP32:
digitalWrite(
RELAY_PIN,
RELAY_ON
);
手機收到:
LED=OFF,RELAY=ON
四十、Relay OFF
寫入:
r
ESP32:
digitalWrite(
RELAY_PIN,
RELAY_OFF
);
手機:
LED=OFF,RELAY=OFF
四十一、查詢目前狀態
寫入:
S
ESP32 執行:
sendStatus();
回傳:
LED=ON,RELAY=OFF
因此 BLE 已經不是單向控制。
而是:
Phone
│
│ Command
▼
ESP32
│
│ Status
▼
Phone
完整雙向通訊。
四十二、BLE Advertising 是什麼?
ESP32 開機後還沒有任何手機連線。
它會先:
Advertising
意思類似:
「我是 ESP32-BLE-Control,我在這裡,而且我提供這個 Service。」
手機:
Scan
才能找到 ESP32。
流程:
ESP32
│
│ Advertising Packet
▼
空氣
│
▼
Phone BLE Scan
四十三、Advertising 不等於 Connected
ESP32:
Advertising
只表示:
可以被發現
手機真正:
Connect
之後才建立 BLE Connection。
所以:
Advertising
≠
Connected
四十四、手機斷線後為什麼要重新 Advertising?
手機連線後 ESP32 可能停止一般 Advertising。
如果手機離開:
Disconnect
ESP32 必須再次:
pServer->startAdvertising();
否則另一台手機可能找不到。
因此程式加入:
if (
!deviceConnected &&
oldDeviceConnected
)
偵測斷線。
四十五、BLE Read、Write、Notify 的差異
| 功能 | 方向 | 說明 |
|---|---|---|
| Read | Client ← Server | 手機主動讀 |
| Write | Client → Server | 手機送命令 |
| Notify | Server → Client | ESP32 主動通知 |
本章:
RX
=
WRITE
TX:
READ
+
NOTIFY
四十六、這就是 BLE UART
整體看起來:
Phone TX
│
▼
ESP32 RX Characteristic
ESP32 TX Characteristic
│
▼
Phone RX
因此可以模擬:
UART
TX
RX
但底層其實仍是:
BLE GATT
Service
Characteristic
不是實體 UART。
四十七、Bluetooth Classic 與 BLE 程式架構比較
Classic
Phone
│
▼
SPP
│
▼
SerialBT
│
▼
read()
程式非常簡單:
SerialBT.read();
BLE UART 架構
Phone
│
▼
BLE Client
│
▼
Service
│
▼
Characteristic
│
▼
onWrite()
程式比較複雜,但架構更彈性。
四十八、什麼情況選 Classic?
如果使用:
ESP32-WROOM-32
+
Android
而需求只是:
Serial Terminal
那麼:
Bluetooth Classic 非常方便。
例如:
- Robot Remote Control
- Debug Console
- Serial Data
- 簡單按鍵命令
- Android Controller
四十九、什麼情況選 BLE?
如果:
Android
+
iPhone
或使用:
ESP32-C3
ESP32-S3
建議:
BLE。
另外以下專案也很適合 BLE:
- Sensor
- Beacon
- Wearable
- Smart Lock
- Thermometer
- Battery Device
- Configuration
- Home Automation
- Provisioning
五十、Classic 與 BLE 選擇表
| 專案 | 建議 |
|---|---|
| ESP32 + Android Terminal | Classic |
| ESP32 + iPhone | BLE |
| ESP32-C3 | BLE |
| ESP32-S3 | BLE |
| 低功耗 Sensor | BLE |
| 簡單 Serial Stream | Classic |
| Wearable | BLE |
| Smart Lock | BLE |
| 手機 App | BLE |
| 長時間連續 Serial Debug | Classic |
五十一、ESP32-S2 要特別注意
ESP32-S2:
沒有 Bluetooth
所以無法執行:
Bluetooth Classic
也無法執行:
BLE
Espressif 官方晶片功能表同樣將 ESP32-S2 的 Bluetooth 支援列為無。
因此購買 ESP32 開發板前要先確認:
ESP32 型號,而不是只看到產品名稱寫 ESP32。
五十二、BLE 為什麼適合 Sensor?
例如 DHT22:
Temperature
Humidity
並不需要每秒傳送幾千筆資料。
可能:
每 2 秒
傳一次即可。
這非常符合 BLE:
Low Power
+
Small Data
+
Intermittent Communication
的使用模式。
五十三、第 13 章 Sensor 可以直接加入 BLE
上一章我們已經有:
DHT11 / DHT22
│
▼
ESP32
原本資料送給:
Web Dashboard
現在也可以加入:
BLE Characteristic
例如:
Temperature Characteristic
Humidity Characteristic
變成:
DHT22
│
▼
ESP32
│
├── Wi-Fi Web Dashboard
│
└── BLE
│
▼
Phone
五十四、BLE 可以同時有很多 Characteristic
例如建立:
Environment Service
│
├── Temperature
├── Humidity
├── Relay
├── LED
└── Battery
每個 Characteristic 都可以有:
自己的 UUID
這比傳統 Serial Protocol 更有結構。
五十五、另一種設計:每個功能一個 Characteristic
目前 UART 版本:
一個 RX
一個 TX
所有命令都經過 RX。
另一種設計是:
LED Characteristic
Relay Characteristic
Temperature Characteristic
Humidity Characteristic
例如:
LED UUID
↓
0 / 1
Relay:
Relay UUID
↓
0 / 1
這種設計更符合 GATT 的資料模型。
五十六、UART BLE 的優點
不過在教學階段:
BLE UART
有很大的優點。
因為:
Classic Version
命令:
1
0
R
r
S
BLE 版本也完全相同。
因此可以直接比較:
Classic SPP
vs
BLE GATT UART
非常適合學習。
五十七、Relay Active LOW 再提醒一次
本程式假設:
#define RELAY_ON LOW
#define RELAY_OFF HIGH
如果你的 Relay 是:
Active HIGH
改成:
#define RELAY_ON HIGH
#define RELAY_OFF LOW
即可。
五十八、Bluetooth 控制 Relay 的安全注意事項
在教學階段建議先使用:
5V LED
12V LED
DC Fan
低壓負載
測試。
不要一開始就控制:
AC 110V
AC 220V
因為市電負載還涉及:
- Relay Contact Rating
- Fuse
- Wire Gauge
- Insulation
- Enclosure
- Creepage
- Clearance
- Grounding
- Terminal Safety
- Inrush Current
Bluetooth 程式正確:
≠
高壓電氣設計就一定安全。
五十九、Bluetooth 控制與 Wi-Fi 控制有何不同?
第 12~13 章:
Phone
│
▼
Wi-Fi Router
│
▼
ESP32
本章:
Phone
│
│ Bluetooth
▼
ESP32
Bluetooth 不一定需要 Router。
六十、Wi-Fi 的優點
Wi-Fi 比較適合:
- Web Server
- Internet
- Cloud
- MQTT
- REST API
- Large Data
- 遠端控制
例如:
Phone
│
▼
Internet
│
▼
Cloud
│
▼
ESP32
六十一、Bluetooth 的優點
Bluetooth 比較適合:
- 近距離控制
- 不需要 Router
- Initial Setup
- Local Maintenance
- Offline Control
- Low Power
- Device Provisioning
例如:
Phone
│
│ 3~10 公尺
▼
ESP32
實際距離會受到:
- ESP32 模組
- 天線
- 手機
- 建築物
- 發射功率
- 無線干擾
影響。
六十二、最實用的 IoT 架構其實是 Wi-Fi + BLE
成熟產品常同時使用:
BLE
+
Wi-Fi
例如設備第一次開機:
ESP32
│
│ BLE
▼
Phone
手機利用 BLE 傳送:
SSID
Password
給 ESP32。
接著:
ESP32
│
│ Wi-Fi
▼
Router
│
▼
Internet
BLE 就只負責:
Initial Configuration
Wi-Fi 負責:
Normal Operation
六十三、ESP32 Provisioning 概念
典型流程:
ESP32 第一次開機
│
▼
BLE Advertising
│
▼
手機 App
│
▼
傳送 SSID / Password
│
▼
ESP32 儲存 Wi-Fi
│
▼
連接 Router
│
▼
Cloud / MQTT / API
這就是很多 IoT 商品常見的:
Provisioning
概念。
六十四、手機控制協定最好怎麼設計?
目前:
1
0
R
r
S
非常適合入門。
但大型專案建議不要一直增加:
A
B
C
D
E
F
最後很難管理。
可以升級成:
LED:ON
LED:OFF
RELAY:ON
RELAY:OFF
STATUS
甚至:
{
"device":"relay",
"state":"on"
}
使用:
JSON Command
六十五、例如 BLE JSON Command
手機送:
{
"relay": true
}
ESP32解析後:
digitalWrite(
RELAY_PIN,
RELAY_ON
);
狀態回傳:
{
"led": true,
"relay": true
}
這樣後面可以更容易整合:
- Android App
- iPhone App
- Flutter
- React Native
- Python
- Web Bluetooth
六十六、Bluetooth 資料也要考慮安全性
如果 ESP32 控制的是:
LED
安全風險很小。
但如果控制:
Door Lock
Gate
Machine
Pump
Industrial Equipment
就不能只要附近任何人連線就接受:
R
正式系統需要考慮:
- Pairing
- Bonding
- Authentication
- Encryption
- Access Control
- Command Validation
- Timeout
- Device Identity
六十七、Classic Pairing 也不要只依賴舊式 PIN
舊教學常使用:
1234
0000
固定 PIN。
但目前 Arduino-ESP32 BluetoothSerial 已改變相關 Pairing 支援方式;官方 README 指出從 3.0.0 起,函式庫的標準使用方式不再支援舊式固定四位數 Legacy Pairing,並提供 Secure Simple Pairing 等方式。
因此新教材不建議只照很多舊網路文章寫:
SerialBT.setPin("1234");
然後假設所有 Arduino-ESP32 版本都可以正常工作。
六十八、BLE UUID 可以自己產生嗎?
可以。
正式產品不要所有專案都照抄:
6E400001...
可以建立自己的:
128-bit UUID
例如:
a7214200-5a62-4a48-86b8-a1d0c48f6a10
Service:
a7214200...
LED Characteristic:
a7214201...
Relay:
a7214202...
Sensor:
a7214203...
這會讓系統設計更清楚。
六十九、ESP32 BLE 完整資料流
手機控制:
Phone
│
│ BLE WRITE
│ "R"
▼
RX Characteristic
│
▼
onWrite()
│
▼
pendingCommand
│
▼
loop()
│
▼
processCommand()
│
▼
GPIO 26
│
▼
Relay ON
狀態回報:
Relay ON
│
▼
createStatus()
│
▼
"LED=OFF,RELAY=ON"
│
▼
TX Characteristic
│
▼
notify()
│
▼
Phone
七十、本章系統架構
Smartphone
BLE Client
│
┌────────┴────────┐
│ │
│ WRITE │ NOTIFY
▼ ▲
RX Characteristic TX Characteristic
│ │
└────────┬────────┘
│
▼
BLE Service
│
▼
ESP32 BLE Server
│
┌────────┴────────┐
│ │
▼ ▼
GPIO 2 GPIO 26
│ │
▼ ▼
LED Relay
七十一、Bluetooth Classic 系統架構
Android Phone
│
│ Bluetooth SPP
▼
BluetoothSerial
│
▼
SerialBT.read()
│
▼
processCommand()
│
├──────────────┐
▼ ▼
GPIO 2 GPIO 26
│ │
▼ ▼
LED Relay
七十二、BLE Server 建立順序
程式中的 BLE 初始化順序可以整理成:
BLEDevice::init()
│
▼
createServer()
│
▼
createService()
│
▼
createCharacteristic()
│
├── RX WRITE
│
└── TX READ / NOTIFY
│
▼
setCallbacks()
│
▼
service.start()
│
▼
Advertising
│
▼
等待 Client
這個順序非常重要。
七十三、BLE 常用指令整理
| 功能 | 程式 |
|---|---|
| BLE 初始化 | BLEDevice::init() |
| 建立 Server | BLEDevice::createServer() |
| 建立 Service | createService() |
| 建立 Characteristic | createCharacteristic() |
| Read | PROPERTY_READ |
| Write | PROPERTY_WRITE |
| Notify | PROPERTY_NOTIFY |
| 設定資料 | setValue() |
| 通知手機 | notify() |
| 啟動 Service | start() |
| Advertising | startAdvertising() |
| 接收資料 | onWrite() |
七十四、Bluetooth Classic 常用指令整理
| 功能 | 程式 |
|---|---|
| Library | #include <BluetoothSerial.h> |
| 建立 Bluetooth Serial | BluetoothSerial SerialBT |
| 開始 Bluetooth | SerialBT.begin() |
| 是否有資料 | SerialBT.available() |
| 讀取 | SerialBT.read() |
| 傳送 | SerialBT.write() |
| 傳送文字 | SerialBT.print() |
| 傳送一行 | SerialBT.println() |
七十五、BLE 名詞總整理
| 名詞 | 意義 |
|---|---|
| BLE | Bluetooth Low Energy |
| GATT | Generic Attribute Profile |
| Server | 提供 Service / Data |
| Client | 連線並使用 Server |
| Service | 一組 BLE 功能 |
| Characteristic | 實際資料單位 |
| UUID | Service / Characteristic 識別碼 |
| Read | Client 讀取 |
| Write | Client 寫入 |
| Notify | Server 主動通知 |
| Advertising | Server 廣播自己存在 |
| Scan | Client 搜尋 BLE Device |
七十六、Bluetooth Classic 與 BLE 最容易搞混的地方
Classic Serial
可以想像:
一條無線序列線
BLE 通訊架構
不要想成只有:
TX
RX
它真正的架構是:
Service
Characteristic
Property
UUID
GATT
BLE UART 只是:
利用 BLE Service + Characteristic 模擬 UART 通訊模式。
理解這一點後,未來學習:
BLE Sensor
BLE HID
BLE Beacon
BLE Mesh
會容易很多。
七十七、本章實作成果
完成本章後,手機可以直接控制:
LED ON
LED OFF
Relay ON
Relay OFF
並取得:
LED=ON,RELAY=OFF
狀態。
而且:
不需要 Web Server
不需要 Router
不需要 Internet
手機直接:
Bluetooth
↓
ESP32
即可控制。
七十八、第 11~14 章的無線網路學習路線
第 11 章
ESP32
↓
Wi-Fi
↓
Router
↓
IP Address
第 12 章
Browser
↓
HTTP
↓
ESP32 Web Server
↓
LED / Relay
第 13 章
DHT11 / DHT22
↓
ESP32
↓
JSON API
↓
Fetch / AJAX
↓
Web Dashboard
第 14 章
Phone
↓
Bluetooth Classic / BLE
↓
ESP32
↓
LED / Relay
因此 ESP32 現在已經掌握兩大無線通訊技術:
Wi-Fi
+
Bluetooth
七十九、本章重點整理
完成本章後,應掌握以下觀念。
1. ESP32 Bluetooth 有 Classic 與 BLE
Bluetooth Classic
BLE
2. 原始 ESP32 支援 Classic + BLE
但:
ESP32-C3
ESP32-S3
主要使用:
BLE
不支援 Classic SPP。
3. Bluetooth Classic 可以使用 BluetoothSerial
BluetoothSerial SerialBT;
4. Bluetooth Classic SPP 類似無線 UART
SerialBT.read();
SerialBT.print();
5. BLE 使用 Server / Client
本章:
ESP32 = BLE Server
Phone = BLE Client
6. BLE 使用 Service
UART Service
7. BLE 使用 Characteristic
RX Characteristic
TX Characteristic
8. UUID 用來識別 BLE 功能
例如:
Service UUID
Characteristic UUID
9. WRITE 用於手機控制 ESP32
Phone
↓
RX WRITE
↓
ESP32
10. NOTIFY 用於 ESP32 回傳狀態
ESP32
↓
TX NOTIFY
↓
Phone
八十、常見問題 FAQ
Q1:ESP32-C3 可以使用 BluetoothSerial.h 嗎?
不適合。
Bluetooth Classic SPP 主要只有原始 ESP32 支援。
ESP32-C3 應使用:
BLE
Q2:ESP32-S3 可以跑本章 Classic 程式嗎?
不行。
ESP32-S3 支援 BLE,但不支援 Bluetooth Classic。
Q3:ESP32-WROOM-32 可以同時使用 Wi-Fi 和 Bluetooth 嗎?
ESP32 本身同時整合 Wi-Fi 與 Bluetooth,可以設計同時使用兩種無線功能的系統。
但兩者會共用晶片資源及 2.4 GHz 無線環境,因此大型專案仍應注意:
- RAM
- Task
- Timing
- RF Coexistence
- Power
Q4:iPhone 建議用 Classic 還是 BLE?
一般 ESP32 手機控制專案:
建議 BLE。
Apple 對 BLE 提供 Core Bluetooth 開發架構,而 Classic 自訂配件通訊涉及不同的配件支援模式。
Q5:BLE 一定要 Internet 嗎?
不用。
BLE 可以:
手機
↕
ESP32
直接通訊。
Q6:BLE 一定要 Wi-Fi Router 嗎?
不用。
這就是它與前面 Web Server 最大的差異之一。
Q7:BLE 可以傳 Sensor Data 嗎?
可以。
例如:
Temperature
Humidity
Pressure
Battery
Light
都可以建立 Characteristic。
Q8:BLE 可以控制 Relay 嗎?
可以。
本章就是透過:
RX Write Characteristic
把命令傳給 ESP32。
Q9:BLE UART 真的是 UART 嗎?
不是。
它是:
BLE GATT
+
Service
+
RX / TX Characteristic
模擬 UART 使用體驗。
八十一、結語
ESP32 的價值並不只是:
GPIO 多
CPU 快
RAM 比 Arduino UNO 多
真正讓 ESP32 成為 IoT 核心開發平台的重要原因之一,就是它整合了:
Wi-Fi
+
Bluetooth
前面我們已經利用 Wi-Fi 建立:
ESP32 Web Server
Web Dashboard
Sensor API
這一章則進一步利用:
Bluetooth Classic
+
BLE
讓手機可以不經 Router,直接控制 ESP32。
Bluetooth Classic 架構:
Phone
↓
SPP
↓
BluetoothSerial
↓
ESP32 GPIO
BLE 架構:
Phone BLE Client
│
▼
ESP32 BLE Server
│
▼
Service
│
├── RX Characteristic
│
└── TX Characteristic
│
▼
GPIO
│
├── LED
└── Relay
手機傳送:
1
0
R
r
S
即可完成:
LED ON
LED OFF
Relay ON
Relay OFF
Status
這代表我們已經建立了一套真正的:
ESP32 Bluetooth Wireless Control System
更重要的是,學會:
BLE Server
BLE Client
Service
Characteristic
UUID
Read
Write
Notify
之後,就不只可以控制 LED。
未來可以直接擴充成:
ESP32 BLE 溫溼度計
ESP32 BLE 電子鎖
ESP32 BLE Robot
ESP32 BLE 遙控器
ESP32 BLE Sensor
ESP32 BLE 設定工具
ESP32 BLE Wi-Fi Provisioning
這也是 ESP32 從單純的 MCU 控制板,進一步成為:
Wireless Embedded IoT Platform
的重要一步。