node-red-contrib-home-assistant-websocketnode-red-contrib-home-assistant-websocket
Guides
Nodes
FAQ
Cookbook
Scrubber
Discussions
Discord
Github
Guides
Nodes
FAQ
Cookbook
Scrubber
Discussions
Discord
Github
  • Guides

    • Getting Started
    • First Automation
    • Action Node Tips and Tricks
    • Conditionals
    • Mustache Templates
    • JSONata

      • JSONata
      • JSONata primer
    • Diagnostics Information
  • Custom Integration

    • Getting Started
    • Exposed Nodes
  • Contribute to

    • Development
    • Documentation

Exposed Nodes

Nodes Available for Exposure

The following nodes can be exposed to Home Assistant, appearing as switches that can be toggled to enable or disable them in Node-RED:

  • Device
  • Events: all
  • Events: state
  • Poll State
  • Sentence
  • Tag
  • Time
  • Trigger: state
  • Webhook
  • Zone

This feature provides a cleaner alternative to creating input_booleans in Home Assistant for controlling flow activation.

Triggering Exposed Nodes via nodered.trigger

Exposed nodes can be activated using the nodered.trigger service call with the following parameters:

entity_id

  • Required
  • The entity_id of the exposed node to be triggered, as seen in Home Assistant. For example, use switch.my_node if that is the node's entity_id.

output_path

  • Optional
  • Default: 0
  • Can be a comma-separated list of output paths.
  • Determines which output path(s) the message will be sent through:
    • 0: Send through all output paths.
    • 1: Send through the first output path.
    • 2: Send through the second output path, and so on.

message

  • Required
  • The message to be sent when triggering the node. This should be a valid JSON object. For example, { "payload": "hello world" } would set msg.payload to hello world.
Help us improve this page!
Last Updated:
Contributors: Jason
Prev
Getting Started