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
Exclude attributes for automation and script domains #70168
Exclude attributes for automation and script domains #70168
Conversation
- The last_triggered was already being saved via restore state
Hey there @home-assistant/core, mind taking a look at this pull request as it has been labeled with an integration ( |
Hey there @home-assistant/core, mind taking a look at this pull request as it has been labeled with an integration ( |
…_script_automation
…_script_automation
…_script_automation
Will need a rebase after #70217 |
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.
Thanks, @bdraco 👍
May need to merge #70217 first pending discussion in #70183 (comment)
Breaking change
The
script
andautomation
entities no longer record thelast_triggered
,max
,current
,mode
,id
, andlast_action
attributes in the database.This does not affect the attributes that are restored at startup as they are not restored from the database.
Proposed change
Type of change
Additional information
Checklist
black --fast homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
..coveragerc
.The integration reached or maintains the following Integration Quality Scale:
To help with the load of incoming pull requests: