Remove white_value support from light

[emontnemery]

Breaking change

Support for white_value, which was deprecated in Home Assistant Core 2021.5, has been removed.

Proposed change

Remove white_value support from light

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:

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
• The code has been formatted using Black (black --fast 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.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

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

[probot-home-assistant]

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

[probot-home-assistant]

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

[probot-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!
_{^{(message by CodeOwnersMention)}}

[epenet]

Did we raise a warning for custom components?

[emontnemery]

@epenet good point. the feature has been deprecated for almost 1.5 years, and it seems to be used by only a handful custom components published on HACS:

# grep -ril "white_value" .
./basnijholt/adaptive-lighting/custom_components/adaptive_lighting/switch.py
./Mr-Groch/HA-Emulated-Color-Temp-Light/custom_components/emulated_color_temp/light.py
./twrecked/hass-virtual/custom_components/virtual/light.py
./claytonjn/hass-circadian_lighting/custom_components/circadian_lighting/switch.py
./andvikt/mega_hacs/custom_components/mega/light.py
./StyraHem/ShellyForHASS/custom_components/shelly/light.py

I think it's enough to publish a dev blog + create issues on the relevant repos?

[epenet]

I think it's enough to publish a dev blog + create issues on the relevant repos?

It was just something that I spotted - so I thought I would raise it. I don't use any of those custom components so I'd be fine with that 😜