ESP32 Wi-Fi and Bluetooth Gateway Integration | Obeita
This configuration is proposed for assessment. Confirm interfaces, components and performance for your specific project.
Connect a small group of IP devices or a Bluetooth SIG Mesh network through an ESP32 gateway with a wired LAN connection. The two firmware roles address different jobs: providing Wi-Fi access for nearby equipment, or carrying commands and reports between Mesh nodes and a host system.
Wi-Fi access for local equipment
STA, AP and combined STA/AP operation provide different deployment choices. A station joins an existing wireless network; an access point gives nearby devices a local connection. This design suits telemetry and configuration traffic rather than broadband routing. Client count and forwarding performance are part of the firmware selection and load test.
A separate Bluetooth Mesh firmware role
The Bluetooth path uses a PB-series module and AT-command exchange to connect a SIG Mesh network. Uplink reports and downlink commands need an agreed message mapping. A Mesh gateway is not a universal bridge for arbitrary Bluetooth audio devices, BLE sensors or proprietary profiles; each endpoint must match the chosen Mesh model.
Where this architecture fits
Meter collection, building control, security nodes and irrigation controllers can share a compact gateway when their traffic and protocol roles are defined. Obeita can scope network provisioning, command routing and enclosure integration around the selected equipment. The development path includes Ethernet bring-up and flashing/debug access; Mesh demonstrations alone do not establish application interoperability.
Proposed design configuration
These are configuration inputs for development; the final assembly, firmware and acceptance tests define the delivered specification.
| Item | Configuration |
|---|---|
| Processor | ESP32 platform |
| Wired link | One LAN port |
| Wi-Fi | 802.11 b/g/n; STA / AP / STA+AP roles |
| Bluetooth path | PB-series module; SIG Mesh; AT-command exchange |
| Provisioning | SmartConfig / AirKiss concepts; selected firmware to be confirmed |
| Development access | Flashing and Ethernet development interfaces |
Project questions
Can Wi-Fi gateway and Bluetooth gateway firmware be treated as the same feature?
No. They are separate operating roles. Select the IP forwarding path or the Mesh message path first; combined operation requires a specific firmware design.
What information is needed for a Mesh pilot?
Provide the node/module type, Mesh model, provisioning method, uplink fields and downlink commands. A successful module link must then be tested with the actual application.
Plan this project
Send the Wi-Fi client count or Mesh node list, message examples and LAN connection requirements so we can choose the appropriate gateway role.