Commit 5bad2995 authored by shastry's avatar shastry
Browse files


parent 40531c45
......@@ -110,8 +110,11 @@ This node is taken directly from the pallete available. Its just used to inject
Node 2: Our custom Node:
This node needs user inputs. Read the placeholders in each field carefully before entering the values of your device. Folow is a picture of how the node looks like
The next section shows the critical config part of the node. As you can see, we have 3 fields to fill and each of this requires special attention as visible in the placeholder instructions as seen blow:
Node 3: Take a simple function node from the pallete and write into it the following code:
......@@ -121,9 +124,11 @@ $ return newmsg;
Node 4: Set msg url:
This node is just a continuance to the output of the earlier node and the properties are set as follows:
Node 5: Select from the nodes pallete on the left, a 'HTTP Request' node. No further actions needed except connecting it. The node looks like this when double-clicked:
Node 6: Just an output debug node selected from the pallete.
......@@ -137,13 +142,16 @@ The Flow starts with an input node which is connected to our custom Test Node. A
### The MQTT Flow
We have a second flow to obtain data back from the lora server - MQTT flow. Here is how th eflow looks like:
Currently we have made use of two LoRa MQTT integration features: Rx and Status messages.
Each of this node requires a command given below to be inserted into the box as shown in the picture after the command:
$ application/[application id]/device/[device_eui]/rx[or status depending on the node]
The MQTT peaks into two integration offerred by chirpstack - Uplink and Status to obtain the corresponding device data. The devie EUI and application id, for now, has to be manually added by the user to the node
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment