Hi,
As the topic says the “Additional settings” on the lovlace ui ore not shown when the light entity is “Off”.
But when i turn it on, i can see the tunable white slider (for example)
Same thing happens on RGB. Is this a setting in the lovlace ui card?
[I’d put the image here but i am not allowed tp post more than one image in a post (BTW Thats shitty)]
Id’ always like to the the whole settings in the popup
I am using the standard cards. Any ideas?
Thanks & best regards
Why?
You can’t use them if the light is off.
lol - he’s found a totally new kind of light with ‘fuzzy logic’ . It can be off but actually on at the same time
If I was you I wouldn’t laughing.
In fact you can.
there are devices (light controllers) which accepts changing light attributes when light is off. It’s pretty helpfull for several use cases like circadian lighting for example.
Because light attributes can be passed to light_on call, setting those attributes prior in order to turn light on with requested values is another use-case which would profit from it.
I don’t understand the motivation of devs who had to intentionally programm hiding those attributes. In result, to achieve changing the attributes when light is off, one has to dodge HA, sending commands to devices other ways (mqtt, http api etc). But GUI remains not usable for such usacase
I wasn’t laughing.
I have Lifx lights. Their attributes can be set when off. After three years of using home assistant I’ve never found a use for that service.
Oh this gets better.
WTF.
So the speed of light (electromagnetic spectrum) and electrons moving through the computer and wiring and lights, are so poor, that there is a need to set attributes when the light is off, so that when it comes on, it has the ‘right settings’.
oh god. come on.
Tell you what, I’m laughing if Tom aint, I’m howling. I would say at you with that response, but that would be most discourteous of me and unfair. So I won’t. I’ll just unwatch this thread and leave you to it
This comment was unnecessary. It doesn’t matter if his take on this doesn’t serve your use cases. The point is, there isn’t a reason (that I can think of) why he shouldn’t be able to see the light colors while they are off. If you have some insight into that, great. If not, keep your crappy responses to yourself. Just because you don’t agree with his approach, that doesn’t make it wrong.
I had. I wanted to turn on a light making sure it’s dimmed (because of a few day old child). But as you know light card doesn’t show brightness slider when light is turned off.
BTW my response about laughing wasn’t directed to you but to post above mine.
I There is a card from HACS that has this option
thanks I didn’t know it has such feature.
For brightness I’m using custom row slider card.
Pity newcomer gets no this featuru starting with “wth” then being forced to use custom cards. I don’mt know single reason why it couldn’t be provided by vanilla ha
Actually that is one attribute it should ( and usually does) show, as lights can be turned on with it.
I wouldn’t bet my live on that, but it must be recent change. IMO half year ago it was not here.
But then… why not to show color picker? You can turn a light with that too.
Look at the screen shot you posted. There is a brightness slider at the bottom of the more info card and the light is off.
All my lights have had this for the three years I’ve been using HA.
I’m not so sure about that. Never tried it ( because it is not visible).
It wasn’t me. But you might be right.
since lights are turned on using light_on service call, and the service accepts colour attributes as arguments (even alone) - yes, it’s possible
Not for all lights LIFX has a set state service that changes the attributes without switching on.
Also I expect the light to turn on when I increase the brightness up from 0. If the light is off and I change the colour temp that’s not the same thing at all.
I’m talking about HA light entity service methods which are used by HA. HA doesn’t use device specific calls for obvious reasons. Light provides only turn_on, turn_off and toggle service methods. And only those services are being used by HA GUI (unless there is option to reconfigure to use custom services)
If your need is to change warmth/color not turning on the light at the same time, I’m entitled to have the same need in regard of brightness, isn’t it?
But you make actually a good point. IMO it’s all about not flexible GUI, limited to only selected user-case. Unfortunately it’s not about the GUI only. The root cause lays deeper in limited features of light entity (see above)
Wow… Interesting kind of responses to my question.
Covering that up, the answer to my question is
“Not that doesn’t work out of the box with the standard element but here are 3rd party elements that will do”
Okay got it.
BTW: setting properties while having an entity off is not a wired thing at all. At least not for me.
But that was not the reason why i asked this “dumb” question.
The main reason was that I’d like to see the color settings even if the lamp is off.
And the second reason is the that GUI’s should not do that like this. GUI’s should disable controls when they are not intended to be used instead to hide them (that only refers to “live” views not to parameterized ones of course). That’s the thing i have learned and at least that seems to be common in non Web UX. But that’s another story and i understand that it may be not the case in WebUx
@ninjaef open your mind and please don’t respond to my questions anymore if you do not have a valuable contribution. Thanks!
All others, thank you for your responses & best regards
Hey @ChriD,
I think your question is legit and I’m not happy with the answers. I don’t think custom component is the way to solve this. I think possibility to turn light in specific colour or temperature should be part of the UI. As somebody already mentioned it is possible to turn it on on specific brightness so why not on any attribute. This is very important for example in the night when I want to turn the light red instead in previous color/intensity.
Moreover I want to see in what settings the light was turned off to know how it will look like when I turn it on again.
Hope we will get better answers why it is not in vanilla HA.
Cheers,
Michal
@pigotka I had a look into the code. Showing the additional info is very easy, but i am not sure if they will accept a pull request event if i parameterize it. Because i’d change the behavior of the “Brightness” slider too that it wont set the lamp on so the settings would be consistent. Not sure if this would have any side effects.
But only to show the additional info is an easy change i
EDIT: Okay. I see that all additional settings will turn on the lamp too if they are changed. So the consistency would be okay. To change the behaviour that you can change settings and then turn on the lamp seems to be a little bit harder. But i think i can do it too.
So i think i will try to add 2 new parameters.
One that will allow the additional settings to be shown always, and another one that changes the behaviour of the settings.
EDIT 2: Okay. Had a further look and changing the behaviour itself (that the light wont turn on on changing settings) would lead to have all existing light components (Artnet, KNX; aso…) to be updated (that means all 3rd party libs XD)
That’s because home assistant core only has turnOn and turnOff methods for the light. Not sure why they do not have some kind of “set” method. In my opinion thats a big flaw. In fact each entity should have a set method. I have no idea why this was designed like this. I think this is a big flaw 
I never asked for second approach. Turning the light on on any change is perfectly fine for me.
Although I can see situation when I need to change multiple attributes before calling turn_on service. For this I have automations. Most lights could accept brightness 0 to keep them off even while calling light_on service but it is not a general rule.