Node-RED - Revision history

Leo: Added categories

2020-06-14T23:48:57Z

Added categories

← Older revision		Revision as of 23:48, 14 June 2020
Line 75:		Line 75:
	A quick guide on using Node-RED with MQTT		A quick guide on using Node-RED with MQTT
	* https://hackaday.com/2020/01/15/automate-your-life-with-node-red-plus-a-dash-of-mqtt/		* https://hackaday.com/2020/01/15/automate-your-life-with-node-red-plus-a-dash-of-mqtt/

			{{Navbox Web}}[[Category:WebApp]]
			{{Navbox Tinkering}}[[Category:Tinkering]]

Leo: /* Crash Course */

2020-05-04T05:11:31Z

Crash Course

← Older revision		Revision as of 05:11, 4 May 2020
Line 50:		Line 50:

	The simplest flow is one that is triggered manually which then causes a debug message to be displayed. Clicking on the empty box left of the input node will cause the timestamp to be injected to the flow which will trigger a debug message to be printed on the right hand pane.		The simplest flow is one that is triggered manually which then causes a debug message to be displayed. Clicking on the empty box left of the input node will cause the timestamp to be injected to the flow which will trigger a debug message to be printed on the right hand pane.
	[[File:NodeRED Flow Example.jpg\|center~~\|900px~~\|NodeRED Flow Example]]		<div class="res-img">[[File:NodeRED Flow Example.jpg\|center\|NodeRED Flow Example]]</div>

	<br clear="all">		<br clear="all">
Line 56:		Line 56:
	We can expand on this example by making use of MQTT. MQTT is a popular message broker that allows devices to push and receive messages based on a 'topic'. The flow can be split in two, with one pushing the timestamp into a topic and another receiving the timestamp by subscribing to the same topic. Create two flows and then configure the MQTT nodes to use the local broker.		We can expand on this example by making use of MQTT. MQTT is a popular message broker that allows devices to push and receive messages based on a 'topic'. The flow can be split in two, with one pushing the timestamp into a topic and another receiving the timestamp by subscribing to the same topic. Create two flows and then configure the MQTT nodes to use the local broker.

	[[File:NodeRED Flow Example 2.jpg\|center~~\|900px~~\|NodeRED Flow Example 2]]		<div class="res-img">[[File:NodeRED Flow Example 2.jpg\|center\|NodeRED Flow Example 2]]</div>
	<br clear="all">		<br clear="all">
	By exposing the MQTT message broker to the network, we can have other devices publish messages to a specific topic (such as a topic for temperature from a ESP8266 sensor) and have NodeRED act on it (such as putting the temperature reading into InfluxDB).		By exposing the MQTT message broker to the network, we can have other devices publish messages to a specific topic (such as a topic for temperature from a ESP8266 sensor) and have NodeRED act on it (such as putting the temperature reading into InfluxDB).

Leo at 21:55, 3 May 2020

2020-05-03T21:55:41Z

← Older revision		Revision as of 21:55, 3 May 2020
Line 1:		Line 1:
	Node-RED is a web-based flow-based development tool for visual programming APIs, hardware devices, and online services.		Node-RED is a web-based flow-based development tool for visual programming APIs, hardware devices, and online services.

	It was originally developed by ~~IBM butt~~ was made open source under the Apache License 2.0 in 2016.		It was originally developed by IBM’s Emerging Technology Services team and was made open source under the Apache License 2.0 in 2016.

	== Installation ==		== Installation ==
Line 70:		Line 70:

	== See Also ==		== See Also ==
			* https://nodered.org/
			* https://nodered.org/docs/

			A quick guide on using Node-RED with MQTT
	* https://hackaday.com/2020/01/15/automate-your-life-with-node-red-plus-a-dash-of-mqtt/		* https://hackaday.com/2020/01/15/automate-your-life-with-node-red-plus-a-dash-of-mqtt/

Leo at 21:50, 3 May 2020

2020-05-03T21:50:57Z

← Older revision		Revision as of 21:50, 3 May 2020
Line 59:		Line 59:
	<br clear="all">		<br clear="all">
	By exposing the MQTT message broker to the network, we can have other devices publish messages to a specific topic (such as a topic for temperature from a ESP8266 sensor) and have NodeRED act on it (such as putting the temperature reading into InfluxDB).		By exposing the MQTT message broker to the network, we can have other devices publish messages to a specific topic (such as a topic for temperature from a ESP8266 sensor) and have NodeRED act on it (such as putting the temperature reading into InfluxDB).

			== Additional Nodes ==
			Additional nodes can be added by installing the appropriate npm package. Since I am using docker, the suggested method by the NodeRED documentation is to build another layer on top of the existing image.

			To add the InfluxDB nodes, create and build with the following {{code\|Dockerfile}}:
			{{highlight\|lang=text\|code=
			FROM nodered/node-red
			RUN npm install node-red-contrib-influxdb
			}}

	== See Also ==		== See Also ==
	* https://hackaday.com/2020/01/15/automate-your-life-with-node-red-plus-a-dash-of-mqtt/		* https://hackaday.com/2020/01/15/automate-your-life-with-node-red-plus-a-dash-of-mqtt/

Leo: Leo moved page Node-Red to Node-RED: naming

2020-05-03T21:48:08Z

Leo moved page Node-Red to Node-RED: naming

← Older revision		Revision as of 21:48, 3 May 2020
(No difference)

Leo: /* Installation */

2020-05-03T21:47:43Z

Installation

← Older revision		Revision as of 21:47, 3 May 2020
Line 4:		Line 4:

	== Installation ==		== Installation ==
	The simplest way to get started is to use the Node-RED docker image. I use the following {{code\|docker-compose.yml}} configuration with docker-compose to get started. Included is a MQTT broker.		The simplest way to get started is to use the Node-RED docker image. I use the following {{code\|docker-compose.yml}} configuration with docker-compose to get started. Included is a MQTT broker which I expose on the docker host on port 1883.

	{{highlight\|lang=text\|code=		{{highlight\|lang=text\|code=

Leo at 21:15, 3 May 2020

2020-05-03T21:15:07Z

← Older revision		Revision as of 21:15, 3 May 2020
Line 4:		Line 4:

	== Installation ==		== Installation ==
	The simplest way to get started is to use the Node-RED docker image. I use the following docker-compose.yml configuration with docker-compose to get started.		The simplest way to get started is to use the Node-RED docker image. I use the following {{code\|docker-compose.yml}} configuration with docker-compose to get started. Included is a MQTT broker.

	{{highlight\|lang=text\|code=		{{highlight\|lang=text\|code=
Line 10:		Line 10:

	services:		services:

	nodered:		nodered:
	image: nodered/node-red-docker:latest		image: nodered/node-red-docker:latest
Line 16:		Line 17:
	- "traefik.port=1880"		- "traefik.port=1880"
	- "traefik.docker.network=traefik"		- "traefik.docker.network=traefik"
	- "traefik.frontend.rule=Host:nodered.~~example~~.com"		- "traefik.frontend.rule=Host:nodered.home.steamr.com"
	- "traefik.frontend.redirect.entryPoint=https"		- "traefik.frontend.redirect.entryPoint=https"
	- "traefik.frontend.auth.forward.address=http://auth/index.php"		- "traefik.frontend.auth.forward.address=http://auth/index.php"
			# environment:
	networks:		networks:
	- traefik		- traefik
			- mqtt-net
	expose:		expose:
	- "1880"		- "1880"
Line 26:		Line 29:
	volumes:		volumes:
	- /var/volumes/nodered/data:/data		- /var/volumes/nodered/data:/data

			broker:
			image: eclipse-mosquitto
			networks:
			- mqtt-net
			expose:
			- "1883"
			restart: always

	networks:		networks:
			mqtt-net:
	traefik:		traefik:
	external:		external:
	name: traefik}}		name: traefik

			}}

			== Crash Course ==
			A flow defines the 'flow' of events that will occur when it is triggered. There are 'input' and 'output' nodes that can be dragged in from the left hand toolbox. Nodes can then be connected together by dragging a line between one node to another. After drawing your nodes and connecting them into a flow, click on the red 'Deploy' button on the top right so that the changes are applied.

			The simplest flow is one that is triggered manually which then causes a debug message to be displayed. Clicking on the empty box left of the input node will cause the timestamp to be injected to the flow which will trigger a debug message to be printed on the right hand pane.
			[[File:NodeRED Flow Example.jpg\|center\|900px\|NodeRED Flow Example]]

	=~~= Usage ==~~		<br clear="all">
	~~Flows define what Node-RED will do when~~ a ~~certain event happens~~.		[[File:NodeRED MQTT Configuration.jpg\|right\|thumb\|450px\|NodeRED MQTT Configuration]]
			We can expand on this example by making use of MQTT. MQTT is a popular message broker that allows devices to push and receive messages based on a 'topic'. The flow can be split in two, with one pushing the timestamp into a topic and another receiving the timestamp by subscribing to the same topic. Create two flows and then configure the MQTT nodes to use the local broker.

			[[File:NodeRED Flow Example 2.jpg\|center\|900px\|NodeRED Flow Example 2]]
			<br clear="all">
			By exposing the MQTT message broker to the network, we can have other devices publish messages to a specific topic (such as a topic for temperature from a ESP8266 sensor) and have NodeRED act on it (such as putting the temperature reading into InfluxDB).

	== See Also ==		== See Also ==
	* https://hackaday.com/2020/01/15/automate-your-life-with-node-red-plus-a-dash-of-mqtt/		* https://hackaday.com/2020/01/15/automate-your-life-with-node-red-plus-a-dash-of-mqtt/

Leo: Created page with "Node-RED is a web-based flow-based development tool for visual programming APIs, hardware devices, and online services. It was originally developed by IBM butt was made ope..."

2020-05-03T20:39:40Z

Created page with "Node-RED is a web-based flow-based development tool for visual programming APIs, hardware devices, and online services. It was originally developed by IBM butt was made ope..."

New page

Node-RED is a web-based flow-based development tool for visual programming APIs, hardware devices, and online services.

It was originally developed by IBM butt was made open source under the Apache License 2.0 in 2016.

== Installation ==
The simplest way to get started is to use the Node-RED docker image. I use the following docker-compose.yml configuration with docker-compose to get started.

{{highlight|lang=text|code=
version: '3.3'

services:
nodered:
image: nodered/node-red-docker:latest
labels:
- "traefik.enable=true"
- "traefik.port=1880"
- "traefik.docker.network=traefik"
- "traefik.frontend.rule=Host:nodered.example.com"
- "traefik.frontend.redirect.entryPoint=https"
- "traefik.frontend.auth.forward.address=http://auth/index.php"
networks:
- traefik
expose:
- "1880"
restart: always
volumes:
- /var/volumes/nodered/data:/data

networks:
traefik:
external:
name: traefik}}

== Usage ==
Flows define what Node-RED will do when a certain event happens.

== See Also ==
* https://hackaday.com/2020/01/15/automate-your-life-with-node-red-plus-a-dash-of-mqtt/