Add group off_state option

[Koenkk]

Rationale: while the current group state OFF behaviour sounds ideal (group state is only OFF when all members in it are OFF) it is not always practical. I see at least two possible cases where this doesn't work well:

• Given that you have e.g. 5 lights in the group controlled by 1 remote, when the remote turns off the lights; all light OFF report have to be received by the coordinator. If one of the messages is dropped (e.g. due to interference) the coordinator considers the group on. In my use case when using the flux integration, flux will turn the group on again (by changing the color temperature) since it still thinks the group is on.
• If one of the devices in the group doesn't support state reporting (e.g. a Philips Hue bulb) the similar problem as above will occur.

[sjorge]

In my use case when using the flux integration, flux will turn the group on again (by changing the color temperature) since it still thinks the group is on.

If your bulbs support it set the color_options.execute_if_off to true, then you can just send the color_temp command and next time you turn them on the bulbs will be the correct color. (Not that this helps the problem you're describing, but it gives a very smooth experience where all my ct lights are the same color temperature depending on ToD even when they just get turned on!)

[Koenkk]

Good tip, thanks!

[jd1900]

I don't know if I understand the meaning of this.

Is this replacing the old behavior or adding s new one?

I've found no new option under HA or Z2M interface.

Is it that now when a off is sent to the group instead of waiting all the devices to be off it stores the off value? Or something different?

[Koenkk]

@jd1900 the default behaviour didn't change, group config is not possible via the UI, you can set it in the configuration.yaml..

[jd1900]

If your bulbs support it set the color_options.execute_if_off to true

@sjorge How can we configure our lights to change to execute_if_off ?
I've found no documentation.