Four resources help you design, verify, and maintain Home Assistant flows in Node-RED: a 22-chapter tutorial, an adoption assessment, a searchable prompt library, and a safe-delivery specification for AI agents.
Four practical resources
Complete 22-chapter tutorial
For installers, flow authors, and maintainers
Work step by step through installation, the editor, msg and logic, context, Home Assistant events, states, and actions, JSONata, the Function node, HTTP, MQTT, backups, security, and troubleshooting, with 14 safe example flows.
For consultants, implementers, and decision-makers
Use discovery questions to assess whether Node-RED or native Home Assistant automations are the better fit. Define versions, architecture, phased adoption, risk controls, acceptance criteria, and maintenance responsibilities—without making blanket ROI or performance promises.
Explore 60 pinned-version prompts across 12 categories. Each requires exact-source evidence and placeholders, follows a preview-first approach, and prohibits deployment on the user’s behalf. Search the library, see the number of results, and copy any prompt with one click.
This single specification defines the order of precedence for pinned sources, product boundaries, the feature manifest, chapter contracts, safe flow JSON, factual and security reviews, read-only screenshots, branding, quality gates, and deployment permissions.
Offline availability: The downloadable versions of the three manuals are available only in Chinese. Each is a standalone HTML file with embedded shared CSS and system fonts and requires no external fonts, icons, styles, or scripts. Search and copy remain available offline in the prompt library. Because the 22-chapter tutorial is a multipage site, download the archive ZIP of the GitHub main branch.
Version reminder:Add-on 22.0.1 / Node-RED 5.0.2 / HA WS 0.80.3 / FlowFuse 1.30.2 (optional; not bundled). FlowFuse Dashboard 2 is optional and is not bundled with the Add-on. Before taking action, revalidate the guidance against the pinned tag or commit and in your own test environment.