Avoid recording additional light attributes

[bdraco]

Breaking change

The following attributes are no longer saved in the database for light entities because their combinations would quickly fill up the database and they are never used by Home Assistant:

• brightness
• color_mode
• color_temp
• color_temp_kelvin
• effect
• hs_color
• rgb_color
• rgbw_color
• rgbww_color
• xy_color

This has no effect on the run time of light entities.

Proposed change

For some cases, these attributes would take up more space in the database than any other data, including all of the long term statistics and states.

We have at least three cases where we can generate a massive amount of data in state_attributes:

• Automations that frequently change light colors
• Lights that report color changes during effects
• Custom integrations like adaptive lighting that frequently change color temp

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes Recorder Many State Attributes for Changing Light Attributes #118670
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[home-assistant]

Hey there @home-assistant/core, mind taking a look at this pull request as it has been labeled with an integration (light) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of light can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign light Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

[frenck]

Thanks, @bdraco 👍

Makes sense right now; maybe in the future these values would be helpful for things like machine learning or away simulations, but that isn't that case right now.

../Frenck