As a tip, for reporting, you can set these options per device as well, to make sure not all devices start reporting. Same goes for most device_options, they can be set per device.
Groetjes,

I'm using zigbee2mqtt without any problems.

Thanks for the help, but I wasn't able to resolve anything.
I'm not sure where I need to put the code? should be on all automations?
//snip - repeat: for_each: '{{ state_attr(entity_light, "entity_id") }}' sequence: - service: mqtt.publish data_template: topic: 'zigbee2mqtt/{{state_attr(repeat.item, "friendly_name")}}/set/color_options' payload: | { "execute_if_off": "true" } - service: mqtt.publish data_template: topic: 'zigbee2mqtt/{{state_attr(repeat.item, "friendly_name")}}/set' payload: | { "color_temp": "{{turn_on_quirk_color_temp_mired_current}}", "transition": "0" } //snip

About transition I got 0 on zigbee2mqtt and adapt_delay, on initial_transition got 1 because it helps disguise the change.

Hi there,
I think you are referring to your issue Zigbee2mqtt to fast for adapt?

To 'prime' the color_temp of your lights, which means set them to the wanted color_temp before you turn them on, you would have to make a script in homeassistant. You can read up here on what that entails.

See here for a tested automation that sets the color_temp of zigbee lights that are controlled by adaptive lighting through the mqtt integration.

There is no simpler way to do this a.f.a.i.k.

Hope that helps,
Groetjes,

Thanks for the explanation, but I don't have the same light name on zigbee2mqtt and HA(this was easy fix) but for AL I got only some entity to control several lights. For exemple got a entity call bedrooms that control all the lights on bed rooms.

And as far I also understand, I would need to have a script to every single light I got. :/ a lot of work.

I will wait for zigbee2mqtt are able to do light Philips Hue box was able to do it. If philips hue box do it, zigbee2mqtt sooner or later will be able too.

To keep this topic to the point, I have posted a comment in your issue here: #996 (comment).

Pre 2.0 of z2m there were some legacy options, which are now (mostly) removed IIRC. So the options are either ignored or you need to remove them prior to updating to 2.0.

These here are the settings in question:

Koenkk/zigbee2mqtt#24198

Hi @jncasey,
It does not look pretty but it seems to work:

    enabled_adaptive_lighting_entities: |-
      {%set ns=namespace(entities=[])%}
      {%for _ in integration_entities("adaptive_lighting") |
              select("match", "^switch\.adaptive_lighting_adapt_color_.*") |
              expand |
              selectattr("state", "==", "on") |
              map(attribute="entity_id") |
              list%}
        {%set ns.entities=ns.entities+[_|replace("adapt_color_", "")]%}
      {%endfor%}
      {{ns.entities}}      

Seems that replace() expects and produces strings, so feeding it a list will break down the list into a string.

Will add your color_temp check to the gist later today,

Thanks a lot for the suggestions!
Grt,

Hi @cipheredsyntax,

Also, one of the caveats of your configuration: when turning a light off after you've set it to a different color (temperature) or brightness, it will turn back on with that same previous color (temperature) or brightness if it's within those 5 minutes of the automation updating every light that's off.

The easiest way would be to just increase the frequency of the automation time trigger. This is not a serious solution of course. Adding a trigger for every adaptive lighting light that is turned off might be an option - will have to do some homework there.

Main reason for making the automation was to take away or at least minimize the transition effect observed when turning on any adaptive lighting controlled lights.

Also, to have it work in the most user configuration agnostic way as possible, so anyone should be able to just add it and have it work for them.

If you ask me, without changing adaptive lighting, a script providing "ON" and "OFF" for every adaptive lighting instance would be preferred. But, that cannot be made easily for any configuration out there and would require any light.turn_on/turn_off anywhere to be replaced with that script. (Button on_tap actions in dashboards etc.)

I don't know if you have one readily available, but I tried creating one myself although to no avail as I am too unexperienced in this. I got as far as this:

triggers:
  - platform: state
    entity_id:
        "{{ expand(state_attr('switch.adaptive_lighting_inside', 'configuration').lights) | map(attribute='entity_id') | list }}"
    to: 'off'
actions:
  - variables:
      adaptive_lighting: >-
        {{ integration_entities("adaptive_lighting") |
           select("match", "^switch\.adaptive_lighting_.*") |
           reject("match", "^switch\.adaptive_lighting_adapt_.*") |
           reject("match", "^switch\.adaptive_lighting_sleep_mode_.*") |
           list | first }}
      turned_off_light: "{{ trigger.entity_id }}"

I know that the entity_id trigger doesn't work this way, but hopefully it explains to you what I'm trying to achieve.

I'll have a think about how this can be added to the automation.
Thanks for the suggestion!
Grt,

Hi @cipheredsyntax,
Seems that the state trigger does not accept templates in the entity_id. I thought about making some template sensor that would accept some template to build a list of lights to watch, but according to the documentation these type of template sensors will be evaluated every minute, which makes sense.

For my setup just added the light groups that run adaptive lighting explicitly:

    - trigger: state
      entity_id:
        - light.entrance
        - light.family_room
        - light.living_room
        - light.work_room
        - light.work_room_table
        - light.hallway
        - light.master_bedroom
        - light.sofa_overhead
      to:
        - 'off'

Adding these to the automation as trigger will also run all actions whenever one of my light groups turns off. I do not want this to trigger if any of the lights are controlled outside of the light group on purpose.

Perhaps someone else has a bright idea here to make the automation as generic as possible.

Grt,

Is there something special I need to do to use this?

I checked multiple AL switches but "state_attr(adaptive_lighting_entity, "configuration").lights" is empty (the whole configuration part is emtpy).

Yes, need to enable include_config_in_attributes.

Hi @fbloemhof,
Added some actions to enable include_config_in_attributes.
(Decided to move the gist to a fork of adaptive lighting, feel free to comment/discuss further there.)
Grt,

no, most of my lights are philips hue. Also have two Gledopto working fine now with that command.

Interesting, I don't see this config for my Hue lights, only at some IKEA lights.

Hi @fbloemhof,
Check here, where @sjorge figured out the execute_if_off and sending the color_temp before turning on Hue lights. The zigbee2mqtt frontend does not always show all the functionality of the device, that has to be coded before it is shown.
Groetjes,

no, most of my lights are philips hue. Also have two Gledopto working fine now with that command.

Interesting, I don't see this config for my Hue lights, only at some IKEA lights.

On HA you need to go to Developer > Actions tab > "GO TP YAML MODE" > paste this code:

action: mqtt.publish
data:
  topic: zigbee2mqtt/friendly name/set
  payload: "\"color_options\": {\"execute_if_off\": \"true\"}"

You need to do it for all lights you have, change on the code the friendly name to the same name as you all on each light on zigbee2mqtt

Hello @R3Cardoso, I tried your workaround but nothing worked correctly. The correct brightness is applied only 0.5s after the light turn on, so there is a brief flash with the previous brightness

Hello @R3Cardoso, I tried your workaround but nothing worked correctly. The correct brightness is applied only 0.5s after the light turn on, so there is a brief flash with the previous brightness

Have you set the {"execute_if_off": "true"} to all lights?