Add LIFX Beam to lights list in products.py, casting it as a MultiZoneLight
#150
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
|
Thank you for troubleshooting this! This was just fixed as a part of a large update of products.py in #153. |
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.
Currently, whenever a LIFX Beam is a part of a Group, it's cast as a generic
Device, limiting its function. Inproducts.py, its index is excluded fromlights, so it's never cast correctly.I tried testing this by adding the index to the lights list at Runtime in a REPL, which caused it to be discovered as a MultiZoneLight next time I ran
LifxLAN().discover