6.1 Connector Nodes
      Back to home
      1. Home
      2. 6: Nodes Reference Guide
      3. 6.1 Connector Nodes

      LoRaWAN Node Configuration Guide

      The LoRaWAN Node enables integration between Rayven and external LoRaWAN network servers by providing an uplink URL endpoint for devices to transmit their payloads. It processes inbound payloads from LoRaWAN gateways using a key-value format and more

      What It Does

      This node listens for uplink messages sent from LoRaWAN network servers to Rayven’s secure ingest URL. It supports:

      • Device UID extraction from nested fields

      • Full or filtered payload ingestion

      • Configurable formatting using key-value pairs

      It is ideal for collecting data from low-power IoT sensors deployed in remote or constrained environments.

      Step-by-Step: How to Configure the LoRaWAN Node

      1. Add the node

        • Drag the LoRaWAN node into your workflow from the Inputs section.

      1. Use the generated Uplink URL

        • This URL is unique to the workspace and must be used in your external LoRaWAN server’s HTTP forwarder or integration setup.

      2. Configure payload format

        • Set the expected payload format. Rayven currently supports Key:Value format.

      3. Map UID field

        • Define the JSON path within the payload that identifies the device UID (e.g., rx.moteeui).

      4. Optional: Enable full payload passthrough

        • Choose whether to pass the entire incoming payload into the Rayven workflow.

       Configuration Fields

      Field Requirement Description
      Node Name* Required Internal identifier for this node within the workflow.
      Uplink URL Auto-filled Read-only endpoint that must be used by your LoRaWAN server to push payloads to Rayven.
      Example: https://relay.rayven.io/api/main?uid=585208d3e
      Payload Format* Required Select the format of the incoming payload. Supported: Key:Value
      UID Field Name Optional Specify the field path to extract the device UID from the incoming payload.
      Example: rx.moteeui
      Pass Entire Payload Optional When enabled, the entire incoming JSON object is passed downstream rather than extracting only mapped fields.
       

      Example Payload

       
      {
      "rx": {
      "moteeui": "0018B200000002DB",
      "data": {
      "temperature": 24.3,
      "humidity": 65
      }
      }
      }

      Configuration:

      Field Value
      UID Field Name rx.moteeui
      Payload Format Key:Value
      Pass Entire Payload Enabled (optional)
       

      Result: The node will extract the UID 0018B200000002DB and ingest all fields within the payload.

       Best Practices

      • Ensure that the UID field uniquely identifies the device in the workspace.

      • Confirm that the LoRaWAN server is configured to forward data to the exact Uplink URL.

      • Use payload filters or parsing nodes downstream to normalize vendor-specific data formats.

      • Enable "Pass Entire Payload" only when you need complete access to the raw structure.

       Use Cases

      • Collect uplink sensor data from LoRa-based weather stations, soil sensors, or asset trackers

      • Visualize values from industrial field sensors without direct internet access

      • Record incoming device values from TTN (The Things Network) or Loriot integrations

       FAQ

      Q: Can I use this with The Things Network (TTN)?

      A: Yes. Use the HTTP Integration feature in TTN and provide the Uplink URL from this node.

      Q: What if the UID is missing or not mapped?

      A: The payload will be rejected or assigned to an undefined device. Always map the UID correctly.

      Q: Can I map nested fields from the payload?

      A: Yes. Use dot notation (e.g., rx.moteeui) to extract nested keys.