events: state outputs even when state does not change about node-red-contrib-home-assistant-websocket HOT 4 CLOSED

It triggers on what Home Assistant considers a state_change event which as you have seen means when anything within the entity changes. For your use case, a trigger-state with the state check or a Report by Exception node is what you'd want to use.

edit: This is working as intended. I understand what you're saying but there are a lot more valid use cases to keep it as it is and there are several easy solutions for it to work as you described.

from node-red-contrib-home-assistant-websocket.

Just to maybe clarify: the "state" is not just made up of the payload (on/off), but the entirety of the object's attributes. So if your lamp has an attribute "brightness", changing that will change the state, even though the lamp is on before and after this state change.

from node-red-contrib-home-assistant-websocket.

I understand, but it's confusing because the state object has an attribute called "state" and I would claim that most people would expect a "state changed" node to (at least by default) only output events when the attribute "state" changes (i.e., on/off, home/not_home, open/closed).

For example, there could be a preference to have the node only output when from_state.state and to_state.state are different. I know I can do this with additional nodes, but again, I would argue that most times this node would be used for actual state attribute changes.

from node-red-contrib-home-assistant-websocket.

For example, there could be a preference to have the node only output when from_state.state and to_state.state are different. I know I can do this with additional nodes, but again, I would argue that most times this node would be used for actual state attribute changes.

I would agree that this is a valid feature request.

from node-red-contrib-home-assistant-websocket.