Node-red-contrib-home-assistant-websocket is my fork of node-red-contrib-home-assistant that I plan on maintaining. One of the major changes is that I have changed over the main communication from using the REST API and Event Stream to use WebSocket where ever is possible.
Some new key feature
- Using WebSocket where ever possible for communication to and from Home Assistant.
- Ability to use Long-Lived Access Tokens to authenticate with Home Assistant as well as still supporting the legacy API password.
- Server credentials are now encrypted and stored in the node-red cred file. This also stops them from being exported in flows.
- A new ‘Fire Event’ Node that allows you to fire events to Home Assistant.
- Check the CHANGELOG for a list of fixes and changes that have been made so far.
Install via Node-RED Manage Palette
Install via npm
$ cd cd ~/.node-red $ npm install node-red-contrib-home-assistant-websocket # then restart node-red
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 output. Check your nodes and make sure they are outputting what you expect.
If you have been using @Spartan-II-117 fork this should be a drop in replacement as of this posting.
If you find any issues/bugs please create a new issue on github so I can address them. Also if you have any feature requests that you think may improve this, I’d also be glad to hear from you.