BLE, Wi-Fi and legacy device connectivity development

Obeita helps equipment manufacturers and integrators connect existing devices and develop defined wireless data paths. We scope the device interface, protocol and host application together, then implement and test the agreed hardware and firmware. Start with one device, one connection route and clear acceptance conditions.

BLE and Wi-Fi integration

For a BLE application, identify the peer devices, central/peripheral roles, required services and characteristics, pairing and provisioning workflow, payload timing and reconnection behavior. These inputs establish the GATT or other profile work a new project needs.

For Wi-Fi, define station or access-point roles, network provisioning, destination service, authentication requirements and behavior when the connection drops. If multiple radios must run together, agree that combination and its test conditions separately.

The ESP32 gateway case separates Wi-Fi/IP access from a Bluetooth SIG Mesh path. It provides a Mesh integration reference; compatibility with arbitrary BLE GATT devices needs separate assessment. The WS63/Hi3863 wireless-module case covers host and wireless-module integration, with SLE, Wi-Fi and BLE as qualified platform directions rather than a promise of simultaneous operation.

Keep the existing device protocol meaningful

For serial or RS485 equipment, review the device model, bus settings, request/response frames, available power and target network. Physical connection, protocol mapping, gateway firmware and host-side integration are checked separately. A working serial link must still carry the right data and commands for the application.

Related delivered examples include serial-to-Ethernet and cellular DTU adaptation, SLE wireless RS485 integration and sub-GHz serial-radio integration. Uplink choices, node layouts and wireless bridge behavior remain specific to the selected configuration.

What a scoped first stage can deliver

A bounded diagnostic conclusion or pilot connection on the agreed equipment.
Interface and configuration notes, message mapping, firmware changes and a test record as agreed for the task.
A defined next scope for source-code handover, enclosure work, site deployment or production where required.

Acceptance should identify device and firmware versions, message types, data volume, network conditions and recovery behavior. Test missing peers, interrupted links and power cycling where relevant. Range, throughput, interoperability and simultaneous radio operation are validated for the intended environment rather than inferred from a module specification.

The linked cases are delivered customer projects whose hardware and software were physically tested to meet agreed requirements. New devices and installation conditions need their own scope and validation.

Share your connection requirements

Send interface manuals, sample messages, peer-device details, the target network or host API, available supply, enclosure constraints and installation conditions. Include required provisioning, security and recovery behavior so the pilot tests reflect the intended application.