Updating max and min brightness to adaptive lighting from app

[Pythm]

What's Changed

This is a continuation of the release to use Adaptive Lighting custom component to control brightness and color temp with support to set the 'max_brightness' and 'min_brightness' from automation, motion and modes.

If max_brightness is not defined with state adaptive the app will set values back to initial startup values as you configured in Adaptive Lighting. In addition to max_brightness you can define min_brightness. The app will not react to min_brightness if not max_brightness is also configured. Typical use case is to differentiate light when motion is detected, and also keep a dimmed down light in rooms that are not occupied, or dim further down with modes activated when TV/media player is turned on.

There is no need to configure Adaptive Lighting with 'detect_non_ha_changes' or 'take_over_control' when you set it up, if you only use Lightwand and Adaptive Lighting as automations for light. Lightwand will set manual control with the provided "Adaptive Lighting" switch that you'll need to define in your room with if a state or mode does not use Adaptive lighting.

  adaptive_switch: switch.adaptive_lighting_yourName

The normal 'automations' is a list. To include max and min brightness it looks like this:

      automations:
      - state: adaptive
        max_brightness: 60
        min_brightness: 10

To use when motion configure with:

      motionlights:
        state: adaptive
        max_brightness: 80
        min_brightness: 30

To use in mode configure with:

      light_modes:
        - mode: your_mode
          state: adaptive
          max_brightness: 100
          min_brightness: 1

Automatic setting of Adaptive Lighting's "Sleep Mode" is now also implemented. All you need to do is define the switch in room with:

  adaptive_sleep_mode: switch.adaptive_lighting_sleep_mode_yourName

The switch will then be activated when night mode is called and keep light at a minimum as configured in Adaptive light, instead of turning it off. This applies to both 'night' and 'night_' + appName.

I do not use Adaptive Lighting actively so please report any unwanted behaviour.

---

This discussion was created from the release Updating max and min brightness to adaptive lighting from app.

[pointlevel]

Its like christmas to open your emails in the morning :) Thanks for the updates.

I notice a problem that when motion is activated, the lights will only crank up when adaptive is doing an update, default 90 seconds.
This setting is configurable by "interval: 1" but that would crash the adaptive/mqtt i believe with a lot of unwanted traffic.

I also notice that the lights is never in the manual_control state in the switch, either in motion or no_motion?

At some times when activating motion, the lights turns on, but after like a seconds it turns down again. (manual_control-problem?)

[pointlevel]

I have grouped the kitchen motion lights in z2m and changed both in AL and LW to use this group instead. I have also deleted the "mode_turn_off_delay: 5" and "mode_turn_on_delay: 5" from LW and also the delay for the motion-sensor.
It seems to work when there is motion, but is waiting for the update from AL before lowering down the lights when no motion.

Looking at the map in z2m seems like my network is good by the values. I have alot of routers and just a couple of end-devices. I have a new coordinator that is supposed to be one of the best and running z2m aside from HA in an LXC with a lot of power, so i dont think there is any problem with my zigbee-network.

[pointlevel]

Correction: It doesnt lower the lights when AL updates. I tried to change the interval in AL to 10 seconds. And when no_motion its still taking a lot of time before its dimming down again, around 60 seconds. I can also confirm that AL is updating during this time, without dimming down the lights.

I also have an input_boolean for fake motion as test in LW, without delay so i know there is no delay in some sensor that could be those 60 seconds.

[Pythm]

There is a default delay to 60 if not provided. Well hidden in the readme... . I will try to make it more obvious. It was put there to not have disco lights with normal motion detection.

The mode turn on/off would still apply I belive, but It would not help much when Adaptive Lighting is creating all the traffic.

[pointlevel]

There is a default delay to 60 if not provided.

Ahh, of course, my bad!

[Pythm]

I had to check the code if it was there, so I did not think of that at all before you mentioned it. Had completely forgotten it...

[pointlevel]

Can...

options:
    - dim_while_motion

...have any impact?

[Pythm]

No, that option only applies if you have light data with brightness in some mode set higher than brightness in light data for motion or if brightness is lowered with time automation

[pointlevel]

With this setting:

adaptive_switch: switch.adaptive_lighting_kitchen_motion

It means that i only can have one adaptive light(-group) in the same room, right?

[pointlevel]

The same with this one:

adaptive_sleep_mode: switch.adaptive_lighting_sleep_mode_yourName

Usecase: If i want only a specified group to act as night-lights.

[Pythm]

Not for long.. I thought one would do but will update. Getting more complex but makes more sens when setting min/max brightness from light.

Adaptive sleep mode only applies to lights with adaptive configured. If you have lights configured with adaptive, you can always override mode night with state: turn_off.

I belive I can do as with options so you can configure both switches in both room and light, where the switch configured under light will overwrite the room switch.

[pointlevel]

Maybe i should write this in the Issues tab, but now it goes here.

This one is not working, the lights just flickers for milliseconds up a bit to then go back to normal when changing mode to "cooking".

light_modes:
   - mode: cooking
     state: adaptive
     max_brightness: 100
     min_brightness: 100

(Maybe thats the bug you were talking about that you found?)

[Pythm]

yep. Will post the update later