New automation setup failed | Home Assistant | Page 1

devout thunder Jan 9, 2025, 11:39 AM

#

Hi, not totally sure if this is an automation question or should be somewhere else. I have an issue when I create new automations, when I save them I get an 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.

I know 2025.1 had a breaking change with LIFX lights that might be causing this. I also messed around with the Ulanzi Desktop Clock. I added and removed changed things so I might of messed something up there too. My issue is I don't know how to fix these things. It shows me 129 problems in the automations.yaml file when I check it in Studio Code Server but I think these are Legacy Syntax issues tho I really don't know what I'm looking at with yaml stuff. Should I take the time to figure what needs to be changed and how to change them, then change all these in the yaml files or can I use the visual editor to fix these, how? Would I just go into every automation that has LIFX lights and change them somehow? When I go into the Developer tools and reload the ALL YAML CONFIGURATION I don't get an error. I'm not totally sure what information I would need to share so someone could hopefully help or push me in the right direction. I found these issue after I deleted all the old backups with release of 2025.1. I don't understand what "the logs" are or what part of the logs I should share. I'm very worried about sharing something I shouldn't and my house get hacked or something. I'm just so confused and have spent since the release of 2025.1 trying to figure it out and I just don't know. I'm sorry for not following all the rules while posting this I'm just so very confused. Thank you for any help you can provide. Sorry for the long post.

snow niche Jan 9, 2025, 1:31 PM

#

devout thunder Hi, not totally sure if this is an automation question or should be somewhere el...

post configuration.yaml

devout thunder Jan 9, 2025, 1:46 PM

#

snow niche post configuration.yaml

Hopefully I'm doing this right

devout thunder Jan 9, 2025, 1:46 PM

#

snow niche post configuration.yaml

default_config:

# Load frontend themes from the themes folder
frontend:
  themes: !include_dir_merge_named themes

# Text to speech
tts:
  - platform: google_translate

automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
template: !include template.yaml

# Build your own notifications  service for any TTS service.
notify:
  - name: living_room # The name
    platform: tts
    # tts_service: tts.google_translate_say # The TTS service
    tts_service: tts.cloud_say # Nabu Casa TT
    # tts_service: tts.amazon_polly_say #for those rocking the Anazon Polly
    media_player: media_player.google_home_speaker #media player

sensor:
  - platform: mqtt_room
    device_id: "Phone"
    name: "Phone BLE"
    state_topic: "espresense/devices/phone"
    timeout: 10
    away_timeout: 60

snow niche Jan 9, 2025, 2:18 PM

#

can you please format that

devout thunder Jan 9, 2025, 2:25 PM

#

yes, how do I do that?

snow niche Jan 9, 2025, 2:29 PM

#

3 backticks before and after the code

devout thunder Jan 9, 2025, 2:33 PM

#

oh sorry I fixed it above

snow niche Jan 9, 2025, 2:34 PM

#

That configuration is fine, nothing in that should lead to the problem you're having

#

have you cleared your browser cache?

devout thunder Jan 9, 2025, 2:36 PM

#

I have not, is that a chrome thing? It gives me this error when I'm editing on my phone and on desktop

snow niche Jan 9, 2025, 2:38 PM

#

can you screenshot the error?

devout thunder Jan 9, 2025, 2:39 PM

#

#

Any new Automation gives me this error. If I update one that was working before it doesn't give me the error

snow niche Jan 9, 2025, 2:48 PM

#

check your logs then

#

homeassistant.log

#

somethings likely bottlenecking your system

devout thunder Jan 9, 2025, 2:53 PM

#

Oh wait I think I found it in the Studio Code Server. How would I know what is bottlenecking my system?

snow niche Jan 9, 2025, 2:54 PM

#

if it's eating all your memory

#

HA won't have any to use

#

For what it's worth, I keep VSCode off unless I'm using it.

devout thunder Jan 9, 2025, 2:56 PM

#

If whats eating all my memory?

#

In storage it only shows 21% used

snow niche Jan 9, 2025, 2:58 PM

#

what about CPU?

#

regardless of that, your system is bogged down doing something

#

figure out what that is, and stop it from happening and it will likely fix the automation issue

devout thunder Jan 9, 2025, 3:09 PM

#

Im so very confused. I cleared my Chrome Brower cache and removed the Music Assistant add-on. I went to Setting >> Systems >> Logs. Cleared the logs to try to get fresh ones. Went to make a quick simple automation. Saved it, it saved, didn't give me an error and it works. So I guess the issue is resolved? Thank you for your patience and assistance with my issue. 🙂

#

And now its doing it again. I have no idea what to do. Thank you anyways for trying to help

snow niche Jan 9, 2025, 3:17 PM

#

are you sure your CPU isn't throttled to the max?

#

there's nothing else that would cause it other than the event stream being filled to the brim with tasks

#

and if that was happening, you'd see a ton of things in your logs

devout thunder Jan 9, 2025, 3:22 PM

#

to see the logs its Settings >> System >> Logs, right? I don't know what I'm looking for

snow niche Jan 9, 2025, 3:27 PM

#

click view live logs

#

and if you see something hammering over and over and over, that's your issue

#

look at the timestamps too

fossil quiver Jan 9, 2025, 3:35 PM

#

That dialog is new. Bram suggested 2s as the timeout value for time to save an automation. If that time is too short, we could try to increase it.

devout thunder Jan 9, 2025, 3:51 PM

#

Thank you again for trying to help

fossil quiver Jan 9, 2025, 3:54 PM

#

If it really is that your system is just responding too slowly, it's likely that automation was successfully saved even if the dialog appears. You could just wait a few seconds, reload the screen, or see if it is present in your overall list of automations to continue editing it.

devout thunder Jan 9, 2025, 3:58 PM

#

Oh, hmm. I'm not sure. It appears to be working again. No idea why lol. I'll leave it at that tho. I am greatful for you all's assistance

fossil quiver Jan 9, 2025, 3:59 PM

#

If it keeps happening please open a frontend issue.

devout thunder Jan 9, 2025, 4:00 PM

#

Will do ^_^

snow niche Jan 9, 2025, 4:29 PM

#

fossil quiver If it keeps happening please open a frontend issue.

Thanks

manic latch Jan 20, 2025, 8:21 AM

#

devout thunder Will do ^_^

Can you share the link to the frontend issue? I have the exact same problem and do not see any "hammering" in the raw logs.

#New automation setup failed