スマートホームには異なるクラスのBluetoothモジュールが必要
Unlike asset trackers or beacons that broadcast and sleep, smart home devices require sustained bidirectional communication, fast connection establishment, and interoperability with ecosystems like Apple HomeKit, Google Home, and Amazon Alexa. Selecting the wrong Bluetoothモジュール for a smart home product means failed certification, poor mesh reliability, or a device that disconnects when the user is in the next room. This guide covers the parameters that actually matter for smart home engineers.
プロトコルサポート：BLE 5.0+は必須
Modern smart home protocols impose specific Bluetooth requirements:
| Protocol | Min BLE Version | Key Requirement | Module Implication |
|---|---|---|---|
| Matter over Thread + BLE | BLE 5.0 | Advertising extensions, coded PHY | Must support 125 kbps long-range PHY |
| Apple HomeKit (BLE) | BLE 4.2+ | Secure pairing, data length extension | Hardware crypto accelerator recommended |
| Google Fast Pair | BLE 4.2+ | Eddystone, account-key rotation | Sufficient flash for key storage (≥64 KB) |
| Amazon Alexa BLE | BLE 4.2+ | GATT server with specific service UUIDs | Minimum 4 simultaneous GATT connections |
| Zigbee Green Power (combo) | N/A (separate radio) | Multi-protocol SoC | Dual-mode BLE + Zigbee/Thread chip |
接続レイテンシとメッシュスループット
In a smart home with 30–50 BLE devices, connection performance becomes critical. Two metrics separate consumer-grade from professional-grade modules:
- Connection establishment time: Time from advertising to encrypted connection. BLE 5.0 with coded PHY typically achieves 30–60 ms. Modules without optimized RF front-ends may take 100–200 ms, which feels sluggish for lighting or lock control.
- Simultaneous connections: Central devices (hubs, speakers, thermostats) must maintain multiple concurrent connections. A smart speaker acting as a Thread border router plus BLE hub needs 6–8 simultaneous connections. Verify the module’s supported connection count under real traffic load, not just the datasheet maximum.
For BLE Mesh networks (used in commercial lighting and sensor networks), the module must support proxy and relay roles. Mesh relay throughput degrades rapidly with hop count: expect 40–80 kbps at 3 hops with standard unicast messages. Larger payload messages should use segmented messages with acknowledged transport, which halves effective throughput but guarantees delivery.
フラッシュとRAM：隠れたボトルネック
Smart home firmware is growing fast. OTA update images for Matter-compatible devices typically require 200–400 KB of flash. Add Bluetooth stack (80–120 KB), application logic, TLS/crypto libraries, and device provisioning data, and total flash requirements reach 512 KB minimum.
| SoC Platform | Flash | RAM | Matter + BLE Feasible? |
|---|---|---|---|
| nRF52832 (Nordic) | 512 KB | 64 KB | Tight — requires optimization |
| nRF52840 (Nordic) | 1 MB | 256 KB | Yes — recommended platform |
| CC2652R (TI) | 352 KB | 80 KB | No — insufficient for full Matter |
| ESP32-C3 (Espressif) | 4 MB (external) | 400 KB | Yes — abundant resources |
| EFR32MG24 (Silicon Labs) | 1.5 MB | 256 KB | Yes — optimized for Matter |
| CYW20819 (Infineon) | 512 KB | 128 KB | Borderline — limited OTA headroom |
RF性能：混雑環境での共存
Smart homes are RF-hostile environments. Wi-Fi access points, microwave ovens, baby monitors, and neighboring BLE devices all compete for the 2.4 GHz band. Module RF performance directly determines whether a smart lock reliably connects from 5 meters or drops at 3 meters.
Key RF parameters to evaluate:
- Output power: Target +4 to +8 dBm for wall-plug devices (no battery constraint). For battery-powered sensors, +0 dBm is typically sufficient if the receiving hub or phone is within 10 m.
- Receiver sensitivity: -90 dBm minimum, -95 dBm preferred. Each 3 dB improvement in sensitivity effectively doubles the range. The difference between -90 and -97 dBm is the difference between covering a living room and covering an entire floor.
- In-band interference rejection: Test with a Wi-Fi access point transmitting at -30 dBm on an adjacent channel. Modules with poor selectivity show 10–15 dB desensitization under these conditions.
- Coexistence interfaces: For devices with both Wi-Fi and BLE (smart speakers, cameras), a hardware coexistence interface (PTA, 3-wire, or 4-wire) between the Wi-Fi and BLE radios prevents time-domain collisions. Without it, Wi-Fi traffic can cause 20–40% BLE packet loss.
消費電力：スリープ電流がバッテリー寿命を決める
For battery-powered smart home devices (door sensors, motion detectors, temperature/humidity sensors), the module’s sleep current is the dominant factor in battery life. These devices spend 99.9% of their time sleeping.
- Target sleep current: < 1.5 µA with RAM retention, < 0.5 µA in shutdown (no RAM). Nordic nRF52840 achieves ~1.1 µA in System ON idle; ESP32-C3 achieves ~0.7 µA in deep sleep.
- Wake-on-RF: Some modules support wake-on-pattern-match, scanning for a specific advertising pattern without waking the main MCU. This enables always-listening sensors at < 5 µA average current.
- Button cell feasibility: At 1 µA average current, a CR2032 (220 mAh) lasts approximately 25 years — well beyond the cell’s shelf life. The practical limit is usually set by BLE connection events: a sensor that connects daily to report and receive configuration changes adds ~10 µA average, still yielding 2+ years on a CR2032.
認証と事前認証
Smart home products face regulatory requirements across multiple regions:
- FCC (US): Module-level FCC certification simplifies product integration. Verify the module has modular approval (grants DO NOT require re-testing the host device if the module is used per its approved configuration).
- CE / RED (EU): Requires radio compliance testing. Pre-certified modules with RED compliance documentation reduce product-level testing to EMC only.
- Matter certification: Requires the module’s Bluetooth stack to pass the Matter interoperability test harness. Silicon Labs EFR32 and Nordic nRF52840 have the most mature Matter-over-BLE support.
Choosing the right Bluetoothモジュール for smart home integration requires looking beyond basic BLE specs. Protocol certification readiness, RF coexistence performance, and flash/RAM headroom for growing firmware requirements are the parameters that determine whether a smart home device ships on time — and works reliably after installation.