Release Notes
Stay up to date with the latest changes to our Cloud API and Device SDK.
2026-09-25
Community: SparkFun ESP32-C6 Thing Plus Guide
SparkFun has published a guide for bringing up the SparkFun Thing Plus - ESP32-C6 on both Hubble networks: Terrestrial and Satellite!
The guide specifically walks through the sat-dual-stack ESP-IDF sample end to end: provisioning a device key in Dash, flashing and configuring via idf.py menuconfig, and provisioning satellite orbital parameters over Bluetooth LE before the device transmits.
🚀 Go further: Sign up or log in then follow along with SparkFun's Hubble Network guide. Consult supported SoCs and review Satellite Quick Start if you're bringing up a different board onto the Satellite Network.
2026-09-23
Satellite Network is Generally Available
The Hubble Satellite Network is now generally available (GA). Transmit low-bandwidth telemetry from areas with no terrestrial coverage with the world's first satellite network for Bluetooth devices.
- Your device transmits directly to a low-Earth-orbit Hubble satellite using the same 2.4 GHz Bluetooth® Low Energy radio it already has — no dedicated satellite hardware — and packets arrive through the same Cloud API, webhooks, and Dashboard you already use for Terrestrial Network.
GAmeans the satellite path is production-supported end to end: stable firmware in Device SDK v3.0, satellite data in the Cloud API, at least one transmit opportunity per day, and delivery typically within 6 hours of a pass.
🛰️ Get started: Try Dash Quick Start for a Hubble-native bring-up flow on a supported developer kit. Then go deeper with the Satellite Quick Start for custom hardware, local Pluto SDR validation, and pass prediction.
New to Satellite Network? Start with how the Satellite Network works, then confirm your SoC, transmit power, and antenna against the Compatibility requirements.
2026-09-16
Community: TI CC2755P10 Satellite Tutorial
Novel Bits has published a deep-dive tutorial on reaching the Satellite Network from Texas Instruments' CC2755P10!
TI's CC2755P10 is an ideal platform for testing satellite transmission using its integrated +20 dBm power amplifier to close the satellite link with no external RF front end. The tutorial builds a real battery-and-temperature payload on the sat-dual-stack sample, covers pass provisioning and Direct Test Mode debugging, and includes on-board power measurements for both the terrestrial and satellite transmit paths.
✅ Go further: Follow along with Novel Bits' CC2755P10 tutorial, then review Transmission Guidance for the satellite link budget requirements referenced in the post.
2026-08-27
Try Hubble Live Free for 45 Days
You can now activate a 45-day free trial of the full Terrestrial Network directly from your Hubble Sandbox. Register up to 100 devices to see real-world detections from our global network of 100M+ gateways.
You will not be charged during the trial, and it does not auto-convert to a subscription. Free trial activation requires a verified business email and a payment method on file to prevent abuse. At the end of your trial, your organization reverts to Sandbox unless you choose to upgrade. Only one trial per organization.
🚀 Get started: Sign up or log in and select "Try Hubble Live" from your Sandbox organization. To keep Live Network access after day 45, compare Growth and Scale subscription plans on the Pricing page in Dash.
Get outside the Sandbox, which operates as a closed-loop test environment: you only receive device transmissions from your own gateways (for example, the Hubble Connect mobile app). The free trial opens your devices up to the Live Network, so you can validate device performance in the wider world.
2026-08-18
Test Devices in Staging Orgs
Customers with a paid plan can now create a standalone Staging Org — a fully siloed environment with its own org ID, user access, and API credentials — to test devices without touching production data. Staging Orgs get the same Live Network access as your production account and support up to 100 non-billable test devices.
- Move devices between your Production and Staging Orgs at any time, in Dash or via the Update Device API.
- Because the device environment is now determined by org, not by tag, the
_envplatform tag is now ignored (see Platform Tags and Custom Tags).
🧪 Get started: Create up to 2 standalone staging orgs from your production account using the in-dash flow. Start by logging in, or review the Sandbox & Staging Orgs guide for more detail.
2026-08-10
Download Hubble Device SDK v3.0
The Hubble Device SDK v3.0 release is now available (full Release Notes on Github).
SDK v3.0 is a major release that brings your end devices onto the Satellite Network, with end-to-end bring-up guides and sample apps for dual-stack devices (Terrestrial and Satellite). With this release, the Satellite Network graduates to a stable, production-ready SDK, alongside new platform and board support across Zephyr, FreeRTOS/TI, and ESP-IDF.
- Use Direct Test Mode (DTM) for continuous beaconing during RF bring-up and certification.
- Implement pass prediction on your endpoint using orbital parameters for efficient, scheduled transmission that extends device battery life.
🚀 Get started: Download SDK v3.0 (.zip) or view the open source repository hubble-device-sdk directly on Github.
Review the SDK Reference for the v3.0 Functions API documentation.
2026-08-06
New Satellite API: Ephemeris and Pass Prediction
Two new endpoints bring Satellite Network data to the Cloud API:
- Get Satellite Ephemeris returns the same TLE and orbital parameters the Hubble Device SDK uses on-device to compute transmission windows, so your backend can access the exact data your firmware relies on.
- Get Upcoming Satellite Passes predicts pass timing — rise, culmination, and set — for a point or a bounding area, useful for powering a frontend or estimating upcoming coverage without replicating pass-prediction logic yourself.
🛰️ Try it: Both endpoints require the new read-satellites API scope. Review Authorization Scopes to add it to an existing token, or create a new one. Manage in Dash at Developer Tools > API Tokens.
2026-07-21
Normalized, Shorter API Routes
API endpoints now live under shortened, canonical https://api.hubble.com/v1/org/... and /v2/... URL paths. This rollout is consistent with our versioning policy: major, backwards-incompatible changes will ship as new version paths (e.g. v2) going forward rather than breaking existing integrations in place.
🔗 What to do: No action required for existing integrations. Legacy /api/... paths continue to work. For new code, prefer the shorter, versioned paths shown in each endpoint's reference, for example Register New Devices.
2026-07-14
Send Test Pings to Your Webhook
You can now trigger an on-demand test delivery for any configured webhook endpoint. It uses the same request shape as live delivery (a sample JSON packet batch, plus HTTP-X-HUBBLE-TOKEN when a secret is configured) so you can confirm connectivity, authentication, and response handling before real packet data starts flowing.
🪝 Try it: Review Send a Test Webhook (requires the write-webhooks API scope).
2026-07-02
See Device Encryption Details
Encryption mode, counter source for ID rotation, and period exponent (for IN100 / AES-128-EAX type devices) now appear in the Get Device API response, so you can confirm a device's encryption configuration after registration. Check the encryption mode directly on the Device Details page in your Dashboard for any encrypted device.
🔒 Why it matters: Useful for verifying encryption for the device registered to your Hubble organization matches the encryption configuration set the Hubble Device SDK.
2026-06-23
Use Granular API Scopes in Dash
Manage API token permissions directly from the Dashboard: create or edit tokens with Global access, use-case scoped presets (e.g. "Device Manufacturer", "Manage Webhooks", "Get Device Data", more), or a fully custom scope selection. Set or update the exact expiration date with the new calendar picker. View a token's scopes at a glance from the token list.
🔑 Try it: Log in and navigate to Developer Tools > API Tokens. Review Authorization Scopes for the full scope reference.
2026-05-20
Set Device Install Location
The install_location field (lat, long, location_name) is now added to all our device endpoints. Set it on device registration or update, and read it back from List Devices / Get Device responses. Send the (0, 0) "Null Island" coordinate pair to clear a previously set location.
🛰️ Why it matters: If you have a fixed-position device on Satellite Network — for example, an asset transmitting sensor data as a custom payload — assigning an install location allows efficient pass prediction, i.e. to know exactly when a satellite is overhead so that the device can transmit.
New to Satellite Network? Start with how the Satellite Network works.
📍 Learn more: Register New Devices and Update Device.
2026-05-18
Live Network Self-Serve Upgrade
You can now upgrade to the full Terrestrial Network and access global coverage for your devices by subscribing to a monthly plan directly from your Hubble Sandbox. Navigate to the Pricing page to compare platform features for Growth and Scale subscription tier. Unlock volume discounts for scale. Cancel any time.
💳 Get started: Log in and navigate to the Pricing page to view plans and subscribe. Contact us if you're interested in Enterprise.
2026-05-04
Export Data from the Dashboard
Hubble is built API-first, so you can always use the API or Hubble CLI to access your data programmatically. But sometimes you just want a quick CSV export of what you're looking at on screen.
Now you can download your device data directly from the Dashboard map view and packet history table:
- Device Detail: for a specific device, download up to 30 days of structured packet location data from the Dashboard.
- Device list: from the Devices page, download your full device inventory (including active, inactive, and registered devices that have never sent a packet) with device name, tags and most recent packet snapshot.
📊 Try it: Log in to your Hubble Dashboard and open any device's detail view to export packet data, or visit the Devices page to download your full device inventory.
2026-04-27
Download Hubble Device SDK v2.0
The Hubble Device SDK v2.0 release is now available (full Release Notes on Github).
SDK v2.0 adds a "timeless" protocol for the Terrestrial Network: devices can now generate encrypted BLE advertisement packets using device uptime as the counter source instead of UNIX time, removing the requirement for a time-aware, real-time clock (RTC) or time synchronization entirely (learn more about device encryption modes). This release also ships platform updates across Zephyr, FreeRTOS, and ESP-IDF, and several API refinements that constitute breaking changes from v1.0.
🚀 Get started: Download SDK v2.0 (.zip) or view the the open source repository hubble-device-sdk directly on Github.
Review the SDK Reference for the v2.0 Functions API documentation.
2026-04-24
Manage Devices in the Dashboard
The Hubble Dashboard now gives you more control over your devices:
- Register a new device directly in Dash: click "Add a Device" and select "I just need a device key" to register a new device with user-defined encryption mode, then copy the base64 encoded key for provisioning.
- Edit device names, and promote devices between your Sandbox and Live environment from the Devices page — for a single device or in bulk edit actions.
✅ Why it matters: Hubble's platform is built API-first, and you can already register devices using the Hubble CLI. We're bringing these actions to the Dashboard. Log in to try it now.
2026-04-01
Device SDK Reference Docs Now on GitHub Pages
The Hubble Device SDK reference is now published at hubblenetwork.github.io/hubble-device-sdk, generated directly from the versioned SDK source.
📚 Why it matters: SDK documentation lives with the code so it's versioned per release. main and each release/* branch publish to their own subdirectory (for example /main/ or /release-1.0-branch/), so you can always reference the exact API surface for the SDK version you're building against.
🔗 Browse it: Find the latest SDK release from the Docs Site on Device SDK.
2026-03-10
Community: Nordic nRF54L15 Tutorial
Industry expert Novel Bits has published a step-by-step tutorial for integrating Nordic's nRF54L15 developer kit with Hubble Network, including instructions to transmit temperature sensor readings as a custom payload to the Terrestrial Network.
✅ Go further: Follow along with Novel Bits' Hubble Tutorial, then review the Sensor Widget guide to visualize your sensor data in your Dashboard.
2026-03-09
Device Detail View in Dashboard
The Hubble Dashboard now includes a Device Detail view, giving you granular visibility into individual device activity — not just the latest network detection, but a full picture of where your device has been and what it has reported.
📊 New granular detail unlocked: Hubble's platform is built API-first, and all packet data can be accessed through the open API. Dash unlocks quick access to device data and insight, including:
- Location Data: See your device's GPS location history over the past 7 days based on its advertising profile and network coverage.
- Network Activity: Visualize network detections over time to understand network performance given your device's beaconing logic.
- Packet History: Access a log of your device's packet data with complete packet contents, without needing to call the API.
- Sensor Widget: View automatically decoded sensor data from your custom payload for supported data types (temperature, humidity, battery, GPS, and more).
🚀 Get started: Log in to your Hubble Dashboard to explore Device Details, or review the Sensor Widget guide to start encoding payload data your Dashboard can decode.
2026-01-15
Hubble Connect Available on iOS and Android
The Hubble Connect mobile app is now available on both iOS and Android, converting your phone into a scanning gateway on the Terrestrial Network for closed-loop device testing in Sandbox.
📱 How to use: Download Hubble Connect and log in with your Hubble Dashboard credentials. Foreground the app to start scanning for nearby BLE devices and see decrypted packet data from devices registered to your organization. See the Hubble Connect guide for supported OS versions and test case walkthroughs.
2026-01-06
Download Hubble Device SDK v1.0
The Hubble Device SDK v1.0 is now available for download directly from the Docs site. This production-ready release provides everything you need to connect Bluetooth® Low Energy (BLE) embedded devices to the Hubble Terrestrial Network.
🚀 Get started: Download SDK v1.0 (.zip), or browse Sample Applications for ready-to-build examples on Zephyr, FreeRTOS, Espressif, and bare metal. View the the open source repository hubble-device-sdk on Github.
Review SDK Reference for Terrestrial Network to see exact Function API defines, parameters and examples.
2026-01-05
Sandbox Self-Serve Sign Up
Anyone can now sign up for a Hubble account to create your own Dashboard and bring your devices onto the network in a Sandbox environment — no additional approvals required. Get started today!
✅ Why it matters: Sandbox gives you a closed-loop testing environment to onboard devices, validate your firmware, build out the backend integration, and see live packet data transmitted by the network before choosing to update to the Live Network. Onboard your first device on the network in minutes with Dash Quick Start, or learn more about Sandbox and what's included with a free account.
2025-11-14
Import Hubble Cloud API Definition
We've published a public URL so that you can instantly import our API definition.
🚀 Why it matters: Get started with the Hubble Cloud API quickly by importing the YAML API file directly into your preferred developer environment (for example, Postman or Insomnia). API endpoints are grouped by resource.
2025-11-11
Register Your Devices with Custom Names and Tags
Streamline your device onboarding flow by assigning a custom name field and/or custom tags to devices at the same time that you register them to your Hubble organization.
✅ How to use: Every device that you register automatically has a Hubble UUID (device.device_id). To simplify mapping devices on your backend, you may also choose to populate the name field with a non-Hubble UUID. Similarly, you may tag devices with custom key:value pairs to organize how data is handled by your backend.
- Register New Devices now supports query parameters for custom name and custom tag arrays upon device creation.
- New endpoint Batch Update Devices allows you to update custom name and tag fields for multiple devices at the same time.
Learn more about Backend Implementation in our rollout process guide.
2025-10-30
Platform Tags and Custom Tags
Use tags to organize devices in your Hubble organization. Assign custom tag key:value pairs to your devices to sort and categorize them and their data. Filter packet data directly with Hubble-defined platform tags, which assigns devices to your "sandbox" environment or your "production" environment.
✅ How to use: Create and assign custom tags using the Update Device endpoint. New devices automatically get a default platform tag, which you can switch using this endpoint. A device can have up to 10 tags in total.
Review Update Device for example HTTP request, parameter definitions and response body.
2025-09-17
Webhook Retry with Exponential Backoff
If your server responds with a non-2xx status code, we will automatically retry webhook requests to the target URL using an exponential backoff strategy. This means the delay between retry attempts will increase over time.
🪝 Why it matters: Hubble maintains an "at least once" delivery system. The updated webhook retry logic enables your system to recover from temporary issues without being overwhelmed by repeated, rapid requests, ensuring more reliable data delivery. As always, you can use our API to backfill any data you may need.
2025-08-01
API Key Authorization Scopes
API Keys can now be created or updated with specific authorization scopes.
🚀 Why it matters: Limit token access by assigning read and/or write permissions per use case. Learn more on our Cloud API documentation.