-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adjustable brightness levels and Moodlight defaults #12
Comments
Currently working (0.4.0-dev) moodlight switcher automations, which would work better if handled by component: - alias: lanbon-moodlight-idle
initial_state: 'on'
trigger:
- platform: state
entity_id: sensor.plate_idle
from: 'short'
to: 'long'
action:
- service: mqtt.publish
data:
topic: hasp/plate/command/page
payload: 1
- service: mqtt.publish
data:
topic: hasp/plate/command/moodlight
payload: '{"state":"ON","color":{"r":255,"g":0,"b":255}}'
- alias: lanbon-moodlight-idle-not
initial_state: 'on'
trigger:
- platform: state
entity_id: sensor.plate_idle
from: 'long'
to: 'off'
action:
- service: mqtt.publish
data:
topic: hasp/plate/command/moodlight
payload: '{"state":"OFF","color":{"r":255,"g":0,"b":255}}'
|
I will definitely implement moodlight as a HA light entity with all the associated services. |
Autodiscovery with 0.4.0-dev already does this for moodlight and backlight. |
But! Moodlight colors are forgotten between restarts. |
Tested with new component version:
|
please check the latest release |
Color still forgotten by the component after power-cycling the plate. |
Would be nice to have these configurable from yaml, as more plates can be present in the system and they may require different settings:
idle_brightness
andawake_brightness
dynamically at HA runtime. To use with automations which could monitor light conditions in the room.The text was updated successfully, but these errors were encountered: