Node-RED | Apporo

Node-RED

Wire Home Assistant logic without writing an integration

Back up the right things, then find out what is actually slow

Back up the right things, then find out what is actually slow

Eleven parts built flows that talk to Home Assistant, call an HTTP API, and publish to MQTT. This part is about the day one of those stops working — because a credential got rotated, a restore did not go the way you expected, or the editor just feels slow and you do not know which of five layers to blame. Everything below is pinned to one exact configuration: Add-on 22.0.1, its bundled Node-RED 5.

Sep 9, 2026 Node-RED

MQTT in Node-RED, and the line between what shipped and what you add

MQTT in Node-RED, and the line between what shipped and what you add

MQTT looks like one thing — a topic box and a payload box — but a working mqtt in or mqtt out node rests on a broker connection, a protocol version, a session, TLS, credentials, QoS and the Retain flag, and every one of those has its own rules. This part also does something the earlier chapters have not: it opens the add-on itself and inventories what is already installed before you add anything.

Sep 9, 2026 Node-RED

One request comes in, another goes out, and neither should ever pick its own destination

One request comes in, another goes out, and neither should ever pick its own destination

This opens the engineering and operations stretch of the guide, and it starts with the part of Node-RED that talks to the outside world. HTTP In opens a route into your flow. HTTP Response is the only node that can finish that same request. HTTP Request is the opposite direction — your flow calling out to someone else's service. And there is a fourth, quieter path: the API node bundled with the Ho

Sep 9, 2026 Node-RED

Reuse a flow across tabs, then stop trusting the first green light

Reuse a flow across tabs, then stop trusting the first green light

A flow that only ever lived on one tab does not need an architecture. The moment the same logic has to be called from somewhere else, or run as five separate copies with five separate settings, you need a real answer to three questions: what calls what, whose state is whose, and what a shared file is allowed to carry once it leaves your machine. This part covers Links, Subflow instances, environme

Sep 9, 2026 Node-RED

JSONata, Mustache, and the Function node: four tools that look alike and share nothing

JSONata, Mustache, and the Function node: four tools that look alike and share nothing

A field in Node-RED that looks like a “template” might be processed by any one of four completely different engines, and pasting the wrong syntax into the wrong field does not always fail loudly — sometimes it just produces a value that looks right and has the wrong type. This part pins down which engine runs where, works through a fixed, offline JSONata transform step by step, and then spends the

Sep 9, 2026 Node-RED

Every intent starts as a proposal, and the Action node stays off until you turn it on yourself

Every intent starts as a proposal, and the Action node stays off until you turn it on yourself

Up to here the series has been about reading Home Assistant — listening for events, querying state, calling one Action you already trusted. This part is about deciding when not to call it. A hallway light, a door left open, a room that is getting warm: three ordinary situations, and three flows that only ever produce a candidate. Every Home Assistant listener, query, wait, and Action node in this

Sep 9, 2026 Node-RED

Where reading stops and doing begins

Where reading stops and doing begins

Part 5 left you with flows that ask Home Assistant questions — what state is this entity in, has it changed. Every node in that part reads. This part introduces the node that writes: the Action node, in the pinned build this guide follows (HA WebSocket integration 0.80.3, node version 7), and the four different ways a flow can be woken up before it ever reaches one. Node behavior here can change b

Sep 9, 2026 Node-RED

Two ways to find out what Home Assistant just did, and what it is doing right now

Two ways to find out what Home Assistant just did, and what it is doing right now

Chapter 8 wired Node-RED to Home Assistant. This chapter is about what happens once that wire is live: how do you actually learn that a light turned on, or that a door has been open for ten minutes? Node-RED gives you two different families of node for that, and they answer two different questions. Events: state is a doorbell — it fires the instant a matching state_changed event arrives, and you n

Sep 9, 2026 Node-RED

Nothing you store remembers on its own, and one connection is already built for you

Nothing you store remembers on its own, and one connection is already built for you

Everything so far has lived inside a single message as it crossed the canvas. This part introduces the first state that outlives a message — a countdown that keeps running after the wire that started it has gone quiet, a counter that has to mean the same thing the next time a different message asks for it. It also introduces the thing every later part in this guide leans on: the map of the 32 Home

Sep 9, 2026 Node-RED

msg carries more than payload, and guessing what type is inside gets expensive fast

msg carries more than payload, and guessing what type is inside gets expensive fast

Part 2 ended with a flow that does nothing to your house: Inject → Change → Debug, one message in, one line out. That message was never just its payload. Every wire in Node-RED carries a JavaScript object called msg, and payload is only the property most core nodes happen to look at by default — not a synonym for the whole thing, and not a guarantee of what type is sitting inside it. This part ope

Sep 9, 2026 Node-RED

Nothing you drag onto the canvas is running yet — until you click one button

Nothing you drag onto the canvas is running yet — until you click one button

Part 1 got Node-RED installed and locked down. This part teaches you to read the editor before you ever touch it live, then hands you a flow with zero real-world consequences to build that reading into muscle memory. You will drag three nodes — Inject, Change, Debug — wire them together, and click Deploy exactly once, with nothing behind that click but a string changing in a sidebar. No light turn

Sep 9, 2026 Node-RED

What “Node-RED” means here, and which door you just opened

What “Node-RED” means here, and which door you just opened

Click OPEN WEB UI in Home Assistant and you get an editor labeled Node-RED. That single word is quietly standing in for four separate pieces of software, each with its own version number, its own job, and its own way of breaking. This part pins all four, walks through the official install sequence for the Home Assistant Community App, and then does the part that actually matters once the editor is

Sep 9, 2026 Node-RED