npm node-red-contrib-home-assistant-websocket 0.12.0

latest releases: 0.64.0, 0.63.2, 0.63.1...
4 years ago

Individuals nodes on the workspace will now have a version number associated with them. This will allow changes to be made to the structure of nodes without affecting all nodes of that type until you edit them. Legacy nodes will have a yellow font until the node has been upgraded to the newest version.

"If State" Changes

If State will now send the message to the first output if true and to the second if not. This is for the events-state, poll-state, and current-state nodes. The old behavior, sending the message to the second output if true, will continue to be in place until you edit one of the existing nodes via the UI and at that time the outputs will automatically be switched. The output tooltips are version-aware and will display the correct text depending on the current version of the node. Hopefully, this change will make if state more intuitive for new as well as existing users.

Bug Fixes

  • config-server: trying to get global namespace before it created (4472072)
  • css change for node label (22c645f)
  • css fixes for 'if state' text boxes (78a2707)
  • fixed error reporting so catch node could be used (861c8e8), closes #119
  • more error reporting fixes (89346e2)
  • Update autocomplete on server change in ui (c8b2e09)

Features

  • if 'if state' = true now outputs to the first output (9fdc6f5)
  • call-service: Ability to use alt tags for mustache templates (0624570), closes #117
  • current-state: Added ability to block input overrides to config (9d46441)
  • trigger-state: More options for custom outputs (3df9c18)

Full Changelog

Don't miss a new node-red-contrib-home-assistant-websocket release

NewReleases is sending notifications on new releases.