fix: send color_temp_kelvin instead of removed kelvin key - #90
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📬 Changes
Home Assistant removed the
kelvinparameter fromlight.turn_on/light.toggle(it now rejects it:extra keys not allowed @ data['kelvin']). Sendcolor_temp_kelvininstead, in the two places the library callslight.turn_on:light-manager.service.mts— the circadian color-temperature looproom.service.mts— scene applyAlso brings the toolchain current (needed to build against the updated dev-types):
@digital-alchemy/hass@^26.6.13(dev-types now exposecolor_temp_kelvin: number)jsonc→ native flat config; wrapsort-keys-fixvia@eslint/compat)tsconfig: addtypes: ["node"](TS 6 /@types/node25 no longer auto-include node globals)upgradescript with thencu --upgradeform🗒️ Checklist
code of conduct