#Cant get automation to work

1 messages · Page 1 of 1 (latest)

ivory moat
#

Hi all i am trying to get my own automation to work but i think i have something wrong somewhere but i cnat figure it out so i need some help
This automation is for tempature in my house through my airco ,i also have a seperate temp sensor for that so it takes the right tempature in the room instead of the airco itself temp sensor.
Every time i want to save it it says :Your new automatisering was saved, but waiting for it to set up has timed out. This could be due to errors parsing your configuration.yaml, please check the configuration in developer tools. Your automatisering will not be visible until this is corrected and automatiseringen are reloaded. Changes to area, category, or labels were not saved and must be reapplied.
So i try to do that to figure out where the mistake i made is.
If needed i can share my config.yaml of the automation.
All help is very welcome

tender geode
#

Do you include the automations.yaml in your configuration.yaml?

ivory moat
#

Loads default set of integrations. Do not remove.

homeassistant:
default_config:

Load frontend themes from the themes folder

frontend:
themes: !include_dir_merge_named themes

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

ivory moat
#

'''alias: Vorstbescherming Slaapkamer (stateful)
description: Vorstbescherming zonder handmatige bediening te overrulen
triggers:

  • id: too_cold
    entity_id: sensor.climacontrol_airco_woonkamer_sensor_naam
    below: 14.5
    for: "00:05:00"
    trigger: numeric_state
  • id: warm_enough
    entity_id: sensor.climacontrol_airco_woonkamer_sensor_naam
    above: 15.5
    for: "00:03:00"
    trigger: numeric_state
    actions:
  • choose:
    • conditions:
      • condition: trigger
        id: too_cold
      • condition: state
        entity_id: climate.climacontrol_airco_woonkamer_climate
        state: "off"
        sequence:
      • target:
        entity_id: input_boolean.vorstbescherming_woonkamer
        action: input_boolean.turn_on
      • target:
        entity_id: climate.climacontrol_airco_woonkamer_climate
        data:
        hvac_mode: heat
        action: climate.set_hvac_mode
      • target:
        entity_id: climate.climacontrol_airco_woonkamer_climate
        data:
        temperature: 16
        action: climate.set_temperature
    • conditions:
      • condition: trigger
        id: warm_enough
      • condition: state
        entity_id: input_boolean.vorstbescherming_woonkamer
        state: "on"
        sequence:
      • target:
        entity_id: climate.climacontrol_airco_woonkamer_climate
        data:
        hvac_mode: "off"
        action: climate.set_hvac_mode
      • target:
        entity_id: input_boolean.vorstbescherming_woonkamer
        action: input_boolean.turn_off
        mode: restart'''
hybrid dirgeBOT
#

To format your text as code, enter three backticks on the first line, press Enter for a new line, paste your code, press Enter again for another new line, and lastly three more backticks.
```yaml
example: here
```
Don't forget you can edit your post rather than repeatedly posting the same thing.

dense finch
#

i have the same. Not sure which version it appeared. could be 2026.03 or earlier. Havent touched an automation for for some time

#

current automations still run fine though. also saving an existing one works. BUT:

#

when i rename an automation and save, then go back to the overview page of all automations, the old name is still there. So not updated. But when i go into the automation again, the newly saved name appears just fine.

#

--
in conf i have:
automation: !include automations.yaml