Allow settings value to not affect a light below 0

[Mattie432]

hi, great addon.

My use case is that I have 6 lights from Zigbee2MQTT, sending individual commands to each lightbulb is network expensive, so I additionally have these 6 in a group so there's only 1x command being sent.

The bulbs don't get very dim, so I want to turn these on one-by-one between brightness levels 1-6, after that, I want to start using the group as normal.

Group is 0 up till brightness level 7, after which it scales to 100.

Individual light 1 turns on at 1% brightness, should stay at 1% until lightner goes past 6%

Individual light 2 turns on at 2% brightness, should stay on at 1% until lightner goes past 6%

... etc

Up to individual light 6

What actually ends up happening between levels 1-6 is that the individual lights are correctly controlled, they are set to 1% brightness in sequence. But the group is also controlled, setting the group brightness down to 0 (turning them all off).

Suggestion is, to add some additional value to the settings (maybe 1:null) which would mean that the light does not get controlled at all during these levels. For my use case, I would set the group to be 6:null, 7:1 so below 7 % the light is not controlled at all (thus not switching off the group).

[tonypp]

I second this, for a different use case. I have a lamp which exposes two different lights in Home Assistant (Yeelight Ceiling Light with a main mode and a moon mode). Now I'd like to create one lightener light which combines those two, from 1-30 the moon light should be used, from 31-100 the main one. With the current implementation changing the brightness will turn off the lamp, as a brightness = 0 command is being sent to the second light - which unfortunately turns off both modes.

[maximuchka]

Great add-on. I would also appreciate it if this gets implemented. I have over 10 Yeelight lamps, and this would help organize them in the interface.