fix(hue): Fix Mirek -> Kelvin conversion constant. #1934
Merged
Conversation
This file contains 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
|
Channel deleted. |
|
Minimum allowed coverage is Generated by 🐒 cobertura-action against 153c9d6 |
1368feb to
cf090e5
Compare
NoahCornell
approved these changes
Feb 13, 2025
cjswedes
approved these changes
Feb 13, 2025
greens
approved these changes
Feb 25, 2025
This constant should be 100, but I resolved a conflict during a rebase incorrectly when prepping the original PR and it got set to 11 instead of 100.
If the bulb's color temperature changes because of an ST-initiated user requested setpoint, we emit that directly instead of clamping to the step size. This is to remain consistent with the way things are done on the rest of the platform with other integrations.
cf090e5 to
59b1da3
Compare
kdbang
approved these changes
Mar 4, 2025
The existing logic utilized the device persistent fields to determine if a range update was needed, as to avoid un-necessary attribute emits. This would lead to existing devices not ever emitting the min/max color temp range values if the saved min/max matched what was reported by the API. This is adjusted to use the cached latest state for the device instead, so that we can detect the `nil` if the device has never emitted a value for its range.
This was referenced Mar 6, 2025
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.
Type of Change
Checklist
Description of Change
This constant should be 100, but I resolved a conflict during a rebase incorrectly when prepping the original PR and it got set to 11 instead of 100.
Summary of Completed Tests