Automations / Scripts: Better explanations for the Response Variable field

[NoRi2909]

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:

Describe the behavior you expected

The two possible strings can be found here:

frontend/src/translations/en.json

Lines 3407 to 3408 in b83be38

	"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