Skip to main content

LoRaWAN integration

Battery-powered LoRaWAN sensors extend BACnet-heavy buildings with affordable IAQ, leak, and occupancy coverage. CONTEXUS consumes network-server webhooks or MQTT feeds into Open IoT Hub — see Open IoT Hub for supported use cases.

Network server integration

  • HTTP webhooks (uplink JSON) from ChirpStack or TTS
  • MQTT broker bridge — topic patterns documented per vendor
  • Per-tenant application keys when multi-tenancy is enabled

Payload decoders

Register JavaScript decoders (Cayenne LPP, vendor binary, or custom) that output normalised metrics. Version decoders so field firmware updates do not break historical charts.

# Example webhook test against local stack (adjust URL + token)
curl -sS -X POST http://localhost:9001/api/iot/lorawan/uplink \
  -H 'Content-Type: application/json' \
  -d '{"devEUI":"0102030405060708","fPort":2,"data":"AQIDBA=="}'

Provisioning workflow

  1. Create tenant application in the network server.
  2. Import DevEUIs and root keys (or participate in OTAA join).
  3. Map device profiles (class A/B/C, ADR, region).
  4. Bind decoded metrics to dashboard widgets — start from gallery IAQ layouts.

Coverage planning

Indoor gateways every 30–50m in concrete-heavy buildings; prefer private indoor gateways for hospital and campus sites. Keep downlink usage minimal to preserve battery life unless actuators require class C.

Operations

Monitor join success rate, spread factor distribution, and missed uplink counters. Persist join logs in PostgreSQL (localhost:5433 via compose) for support tickets.

Next steps

Explore a running stack, review the open source repositories, estimate ROI for a deployment, or talk with the CONTEXUS team about integration and licensing.

Module licensing details are summarised on /licensing. Browse reference dashboards in the gallery.