ChirpStack integration

Connect ChirpStack so LoRaWAN uplinks appear as telemetry on Autoconnecto devices.

Before you start

1. Device exists in Autoconnecto.
2. Device attribute lorawan.dev_eui (or integration.lorawan.dev_eui / integration.external_id) equals the ChirpStack DevEUI (hex, no separators preferred).

In Autoconnecto

1. Open Integrations → New integration.
2. Choose ChirpStack, name it, create.
3. Copy the HTTP endpoint URL.
4. Click Generate webhook secret and copy the value (shown once).
5. Click Start receiving uplinks (or Start on the detail page).

In ChirpStack

1. Open Applications → [your application] → Integrations.
2. Add HTTP.
3. Paste the Autoconnecto endpoint into Event endpoint URL(s).
4. Add header:
   • Name: X-Webhook-Secret
   • Value: the secret from Autoconnecto
5. Save.

Dry-run without ChirpStack

From the device SDK repo (examples/integrations/):

export TENANT_ID=… WEBHOOK_SECRET=… DEV_EUI=…
./chirpstack-webhook.sh

Uses chirpstack-uplink.sample.json (DevEUI must match the Autoconnecto device).

Verify

Send an uplink from a device. In Autoconnecto open the integration → Recent events — you should see success. Open the device → telemetry for decoded fields (e.g. from ChirpStack object).

Optional transform

On the integration detail page, add Transform steps (rename, scale, …) if you need to reshape keys after decode. Use Dry-run preview with a sample ChirpStack JSON before going live.

For custom decoding, enable Script transform (function transform(data, metadata) { … }) — runs after pipeline steps in a sandbox.

Auto-create devices

On create (or detail → Device matching), enable Auto-create device on first uplink. Unknown DevEUIs create a device with lorawan.dev_eui set. Leave off if you want only pre-provisioned devices.

Downlink

1. Open the integration → Downlink.
2. Enable downlink and enter ChirpStack API base URL + API token.
3. Save.
4. Enter Autoconnecto device ID, fPort, and hex payload, then Send downlink.

The device must already have lorawan.dev_eui set.

Rule Engine

On the integration → Downlink → Auto-downlink from telemetry, create a Rule Engine that queues a downlink when telemetry includes a hex key (default downlink_hex). Then bind that engine on Device Profile → Edit → Rule engine.

You can also author node integration_downlink via API (integrationId, payloadHex or payloadFromKey).