I’m running into an issue where I can’t create new automations. I keep getting the following error:
“New automation setup failed. Your new automation has saved, but waiting for it to setup has timed out. This could be due to errors parsing your configuration.yaml, please check the configuration in developer tools. Your automation will not be visible until this is corrected, and automations are reloaded. Changes to area, category, or labels were not saved and must be reapplied.”
It doesn’t matter if I use a blueprint or try to create an automation from scratch using the GUI—I always get the same error.
I’ve searched around and found that some people mention it’s important to have the following line in configuration.yaml:
automation: !include automations.yaml
I’ve always had this line in my configuration, and I triple-checked to make sure it’s still there.
Here is some more info just for debugging:
Restarted the entire machine – no effect.
Running Home Assistant OS directly on bare metal.
Haven’t modified my configuration.yaml in a long time.
Can’t find anything obvious in the logs.
I’m running out of ideas—does anyone have any suggestions on what I might be missing or something else I can try?
I have the same problem, even with new scripts too. I did everything you did as well, but nothing worked. But I realized that this only happens when I connect remotely to Home Assistant (I use nabu casa), If I connect locally, the setup error doesn’t appear. I think this is not a problem related to the configuration.yalm. Try to connect locally and see what happens.
Hi, I encountered the same error (“new automation setup failed”). However, all my automations and blueprints were successfully saved and visible afterward. For me, it seemed to be a cosmetic issue rather than a functional one.
I had the “dwains-lovelace-dashboard” integration, which showed errors in the logs. After removing the integration and restarting Home Assistant, the error message disappeared while saving an automation.
The error in my HA log was:
Logger: homeassistant.helpers.frame
Source: helpers/frame.py:234
(1 occurrences)
Detected code that calls async_forward_entry_setup for integration, dwains_dashboard with title: and entry_id: 0123456789ABCDE, which is deprecated, await async_forward_entry_setups instead. This will stop working in Home Assistant 2025.6, please report this issue
Another Error:
Logger: homeassistant.helpers.frame
Source: helpers/frame.py:324
(3 occurrences)
Detected that custom integration ‘dwains_dashboard’ calls hass.http.register_static_path which is deprecated because it does blocking I/O in the event loop, instead call await hass.http.async_register_static_paths([StaticPathConfig("/dwains_dashboard/js", "/config/custom_components/dwains_dashboard/js", True)]) at custom_components/dwains_dashboard/load_plugins.py, line 13: hass.http.register_static_path(“/dwains_dashboard/js”, hass.config.path(f"custom_components/{name}/js"), True). This will stop working in Home Assistant 2025.7, please create a bug report at GitHub · Where software is built
Detected that custom integration ‘dwains_dashboard’ accesses hass.components.websocket_api, which should be updated to import functions used from websocket_api directly at custom_components/dwains_dashboard/notifications.py, line 220: hass.components.websocket_api.async_register_command(websocket_get_notifications). This will stop working in Home Assistant 2025.3, please create a bug report at GitHub · Where software is built
Detected that custom integration ‘dwains_dashboard’ calls async_add_job, which should be reviewed against Deprecating `async_run_job` and `async_add_job` | Home Assistant Developer Docs for replacement options at custom_components/dwains_dashboard/init.py, line 1590: hass.async_add_job(. This will stop working in Home Assistant 2025.4, please create a bug report at GitHub · Where software is built
BTW: I can actually reproduce the error “new automation setup failed” every time I install the “dwain-dashboard” integration. The Integration Version is 3.7.1
New automation setup
failed…
Your new automation has saved, but waiting
for it to setup has timed out. This could be
due to errors parsing your configuration.yaml
please check the configuration in developer
tools. Your automation will not be visible until
this is corrected, and automations are
reloaded. Changes to area, category, or labels
were not saved and must be reapplied
I’m about to give up ! No Matter how hard i try i cant a solution ! Neither literature or troubleshooting ideas !
Happening Regardless remotely or locally
Anyone here having the same isue found a solution or a work around this ? And mind to Share ?
I’ll be Greatly Apreciated!
To make things even worse all My Automations Stoped workig and Dissapeared from the GUI
But Still exist in The automations.yalm when i use the file editor