Migrate zwave_js light tests to use Kelvin

[epenet]

Proposed change

Based on #79591, needed for #132680

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
• 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/z-wave, mind taking a look at this pull request as it has been labeled with an integration (zwave_js) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of zwave_js 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 zwave_js 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, @epenet 👍

../Frenck

[MartinHjelmare]

Why is it 2702 instead of 2700 as above?

[epenet]

2700 above is the "min kelvin" which gets set once

core/homeassistant/components/zwave_js/light.py

Lines 108 to 109 in 72cc1f4

	_attr_min_color_temp_kelvin = 2700 # 370 mireds as a safe default
	_attr_max_color_temp_kelvin = 6500 # 153 mireds as a safe default

2702 is the current value from the integration (looks like a % ratio converted to mireds)

core/homeassistant/components/zwave_js/light.py

Lines 498 to 500 in 72cc1f4

	self._color_temp = color_util.color_temperature_mired_to_kelvin(
	MAX_MIREDS - ((cold_white / 255) * (MAX_MIREDS - MIN_MIREDS))
	)

I see three options:

• the current code is kept with slight rounding discrepencies
• we can change the min/max from 2700/6500 to 2702/6535 to more closely match the previous defaults
• the formula is changed so the % ratio is based on Kelvin and not Mireds

[MartinHjelmare]

I'd use numbers in the tests that make sense when using Kelvin. It looks weird at the moment.