Ecosmart Remote Crashing Automations

I have an EcoSmart 4 button remote setup with an automation but when I click the trigger button HA just fires off a warning about invalid config.

I also tried these two blue prints with the same result

Error in HA notifications

image

The logs just show what looks like a snippet of my configuration.yaml

Logger: homeassistant.config
Source: config.py:464
First occurred: 07:59:47 (5 occurrences)
Last logged: 08:06:51

Invalid config for [automation]: Invalid trigger configuration. Got OrderedDict([('logger', {}), ('lock', {}), ('my', {}), ('cloud', {}), ('sun', {}), ('input_datetime', {}), ('ssdp', {}), ('input_boolean', {}), ('person', {}), ('config', {}), ('history', {}), ('updater', {}), ('zeroconf', {}), ('system_health', {}), ('mobile_app', {}), ('zha_toolkit', {}), ('remote_syslog', {}), ('zha', OrderedDict([('custom_quirks_path', '/config/custom_zha_quirks/'), ('zigpy_config', OrderedDict([('ota', OrderedDict([('ikea_provider', True), ('ledvance_provider', True), ('.... (See /config/configuration.yaml, line 212).
Invalid config for [automation]: Invalid trigger configuration. Got OrderedDict([('logger', OrderedDict([('default', 'critical'), ('logs', OrderedDict([('homeassistant.core', 'fatal'), ('homeassistant.components.mqtt', 'error'), ('homeassistant.components.recorder', 'error'), ('homeassistant.components.influxdb', 'error'), ('homeassistant.components.zha', 'debug'), ('bellows.zigbee.application', 'debug'), ('bellows.ezsp', 'debug'), ('zigpy', 'debug'), ('zigpy_deconz.zigbee.application', 'debug'), ('zigpy_deconz.api', 'debug'), ('zigpy_xbee.zigbee.application'.... (See /config/configuration.yaml, line 212).

The Device shows battery percent etc
image

Here is the automation

alias: EcoSmart Test
description: ''
trigger:
  - event_data:
      command: 'on'
      device_ieee: cc:cc:cc:ff:fe:c2:cd:f3
    event_type: zha_event
    platform: event
  - event_data:
      command: 'off'
      device_ieee: cc:cc:cc:ff:fe:c2:cd:f3
    event_type: zha_event
    platform: event
condition: []
action:
  - service: light.turn_on
    target:
      device_id: 3ad03785f227934004b33cff89ba7dde
mode: single

Any insight or help is greatly appreciated

That automation is fine, the cause must be somewhere else, probably the way you integrate that automation.

What does your "automation: " line in configuration.yaml look like (standard is automation: !include automations.yaml)?

Looks like the standard implementation
Line 212 in Configuration.yaml

automation: !include automations.yaml