-
-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Targets not showing in action node after upgrading to 18.1.1 #1969
Comments
I have exactly the same issue. No targets property showing in the action node making Node Red unusable. if I go into Node Red directly using :1880 the target property shows but then vanishes. |
Correction mostly working now except Z Wave JS and that is probably me. |
What's also strange is, on another installation I also updated to 18.1.1 but there it's still called "call service" node i.s.o. "action" |
Log looks fine at startup: `Welcome to Node-RED8 Oct 07:34:41 - [info] Node-RED version: v4.0.3 |
+1 same issue. Reverted back to 18.0.5 |
Certainly the issue is related to this change: https://www.home-assistant.io/blog/2024/10/02/release-202410/#improved-yaml-syntax-for-automations I think the addon must be updated by the developers. |
Problem/Motivation
After updating from 18.0.5 to 18.1.1 NR asked me to update HA nodes. After that I noticed multiple issues for my action (previously "call service") nodes. All of them told me that entity_id should be in "data" and not in "target". I could not find the "targets" property, so no way to find the entity_id. According to screenshots of other people, there should be a "targets" property.
Reverted back to 18.0.5 and everything is ok now. Phew, that was scary.
Expected behavior
I expect to still be able to use the "targets" property and not having to define the target entity_id in the data property. Also, the target property should be shown.
Actual behavior
Targets property is missing. Multiple errors, although I did not change anything.
Steps to reproduce
Update from 18.0.5 to 18.1.1 and then confirm update HA nodes.
The text was updated successfully, but these errors were encountered: