ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #nodered
Decide between the Node-RED Change node and Function node. Learn when to use declarative visual mapping versus custom JavaScript to optimize performance and maintainability.
Large Node-RED flows become hard to read and maintain. Subflows offer a built-in way to encapsulate repeated logic, but they come with trade-offs around debugging and context isolation.
A decision guide for Node-RED context persistence: when localfilesystem storage is the right choice for single-instance restart survival, and how to configure and validate it safely.
Duplicate API polling nodes create drift. A parameterized subflow with environment variables lets you reuse the same logic with per-instance config while keeping state isolated.
Default Node-RED context lives in memory and vanishes on restart. Learn how to evaluate file-based versus in-memory stores for stateful flows, with a counter example and verification steps.
Learn how to build a minimal, secure Node‑RED flow that ingests MQTT sensor data into a time‑series database, with guidance on trust boundaries, operational checks, failure modes, and when to redesign.
Persist Node‑RED state locally with built‑in file context storage: requirements, design, trust boundaries, operational checks, failure modes, and when to upgrade.
Learn how to create, configure, and reuse Node-RED subflows so that updates propagate automatically across all instances, with a worked example and notes on limitations.
Node-RED subflows let you package reusable node groups into single palette components. This blog walks through building a Celsius-to-Fahrenheit conversion subflow, exposing configurable properties, and verifying the result — plus debugging limits and portability gotchas.