Various nodes to assist in setting up automation using Node-RED communicating with Home Assistant.
Project is going through active development and as such will probably have a few 'growing pain' bugs as well as node type, input, output and functionality changes. At this stage backwards compatibility between versions is not a main concern and a new version may mean you'll have to recreate certain nodes.
This assumes you have Node-RED already installed and working, if you need to install Node-RED see here.
NOTE: This requires at least Node.js v8.12.x and Node-RED v0.19.x.
Install via Node-RED Manage Palette
node-red-contrib-home-assistant-websocket
Install via npm
$ cd ~/.node-red
$ npm install node-red-contrib-home-assistant-websocket
# then restart node-redFor Hass.io add-on users:
The Community Hass.io add-on ships with this node right out of the box.
Under the server node config just check the checkbox for I use Hass.io
The add-on can be found here: https://github.com/hassio-addons/addon-node-red#readme
Coming from a different version, e.g. @Ayapejian or @Spartan-II-117?
If you have been using @Ayapejian version there are some breaking changes with two of the nodes. The ‘Poll State’ and ‘Current State’ both have a little different formatted outputs. Check your nodes and make sure they are outputting what you expect. A more in depth example can be found here.
If you have been using the @Spartan-II-117 fork this should be a drop in replacement.
The installed nodes have more detailed information in the Node-RED info pane shown when the node is selected. Below is a quick summary
Listens for all types of events from home assistant with the ability to filter by event type
Listens for only state_changed events from home assistant
Much like the State Changed Node however provides some advanced functionality around common automation use cases.
Outputs the state of an entity at regular intervals, optionally also at startup and every time the entity changes if desired
Sends a request to home assistant for any domain and service available ( light/turn_on, input_select/select_option, etc..)
Fire an event on the event bus
Fetches the last known state for any entity on input
Get entities based on search criteria with 3 different output options
Fetches HomeAssistant history on input
Allows rendering of templates on input
When an input is received the node will wait until the condition is met or the timeout occurs then will pass on the last received message
Check out the wiki page for setting up an environment with Home Assistant/Node Red.