Congrats @Blacky, this must be one of the best blueprints here. Great work. Really appreciated.
But I have a small problem I hope you can help me with. My lights are controlled by a motion sensor with integrated lux sensor. With your automation, I have properly set them up to be switched on when a motion is detected, but only below a certain lux value.
The problem is, that as soon as the lamp is switched on, the lux value goes up. When I leave the room, after one minute, the lights go off. So far, so good. But when I re-enter the room less than one minute after the lights went off, the lights donât go back on. Hereâs why: the lux sensor has not yet updated the lower lux value, as it only sends the new lux value every 60 seconds, if there is no motion detected.
So what I need is kind of a grace period, in which the lux value is ignored, so the light always switches back on, when there is a motion detected. Is this possible? I think it could be done with a timer, which is set every time the light is switched off by your automation, and the running timer is a bypass for the check if the lux value is low enough to switch on the light.
I have seen this in another blueprint in this forum, but the blueprint was otherwise far from being as great as yours is.
Just a quick thought. What is your low lux value and what is the lux value when the lights are ON. Is this close or could you live with raising the lux value to be just above the value when the lights are ON. The reason I ask is sometimes when the lights turn ON the lux value only raises a bit but I have no idea of your site.
I have âsolvedâ the problem by creating a sensor using the statistics platform. The newly created sensor contains the lowest value measured by the real illuminance sensor in the past 30 minutes. By referencing the statistics sensor in the automation created with your blueprint, the change of illuminance caused by the lamps switching on doesnât interfere anymore.
sorry this might be a silly question but what ways are there no to trigger this automation?
For example if I wanted to use this automation for bedroom and I donât want it to run in the middle of the night when Iâm asleep?
Okay, I would also contact the manufacture as the 60 sec is not realy that good. Some do a 60 sec but also have a 5% max change. They may have a work around or they may update their firmware (they should⊠at least give you the option). If not maybe just dont purchase another one. Anyway looks like your up and running and that is the main thing.
@Blacky I have an entertainment room that has a presense sensor, an Apple TV and Hue lights. I have a custom automation that turns on the lights based on presence to about 75%. But when I turn the Apple TV on they dim to about 10%, and go back to 75% when the ATV turns off. Is there a simple way to do this with your blueprint?
Sorry so if i want the automation to run only during the times when sun is down, and if the entity group âPhone Chargingâ is state false, this this how you would set it up?
Basically only run during the sunset, donât run automation if the âPhone Charging Sensorsâ is true?
You can do it like that. Be mindful with the âPhone Chargingâ⊠the state may change when it is charged and turn OFF. We use âfocusâ but in night lights as we would like some light to come ON if we get up. Focus is the apple of do not disturb.
Tip: With your by-pass option 3 it will just keep the current state of your light so if they are ON you will have to turn it OFF. If you use option 2 it will turn your light OFF for you. You can set the âBy-pass - Time Delayâ so when you plug it in it will go OFF in the set time period.
my front light goes on an 20% when its dark, this is controlled by another scene.
If somebody comes to my door, a motion sensor triggers and the front light and an extra ceiling light go on at 100% until the motion is gone. After that time T (5 min), the ceiling light goes off and the front light goes back to 20%.
This can be done with your blueprint, i call an extra scene as a turn-off scene. In this scene i set the front light at 20%. This idea was already suggested by you.
But: it doensânt work as expected. If the front light is already on, BOTH lights wil turn off after time T.
But i noticed that if the front light is off before the blueprint is called it works as expected: the ceiling lamp goes of after time T and the front light goes to 20%.
Is this expected behaviour or not? i would assume not? the inital state should not matter i would expect.
thks
Jacco