Automation: !include automations.yaml

Release 45 worked great but was too old to upgrade. New install of Hassbian 61 workes execpt for automations.

What is the correct configuration.yaml for automations now
automation: !include automations.yaml throws the error:
Invalid config for [automation]: expected dict for dictionary value @ data[‘action’][0][‘data’]. Got None

automation.yaml is:

  • alias: Minimote 1 Button 1 Short Press
    initial_state: True
    hide_entity: True
    trigger:
    platform: event
    event_type: zwave.scene_activated
    event_data:
    entity_id: aeotec_dsa03202_minimote_7
    scene_id: 1
    action:
    • service: switch.toggle
      data:
      entity_id: light.bedroom_lamp

You’re using switch.toggle on a light ?

Worked like a charm in 45 one minimote buttion one push on next push off.

This was my 45 verion automations.yaml format:
Just the first two but I had 8 minmote scenes and 8 keyfob scenes all working.

  • id: Minimote-1-1-S
    alias: Minimote 1 Button 1 Short Press
    initial_state: True
    hide_entity: True
    trigger:
    • platform: event
      event_type: zwave.scene_activated
      event_data:
      entity_id: aeotec_dsa03202_minimote_7
      scene_id: 1
      action:
    • service: switch.toggle
      data:
      entity_id:
      - light.bedroom_lamp
  • id: Minimote-1-1-L
    alias: Minimote 1 Button 1 Long Press
    initial_state: True
    hide_entity: True
    trigger:
    • platform: event
      event_type: zwave.scene_activated
      event_data:
      entity_id: aeotec_dsa03202_minimote_7
      scene_id: 2
      action:
    • service: switch.toggle
      data:
      entity_id:
    • light.bedroom_tv
  • id: Minimote-1-2-S
    alias: Minimote 1 Button 2 Short Press
    initial_state: True
    hide_entity: True
    trigger:
    • platform: event
      event_type: zwave.scene_activated
      event_data:
      entity_id: aeotec_dsa03202_minimote_7
      scene_id: 3
      action:
    • service: light.toggle
      data:
      entity_id:
    • light.living_room_table

OK - but have you tried changing it to light.toggle ?

Yes, Tried many different ways.

If I could figure out how to enter the scene_id into the GUI automation I would be able to see the result in the cli and replicate it.

I’ll try to keep this basic:

What used to work in version 45 and does not in Version 63

I wan’t: (scene_id 1)
Log from button press:
Feb 12 21:46:09 hassbian hass[8621]: #033[32m2018-02-12 21:46:09 INFO (MainThread) [homeassistant.core] Bus:Handling <Event zwave.scene_activated[L]: scene_id=1, node_id=2, entity_id=zwave.aeotec_dsa03202_minimote>#033[0m
To toggle entity_id: light.bedroom_lamp

And (scene_id 2)
Feb 12 21:46:58 hassbian hass[8621]: #033[32m2018-02-12 21:46:58 INFO (MainThread) [homeassistant.core] Bus:Handling <Event zwave.scene_activated[L]: scene_id=2, node_id=2, entity_id=zwave.aeotec_dsa03202_minimote>#033[0m
to toggle entity_id: light.bedroom_tv

In ver45 used to be in automations.yaml

id: Minimote-1-1-S
alias: Minimote 1 Button 1 Short Press
initial_state: True
hide_entity: True
trigger:
- platform: event
event_type: zwave.scene_activated
event_data:
entity_id: aeotec_dsa03202_minimote_7
scene_id: 1
action:
- service: light.toggle
data:
entity_id: light.bedroom_lamp

	------many more-------

Finally found a properly formatted example thanks to Waxhell on github.

  • alias: Minimote Button 1 Pressed
    hide_entity: True
    trigger:
    platform: event
    event_type: zwave.scene_activated
    event_data:
    entity_id: zwave.aeotec_dsa03202_minimote
    scene_id: 1
    action:
    service: switch.toggle
    entity_id: switch.linear_ps15z2_plugin_appliance_module_switch
  • alias: Minimote Button 1 Held
    hide_entity: True
    trigger:
    platform: event
    event_type: zwave.scene_activated
    event_data:
    entity_id: zwave.aeotec_dsa03202_minimote
    scene_id: 2
    action:
    service: switch.toggle
    entity_id: switch.aeotec_dsc06106_smart_energy_switch_switch
  • alias: Minimote Button 2 Pressed
    hide_entity: True
    trigger:
    platform: event
    event_type: zwave.scene_activated
    event_data:
    entity_id: zwave.aeotec_dsa03202_minimote
    scene_id: 3
    action:
    service: light.toggle
    entity_id: light.bedroom_lamp
  • alias: Minimote Button 2 Held
    hide_entity: True
    trigger:
    platform: event
    event_type: zwave.scene_activated
    event_data:
    entity_id: zwave.aeotec_dsa03202_minimote
    scene_id: 4
    action:
    service: light.toggle
    entity_id: light.bedroom_tv
  • alias: Minimote Button 3 Pressed
    hide_entity: True
    trigger:
    platform: event
    event_type: zwave.scene_activated
    event_data:
    entity_id: zwave.aeotec_dsa03202_minimote
    scene_id: 5
    action:
    service: light.toggle
    entity_id: light.living_room_rear
  • alias: Minimote Button 3 Held
    hide_entity: True
    trigger:
    platform: event
    event_type: zwave.scene_activated
    event_data:
    entity_id: zwave.aeotec_dsa03202_minimote
    scene_id: 6
    action:
    service: light.toggle
    entity_id: light.living_room_table

Does this config still work for you?

For me this creates a number of errors and will not run.