Bugfix automation fire on bootstrap #6770
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pvizeli
force-pushed
the
automation_on_start
branch
from
5e7ffa7 to
e7c4568
Compare
|
This has the side effect of not being able to have automations that subscribe to the EVENT_HOMEASSISTANT_START. |
|
@pvizeli thank you for this! |
|
@pvizeli So, call me crazy, but I feel like it worked once and now all automations fire every time again. Definitely on .41 |
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Enable automation only on startup of home-assistant or running state
Related issue (if applicable): fixes #6745