ChirpStack Integration
Connect your ChirpStack network server to DataKubo in minutes. This guide covers HTTP integration setup, tenant mapping, and troubleshooting.
Prerequisites
- A DataKubo account with an API key (sign up)
- ChirpStack v4 with at least one device provisioned (v3 payloads are not supported)
- Network connectivity between ChirpStack and
api.datakubo.com
Step 1: Create an HTTP integration
In your ChirpStack dashboard:
- Navigate to Applications → Your Application → Integrations
- Click Add and select HTTP
- Configure the integration:
| Field | Value |
|---|---|
| Event endpoint URL | https://api.datakubo.com/api/v1/ingest/water-consumption |
| Headers | X-API-Key: your_api_key |
| Encoding | JSON |
- Enable the Up event type (device uplinks)
- Click Submit
Step 2: Verify tenant mapping
DataKubo uses the tenantName field from ChirpStack payloads to identify your organization. Ensure your ChirpStack tenant name matches the one configured in your DataKubo settings.
{
"deviceInfo": {
"tenantName": "your-tenant-name",
"devEui": "a1b2c3d4e5f60001"
}
}💡
You can find your tenant name in Settings → Organization in the DataKubo admin panel.
Step 3: Test the connection
Trigger a device uplink (or wait for the next scheduled transmission) and check:
- ChirpStack — Integration events tab should show a successful HTTP POST
- DataKubo — The device should appear in your admin dashboard under Devices
Troubleshooting
| Issue | Solution |
|---|---|
| 401 Unauthorized | Check your API key in the HTTP integration headers |
| Device not appearing | Verify the tenantName matches your DataKubo organization |
Readings show 0 m³ | The device profile codec must output cumulativeFlowM3 (or cumulativeFlowLiters) — see the supported fields |
Next steps
- Webhook Integration — full payload format reference
- API Reference — query ingested data via API