-
-
Notifications
You must be signed in to change notification settings - Fork 33.8k
Remove deprecated automation keywords #8510 8000
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree it's been long enough. Let's keep the test though.
'trigger': { | ||
'platform': 'state', | ||
'entity_id': 'test.entity', | ||
'state': 'world' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's keep this test and just change this to to
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That test already exists in test_if_fires_on_entity_change_with_to_filter
or am I missing something?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, you're right. My mistake!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🐦
For those clicking through looking to fix their HA... Find all TRIGGER CONDITIONS that use "state:" Example: From:
TO:
|
Thanks @runraid – I have copied your instructions to the top of this issue to make them more visible, hope you don't mind. |
Given the following config:
should |
@frekel No. Do not change conditions, only change triggers. |
@amelchio I'm having trouble identifying what the issue is with my changes to comply with the Thanks so much, really appreciate it... |
@brianjking Please look at the docs little more carefully. No changes to |
Please limit PR comments to development discussion. Further config questions can be directed to one of our support channels: https://home-assistant.io/help/ |
Description:
The state trigger keyword
state
and the time trigger keywordafter
were deprecated in 0.46. I think now is a good time to remove them completely.For those clicking through looking to fix their HA
Find all
platform: state
TRIGGERS that use "state:
"Change those to "
to:
"Do the same for
platform: time
TRIGGERS, i.e. change "after:
" to "at:
"Note: Only TRIGGERS (not conditions)!
Example:
FROM:
TO:
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.io#2997
Checklist:
If user exposed functionality or configuration variables are added/changed:
If the code does not interact with devices:
tox
run successfully. Your PR cannot be merged unless tests passaddedremoved to verify that the new code works.