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

Naming a script in local language Bug #115411

Closed
Opontios opened this issue Apr 11, 2024 · 7 comments
Closed

Naming a script in local language Bug #115411

Opontios opened this issue Apr 11, 2024 · 7 comments

Comments

@Opontios
Copy link

The problem

The expected behavior is the entity_id of the script, when naming the script in local language, to be transcripted into English. Instead it is named "unknown" with an incremented number at the end.

What version of Home Assistant Core has the issue?

2024.4.2

What was the last working version of Home Assistant Core?

2024.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@Opontios Opontios changed the title Naming a script in local language became impossible Naming a script in local language Bug Apr 11, 2024
@joostlek
Copy link
Member

What do you mean with local language?

@Opontios
Copy link
Author

What do you mean with local language?

Not English. Russian in particular case.

@joostlek
Copy link
Member

So wait, you create a script with those letters and it will name the entity unknown?

@Opontios
Copy link
Author

How can I explain it simpler? Before the update if I named an automation or a script like this: "Привет", the entity_id of the script would be "script.privet". And now it's "script.unknown". The second script named differently and again in local language is named "script.unknown_2" and etc.
The issue is not the naming itself. You can always rename the entity_id. But, as already mentioned here "#115334", after changing the entity_id of the script the "service: script.new_entity_id" produces an error and the service call continues to work with the initial entity_id, although it doesn't exist any more. I see that you commented in that post also and the thing that amazed me that you weren't aware of the fact that to run a script you could just write "service: script.entity_id", and not necessarily "service: script.turn_on" and the name of the script, and the difference those 2 expressions have.

@rrooggiieerr
Copy link
Contributor

@Opontios What happens to the entity name of your automation if your copy it and give it a new name in your local language? Do you still get script.unknown or do you get the right entity name? For me making a copy with the right name and deleting the original works, while renaming doesn't. I'm curious to know if this is similar in your case.

@Opontios
Copy link
Author

@Opontios What happens to the entity name of your automation if your copy it and give it a new name in your local language? Do you still get script.unknown or do you get the right entity name? For me making a copy with the right name and deleting the original works, while renaming doesn't. I'm curious to know if this is similar in your case.

As I mentioned, the issue is not the entity_id of the script itself, although it was very convenient that the system converted the cyrillic name to a latin. The issue is that to run the script you can only use the original entity_id of the script created by the system, even if you change it it doesn't recognize the new entity_id created and runs with the original one, even though as an entity it doesn't exist any more.

@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@issue-triage-workflows issue-triage-workflows bot closed this as not planned Won't fix, can't repro, duplicate, stale May 15, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Jun 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants