Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Fields disappear (Call Service node) #1922

Closed
hassos246 opened this issue Aug 9, 2024 · 11 comments
Closed

Fields disappear (Call Service node) #1922

hassos246 opened this issue Aug 9, 2024 · 11 comments
Labels
stale There has not been activity on this issue or PR for quite some time.

Comments

@hassos246
Copy link

Problem/Motivation

When using Call Service node with domain switch the fields area, device and entity disappears when using services toggle or turn_off

Expected behavior

I expect the fields stated above not to disappear.

Actual behavior

The fields disappear.

Steps to reproduce

Create a Call service node. Select domain Switch. Select turn_off or toggle

Proposed changes

Screenshots

Service turn_on Service toggle Service turn_off
@lucode
Copy link

lucode commented Aug 10, 2024

Had the same problem, but can't remember what exactly was the cause. Did you check if you have more than one Home Assistant Configuration nodes (server)? That might be related. I renamed mine to "Home Assistant ok" to be aware if a node uses a different one. More than 3 will slow down the interface dramatically.
image

@hassos246
Copy link
Author

I only have one server in node red.

Copy link

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

@github-actions github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label Sep 10, 2024
@gwilford
Copy link

I also have this issue and I'm not sure when it occurred as I haven't needed to edit or develop any NR flows for a while. Tried manually updating node-red-contrib-home-assistant-websocket, tried restoring an add-on backup (v17.0.13). Tried accessing NR via port 1880 rather than sidebar. Nothing has worked. This is on HA 2024.9.1. First noticed using NR add-on v18.0.5.

Anyone have an ideas?

@github-actions github-actions bot removed the stale There has not been activity on this issue or PR for quite some time. label Sep 14, 2024
@daviss57
Copy link

Same issue here, cant update any nodes.

@ndoggac
Copy link

ndoggac commented Sep 20, 2024

Oops, filed separate issue before seeing this one. Seeing the same thing. Even my old nodes are affected. Nodes I know referenced items by device name are not showing them.

@ndoggac
Copy link

ndoggac commented Sep 23, 2024

Surprised this issue has been allowed to stick around for going on 2 months. This is a major bug.

@ndoggac
Copy link

ndoggac commented Sep 24, 2024

See the discussion linked below. Apparently this is not the right place for this issue?? Unhelpful responses there....so where is the proper location? I looked within the core repository with no luck.

Not all of us have a working knowledge of the code base in order to know the correct location to submit a bug. Realize devs may get frustrated with us pleebs, but the community is trying to help ID this (in my opinion anyway) significant bug. Can confirm the HASS core update to 2024.9.3 this morning did not fix this issue.

#1678

@ndoggac
Copy link

ndoggac commented Sep 24, 2024

ok, tried posting a new issue here. zachowj/node-red-contrib-home-assistant-websocket#1600

I updated all the palettes in NR as well. still no fix. In the new palette the "call service" node is now called "action". even creating a new action node, adding a device (which is also a new mechanism +), and then selecting the "Action" from the dropdown, the items still disappear.

Something I always forget is that palette updates require manual intervention, with no notifications.

@sinclairpaul
Copy link
Member

One thing you might want to validate is if the issue exists using the default theme, and gathering data via the Browser Console.

Copy link

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

@github-actions github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label Oct 25, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 2, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Dec 2, 2024
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
stale There has not been activity on this issue or PR for quite some time.
Projects
None yet
Development

No branches or pull requests

6 participants