Getting an config error that I can't figure out

For a few day I noticed that I am getting an error on the config files.

Logger: homeassistant.config
Source: config.py:415
First occurred: 21:14:57 (2 occurrences)
Last logged: 21:14:57

Invalid config for [automation]: expected dict for dictionary value @ data['action'][0]['data']. 
Got None extra keys not allowed @ data['action'][0]['message']. 
Got None extra keys not allowed @ data['action'][0]['title']. 
Got None. (See /config/configuration.yaml, line 58).

I have been looking over and over these files but I can’t figure out what is wrong.

I don’t even know in what file i have to look. I think it should be an error in the automation.yaml.
Now I have split up the automations in different files.and put an !include automation.yaml in the config.yaml. in that folder I have the automations.yamltogether with some others like lights.yaml and notifications.yaml.

Right at the root I also have an automations.yaml which contain the automations I created using HA.

Because I don’t know exactly which file to look, I haven’t added a file yet.
If someone can point me in a direction, than I can put that file here and maybe you see what I am missing.

I put all my files through a parser with no errors and HA alo checkes the files ok.

Can you post your configuration.yams?

You can disable (put # in from of the lines) the automations one by one, but looks like you have a indentation fault in one of the actions of an automation.

It should look like:

    - service: notify.mobile_app_tiphonex
      data:
        title: "Groovy title here"
        message: "We have the best messages"

I have a lot of them, but using the # I think i narrowed it down to the notifications.yaml.

Thanks, I am using it now and narrowed it down to the notifications.yaml.

Found it,

- id: notifytado
  alias: Notify tado offline
  trigger:
    - platform: state
      entity_id: sensor.kamer_link
      to: 'OFFLINE'
  action:
  - service: notify.oneplusa6013
      data:
      message: Tado verbinding verloren
      title: TADO

I had - service two space wrong.
Now that I have this automation shown here, do you guys think this is a working one? I don’t know if OFFLINE is a valua that I can use as a trigger.

If OFFLINE is indeed a state the sensor can have, then it will work… But only if TADO uses that state… Hass will use “unknown” most likely if it has no connection to tado and/or the sensor.

So, if you are looking for the state “what happens if Home Assistant can’t talk to TADO anymore?” Then I think you should go for “unknown”.