fix: correct supported features type in Tapo light entity #827
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
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.
This pull request fixes a TypeError occurring when Home Assistant expects
supported_featuresto be iterable, but receives an integer instead. The issue has been resolved by ensuring thatsupported_featuresis always a set, even when no effects are supported.I had the same issue as is #825, but I'm owner of Light Bulb L510, so for some reasons code changes from PR #826 didn't work for me, after more tweaking I come to this solution.
Tested with Home Assistant version:
Light Bulb: Tapo L510 Series (software 1.3.1)