# Prevent light from dimming to 0 **URL:** \ **Category:** Questions & Help\ **Tags:** ikea, advancedflow\ **Created:** [November 4, 2026, 3:59pm UTC](https://community.homey.app/t/prevent-light-from-dimming-to-0/161775 "2026-11-04T15:59:29Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![tb\_e](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tb_e/32/178798_2.png) [@tb\_e](https://community.homey.app/u/tb_e)\ **Post date:** [November 4, 2026, 3:59pm UTC](https://community.homey.app/t/prevent-light-from-dimming-to-0/161775/1 "2026-11-04T15:59:29Z")
As I’m getting started with Homey I’ve tried to replicate the default functionality of my IKEA Bilresa & Kajplats remote and light bulb as close as I can with the advanced workflow. What I unfortunately cannot figure out is how to prevent the bulb from turning off when I dim the light as much as I can. I’ve added an extension which immediately turns the light back on if I dim it to 0, but that causes the light to briefly turn off and is overall unpleasant. Is there a way to trigger the “stop dimming” when the dim value reaches a certain number, or is there some other way to create this behaviour? I’d rather avoid getting into full scripts. ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/8/98a34a8e943b02c197bea5036febe1487596a9e8.png) Also, since I’m making this posts anyway, does this seem like a reasonable flow on the whole? Or are there perhaps more clever ways in which I could have gone about this. ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/9/59579c028b8b7b471ab1f96c0228afabd60a0ec0.png) ---
**Author:** ![discourse\_ai\_spam](https://avatars.discourse-cdn.com/v4/letter/d/c68b51/32.png) [@discourse\_ai\_spam](https://community.homey.app/u/discourse_ai_spam)\ **Post date:** [November 4, 2026, 3:59pm UTC](https://community.homey.app/t/prevent-light-from-dimming-to-0/161775/2 "2026-11-04T15:59:41Z")
Unlisted on November 4, 2026, 3:59pm UTC ---
**Author:** ![system](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/system/32/1_2.png) [@system](https://community.homey.app/u/system)\ **Post date:** [November 4, 2026, 5:18pm UTC](https://community.homey.app/t/prevent-light-from-dimming-to-0/161775/3 "2026-11-04T17:18:40Z")
Listed on November 4, 2026, 5:18pm UTC ---
**Author:** ![Drako74](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/drako74/32/150506_2.png) [@Drako74](https://community.homey.app/u/Drako74)\ **Post date:** [November 4, 2026, 6:24pm UTC](https://community.homey.app/t/prevent-light-from-dimming-to-0/161775/4 "2026-11-04T18:24:13Z")
> [@tb\_e](#): > > What I unfortunately cannot figure out is how to prevent the bulb from turning off when I dim the light as much as I can. Hello, My solution to this problem is below. The key part is highlighted, preventing the dim value from ever getting to zero. The dim percentage is expressed in Homey for most lights as a value from 0 to 1, so 10% would be 0.1 and 90% 0.9. By checking if the dim level is greater than 0.19 (or 19%) and the decrements being 0.1 (or 10%) when you get down to 20% brightness it will only allow one more dim down to 10%, and then it won’t go any lower, so won’t turn off. ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/1/3116e748f54e6c32a72e8f5f4f938048a035e4b6.png) The other half of that automation is in a separate Flow (separating the button logic from the hardware control, allowed me to re-use the hardware control in other Flows… you could easily stitch the two together and receive the same result.) ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/7/078f396a4315ebc5690d332ad035354a30111459.png) ---
**Author:** ![tb\_e](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tb_e/32/178798_2.png) [@tb\_e](https://community.homey.app/u/tb_e)\ **Post date:** [November 4, 2026, 6:57pm UTC](https://community.homey.app/t/prevent-light-from-dimming-to-0/161775/5 "2026-11-04T18:57:14Z")
I don’t quite understand how these items are passed through to the other flow, though as far as I can gather it would seem we go about dimming in different ways. If I did it in steps I would be able to figure it out, I did something similar for the light temperature. But I think I need to interrupt the “Continuously dim down at XX% per second” action. - I cannot take the current brightness as a “when” block to call the interrupt. - I have tried attaching an “and when brightness is below X” block to various when/then blocks, and linking that through to the “Stop dimming” action. But if anything can be done through that, I have not found it. - I don’t think I can set a minimum value elsewhere. - I could probably create some looping calculation prompt and set my limits on that, but that would undoubtedly result in the light dimming in steps, rather than smoothly/gradually in the way it currently does. I do like the reusability of your flow. I’ll look more into that. ---
**Author:** ![Drako74](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/drako74/32/150506_2.png) [@Drako74](https://community.homey.app/u/Drako74)\ **Post date:** [November 4, 2026, 7:55pm UTC](https://community.homey.app/t/prevent-light-from-dimming-to-0/161775/6 "2026-11-04T19:55:09Z")
Apologies, I’m using the Advanced Triggers app to start the second flow. You assign a name to the WHEN advanced trigger card (picking how many optional values you want to pass in when you select the WHEN card). Then from any other Flow you can trigger that named WHEN card with a THEN card that has the same number of optional values and the same name assigned to it (in my example I assigned the name Porch-Spotlights, and I used the boolean Yes/No value (No = Off, Yes = On or Dim change). The first Zigbee Button Flow has 3 buttons, On/Off, Up, and Down. The On/Off is fairly obvious, if on then turn off by passing No. If not on then turn on by passing Yes. The Up and Down buttons check if the lights are on, and if so the down also checks that the dim level logic variable is greater than 0.19 (19%, because I chose 10% increments for dim level, and I don’t want it to go below 10% and turn off). Then the Up button adds 0.1 (10%) to the dim level variable. And the Down button subtracts 0.1 (10%) from the dim level variable. Then whichever button was pressed then calls the Porch-Spotlights trigger, passing Yes for On/Dim. This approach allowed me to change the dim level and white colour temperature variables depending on the time of day, sunrise/sunset, and the ambient light levels from a light sensor. It also spared me re-doing all four spotlights with dimming duration (transition) in every Flow I wanted to control the lights. I just place an Advanced Triggers card with the name Porch-Spotlights, and pass Yes or No… so when I come home and it’s dark… when someone rings the video doorbell between sunset and sunrise… when the font door or inner porch door are opened and it dull or dark. The second part of this example is re-usable as many times as you want from any Flow you want, with just a single THEN card. I hope that makes sense. I have done the best to get down what’s in my head in legible text ha ha > [@tb\_e](#): > > Continuously dim down I think the main problem you are experiencing is because you are using the Continuously dim down card. What is the controller/button you are using to control the lights? ---
**Author:** ![tb\_e](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tb_e/32/178798_2.png) [@tb\_e](https://community.homey.app/u/tb_e)\ **Post date:** [November 4, 2026, 8:05pm UTC](https://community.homey.app/t/prevent-light-from-dimming-to-0/161775/7 "2026-11-04T20:05:53Z")
But when it comes to changing the brightness, do you press or hold the button? Say the brightness is currently at 80%, and you want to go to 50%. Do you press the button three times to subtract 0.1 thrice, or do you hold the button down to gradually decrease the brightness until it reaches a level you like and then let go of the button. As I read it, the first scenario is what you have, the second scenario is what I’m trying to figure out. I have two distinct events. “Button X was clicked”, which turns the lights on, and “button X was held down”, which gradually dims the light. (and a third event “long pressed and released”, which calls the “stop dimming” function.) “Continuously dim down at XX% per second” is the action I want to interrupt before the brightness reaches 0. ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/6/165f217c037d44585374bdddb3c16ab4f79f68f4.png) ---
**Author:** ![Drako74](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/drako74/32/150506_2.png) [@Drako74](https://community.homey.app/u/Drako74)\ **Post date:** [November 4, 2026, 9:25pm UTC](https://community.homey.app/t/prevent-light-from-dimming-to-0/161775/8 "2026-11-04T21:25:12Z")
> [@tb\_e](#): > > and a third event “long pressed and released”, which calls the “stop dimming” function Perhaps that trigger card doesn’t work the way you expect it to in that scenario? Because the press and hold is still operating on the first trigger, it might not see the second. Perhaps what you need to try is something like this: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/7/a77b7575d8682c3d3404100a4e47fe4f909ba266.png) One button pressed and released starts the dimming (if your button supports multiple presses, you could have a double press or long press and release start it) and then a different button press (my button has 5 buttons all single press… but if yours supports single, double, and long… you could use the same button’s single press to stop the dimming). The key points being the continuous dimming is started by one press and release, and then stopped by a different press and release. And writing to the Timeline for each of the different trigger events will hopefully tell you what Homey is actually seeing. You could go the extra mile and add another unique Timeline message to the right side of the Stop dimming card, so you know if it is actually executed or not (just because you pushed the button, doesn’t necessarily mean Homey actually executed the action).