ChirpStack integration for DeviceChain
If your LoRaWAN sensors already report to a ChirpStack v4 server, DeviceChain can be the place the readings go. ChirpStack forwards each uplink over HTTPS, decoded by its codec or by a payload decoder on the DeviceChain device profile, and DeviceChain stores the values as ordinary measurements, so they appear in history, live state, dashboards and rules like any other reading. The device never connects to DeviceChain.
- Read None
- Write None
- Subscribe Partial
How it is wired
An integration is a resource of a tenant. You create one in the console with the sender type ChirpStack v4, scope it to the device types it may reach, and copy its bearer token. The token is generated by the server, shown once, and stored only as a keyed digest.
In ChirpStack you add the HTTP integration to an application, set the payload encoding to JSON, point the event endpoint at the integration's URL and send the token in an Authorization header. A Protobuf integration is refused, and the message names the setting to change.
What the platform reads
Without a payload decoder on the device's profile, the platform stores the values the network server decoded, so the device profile in ChirpStack needs a JavaScript payload codec; without one, ChirpStack sends the raw frame and no decoded object, and the uplink is counted as undecoded instead of stored. With a payload decoder on the profile, DeviceChain decodes the frame itself, and what the network server decoded is not stored.
Uplinks are read, and so are the ack and txack events that settle confirmed downlinks. Join and status events go to the same URL and are answered with 204 and ignored. The message time is the time ChirpStack reports, or the time the platform received it when that field is absent.
Matching devices
You add each device in DeviceChain with its DevEUI as a lorawan.deveui alias. A device outside the integration's scope, or no device at all, means the message is not stored, and an unknown identifier is listed for you to add rather than created automatically.
Commands
When the operator switches LoRaWAN downlink on, a published lorawan_downlink connector links the integration to its ChirpStack server, and a command to a device with a lorawan.deveui alias is queued there as a downlink. Its parameters are the raw port and payload, or typed values that an encoder on the command definition turns into bytes.
An unconfirmed downlink succeeds when the network server queues it, which is not an acknowledgement from the device. A confirmed downlink waits for the device to acknowledge it; with no acknowledgement by its deadline, the outcome is unknown.
Trust
Treat the bearer token like a password for the whole fleet: an integration token speaks for every device of its scoped types that carries an alias for it. Scope an integration narrowly, use one per network server or fleet, and rotate the token if it may have been exposed. There is no payload signature, so the transport must be TLS.
What it does not do.
- LoRaWAN downlink is off unless the operator switches it on. Until then, a command to a device that last reported through an integration is accepted and then fails, with COMMAND_TRANSPORT_UNSUPPORTED, instead of waiting until it expires.
- Join, status and location messages are acknowledged and ignored.
- Only numbers and booleans become readings; strings and nulls in the decoded object are skipped. A message that arrives while the tenant is over its ingest allowance is answered with 202 and not stored, which is why the matrix marks subscribe as partial.
Inbound integrations: ChirpStack v4 → · Transport matrix → · All integrations →