Skip to content
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

Automations / Scripts: Better explanations for the Response Variable field #22824

Open
2 of 4 tasks
NoRi2909 opened this issue Nov 14, 2024 · 0 comments · May be fixed by #22920
Open
2 of 4 tasks

Automations / Scripts: Better explanations for the Response Variable field #22824

NoRi2909 opened this issue Nov 14, 2024 · 0 comments · May be fixed by #22920

Comments

@NoRi2909
Copy link
Contributor

NoRi2909 commented Nov 14, 2024

Checklist

  • I have updated to the latest available Home Assistant version.
  • I have cleared the cache of my browser.
  • I have tried a different browser to see if it is related to my browser.
  • I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.

Describe the issue you are experiencing

When an action does return a result you can save this in a variable that can be used in the next actions in your sequence.

(If I understand it correctly) that variable is created by simply naming it in the action. This should be made clearer in the two strings that describe this option.

Here is one example where this shows up:

image

Describe the behavior you expected

The two possible strings can be found here:

"has_optional_response": "This action can return a response, if you want to use the response, enter the name of a variable the response will be saved in",
"has_response": "This action returns a response, enter the name of a variable the response will be saved in",

First of all they are lacking a period at the end of both sentences. In addition they leave it open to the user how to interpret the creation of the variable: Does it have to exist or do I create it here, and what can I do with it?

By using "… name for a variable …" becomes inherently clear that this variable will be created by the action.

I'm not sure if it is that obvious in English, but in German "… der Name einer Variable …" implies that it already exists under that name, while " … der Name für eine Variable …" implies that it will be created with that specified name. That's where the main motivation for the bug report comes from.

What version of Home Assistant Core has the issue?

core-2024.11.1

@NoRi2909 NoRi2909 linked a pull request Nov 20, 2024 that will close this issue
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant