Skip to content

Bugfix automation fire on bootstrap#6770

Merged
balloob merged 3 commits into
home-assistant:devfrom
pvizeli:automation_on_start
Mar 24, 2017
Merged

Bugfix automation fire on bootstrap#6770
balloob merged 3 commits into
home-assistant:devfrom
pvizeli:automation_on_start

Conversation

@pvizeli
Copy link
Copy Markdown
Member

@pvizeli pvizeli commented Mar 24, 2017

Description:

Enable automation only on startup of home-assistant or running state

  • unittest

Related issue (if applicable): fixes #6745

@pvizeli pvizeli added this to the 0.41 milestone Mar 24, 2017
@mention-bot
Copy link
Copy Markdown

@pvizeli, thanks for your PR! By analyzing the history of the files in this pull request, we identified @balloob, @milaq and @fabaff to be potential reviewers.

@balloob balloob merged commit f4e9466 into home-assistant:dev Mar 24, 2017
@lwis
Copy link
Copy Markdown
Member

lwis commented Mar 25, 2017

This has the side effect of not being able to have automations that subscribe to the EVENT_HOMEASSISTANT_START.

@cmsimike
Copy link
Copy Markdown
Contributor

@pvizeli thank you for this!

@cmsimike
Copy link
Copy Markdown
Contributor

@pvizeli So, call me crazy, but I feel like it worked once and now all automations fire every time again. Definitely on .41
image

@fabaff fabaff mentioned this pull request Apr 6, 2017
@home-assistant home-assistant locked and limited conversation to collaborators Jul 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Automations fire on hass startup

7 participants