Fixed bugs in By-pass option when entering by-passes entities in a disabled option and entity is ON preventing the by-pass option from running correctly.
If you like this blueprint? Consider hitting the button in the top post
If you like my blueprints, and would like to show your support or just say thank you? Click Here
I change the sensor for the Dynamic Light - Ambient Light Sensor to my secondary (The one away from the light) and it stopped going back and forward. I was also able to confirm that when I go back to the main Sensor it flips back and forward between dimmed and 100%âŠ
Both Sensor (Main Sensor and Secondary Sensor) are Z-Wave and both have the same settingsâŠ
I see, this will be the dynamic lighting control. You can use the transition to slow this down. You heartbeat is 1 min and your transition is 1/2 second to 10 seconds. You will have to adjust the transition and the heartbeat. Maybe start with your transition greater then your heartbeat 2:1 ratio. The transition slider you will have to type your values in and click save. Also positioning the LUX sensor were it will be less effected by the lights will help to.
Let me know how you go, as it will help with future development.
Is it just me? I get the following error while trying to import your Blueprint:
Invalid blueprint: extra keys not allowed @ data[âblueprintâ][âinputâ][âambient_light_sensorâ][âselectorâ][âfilterâ]. Got None extra keys not allowed @ data[âblueprintâ][âinputâ][âdynamic_lighting_lux_sensorâ][âselectorâ][âfilterâ]. Got None extra keys not allowed @ data[âblueprintâ][âinputâ][âend_scenesâ][âselectorâ][âfilterâ]. Got None extra keys not allowed @ data[âblueprintâ][âinputâ][âmotion_triggerâ][âselectorâ][âfilterâ]. Got None extra keys not allowed @ data[âblueprintâ][âinputâ][âpeopleâ][âselectorâ][âfilterâ]. Got None extra keys not allowed @ data[âblueprintâ][âinputâ][âzoneâ][âselectorâ][âfilterâ]. Got None
Will you be adding a Lux controlled brightness + color temp option? I love the lux controlled brightness, but really really want it combined with sun elevation color temp.
Hi, this is super cool and saves a lot of work creating automations but I canât make mine turn on the lights using an occupancy sensor. The lights turn off though and pretty fast ignoring the cooling off period I set up. What am I doing wrong? Thanks!
Did you make sure you only have Entities listed in the âLights - Switches - Scenes - Scripts *â section? If you have Areas or Devices listed there, you need to expand them out to the actual Entities.
If it is not turning them ON it will not turn them OFF trough the normal trigger. Check your logbook to see what is turning them OFF as something could be going on here.
Could you please provide us your YAML of the automation? This YAML code are the settings you have selected in the automation so I can help. To do this go into your automation, top right 3 dots, Edit in YAML, copy all the code, come back to the forum and in your reply at the top tool bar click on â</>â and paste code in there.
Will do when I make it home. Two things to mention though. The bulb and the helper group Iâm trying to use are Hues connected via the hue integration. I tried with a Zigbee plug connected via ZHA and it works. Thanks!
This blueprint seems to offer everything what I am looking for but havenât found a solution for one of the cases.
I have:
Hue fixture with ability to dim / change color
Zigbee doorswitch
I would like:
Light goes full on when door is opened during the day
Light goes on in a dimmed state when door is opened after sunset/night
Light goes off after x minutes
Light goes off immediately when door is closed
All cases work flawless except the last one. If the timeout is set at 0; the light switches ON and OFF when the door is opened/closed. I would like to use the timeout only when opening the door and ignoring it when closing the door.