Xiaomi Aqara Wireless switch - automation don't fire [SOLVED]

Configuration
1

Hi’

I’ve spend hours to get automation working with my new WXKG02LM wireless Aqara switch - but no luck so far… :frowning:

Environment: Hassio Home Assistant v0.93.2
Example simple automation:

- id: Xiaomii Wall Switch
  alias: Xiaomii Button
  initial_state: 'on'
  trigger:
    platform: event
    event_type: xiaomi_aqara.click
    event_data:
      entity_id: binary_sensor.vswitch
      click_type: single
  action:
  - service: light.toggle
    entity_id: light.kontor

Debug log actually shows all events fire as expected, also the xiaomi_aqara.click event, but automation still don’t fire ?

2019-06-21 00:13:33 DEBUG (MainThread) [homeassistant.components.xiaomi_aqara] PUSH >> <Entity Wall Switch (Both)_158d00031348bf: off>: {'channel_0': 'click'}
2019-06-21 00:13:33 DEBUG (MainThread) [homeassistant.components.xiaomi_aqara] PUSH >> <Entity Wall Switch (Left)_158d00031348bf: off>: {'channel_0': 'click'}
2019-06-21 00:13:33 DEBUG (MainThread) [homeassistant.components.xiaomi_aqara] PUSH >> <Entity Wall Switch (Right)_158d00031348bf: off>: {'channel_0': 'click'}
2019-06-21 00:13:33 DEBUG (MainThread) [homeassistant.components.xiaomi_aqara] PUSH >> <Entity Wall Switch (Left)_158d00031348bf: off>: {'channel_0': 'click'}
2019-06-21 00:13:33 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event xiaomi_aqara.click[L]: entity_id=binary_sensor.vswitch, click_type=single>

I’ve tried both the original Xiaomi and the custom component I normally use (harware hacked motion sensors), but result is the same.

States shows sensors correctly and I’ve tried numerous syntax variants of this particular automation, but no luck.

Have i completely missed something obvious or… ??

Regards
Henning

2

[SOLVED]
Automation works fine…
Problem was editing with Visual Studio Code was showing cached automations.yaml files which was actually not saved to Hassio sd card :frowning: :frowning: :rage:

I didn’t pay much attention to automations file actual date/time stamp until now.
Have to find the reason for this sudden Visual Studio Code behaviour…