Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Payload Formatter for LoRaWAN™ platform sources.
A Payload Formater takes a buffer as well as the port of the message and normalizes data on-the-fly to be stored.
Device payload formatters allow you to specify a unique payload formatter for each device.
First, for Qubitro to be able to decode the data coming from integration, you need to create an uplink payload formatter. Payload formatter can be created on Qubitro.
The example uplink payload formatter is shown below.
The returned value must be a JSON object with the 'data' key.
Qubitro supports JavaScript payload formatter. You can find further documentation down below.
Once the payload formatter is set up correctly, it is possible to utilize all Qubitro features, including visualizing data and building custom applications with Qubitro APIs and make your life much easier.
You can find some of the examples and documentation down below.
It is possible to utilize Qubitro APIs for various scenarios. Visit API documentation below to learn more.
You can quickly and easily create your payload formatter with Qubitro Portal.
To create a payload formetter for Uplink, select your device and choose the Formatter tab.
The function name must be 'decodeUplink' and must accept only a single parameter.
You can validate your data under the Data tab.
Javascript payload formatters allow you to write your own functions to encode or decode messages. Javascript functions are executed using an JavaScript ECMAScript 5.1 engine.
The payload formatters should be simple and lightweight.
There are three different types of Qubitro JavaScript payload formatters:
The payload formatters should be simple and lightweight.
Read the documentations to further learn about these formatters and find associated examples.
If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this invitation link.
If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this invitation link.
Payload formatters use ECMAScript 5 (2009), which has some distinct differences compared to newer, commonly used ECMAScript revisions. See for a quick comparison. Notably, let
, const
, and arrow functions are not supported by ES5.
If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this .
The decodeDownlink()
function is called to decode a downlink message to JSON format, if it was scheduled with payload as bytes, or if it was scheduled with human-readable JSON payload but also was encoded with the encodeDownlink()
function.
Downlink messages sent upstream as part of events or downlink queue operations are therefore decoded, just like uplink messages (see Uplink Decoder).
Downlink Decoder feature will be available soon in Qubitro Portal.
The Javascript decodeUplink()
function is called when a data uplink message is received from a device. This function decodes the binary payload received from the end device to a human-readable JSON object that gets send upstream to the application.
The returned value must be a JSON object with the 'data' key and the function name must be 'decodeUplink' with a single parameter.
An example function:
The encodeDownlink()
function is called when a downlink message, with a payload in JSON format, is scheduled to be sent to the end device. The encodeDownlink()
function encodes the JSON object of the downlink message to binary payload that gets transmitted to the end device.
You can find some examples for utilizing features and working with data.
Once the payload formatter is set up correctly, it is possible to utilize all Qubitro features, including visualizing data and building custom applications with Qubitro APIs and make your life much more easier.
You can easily visualize your data with our widgets from the Monitoring section on the left side of our portal or under the Analytics tab in your project. Multiple charts are also can be added under a specific device.
Also, you can quickly filter your data by clicking the calendar under Data or Analytics.
It is possible to utilize Qubitro APIs for various scenarios. Visit API documentation below to learn more.
If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this invitation link.
You only need these two requirements to make possible proper no-code integration. You can automatically synchronize the sensor values and other platform-specific information to visualize on .
If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this .
Downlink Encoder feature will be available soon in .
If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this .
If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this .