Release 3.0.0 - Backlight/Ambilight Support #116
Merged
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 PR introduces initial support for controlling the power, brightness and color of the backlight (also known as ambilight) of YeeLight devices that have support for it. 🎉
It also changes the way moonlight mode is detected to not depend on model names, instead looking for the presence of the property
active_mode
, which should only exist in devices supporting moonlight, according to the spec. This also allows the feature to be blacklisted inconfig.json
in case you don't want it (see README on how to blacklist features).Please note that 3.x requires node >= 16.16 and homebridge >= 1.3.0.
Related issues: #102, #81, #78, #65, #51, #40, #108
Not seeing the new features?
Your device might be cached. Edit the
config.json
and add the following block (replace5c4bc1
with the id of your device) and restart homebridge.Your device will disappear from the Home app.
After that you can revert back your
config.json
(removing"blacklist": true
) and restart homebridge.