Tekos Flow
A short overview what is tekos flow capable of
Last updated
A short overview what is tekos flow capable of
Last updated
Our tekos flows is based on node red technology. To understand how it works you first need to know how nodes together create a flow.
The Node-RED is a simple “wiring” of nodes or predefined code blocks to perform the tasks. One happy news is that it doesn’t need huge blocks of codes. No need to waste time running the code. It is a flow-based development tool in which the runtime is built on Node.js. The flows created are stored in JSON. By storing in JSON, we can share, import and export to the real world. An online flow library allows you to share your best flows with the world.
Input nodes: It allows you to enter the input data into the flow. They have a grey square on their right side which you can connect to the other nodes. By connecting this node to another node, you can send the input data. You can also connect services like Twitter, Google, serial, web sockets and send those data as inputs to the other nodes. Or else you can manually enter the input data using the node called “inject”.
Output nodes: It allows you to send the data to the outside world, to other services for example twitter. It has a grey square on their left side which they can be connected to either input node or function. If you don’t want to send the data to any services like Twitter or email nodes, you can simply debug those messages by using the tab “deploy” on the top right corner of the editor.
Processing nodes: The processing nodes are used to process the data in which they have one input endpoint and one or more output endpoints. They are used to transform the data types, to write the custom codes and to trigger a message.
The examples of the connected nodes:
Input nodes: inject, catch, status, mqtt, etc
Processing nodes: comment, delay, function, switch, change, etc
Output nodes: debug, link, tcp, udp, websocket, http request, etc
The Node-RED can be used in weather reports or alerts, sending TCP requests, using Twitter or other social services to control Raspberry Pi, alerts when you are falling off a schedule, etc.