node-red_skill

Overview

This skill helps create and validate Node-RED flows for Home Assistant using node-red-contrib-home-assistant-websocket nodes. It focuses on current node names, correct configuration patterns, and safe defaults so flows import cleanly and work as expected. It also guides decisions when automation could instead be YAML or ESPHome.

How this skill works

I inspect requested automation goals and confirm whether you explicitly want a Node-RED flow or one of the alternatives (Home Assistant YAML or ESPHome). I produce importable flow JSON with placeholder entity IDs, leave the server field empty, and include comment nodes explaining required edits. I also flag deprecated node names, required integrations (like hass-node-red for entity nodes), and async/function-node pitfalls.

When to use it

• You explicitly ask for a Node-RED flow or mention Node-RED in your request.
• You want a visual, importable automation flow rather than handwritten YAML.
• You need guidance translating an existing YAML automation into Node-RED.
• You require examples that use current node names and live Home Assistant websocket nodes.

Best practices

• Always confirm the user wants Node-RED flow vs YAML or ESPHome before proceeding.
• Use current node types: trigger-state, api-call-service, api-current-state, poll-state, etc.
• Leave server config empty and use placeholder entity IDs with a clear comment to change them.
• Use trigger-state with extend: true for motion timers instead of separate timer flows.
• Prefer the built-in http request node over global libraries; warn if settings.js changes are required.
• When checking multiple entities, use regex in trigger-state or a function node to iterate — api-current-state accepts only one entity.

Example use cases

• Motion-triggered hallway light with a single trigger-state node and extend timer.
• Turn on HVAC modes via api-call-service using dynamic msg payload from a function node.
• Monitor multiple motion sensors using trigger-state with entityIdType: regex.
• Build a presence check that queries several person.* entities via a function node and global homeassistant states.
• Create an error-handling path using a catch node scoped to a service call and a retry delay node.