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
Describe the bug
When using multiple home-assistant instances, Entity IDs are not loaded from selected server, but from the first one. Even if I select different server in node properties and hit deploy, entities are still pulled from the wrong server.
To Reproduce
Steps to reproduce the behavior:
add second hass server
add new hass node
select second hass server
try to find entity from the second server (only from first one are populated).
Expected behavior
Etities from new server should show up in EntityID selector.
Environment (please complete the following information):
Node Red Version: 0.19.5
NR Home Assistant Plugin Version: 0.3.1
Is Node Red running in Docker: yes
Other (please complete the following information):
Have you searched previous issues for duplicates?: yes
Did you attempt to reproduce the issue in the dev docker environment, if so what were results (See README.md): yes
The text was updated successfully, but these errors were encountered:
Yes, this was a bug on the original fork. I have this on my TODO list but since no one had brought it up it was a low priority. I'll bump it up now and get a fix in for it.
latest version exhibits this behavior still... you have to select the next server, click done, then go back into the node edit mode to get the other server's entity list.
Describe the bug
When using multiple home-assistant instances, Entity IDs are not loaded from selected server, but from the first one. Even if I select different server in node properties and hit deploy, entities are still pulled from the wrong server.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Etities from new server should show up in EntityID selector.
Environment (please complete the following information):
Other (please complete the following information):
The text was updated successfully, but these errors were encountered: