Current state prefers payload entity_id instead of configured one about node-red-contrib-home-assistant HOT 2 CLOSED

When you select a node look at the info tab on the right side of the screen. If you read "current state" node documentation it says

Inputs
payload.entity_id string
Overrides or sets the entity_id for which the current state is being fetched

If you put a debug node on the "events: all" node, then you'll see that payload.entity_id is populated. So it does what it says it will do.

You can either use a change node and delete the property, or what most people do is they use one or more "events: changed" node. Note that the "events: changed" node uses a substring match, so an entity_id filter of binary_sensor will return state changes for all binary sensors in your HA setup.

from node-red-contrib-home-assistant.

@nordlead2005 is correct, by your description @sibbl everything seems to be functioning as designed. My personal view on this was the node configuration value could be thought of like how environment values are used in many cli systems, if you don't pass a cli argument then the environment variable is used as a default, if you pass an argument ( the node input ) then the environment variable ( the default node value ) is discarded.

I do agree that the documentation needs some love however and to that end I created #22 for when I have time to address

from node-red-contrib-home-assistant.