Bluetooth Mesh
Understanding Bluetooth Mesh
Managed flooding is the core mechanism: every relay node re-broadcasts every new message it hears. The message cache (sequence number + source address) prevents duplicate forwarding. TTL (default 7) limits the maximum number of hops. This creates reliable, multipath propagation without routing tables or single points of failure.
Nodes are classified by features: Relay (forwards messages), Proxy (GATT-based bridge for phones), Friend (stores messages for sleeping Low Power Nodes), and Low Power Node (sleeps between polls). Models define behaviors: Generic OnOff, Light Lightness, Sensor, etc.
Group addresses: 16,384
TTL: 0-127 (default 7 hops)
Latency per hop: 20-50 ms
Message size: up to 380 bytes (segmented)
Security: AES-128 (network + application keys)
Mesh Technology Comparison
| Feature | BT Mesh | Zigbee | Thread |
|---|---|---|---|
| Routing | Flooding | AODV | MLE (IPv6) |
| Max nodes | 32,767 | 65,535 | ~250 |
| Phone provision | Yes (native) | Hub required | Border router |
| Primary use | Lighting | Home automation | Matter |
Frequently Asked Questions
How does it work?
Managed flooding on BLE advertising channels. Relay nodes retransmit. TTL limits hops. Message cache prevents duplicates. No routing tables.
Scale and latency?
32,767 nodes, 16,384 groups. 20-50 ms per hop. 5-hop network: ~100-250 ms. Directed forwarding (1.1) improves large networks.
BT Mesh vs Zigbee?
BT Mesh: flooding, phone-provisionable, lighting. Zigbee: routing, hub required, home automation. Both 2.4 GHz.