HTTP/HTTPS Integration to Forward LoRaWAN® Data to the Cloud

The HTTP/HTTPS Integration feature allows your RAK gateway (with the built-in LoRaWAN® Network Server) to send device data directly to any cloud platform using standard HTTP POST requests.

This feature enables smooth data transfer between your gateway and cloud services such as ThingsBoard, Datacake, or your custom backend by pushing key LoRaWAN events to user-defined endpoints. It eliminates the need for additional middleware and supports both HTTP and secure HTTPS communication.

How It Works

Once HTTP/HTTPS Integration is enabled for an application, the built-in LoRaWAN Network Server (LNS) on the WisGateOS 2 gateway handles incoming traffic from connected LoRa® end devices. It processes each uplink and identifies key events such as:

• Uplink – device transmits data to the gateway.

• Join Notification – device successfully joins the network.

• ACK Notification – device acknowledges a downlink

• Device Status Notification – device reports battery or link status

For each event, the LNS constructs a structured HTTP POST request and forwards it to the user-defined endpoint(s). Each POST contains:

• Device identifiers (e.g., DevEUI, applicationName)

• Encoded payload data (Base64 or HEX, depending on configuration)

• Timestamp – time of event processing

• Metadata (e.g., RSSI, SNR, frequency) – included only if Report LoRa® Radio Information is enabled

• Optional custom headers – such as Authorization or API keys, if configured in the integration settings

Prepare Your Server-Side Endpoint

Before configuring the gateway, ensure your server or cloud platform is ready to receive data.

Your server must be able to:

• Accept HTTP POST requests at the specified URLs

• Parse JSON payloads sent by the gateway

• Decode the data field (Base64 or HEX, based on your gateway setting)

• (Optional) Validate HTTP headers for authentication (e.g., API key or token)

Enable Integration in Gateway

Before you begin, ensure the following prerequisites are met:

• The built-in LoRaWAN® Network Server is enabled on your WisGateOS 2 gateway

• At least one Application and its devices have been properly set up

To learn how to enable the built-in network server and add Applications/Devices, refer to LoRa Configuration – Built-in Network Server.

1. Go to the gateway web UI and navigate to:
   LoRa® > Applications > [Your Application] > Configuration > Integration Parameters.

2. Toggle the switch Enable HTTP/HTTPS Integration to turn on the feature.

3. Provide the destination URL(s) for each type of event:

   • Uplink Data URL

   • Join Notification URL

   • ACK Notification URL

   • Device-Status Notification URL

4. Configure optional settings.

   • Decode Type: Choose either Base64 (default) or HEX

   • Report LoRa® Radio Information: Enable this option if you wish to include RSSI, SNR, and frequency

   • Headers name/Header value: Add key-value headers for API authentication

   • Maximum number of concurrent connections

   • Maximum length of queue

5. Click Save changes to activate the integration.

Further Reading

For a practical step-by-step HTTP/HTTPS integration guide, read ThingsBoard Integration Guide.

This guide demonstrates how to configure an HTTP endpoint on ThingsBoard Cloud to receive uplink data from the WisGateOS 2 gateway.

While it uses ThingsBoard as an example, the same principles apply to other platforms like Datacake or custom backends.

FAQs

1. What is the payload format?
   All event data is sent as JSON. The data field is encoded in Base64 or HEX depending on the selected Decode Type.

2. Can each event type use a different endpoint?
   Yes. Uplink, Join, ACK, and Status notifications can each be routed to different URLs.

3. Is HTTPS supported?
   Yes. HTTPS is fully supported with valid SSL certificates. Avoid using self-signed certificates unless the gateway explicitly trusts the CA.

Updated November 07, 2025 04:05