Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Event trigger broken in 0.56.1 #10046

Closed
dale3h opened this issue Oct 22, 2017 · 2 comments · Fixed by #10049
Closed

Event trigger broken in 0.56.1 #10046

dale3h opened this issue Oct 22, 2017 · 2 comments · Fixed by #10049

Comments

@dale3h
Copy link
Member

dale3h commented Oct 22, 2017

Home Assistant release (hass --version):
Problem is present in 0.56.1 and 0.57.0.dev0

Python release (python3 --version):
Python 3.5.2

Component/platform:
automation

Description of problem:

2017-10-22 14:15:19 INFO (MainThread) [homeassistant.core] Bus:Handling <Event zwave.scene_activated[L]: scene_id=1, entity_id=zwave.blue_iris_remote, node_id=12>

Expected:
Expected behavior is for the automation to trigger upon the event firing.

Problem-relevant configuration.yaml entries and steps to reproduce:

automation:
  - alias: minimote_button_pressed
    initial_state: 'on'
    trigger:
      - platform: event
        event_type: zwave.scene_activated
    action:
      ...
@emlove
Copy link
Contributor

emlove commented Oct 22, 2017

Likely caused by #9732 I'll take a look

@jamieshaw
Copy link

I'm seeing this too. Triggers monitoring state_changed are failing to execute; condition or otherwise.

@home-assistant home-assistant locked and limited conversation to collaborators Mar 2, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants