Bluetooth แบบคลาสสิกเทียบกับ BLE

Bluetooth comes in two flavors that share a name but behave very differently. Picking the right one shapes your whole IoT project. 📡

Classic Bluetooth keeps a steady connection open, like a wireless serial cable. It is great for streaming audio or a constant flow of data.

BLE, or Bluetooth Low Energy, wakes up, sends a tiny burst, and sleeps again. That on-off rhythm is why it barely touches your battery.

Classic keeps the radio busy and drains cells fast. BLE can run a sensor for months on a coin cell because it stays quiet between short messages.

Classic moves big continuous streams well. BLE is built for small, occasional values like a temperature reading, not for sending music or video.

Classic Bluetooth often uses SPP, the Serial Port Profile. To your code it feels exactly like a normal serial stream you already know.

BLE does not stream a line of text. Instead it exposes named slots called characteristics that a phone can read or write on demand.

Modern iPhones only talk to BLE from hobby boards, not Classic SPP. If an iOS app must connect, BLE is your only real choice.

The ESP32 is generous: it supports both Classic Bluetooth and BLE. So you can pick whichever profile fits the job you are building.

Need constant streaming or a wireless serial swap? Reach for Classic. Need low power and phone-friendly control? Choose BLE every time.

Both reach roughly ten meters indoors. The real difference is not distance but power and how the data is shaped and delivered.

You want a coin-cell sensor that a phone reads now and then.

Classic streams steadily; BLE sips power with small bursts and friendly characteristics. For phone-controlled IoT, BLE on the ESP32 wins. 🎉