Invalid config for [automation]: [after]

I have the below in my automation.yaml and when checking the config, I get the error;

Invalid config for [automation]: [after] is an invalid option for [automation]. Check: automation->trigger->1->after.

I’m assuming it has an issue with using ‘after’, but I can’t work out why, and if it does… what do I change it to?

- alias: Send alert when dryer is dry
  trigger:
    - platform: state
      entity_id: input_select.dryer_status
      to: Dry
    - platform: time
      after: '08:30:00'
    - platform: state
      entity_id: device_tracker.bens_iphone
      to: 'Home'
      for:
        minutes: 10
    - platform: state
      entity_id: device_tracker.lucys_iphone
      to: 'Home'
      for:
        minutes: 10
  condition:
    condition: and
    conditions:
      - condition: time
        before: '22:30:00'
        after: '08:29:00'
      - condition: state
        entity_id: group.people
        state: 'home'
      - condition: state
        entity_id: input_select.dryer_status
        state: Dry
      # Don't send this alert if it was last triggered less than 30 minutes ago (1,800 seconds)
      - condition: template
        value_template: >
          {% if states.automation.send_alert_when_dryer_is_dry.last_triggered is not none %}
            {% if as_timestamp(now()) | int   -  as_timestamp(states.automation.send_alert_when_dryer_is_dry.attributes.last_triggered) | int > 3600 %} true {% else %} false
            {% endif %}
          {% else %}
          false
          {% endif %}
  action:
    - service_template: >
        {% if (is_state('device_tracker.bens_iphone', 'home')) and (is_state('device_tracker.lucys_iphone', 'home'))  %}
          notify.ben_and_lucy
        {% elif is_state('device_tracker.bens_iphone', 'home') %}
          notify.ben
        {% elif is_state('device_tracker.lucys_iphone', 'home') %}
          notify.lucy
        {% endif %}
      data:
        message: 'The Dryer has finished and is ready to be emptied!'
        title: 'Dryer Update'

Thank you in advance.

Change it to at:

You’ll also want to put lowercase Hs on Home for the states triggers.

Check the trigger docs - after isn’t valid (it was, a long long time ago), and as @anon43302295 correctly pointed out, your states are wrong in the triggers.

Always look at Developer tools -> States to see the actual states of an entity, rather than the human friendly one provided in the overview.

Thank you. Will -at still allow it to operate in the same way? By looking at the times in between the after and before?
I assume I need to change both after and before to at?

Nope, you need to read the automation docs so you know what’s valid where.

Triggers are - when this becomes true, start processing the automation
Conditions are - when this is currently true, allow the automation to continue

So, the time trigger uses at, and the time condition uses after and before