💡 Sensor Light - Motion Sensor - Door Sensor - Sun Elevation - LUX Value - Scenes - Time - Light Control - Device Tracker - Night Lights

[Blacky]

@aberenguel

Welcome to the community.

Thanks for your suggestion.

The blueprint is working correctly, the issue is that you’re manually turning OFF the light instead of letting the automation handle it. If you prefer the light to turn ON automatically but then require you to turn it OFF manually, you could try my Smart Light

It’s great that your lux sensor reports quickly, but in your case it may actually work better if it reacts more slowly. This really depends on how your motion sensor behaves. For example, if your motion sensor remains in the “detected” state for a while after you enter the room, slowing down the lux sensor’s reporting can prevent the light from turning back on too soon after you manually switch it off. By keeping the lux value higher for a little longer, it gives your motion sensor enough time to clear before the light is allowed to turn on again.

To achieve this, you can either adjust the reporting interval of your lux sensor or create a template sensor that smooths the lux readings, then use that template sensor in the automation.

@aberenguel

PS: The diff also includes a small correction to the t10 trigger. Removing the ambient_light_option_disabled check allows the “turn off light when lux is high” feature to work correctly, even when the “sensor is affected by lights” option is enabled.

This then would break the condition and why it is there.

Blacky