Regards to the bypass. If you turn one on and it is turn ON then the light turn ON. If you then turn the bypass for turn OFF then the lights turn OFF, if you then turn the bypass for turn ON then the light turn back ON etc, it reacts to the last one you did. If you have 2 ON then all af them have to be OFF for the automation to run again.
Can you explain in a easy step guide on what you are trying to achieve. Then provide your yaml with all the entites in there so I can edit it. Also make 2 helpers for your scenes, put one in Scenes & Scripts - Toggle Helper and one in Night Lights - Scenes & Scripts - Toggle Helper
there are 2 scenarios Before Sun Set and After Sun Set
1: Before Sun Set
Turn ON light.kitchen_lights nothing else happens.
Turn OFF light.kitchen_lights nothing else happens.
In this Scenario the motion sensor has NO effect at all.
2A After Sun Set
NO LIGHTS ON, NO MOTION IN ROOM
TURN ON light.kitchen_lights and I want the scene scene.kitchen_motion_light_on to ACTIVATE (so it TURNS ON light.kitchen_cabinets, light.kitchen_floor_led). and have the motion sensor IGNORED while light.kitchen_lights are ON, so ALL lights stay ON.
TURN OFF light.kitchen_lights and I want the scene scene.kitchen_motion_light_off to ACTIVATE (so it TURNS OFF light.kitchen_cabinets, light.kitchen_floor_led).
2B After Sun Set
NO LIGHTS ON, NEW MOTION DETECTED IN ROOM
I want the scene scene.kitchen_motion_light_on to activate (so it TURNS ON light.kitchen_cabinets, light.kitchen_floor_led). and have a 1.5 minute timeout, so if after 1.5 mins of NO MOTION I want the scene scene.kitchen_motion_light_off to ACTIVATE, so it TURNS OFF light.kitchen_cabinets, light.kitchen_floor_led
2C After Sun Set
MOTION ALREADY DETECTED IN ROOM (scene.kitchen_motion_light_on ALREADY ACTIVATED)
TURN ON light.kitchen_lights, I want the motion timeout IGNORED, so ALL lights stay ON.
TURN OFF light.kitchen_lights I want the scene scene.kitchen_motion_light_off to ACTIVATE, so it TURNS OFF light.kitchen_cabinets, light.kitchen_floor_led
this allows 1: Before Sun Set, 2B After Sun Set and 2C After Sun Set seem to be working fine, it is just 2A After Sun Set that does not work.
IF I use:
include_bypass:
- bypass_enabled_turn_on
then 2A After Sun Set, 2B After Sun Set and 2C After Sun Set works, but 1 Before Sun Set does not work correctly as it ACTIVATES scene.kitchen_motion_light_on BEFORE SUN SET. and it does not allow you to use
Hello Community. And big thanks for this amazing BluePrint!
I have already dived into this project a little and implemented basic light control in one room. It is a pity that I had to redefine the standard behavior to make it match my color_temp with âmiredâ units. Because current slider support only kelvin. Anyway is okay.
I have two scenarios that cannot be implemented using this project:
If the light is turned on via the input relay via mqtt(send single press or other events), which sent a signal to turn on the lamp, then the algorithm for turning off the light after delay without moving does not work, because there is no initial trigger. Now it is only a motion sensor.
If the light is switched via any smart home interface(HA dashboard like example), then the algorithm for turning off also does not work.
The only thing that comes to mind without major changes to the project is implementation via a bypass. But with the addition of a separate timer only for turning on:
Enable the Bypass - Turn lights ON
Bypass Switch - Turn lights ON. Add light on state value.
Bypass Auto OFF - Time Delay. Here I need add one more trigger only for âEnable the Bypass - Turn lights ONâ case. Because common timer is needed for OFF light with big delay
I have a similar scenario to you, where some lights are ordinarily controlled via a motion sensor however on occasion there is a manual switch that can be used to turn on the lights. The way I did it was to use blackys Manual Off blueprint along with this one.
Or try it using just the entities only, no senes (see YAML code below). You will have to set up light control for your light.kitchen_cabinets and light.kitchen_floor_led lights. If this works and you still would like to use the scenes then in the autoamtion YAML above you will need to create a toggle helper and enter it into Scenes & Scripts - Toggle Helper
The problem I see if you turn ON light.kitchen_lights before sunset. You may have to do a script for this automation.
One More Option - Option 3
The other thing that I can also think of is I have another blueprint in beta that will turn your light.kitchen_lights into a toggle helper and you can enter it into Night Lights - Entity State then enter in your light.kitchen_lights, light.kitchen_cabinets and light.kitchen_floor_led lights into Night Lights. If the above not working I can set you up to try the beta blueprint. This may work a lot better I think but I have not tested this theory as it is just in my head so I could be wrong.
thanks for taking the time to look at this, Iâll just stick with using
include_bypass:
- bypass_enabled_stop
and use a secondary automation to sync cabinet / floor ledâs with main kitchen lights, it just a shame that
include_bypass:
- bypass_enabled_turn_on
can not be set too adhere to sun settings swell, that way the motion scene could be only be controlled after sunset for both motion and bypass on, which I thought would be what it should be doing if sunset option is used. I do not understand why you would want bypass controlled when the motion trigger is not being used at that time.
ie you say this:
By-pass Switch - Turn lights ON.
Select the switches that will turn your lights ON, bypass the trigger sensor, and allow your lights to function as normal. Please note that the entity cannot be included in the âLights - Switches - Scenes - Scriptsâ or âNight Lightsâ selections.
I had been having trouble with my automation after upgrading from V2 top V7. I do not use bypass, but after much debugging, I found that the bypass list was populated with bypass_disabled. It looked like this:
I removed it and made the list empty by editing the yaml:
include_bypass: []
This solved the issue. This may be too much of an edge case to matter, and I guess I could have remade the automation easily enough, since its a blueprint, but thought it would be good to let you know. It could probably be solved with an additional check in the bypass enabled check.
This is the trace where I found it. I can share the whole trace if it is helpful
@Blacky - are there any current problems known?
I have the most simplest of setups for testing purposes but it doesnât work. I tested it with a manual automation and it works fine. Light works, sensor gets occupied.
Iâm not fully understanding the capabilities of this blueprint Can somebody please let me know if it would be possible to use this using a grouped âoutdoor lightsâ and grouped âaverage outside luxâ sensors as well as a outdoor motion sensor to do the following:
Lux Value 100 and below: Turn On the Lights in âNight Modeâ dimmed
Motion is detected turn them to full brightness and go back to dimmed after no motion
Lux Value 100 and above: Turn off the lights completely.
Ideally the Lux value should be after its been above/below for 15 minutes, But I can live without that.
Or is this (turn on dimmed at âduskâ, full brightness on motion and off at dawn) out of the scope for this blueprint and I should just write my own basic boring automation for it.
Going from V2 to V7 there are many thing you had to do along the way. You can see them in the FAQ down the bottom. Best to just create a new automation fresh. Disable your existing one. Then create a new one. You can reference the old one as you to it. Then once your happy just delete the old automation.
Your in luck I just updated another blueprint. Looks like you are doing outdoor lights. The blueprint below can work with lux but you may want to consider sun elevation as then it will only turn ON at night. Have a look at the trigger FAQ in the below blueprint for a stairwell as it is the same for what you are doing. If you need a delay then sometimes your motion sensor has a setting for it or you can create a template sensor that has a delay OFF for you motion sensor and then use that template sensor in your night lights state trigger rather than your motion sensor.
If you need help for the template sensor then just let us know but if you using the other blueprint post the question there.
The blueprint is all good. I just created a basic one like yours and it worked perfectly.
For some reason you are getting this code added to your YAML.
action: []
It shold not be there. Try remove the blueprint (uninstall it, 3 dots next to the blueprint on left, then delete blueprint), restart your HA then reinstall the blueprint again and see if that cleans it up. Your code should look like this.
@Blacky - very strange. Did all that and now for testing purposes I just clicked on âCreate new automationâ and the line you mention already exists before changing anything.
Very strange, what version of HA are you on⌠maybe update if your not on the latest version. This is what you should have when it first opens the blueprint.
That makes sense now. You are on the Beta version of Home Assistant. I would like to keep the 2024.8 update details for HA to announce but this is directly related to the beta and what they are doing. Please let Home Assistant know as they will bee keen to hear from you and my guess they will resolve this ASAP before the stable version comes out but you will need to let them know.
For now you know what is wrong so you can fix it and HA will resolve this for you. Please note it is not the blueprint but the beta of HA you are running.
Can somebody please let me know if it would be possible to use this using a grouped âoutdoor lightsâ and grouped âaverage outside luxâ sensors as well as a outdoor motion sensor to do the following: