You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For all of my server-state-changed 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 figure out how to resolve it.
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.
To Reproduce
Open the Node-Red UI
Drag a server-state-changed node on to the workspace
Double click server-state-changed node to edit it
Take note of initial entry in Entity dropdown (is the first alpha entity option available)
Change to the required entity
Click Done
Click Deploy
Double click server-state-changed node to edit it
Entity dropdown will be displaying the first alpha entity option again
Expected behavior
To retain the chosen/correct entity in the Entity dropdown
Screenshots
Fresh server-state-changed node:
Changing just the entity to any other available and deploying:
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):
I can confirm this behavior. Do you experience slow opening of some nodes as well? See #839
How many entities do you have? I just did a select count(distinct entity_id) from states; and apparently I have over 3000 entity ids. I need to dig a bit deeper I guess.
Describe the bug
For all of my
server-state-changed
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 figure out how to resolve it.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.
To Reproduce
server-state-changed
node on to the workspaceserver-state-changed
node to edit itEntity
dropdown (is the first alpha entity option available)Done
Deploy
server-state-changed
node to edit itEntity
dropdown will be displaying the first alpha entity option againExpected behavior
To retain the chosen/correct entity in the
Entity
dropdownScreenshots
Fresh
server-state-changed
node:Changing just the entity to any other available and deploying:
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):
Example Flow
This package's version (not the Home Assistant add-on version)
0.48.0
Is Node-RED running in Docker?
Home Assistant add-on
Node-RED version
3.0.2
Node.js version
Unknown (sorry)
Additional context
Please let me know if you need any further info.
The text was updated successfully, but these errors were encountered: