Skip to main content
Bota devices support multiple connectivity methods for uploading recordings to the cloud. Each device manages its own network connections — selecting the best available path, handling failovers, and resuming interrupted transfers automatically.

​
Upload Methods

Bota supports four upload methods across its device lineup:

​
Bluetooth Sync

The device transfers recordings to the companion mobile app over Bluetooth Low Energy. The app then uploads to the Bota cloud. This is the default method for all devices and works in any environment where a paired phone is within range.
  • Supported on all devices
  • Typical range: ~10 meters
  • Transfer speed depends on Bluetooth connection quality

​
Wi-Fi Direct

The device creates a peer-to-peer Wi-Fi connection with the companion app — no Wi-Fi router needed. This provides faster transfer speeds than BLE, making it useful for syncing large recordings or batch transfers.
  • Supported on all devices
  • Faster than BLE; no network infrastructure required
  • Initiated from the companion app

​
WiFi Upload

The device connects to a Wi-Fi network and uploads recordings directly to the Bota cloud, bypassing the phone entirely. Wi-Fi credentials are configured through the WiFi Config Grant flow via BLE.
  • Supported on all devices
  • Lowest latency for direct upload when Wi-Fi is available
  • Ideal for desk setups, clinics, and offices

​
4G Upload

The device uses its built-in cellular modem to upload recordings directly to the cloud. No phone or Wi-Fi needed — the device operates fully independently.
  • Supported on Bota Pin and Bota Pin Pro
  • Works anywhere with cellular coverage
  • See Cellular Mode for data management and configuration

​
Device Support Matrix

​
How Connectivity Works

Devices self-manage their network connections based on configured preferences. You control the behavior through device settings — the device handles the rest.

​
Configuration

Upload behavior is configurable per device via the Update Device endpoint:

​
Automatic Failover

When the preferred connection is unavailable, the device falls back to the next option in upload_network_preference. For example, with ["wifi", "cellular", "ble"]:
  1. Try WiFi — if connected and reachable, upload over WiFi
  2. Fall back to 4G — if WiFi is unavailable or fails
  3. Fall back to Bluetooth — wait for phone to come in range and sync
Failover is automatic and transparent. The device resumes interrupted uploads when connectivity returns.