State node always displays first entity in list

[SimonM]

Hi all,
I've an odd problem that I can't figure out.

For all of my state nodes, when re-editing them the entity dropdown is displaying the wrong entity it always shows the first available entity in the list. By all accounts, my flows work as expected but this issue is really frustrating, as I can't resolve it.

Fresh state node:

Changing just the entity to any other available and deploying:

As I'm new I can only embed two images, so please see first reply for third.

I've tried restarting my instance, multiple times. Uninstalling, clearing out any left over folders and reinstalling Node-Red fresh. Even rebuilding flows from scratch. Yet this same issues keeps occurring and from search and posting on Reddit and the Home Assistant forum, it appears to only affect my setup.

Node-Red v3.0.2
Home Assistant Community Add-on v14.0.0
Home Assistant 2022.12.8
Supervisor 2022.12.1
Operating System 9.4
Frontend 20221213.1 - latest
All nodes in palette on latest

Does anyone have any ideas on how to sort this out please?

Thanks,

Simon

[SimonM]

Third image.

Re-editing the same node and the dropdown is back to the first in the list, although note the auto name of the node (highlighted):

[TotallyInformation]

It helps everyone if you could add the full node package name as a tag.

[SimonM]

Apologies, I searched in the optional tags when I created the post, but no options for it are available.

node-red-contrib-home-assistant-websocket : server-state-changed

However, following your post I went checking and have since realised that the events: state node isn't a default one and is part of the Node-RED Companion Integration for Home Assistant.

[TotallyInformation]

Which gives people a lot more to go on. Unfortunately, HA related help is quite limited in this forum because not many of the super-cool Node-RED experts in the forum actually use HA I'm afraid. So you might need to try to get some help in the HA forum.