Skip to content
YHubulu

Device Connect

Connect YHubulu hardware to your software in minutes.

Everything you need to pair YHubulu physical systems with Hubulu Cloud, your apps and your existing business systems.

Get startedTalk to an engineer

Architecture

How data flows

Each layer is secured and observable, from the sensor on the wall to the dashboard on your screen.

  1. 01

    Device

    Hubulu hardware with secure firmware & identity

  2. 02

    Connectivity

    Wi-Fi · BLE · LoRaWAN · Cellular

  3. 03

    Edge

    Local control, AI and offline buffering

  4. 04

    Hubulu Cloud

    Telemetry, rules, OTA, device registry

  5. 05

    Your software

    Apps, dashboards, APIs & webhooks

Quick start

Four steps from box to dashboard

  1. 1

    Power on & discover

    Switch on your YHubulu device. It advertises over Bluetooth LE (or joins your LoRaWAN gateway) and is ready to pair.

  2. 2

    Pair with the Hubulu app

    Scan the QR code on the device. The app transfers Wi-Fi or network credentials securely — no passwords typed on tiny screens.

  3. 3

    Provision to Hubulu Cloud

    The device receives a unique certificate-based identity and appears in your workspace with live telemetry.

  4. 4

    Connect your software

    Pull data through the REST API, subscribe over MQTT, or receive webhooks — and send commands back to the device.

For developers

Integrate with the tools you already use

Use our APIs and SDKs to read data and control devices from any application.

  • REST API — Query devices & history

    JSON over HTTPS with API keys or OAuth 2.0

  • MQTT — Real-time telemetry & commands

    TLS-secured topics per device and workspace

  • Webhooks — Event-driven integrations

    Signed payloads for alerts, state changes, OTA status

  • SDKs — Build apps faster

    JavaScript/TypeScript, Python, Kotlin & Swift

example.ts
// Subscribe to live readings from a Hubulu Sense device
import { HubuluClient } from "@yhubulu/sdk";

const hubulu = new HubuluClient({ apiKey: process.env.HUBULU_API_KEY });

const device = await hubulu.devices.get("sense-7f3a21");

device.on("telemetry", (reading) => {
  console.log(reading.temperature, reading.humidity);
});

// Send a command back to the physical device
await device.command("set_interval", { seconds: 60 });

Connectivity

The right network for every environment

TechnologyRangeBest for
Wi-FiIndoor / buildingHomes, offices, high-bandwidth devices
Bluetooth LE~10–50 mPairing, wearables, local control
ZigbeeMesh, building-wideSmart-home accessories
LoRaWANUp to ~10 kmFarms, utilities, remote sensors
Cellular (LTE-M / NB-IoT)National coverageMeters, vehicles, distributed assets

Security

Secure by design, at every layer

Unique device identity

X.509 certificates provisioned per device — no shared secrets.

Encrypted end-to-end

TLS 1.3 in transit, encrypted storage on device and in cloud.

Secure boot & signed OTA

Only firmware signed by YHubulu (or you, for OEM) can run.

Access control

Role-based permissions and audit logs for every workspace.

FAQ

Common questions

Do devices keep working without internet?

Yes. Hubs and Edge Gateways run automations locally and buffer data until connectivity returns, then sync to Hubulu Cloud.

Can I connect YHubulu devices to my own backend instead of Hubulu Cloud?

Enterprise and OEM licences support on-premise deployment and direct MQTT bridging to your own broker.

Can I connect third-party devices to Hubulu Cloud?

Yes. Any device that speaks MQTT or HTTPS can be provisioned, and the Edge Gateway bridges Modbus, CAN and RS-485 equipment.

How are firmware updates delivered?

Over the air, staged by device group, with automatic rollback if an update fails health checks.

Need help integrating?

Our engineers can help connect YHubulu devices to your ERP, billing, analytics or custom platform.

Talk to an engineerBrowse products