I have an automation that turns on various accent lights around the house, including an Inovelli dimmer for the dining room. The automation runs, sets the dining light to 45 percent brightness 30 minutes before sunset and all is relatively good.
However, I grumbles from the family because sometimes they will be in the dining room working and especially on a cloudy-ish day where they’ve turned the light on to full bright before the automation has gone off.
Is there a way to set something like if dining is already at X brightness don’t change ?
Or a range of brightness: If dining is 45-100%, don’t change
I looked at Conditions but didn’t get far, is it Condition and Condition State, then specify the range? Where does the Condition set go in conjunction with the DIning Light?
This is what I setup, which did not turn the lights on at all, when they were off this morning. Conditional State, above set to 75. So, if the light is on and above 75% brightness I don’t want it to run because that assumes we already turned the light on. Do I need a “below” number as well?
You have to specify that you’re testing the brightness attribute.
Also, it goes form 0 → 255, so 75% would be 192 (unless your light have someting like an brightness_pct attribute. See the state in the developer tools to know.
Also, if I understand you correctly, you actually only want the action to run if brightness is below a value
Yes, if the light is already on I don’t want it to run the “wakeup” cycle. As in; on a normal day 6:30am is a good enough start time for my wife and I’s wake up routine. On occasion one of us has to go into work early in which we’d have already turned the bathroom lights on to full bright at say 6:15am. I don’t want the “wake-up” routine to run because it’s going to dim the light back down to 50% then 75% then 100 finally.
And my sincerest apologies for pasting in the wrong code to start with. The last one, Turn on Powder is what I’m working on.
This is the current code which did not turn the lights on this morning. Brightness of 108 is about 40%, so I went with 120 as the “below”. It seems like were on the right track, the light was off this morning so brightness was at zero, so why wouldn’t it pass the condition and turn things on?
I’m obviously no expert, but to me if the light is off that equals a condition attribute of zero so why does it not pass and move on? Looking at the Conditions example it should:
condition:
alias: "Paulus home OR temperature below 20"
condition: or
conditions:
- condition: state
entity_id: "device_tracker.paulus"
state: "home"
- condition: numeric_state
entity_id: "sensor.temperature"
below: 20
Zero brightness is still below 120 brightness so it should pass that condition move on down correct?