home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
72.67k stars 30.42k forks source link

Error when saving automation using YAML editor: Failed to format translation for key 'ui.panel.config.automation.editor.actions.unsupported_action' in language 'en-GB'. #127575

Open adamf83 opened 2 weeks ago

adamf83 commented 2 weeks ago

The problem

When creating and saving a new automation using the YAML editor, the following was logged as an error:

Failed to format translation for key 'ui.panel.config.automation.editor.actions.unsupported_action' in language 'en-GB'. Error: The intl string context variable "action" was not provided to the string "No visual editor support for action: {action}"

The automation does appear to work so I’m not sure if there are any wider implications or things that may not work as a result of this error.

What version of Home Assistant Core has the issue?

core-2024.10.0

What was the last working version of Home Assistant Core?

core-2024.9.2

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Automation

Link to integration documentation on our website

https://www.home-assistant.io/docs/automation/

Diagnostics information

No response

Example YAML snippet

action:%20input_datetime.set_datetime%0Ametadata%3A%20%7B%7D%0Adata%3A%0A%20%20date%3A%20%22%7B%7B%20now().strftime('%25Y-%25m-%25d')%20%7D%7D%22%0Atarget%3A%0A%20%20entity_id%3A%20input_datetime.washing_machine_last_run_date%0A

Anything in the logs that might be useful for us?

Logger: frontend.js.modern.202410022
Source: components/system_log/__init__.py:331
First occurred: 15:31:59 (55 occurrences)
Last logged: 15:35:24

Failed to format translation for key 'ui.panel.config.automation.editor.actions.unsupported_action' in language 'en-GB'. Error: The intl string context variable "action" was not provided to the string "No visual editor support for action: {action}"

Additional information

No response

joostlek commented 2 weeks ago

Please raise this issue in the frontend issue tracker, thanks :)

Polbaci commented 2 weeks ago

I have the same issue.