How to decode the payload of your device

Published on by Marius Giger
Data Parsing VIsual

What is payload decoding?

Let's start with the basics. In essence, payload decoding is the process of translating raw data received from a device into readable, structured data. During this conversion, packets of data, typically transmitted in hexadecimal format, are decoded into human-readable values, such as humidity or temperature readings.

Why is it essential for LPWAN technologies?

LPWAN connectivity technologies such as LoRaWAN and Sigfox are well suited for low-power IoT solutions in which small amounts of data need to be sent at regular intervals. These are perfect for smart applications in which IoT devices are operating autonomously for extended periods (possibly years) and sending their data periodically to the cloud.

To reduce energy consumption and keep the data packets as small as possible, LPWAN devices send their data via a payload encoded in hexadecimal format. This differs from other protocols that define standard data payload formats and communicate through structured data such as JSON or XML.

The result is that countless device manufacturers in the IoT market define their own payload formats for their particular sensors. For someone who wants to integrate different sensors in one IoT solution, this translates into effort invested in encoding/decoding the data when setting up the project.

Towards a dictionary of IoT devices

This bothersome data parsing process should not be left solely on the shoulders of the IoT project leader. This is why we offer a device type library to ease the payload encoding/decoding process.

The akenza Device Type Library hosts an extensive list of standard device types to ease the registration of new devices into an IoT project by taking care of the data parsing automatically.

Device type library

For each device type, we offer a detailed description of the sensor's capabilities and measurements values. This also means that the Device Type Library can be used as a valuable reference to select the appropriate sensors for a particular use case and guide the purchase of new devices.

Thanks to the no-code Data Flow of akenza, you can directly use those device types inside your project in a few clicks. Just select the right connectivity for your device, pick the desired device type in our library and select the output connector defining where the data shall be stored. You are now ready to register your device and start collecting data.

Data flow 1200x675 1

The device library allows to include any device into a new data processing chain in minutes.

If the device of your choice is not present in our Device Type Library, you can also create your own device type very quickly using the Device Type Studio.

Luckily for you, we have a dedicated webinar that will guide you through the whole process:

Recent blog posts

Silverlight x Akenza
How an IoT Company Revolutionises Soil Moisture Monitoring for the Construction Industry: The case of Silverlight Ltd.

Silverlight aimed to create a solution that allows remote monitoring of the soil moisture levels, reducing the manual read-outs and receiving periodic data updates. After only two years of development and testing, the company released a reliable and unobtrusive solution.

Read the post
akenza IoT platform
Going digital with IoT: Do I need an IoT Platform?

Discover what are the main components of the IoT stack and how to choose an IoT platform for your next smart solution.

Read the post
Azure IoT Hub intergration with akenza
Enabling Low Power Devices in the Azure IoT Hub with the latest version of

Akenza is glad to announce the integration of Microsoft’s Azure IoT Hub as a new Output Connector on the akenza IoT platform.

Read the post