Skip to main content
For the complete documentation index, see llms.txt.

Hubble Network developer documentation: integrate Bluetooth devices with terrestrial and satellite connectivity.

Hubble Connect

Convert your mobile device into a scanning gateway on Terrestrial Network, for device testing and closed-loop connectivity in Sandbox.

Test with Hubble Connect​

Detect any test device successfully broadcasting on the Hubble protocol and registered with your organization with the Hubble Connect mobile app.

Hubble Connect app is required to retrieve data in Sandbox.

Supported Mobile OS​

Mobile OSMinimum VersionForeground ScanningBackground Scanning
iOSRequires iOS 15.0 or later.Continuous.Requires "always allow" permission and active login. Typical scan interval: 30 min.
AndroidRequires Android 11 or later.Continuous.*Requires "background scanning" permission enabled in app settings.* Typical scan interval: 30 min.

*Android scanning includes a brief periodic refresh every several minutes to comply with OS-level scan throttling.

Login​

Use your same Hubble Dashboard credentials to authenticate with Hubble Connect.

Features​

Scan for Bluetooth Devices​

View any Bluetooth® Low Energy (LE) device beaconing in proximity.

  • Continuous scanning for local Bluetooth advertisements when app is in the foreground.
  • Toggle "Show only Hubble Devices" to filter results.
  • Pause scan to freeze results, and resume to get the latest device data.

Test Case 1: Is your device beaconing on the Hubble protocol? Is the advertising packet correctly formatted for Terrestrial Network?

On "Scan", toggle "Show only Hubble Deviecs" and check if your device is detected.

View Your Devices & Packet Data​

Use "My Devices" to view decrypted devices in scanning range that belong to your organization.

  • Hubble decrypted the ephemeral device ID (EID) from the Bluetooth advertisement to determine if the device is one that you own.
  • Click on a device to see the complete JSON data packet, and click "Refresh" for the next snapshot (subject to the advertising interval).

Test Case 2: Can Hubble successfully decrypt your packet? Are you using the advertisement retrieval function in the Device SDK correctly, and are you maintaining time on the device?

Devices on "My Devices" only appear after a roundtrip to the Hubble backend to decrypt the payload and determine if this device belongs to your organization.

Test Case 3: Are you successfully sending custom payloads?

We return the complete JSON payload for your packet. A packet's decrypted payload in returned in Base64 format.

Data on My Devices will not refresh if scanning is paused on "Scan".

Settings​

  • View your user and organization information.
  • View app release version.
  • View Product Terms & Conditions, and Hubble's Privacy Policy.
  • This is where you can log out.
  • You may permanently delete your account.