# Controlling lights based on lux variables and manual

**URL:** <https://community.homey.app/t/controlling-lights-based-on-lux-variables-and-manual/154716>\
**Category:** Questions & Help\
**Created:** [May 10, 2026, 8:19am UTC](https://community.homey.app/t/controlling-lights-based-on-lux-variables-and-manual/154716 "2026-05-10T08:19:43Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Julian\_Borghuis](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/julian_borghuis/32/113503_2.png) [@Julian\_Borghuis](https://community.homey.app/u/Julian_Borghuis)\
**Post date:** [May 10, 2026, 8:19am UTC](https://community.homey.app/t/controlling-lights-based-on-lux-variables-and-manual/154716/1 "2026-05-10T08:19:43Z")

</div>

Hi everyone!

I currently control my living room lights based on lux values. However, I’m struggling with the situation where I also want to manually control the lights sometimes.

Right now, I have a flow that checks a variable. If the variable is set to “yes,” the lights won’t turn on or off automatically based on the lux values. The issue I’m facing is deciding when to set that variable back to “no” so the automation starts working again.

I want to keep it as simple and user-friendly as possible for others in the house, but I honestly have no idea what the best approach would be.

Good to know is that i am using buttons instead of switches.

Do you guys have any tips or ideas? Let me know! Complete other ideas are also welcome!

---

<div class="post-metadata">

**Author:** ![Bubiai\_2](https://avatars.discourse-cdn.com/v4/letter/b/9f8e36/32.png) [@Bubiai\_2](https://community.homey.app/u/Bubiai_2)\
**Post date:** [May 10, 2026, 9:01am UTC](https://community.homey.app/t/controlling-lights-based-on-lux-variables-and-manual/154716/2 "2026-05-10T09:01:56Z")

</div>

If I understood the core of the problem correctly—I used Virtual Devices (sockets) to solve it. When the outdoor lux level matches ‘Day,’ the VD plug is OFF. When lux equals [value], it’s ‘Night’ and the plug is ON. I assigned different modes to rooms and scenes, such as Auto, Manual, Scene, TV, and Sleep. If someone presses a button, the automation switches to Manual mode and stays that way until the next trigger. (Ex.If the zone is inactive for … min: Auto = ON, Manual = OFF.)

---

<div class="post-metadata">

**Author:** ![Wim\_Post](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/wim_post/32/56793_2.png) [@Wim\_Post](https://community.homey.app/u/Wim_Post)\
**Post date:** [May 10, 2026, 10:24am UTC](https://community.homey.app/t/controlling-lights-based-on-lux-variables-and-manual/154716/3 "2026-05-10T10:24:29Z")

</div>

For your inspiration:  
I have this flow for the light above my countertop.  
One YES/NO-variable ‘keuken handmatig aan’  
One number-variable ‘lux keuken’ with the luxvalue I want to turn on the lightstrip.  
One number-variable ‘dimlevel’. The value of the last one is changed by the different triggers. The fun part is when the value is ‘changed’ from 0.5 to 0.5 Homey doesn’t sees it as a change, so nothing happens. If it does changes the trigger at the bottom is activated.

 ![IMG2164](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/d/fd1f5f0eecdfe9fdef5b0ed122a4a6f3979be56f.jpeg)

Near the countertop I have a button:  
One click: on/off manually  
Double click: dimlevel 1 and color temperature 0.

The timer is started by movement in the garden. When I am away or asleep the light is off. When the timer reaches 135 seconds left the light turns on, thus mimicking my reaction to the movement.😜

---

<div class="post-metadata">

**Author:** ![dsdevries](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dsdevries/32/80220_2.png) [@dsdevries](https://community.homey.app/u/dsdevries)\
**Post date:** [June 5, 2026, 2:54pm UTC](https://community.homey.app/t/controlling-lights-based-on-lux-variables-and-manual/154716/4 "2026-06-05T14:54:01Z")

</div>

@Julian_Borghuis  
I’ve written an extensive tutorial that covers exactly your wishes. You can find it here:  
I use a virtual motion trigger to gain extra control over enabling and disabling the automatic flows. Because a virtual motion trigger is a simple device in the device list that you can also enable and disable, it is very user friendly!

> [@\[HOW TO\] Gain full control over Zone Activity using Motion Sensors (PIR), Presence Sensors (Aqara FP300) and Virtual Motion Triggers](https://community.homey.app/t/how-to-gain-full-control-over-zone-activity-using-motion-sensors-pir-presence-sensors-aqara-fp300-and-virtual-motion-triggers/144082):
>
> UPDATE: Added implementation using AQARA FP300 presence sensor below Introduction This is not a guide on how to implement a specific use case, but rather a framework that will give you full control over zone activity. Many flows like turning on/off lights could be done much simpler. However, when my personal flows became more complex, I ran into a lot of caveats and quirks that caused me to rethink how I work with motion sensors. I came up with this system which allowed me to solve all the bugs …

You can even use Homey’s moods feature and disable automatic dimming when a specific mood is activated:

 ![Screenshot 2026-06-05 at 16.57.39](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/3/a32750140fd3e20c561b78af79c25bdd4f75d786.png)
