Configuring Command Line `notify` using YAML has moved

I have the same problem as the title of this topic.

Configuring Command Line `notify` using YAML has moved.
Consult the documentation to move your YAML configuration to integration key and restart Home Assistant to fix this issue.

In my configuration.yaml file, I created an !include to /config/command_lines.yaml.

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

# Text to speech
tts:
  - platform: google_translate

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
command_line: !include command_lines.yaml

In the command_lines.yaml, I paste the following text, which was first in configuration.yaml.

notify:
  - name: Signal
    platform: command_line
    command: 'wget $(cat) -O /dev/null'
  - name: WhatsApp
    platform: rest
    resource: https://api.callmebot.com/whatsapp.php
    data:
      source: HA
      phone: ****   #enter your phone number here
      apikey: ****       #enter your apikey here (see Setup above) 

I get the following error message when reloading all .yaml files.

Kan de configuratie niet opnieuw laden
Cannot quick reload all YAML configurations because the configuration is not valid: 
Invalid config for [command_line]: expected a dictionary for dictionary value @ data['command_line'][0]['notify']. Got [{'name': 'Signal', 'platform': 'command_line', 'command': 'wget $(cat) -O /dev/null'}, 
{'name': 'WhatsApp', 'platform': 'rest', 'resource': 'https://api.callmebot.com/whatsapp.php', 'data': {'source': 'HA', 'phone': ****, 'apikey': ****}}]. (See /config/configuration.yaml, line 11).

What should I change?

At least two things :

  1. The WhatsApp part has got nothing to do with ‘command lines’, so does not belong in this yaml file
  2. from the Signal part the ‘platform: command_line’ line must be removed, as per the new syntax, and because it is implicit in your new ‘include’-setup

@pav
That was indeed the solution, thank you.
When I made changes, error messages gone, only during an activation of an automation, I no longer get Signal notification.

That’s just figuring it out, for me, next time.

This is what worked for me to update the command_line notify to the new format. The other entries under “notify:” stayed the same.
old:

notify:
  - name: cli
    platform: command_line
    command: '/config/notify_cli.sh'

new:

command_line:
  - notify:
      name: cli
      command: '/config/notify_cli.sh'

Also note that there is a Signal Messenger Add-on available.