fix: Cast led_override_color_brightness from API to int#954
Merged
Conversation
Owner
|
Nice! Please add a small test as well |
Contributor
Author
|
@Kane610 done ✅ |
Owner
|
Thanks! I'll try to do a release tomorrow |
This was referenced Nov 19, 2025
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
2 participants
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.
The device API sometimes returns the
led_override_color_brightnessasstr.I've now managed to observe this behavior in the wild on my setup with the debugger attached!
Adds a cast to
intto ensure consistent datatypes for downstream consumers.As discussed here: home-assistant/core#155936 (comment)
I can open a PR to HA once the fixed version is available.