šŸ’” Sensor Light - Motion Sensor - Door Sensor - Sun Elevation - LUX Value - Scenes - Time - Light Control - Device Tracker - Night Lights

@Blacky : Many thanks. :pray:

1 Like

@Sibi1337

Welcome to the community.

To me without seeing your YAML of the automation it looks like you are using a device in lights. You need to expand it down. The FAQ shows you how to do this click here

If this is not the case then 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.

Hope this helps.

Blacky :smiley:

@Krolykke

You can do this already. You just need to create another automation using the same blueprint for the other rooms and adjust the light level you would like.

TIP: If you are creating the same automation with just a few changes (different lights and light level) you can use the Duplicate button. You will find this when you are in automations, click on the 3 dots on the automation and select Duplicate. You then can make some minor adjustments saving you time.

Blacky :smiley:

1 Like

I think weā€™re misunderstanding each other :smiley: Iā€™m not trying to alter the blueprint itself, but rather my automation based upon it.

Alsoā€¦ youā€™re right about the brightness, itā€™s redundant. Originally it was because the script had more responsibility than now.

But brightness wasnā€™t the issueā€¦ itā€™s the light field. Youā€™re ā€œhardcodingā€ the light entity in your example here - and in my version itā€™s an input/variable/field to the script to avoid having identical scripts for every light group I have.

This part of the script:

fields:
  light:
    selector:
      entity:
        multiple: false
      required: true
      name: Light
      description: The light group you want to control with the script. Only one entity.

is used here:

sequence:
  - action: light.turn_on
    metadata: {}
    data:
      transition: 0.5
      kelvin: 2202
      brightness_pct: 90
    target:
    entity_id: "{{ light }}"

So instead of having 10+ identical scripts with only the light entity as difference, I have one script where Iā€™m able to input the light entity. Howeverā€¦ Iā€™m just not aware of how I should do that with your blueprint?

Iā€™m sorryā€¦ I donā€™t know how I shall explain further :smiley: :smiley:

Here is an example of my script being called from elsewhere in my ecosystem:

- id: entrance-smart-switch-2
  alias: entrance/smart_switch_2
  description: Switch closest to dining room
  use_blueprint:
    path: smartkontakten.yaml
    input:
      controller: entrance/smart_switch_2
      button_1_pressed:
      - choose:
        - conditions:
          - condition: state
            entity_id: light.entrance
            state: 'off'
          sequence:
          - action: script.light_time_of_day   <---   | This is what
            metadata: {}                       <---   | I'm trying to
            data:                              <---   | accomplish.
              light: light.entrance            <---   |
          alias: Turn on if lights are off, with brightness determined by time of
            day

The blueprint wont work like that. It will run a script but you will need to tell it what to do, so you would need to create a script for every automation stating what lights to turn ON.

You probably best to do a custom automation.

Blacky :smiley:

Okay, thatā€™s unfortunate. Think I need to dismiss your beautiful blueprint :frowning: Thank you for support though, top class :clap:

1 Like

Sorry for the late reply!
I ensured that both of the conditions are true, however they still come on at 100% instead of the 10% that I have it set for. I even just tested it now with just having the do not disturb condition as the only one, and it came out at 100%

@Yaksha

Hi John,

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.

Blacky :smiley:

Hi,

Question. I canā€™t get night light to work.
I selected 2 entities ( helpers) and a time frame in which the night lights if one of those conditions are met should turn on.
But the lights still go to the normal lowest dynamic light setting.
How should I troubleshoot this?

Cheers

@victoroos

If you have selected a night light state and a night light time condition then both need to be met for night lights to be active.

Blacky :smiley:

New update 7.2

Your lighting experience, your way ā€“ take control and customize it to perfection! :bulb::sparkles:

Maintenance :toolbox:

  • From time to time, Home Assistant updates their YAML standards and coding practices. To align with their roadmap, weā€™ve updated the code accordingly. We will continue to apply these updates across all our blueprints as they are revised.
  • Update some conditions.
  • Update night light UI conditions text.

If you like this blueprint? Consider hitting the :heart: button in the top post :+1:

If you like my blueprints, and would like to show your support or just say thank you? Click Here :smiling_face_with_three_hearts:

Enjoy

Blacky :grinning:

3 Likes

Oooh that makes sense. Thanks!
Then I have to find a solution for my "problem

Regarding the entity, is that also an" and" expression or is that an or?

Ohā€¦ And. First time blue print user. Does it update automatically? Cheers.
Again. Thanks for taking time to reply and support!!!

@victoroos

All the night light conditions are ā€œandā€

No you have to do it manually. You can do this in the UI or you just click the import blue button at the top again follow along and it will update it.

Blacky :smiley:

So it is better to combine them in one group if I want it to be or?
Thanks! I see I should read your FAQs waay better!

Yes you can do that.

EDIT: Sorry I didnā€™t read it correctly. If you use entity state you can have multiple entities and only one needs to be true so it is an OR.

Blacky :smiley:

1 Like

First of all, this is very nice blueprint, good job!
But Iā€™m a bit confused about something, it might be me misunderstanding it.

I have a simple setup of motion sensor as trigger, turn light on with 2 minutes time delay and dynamic lighting based on 4 - Sun Elevation Lighting - Brightness.

If I go into the room and increase the brightness with a button while the motion is on, it will reset to dynamic brightness setting as soon as the motion goes off, and on again. Even if itā€™s within the Time delay of 2 minutes. Is this working as intended?

I would have thought it would keep the set brightness untill the time delay ran out.

I might have to use the Bypass Switch - Keep The Lights Current State, but Iā€™m not entirely sure how. Settings the same button that increases the brightness doesnā€™t work, it just keeps resetting to the dynamic brightness.

Iā€™ve tried creating a helper switch which is turned on when the button is pressed, and off if the button is pressed and this light is turned of, but this triggers that the light goes back to sensor default for 2 minutes.

That was the solution. Thanks for pointing it out. I must admit, as a foreign speaker, I have read this part in the FAQ, but did not understand it. My bad, but hopefully someone else will read your answer according to google results of my question and will get help in the future as well. Thank you very much!

1 Like

@xtfrost

Yes, dynamic lighting will keep changing your brightness as required even if you change the brightness.

In dynamic lighting option 4 when the sun elevation changes it will update the brightness. It will also do this on every re-trigger when the lights are ON.

Maybe donā€™t use Dynamic lighting and just set your brightness through light control. If you do it this way when you manually adjust the brightness it will stay the same until the light turn OFF and back ON again.

Blacky :smiley:

Hello, thanks for the great blueprint!
I have a question and I am sorry in case it was asked already.
Is there a way to bypass the automation when some lights are on already? In this case the motion sensor would not turn on or off any of the lights and leave them in their current state. I tried to set the lights as bypass switch (option 3) but as I understand thatā€™s not how itā€™s intended and it also didnā€™t fully work.

Thank you!

My usecase is to have a motion triggered light which brightness is determitted by either day/night or sun position when triggered. I also have a manual override for the light, a one-button control for on/off and dimming on button hold, this should always overrule the motion settings.

Is dynamic light still triggered when the ā€œBypass Switch - Keep The Lights Current Stateā€ is true? - my testing shows it will remain at the same brightness as long as the bypass is true (which is what Iā€™m hoping)

If Iā€™m using the ā€œLight Controlā€ I have to combine it with Night Lights to get some kind of conditional lighting - But Iā€™m really hooked on the brightness determitted by sun elevation