Error in Logs about automation

Installation Home Assistant OS
1

I keep receiving this:

Logger: homeassistant.config
Source: config.py:454
First occurred: 8:31:37 AM (1 occurrences)
Last logged: 8:31:37 AM

Invalid config for [automation]: required key not provided @ data['entity_id']. Got None. (See /config/configuration.yaml, line 9).

Watchman Report found no errors

this is my configuration file:

# Configure a default setup of Home Assistant (frontend, api, etc)

default_config:

homeassistant:

  customize: !include customize.yaml

# Text to speech

tts:

  - platform: google_translate

automation: !include automations.yaml

group: !include groups.yaml

script: !include scripts.yaml

scene: !include scenes.yaml

#--------------Sensors Configuration Start----------------------------

#includes: sonarr, radarr, system information, time_date

sensor: !include_dir_merge_list ./sensors

#--------------Sensors Configuration End------------------------------

#--------------Custome Attributes Start-------------------------------

template: !include_dir_merge_list ./_templates

#--------------Custome Attributes End---------------------------------

#--------------LG WebOS TV Configuration Start------------------------

wake_on_lan: # enables `wake_on_lan` domain

media_player:

notify:

device_tracker:

  - platform: bluetooth_le_tracker

the automations keep running as they should,
but this specific notification keep showing up
image

and it’s really annoying to my OCD :sweat_smile:

I am a noob in Home Assistant :sweat_smile:

2

I would suspect there is something wrong in your automations.yaml file and probably a small indentation / spacing issue.

The best way to try and narrow it down would be to use a file editor and block comment out sections at a time, reload automations and recheck.

Keep doing this until the offending section is found. Hopefully then the issue will be easier to find.

3

you are correct :slight_smile:
it seems that there was an automation that i deleted from the automation frontend, but it did not get deleted from the automation.yaml,
so I started using the elimination process, by commenting sections of the yaml file and see if the error kept showing.

thank you very much :slight_smile:

1 Like