Human- understandable data
Once a device is joined and configured in a Chirpstack system, data is periodically sent from the device to the Chirpstack server. To minimise the bandwidth used, the messages are highly compressed. So the raw payload coming from a device needs to be decoded.
During the device profile creation, a decode function, in Javascript, should have been provided, to generate human-understandable information from the raw payload.
In Chirpstack, this information can be seen in the event section of a device page.
By clicking on the up button, the decoded payload can the seen in the object part of the data structure.
Sending Data to your solution
Chirpstack doesn’t include a data analytics engine. This means that Chirpstack cannot be the final piece of a full LoRa-based system, but only a pipe to receive LoRa data, decode it and send it to the final analytic engine.
In the Application Integration page, Chisptack provides natively integrations for analytics tools:
More details can be found on the official documentation:
Integrations - ChirpStack open-source LoRaWAN® Network Server documentation
Example: device data on the VeeaHub MQTT
The MQTT integration publishes all the data it receives from the devices as JSON over MQTT. This integration is already enabled by default.
The MQTT integration exposes all events as documented by Event types. The default event topic is: application/APPLICATION_ID/device/DEV_EUI/event/EVENT
In the MQTT broker documentation, you can find an example about how to get such data: https://support.veea.com/hc/en-us/articles/28933418510611-Service-Data-Broker-Configuration