hassio-addons/addon-node-red

current state node doesn't work if preceded by an events: all node #575

stefanlod posted onGitHub

Problem/Motivation

The current state node is essential for constructing flows with differing conditions. If it doesn't work properly for all scenarios, its usefulness is limited.

Expected behavior

When receiving a message from the events: all node, the current state node should be able to query the relevant conditions in Home Assistant and provide either a positive or negative answer. This is the standard behaviour that is seen from other nodes, such as trigger: state.

Actual behavior

When receiving the message from events: all node, the current state node doesn't properly query anything and always fails.

Steps to reproduce

In my particular flow, I've got an events: all node that listens for events from zwave.scene_activated. That is connected to a current state node that checks for whether a light is on or not.

Proposed changes

If you don't have any specific actions tied to a fail, you can swap out the current state node for a wait until node with a very short timeout.


Hi there @stefanlod!

Thanks for opening up an issue. However, add-ons wrap existing applications, in this case, Node-RED and its nodes. It seems like your issue is with the Home Assistant Node for Node-RED.

Please report your issue here:

https://github.com/zachowj/node-red-contrib-home-assistant-websocket

Thanks! 👍

<blockquote><img src="https://avatars2.githubusercontent.com/u/37859597?s=400&v=4" width="48" align="right"><div><img src="https://github.githubassets.com/favicons/favicon.svg" height="14"> GitHub</div><div><strong><a href="https://github.com/zachowj/node-red-contrib-home-assistant-websocket">zachowj/node-red-contrib-home-assistant-websocket</a></strong></div><div>Node-RED integration with Home Assistant Core. Contribute to zachowj/node-red-contrib-home-assistant-websocket development by creating an account on GitHub.</div></blockquote>

posted by frenck almost 5 years ago

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.

posted by addons-assistant[bot] almost 5 years ago

Fund this Issue

$0.00
Funded

Pull requests