All-in-One LoRaWAN Gateway Integration
An all-in-one LoRaWAN gateway — also called a standalone gateway or embedded network server gateway — runs its own network server directly on the device, instead of relying on TTN or ChirpStack in the cloud.
That means the gateway itself decodes uplinks and manages device sessions, and it typically ships with a local web interface for integrations. Installers use these gateways when they want a self-contained deployment for a single site — no separate network server to host or maintain, just the gateway and the meters talking to it.
How it works with Datakubo
These gateways expose a local webhook or integration settings page in their admin interface. Point that webhook at Datakubo's ingest URL — the same webhook pattern used for ChirpStack and The Things Network — and readings flow straight into your branded portal. There is no intermediate network server to configure: the gateway is the network server.
Datakubo normalizes the payload on arrival regardless of which embedded network server sent it, so meters connected through an all-in-one gateway show up in the same fleet view as meters connected through ChirpStack or TTN.
Supported all-in-one gateway models
Datakubo works with any all-in-one gateway that can forward decoded uplinks over HTTP webhook. These are the models installers most commonly deploy:
| Model | Vendor | Notes |
|---|---|---|
| LPS8N | Dragino | Embedded network server with built-in HTTP/MQTT forwarding for outdoor or indoor sites. |
| UG65 / UG67 | Milesight | Indoor (UG65) and outdoor (UG67) gateways with a local network server and webhook integration. |
| Wanesy Edge | Kerlink | Edge network server aimed at private LoRaWAN deployments, with HTTP integration support. |
| RAK7268 / RAK7240 | RAK Wireless | Indoor (RAK7268) and outdoor (RAK7240) gateways that can run an embedded network server. |
How to set it up
Open your gateway's integration settings
In the gateway admin interface, find the webhook, HTTP push, or "third-party server" integration section — the exact name varies by vendor, but every embedded network server has one.
Point it at Datakubo's ingest URL
Paste Datakubo's webhook endpoint into the gateway's integration settings, the same way you would for a ChirpStack or TTN HTTP integration. Each meter auto-registers on its first uplink — no manual entry per device.
Let your clients see the data
Invite the community manager and residents to your branded portal. From then on, readings and alarms surface automatically — no separate network server for you to host.
Frequently asked questions
Do I need ChirpStack if my gateway has a built-in network server?
No. If your gateway runs an embedded network server — as Dragino, Milesight, Kerlink, and RAK all-in-one models do — the gateway itself already handles device sessions and payload decoding. You point its webhook directly at Datakubo instead of adding a separate ChirpStack or TTN layer.
What's the difference between a standalone gateway and a ChirpStack/TTN gateway?
A gateway used with ChirpStack or TTN is a "dumb" radio bridge — it forwards raw packets to a network server running elsewhere (self-hosted ChirpStack, or the TTN cloud). An all-in-one gateway runs that network server logic on the device itself, so there is no separate server to install or manage.
Can I mix an all-in-one gateway with meters connected through ChirpStack or TTN?
Yes. Datakubo ingests webhooks from ChirpStack, The Things Network, and embedded network server gateways through the same endpoint, and normalizes all of them into one fleet view. You can run a mix of network servers across different sites without splitting your portal.
Does Datakubo support Dragino, Milesight, Kerlink, and RAK gateways?
Yes. Any of these vendors’ all-in-one gateways with an embedded network server (for example the Dragino LPS8N, Milesight UG65/UG67, Kerlink Wanesy Edge, or RAK7268/7240) can forward decoded uplinks to Datakubo over its webhook integration.