Use Attribute enum in light

[epenet]

Proposed change

As follow-up to #174589

Linked to home-assistant/epics#104

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 #
• This PR is related to issue:
• Link to documentation pull request:
• Link to developer documentation pull request:
• Link to frontend pull request:

Checklist

• I understand the code I am submitting and can explain how it works.
• 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.
• Any generated code has been carefully reviewed for correctness and compliance with project standards.

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 diff between library versions and ideally a link to the changelog/release notes 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 mark-draft Mark the pull request as draft.
• @home-assistant ready-for-review Remove the draft status from 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 update-branch Update the pull request branch with the base branch.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) on the pull request.

[Copilot]

Pull request overview

This PR continues the epic (#104) started in #174589, which introduced the LightEntityStateAttribute and LightEntityCapabilityAttribute StrEnums in light/const.py. It replaces raw ATTR_* string constants used to read/compare light entity state and capability attributes with the corresponding enum members, improving type safety and clarity. Since each enum member's value is identical to the original constant string, the change is behavior-preserving.

Changes:

• Migrated state-attribute reads/comparisons in trigger.py, condition.py, significant_change.py, and reproduce_state.py to LightEntityStateAttribute.
• Migrated capability-attribute reads in __init__.py to LightEntityCapabilityAttribute.SUPPORTED_COLOR_MODES.
• Restructured reproduce_state.py's ATTR_GROUP/COLOR_GROUP into (state_attribute_enum, service_parameter_str) tuples to clearly separate the state attribute (used for reads) from the service-call parameter (used for writes).

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
homeassistant/components/light/trigger.py	Uses LightEntityStateAttribute.BRIGHTNESS in the brightness domain spec and drops the now-unused ATTR_BRIGHTNESS import.
homeassistant/components/light/condition.py	Same enum substitution for the brightness condition domain spec.
homeassistant/components/light/significant_change.py	Replaces ATTR_* reads with enum members and simplifies imports to LightEntityStateAttribute.
homeassistant/components/light/reproduce_state.py	Converts attribute groups to (enum, service_arg) tuples, updates helpers/typing, and removes the unused ATTR_COLOR_MODE import.
homeassistant/components/light/init.py	Reads supported_color_modes from state/registry via LightEntityCapabilityAttribute.SUPPORTED_COLOR_MODES.

I verified that every enum member value matches its original ATTR_* string constant, that no stale ATTR_* references remain after the import changes, and that the reproduce_state.py restructuring keeps reads keyed on the state attribute and writes keyed on the service parameter (identical strings for these groups, so no behavioral change). check_attr_equal is only used within its own module, so its narrowed parameter type is safe.

[frenck]

Thanks, @epenet 👍

../Frenck

                       

Blogging my personal ramblings at frenck.dev