node-red

# Node-RED for Home Assistant Build Node-RED flows using node-red-contrib-home-assistant-websocket nodes (v0.80+). **Requirements:** Node-RED 4.x (Node.js 18+), Home Assistant 2024.3.0+. ## The Iron Law ``` USE CURRENT NODE NAMES - NEVER OUTDATED ONES ``` The node-red-contrib-home-assistant-websocket package has renamed several nodes. Using old names produces broken flows that silently fail. ## Delivery Contract (read first, applies to every output) **Every flow ships as files in a project folder on disk. Chat output is not delivery.** A flow JSON pasted in chat is not a delivered flow. Create `<project-slug>/` (or write into the existing project folder in a multi-agent build), write the flow JSON under `node-red-flows/`, and write a `README.md` per Iron Law 3 in `../aurora/souls/river.md`. README sections follow `../aurora/references/deliverables/manual-format.md`: What this does, Installation, Troubleshooting, Recovery. No chat-only output option. ## The Process ``` User request │ ▼ HA server config node exists in Node-RED? │ no ─────────────────────────┐ │ yes ▼ │ Set up `server` config first │ (URL, access token, allow self-signed if needed) │ │ ▼ ◀────────────────────────────┘ Pick trigger node (current names only — see table below) │ │ time-based? ──▶ inject (time) or trigger-state with cron │ state-change? ──▶ tr...