New automation setup failed on 2025.1.2

[sage sorrel]

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?

Thanks in advance!

[latent carbon]

Have you run Check Configuration from devtools/yaml? No errors?

[sage sorrel]

Yes i have and no errors.

[latent carbon]

Can you refresh and check if the automations you made (that had this error) are created anyway in the main table of automations?

[sage sorrel]

sure i can just try make a new one. give me 1 min

[latent carbon]

This is a new dialog and it was recently identified that the timeout may be too short (and it was increased but not yet in production).

But even if it fires falsely your automations would still be created.

[sage sorrel]

i can see it in my automation list yes:

but i do not seem like it works:
i just did a simple thing like
`alias: test
description: ""
triggers:

• device_id: 4d71c5b932cd7ef0a2d3459d15dedaca
  domain: zha
  type: remote_button_short_press
  subtype: turn_on
  trigger: device
  conditions: []
  actions:
• action: light.toggle
  metadata: {}
  data: {}
  target:
  area_id: kitchen
  mode: single`

[latent carbon]

Is your server on the older/slower side, or any reason why it might have high latency?

The timeout was increased from 2s to 5s, so hopefully on next version you'll see less issues.

That looks like it's working correctly.

[sage sorrel]

no its a nuk only running HA.

[latent carbon]

hmm

[sage sorrel]

let me try another device just to make you its that.

Okay, it works! It was just my button that also had an issue,what a great coincidence while debugging! 😅

But alright, so the message just pops up, but the automation still works.
So it’s just as you assumed.

[sacred minnow]

I have the exact same issue...

[sacred minnow]

And I found the solution (I Think). It turned out that Local Tuya messed up my system resources.