Commit 2e5ebdea authored by shastry's avatar shastry
Browse files

Update README.md

parent 0260ccb5
......@@ -104,12 +104,12 @@ In our case, we have defined a function - 'create_yaml' which contains our logic
2. The HTTP Flow
3. The Flask server- Yaml interface
#### THE APPLICATION FLOW
![Flow1](Flow1.PNG)
![Flow1](Flow1.png)
The Flow starts with an input node which is connected to our custom Test Node. As the code is written to act upon each input, once an input enters the system, we send it to the Node we created. In the custom node, we take in the application data (details of fields found in the javascript explanation) and these pass this data as parameters in message payload to a create URL which now has localhost as the address with msg.payload attached at the end. Then we use the inbuilt Node-Red **Change** Node to set URL according to the payload received. Then this whole detailed setup is represented as an HTTP request and the message payload is available to the user for verification.
### The MQTT Flow
![Flow2](Flow2.PNG)
![Flow2](Flow2.png)
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
### The Flask server Yaml Interface
......
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