♾ Sensor Light Add On - Media & Movie Lights - House Alarm Lights - Smoke Alarm Lights & Exhaust Fans + More

@kobejo34

I am working on this now… 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.

This way I can test it all working.

Thanks for your help.

Blacky :smiley:

I have Lutron lights where to get lights to switch off together I need to create a set button within their hub. That button can then be seen in HA. For the lights, I have created 3 buttons - Lights On Day, Lights Off, Lights On Night. I then created 3 scripts with the same name. Each script simply pressing the button as well as adjusting one other non-Lutron light in the room.

For my automation config, I’m not seeing the scripts being activated and it seems that the trace shows the automations going thru the “else” route, bypassing things. I have toggles inputted and from what I’ve read I think I am doing it right but obviously not. I’m using Blueprint v7.0 and HA 2024.7.4. What am I missing?

Here is one of the scripts (other scripts are duplicates of this)

alias: Great Room Day On
sequence:
  - parallel:
      - service: light.turn_on
        metadata: {}
        data:
          kelvin: 3092
          brightness_pct: 100
        target:
          entity_id: light.lights_side_table_lamp_lamp
      - service: button.press
        metadata: {}
        data: {}
        target:
          entity_id: button.utility_phantom_keyapd_position_1_keypad_great_room_day_on
description: ""
mode: restart

Here is YAML of blueprint.

alias: Blacky - Great Room
description: ""
use_blueprint:
  path: Blackshome/sensor-light.yaml
  input:
    night_boolean_scenes_scripts: input_boolean.great_room_toggle_night
    motion_trigger:
      - binary_sensor.great_room_motion_group
    light_switch:
      entity_id: script.great_room_day_on
    boolean_scenes_scripts: input_boolean.great_room_lights_on_toggle
    end_scenes:
      - script.great_room_day_off
    include_bypass:
      - bypass_enabled_stop
      - bypass_enabled_turn_on
    motion_bypass_lights_stop:
      - input_boolean.auto_lights_bypass_great_room_landing
    include_night_lights: night_lights_enabled
    night_lights:
      entity_id: script.great_room_night_on
    include_night_light_control:
      - manage_scripts_crossing_over
      - if_lights_are_on_adjust_when_crossing_over
    night_lights_conditions:
      - entity_state_enabled
    night_lights_entity_state:
      - input_boolean.night_toggle
    night_time_delay: 0
    time_delay: 0
    motion_bypass_lights_on:
      - binary_sensor.door_master_bathroom

It may be because I am calling for a script instead of a scene? I’m not sure then how to otherwise incorporate a button press as you can call that action through a script, but not a scene.

@tyjthomas

Thanks for reaching out.

Yep, scripts are not in this blueprint but I am working on this BP now so I will look to add them in.

Blacky :smiley:

That’d be awesome.

As I have read through massively long threads on your automation, you’re always happy to help and not condescending. It makes me love this blueprint 10x. Thank you.

@tyjthomas

Thanks for your kind words… it is all done and ready to go. Hope you like it.

Blacky :smiley:

New Update - Version 2.2

Lights, Camera, Action! Get ready to grab the popcorn because it’s movie time with a touch of cinematic magic! :clapper::sparkles:

:new: New Feature

  • Light Colour: You now have the option to select RGB, RGBW or RGBWW in your light control option.

  • Scripts: You can now use scripts.

  • Collapsible Sections - Added collapsible sections to the blueprint. This enhancement improves the blueprint user interface by making it cleaner and more organized, allowing sections to be collapsed.

    :warning: This feature was introduced in Home Assistant 2024.6, so you must have this version or later for the blueprint to work.

:bug: Bugs Fixed

  • Fixed bugs in bypass.
  • Fixed bugs in scenes.
  • Fixed bugs when crossing over to intermission and vice versa.
  • Fixed bug when using sun or ambient conditions.

:toolbox: Maintenance

  • Update the description.
  • Clean up code.

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:

Cool. Thanks. Would it be possible for you add scripts to the standard sensor light automation as well? I’ll move over to the sensor light automation thread.


Hi, looking to have Jellyfin for Android TV added to the list of apps. :slight_smile: Great blueprint, thanks very much!

@ZOXSOCKS

You can add Jellyfin in if your like. Just simply type the app name in and hit enter. This is the name you need to enter.

org.jellyfin.androidtv

Blacky :smiley:

@Blacky

Few questions,

I am trying to make the light turn off when the movie starts but they won’t turn off, the only thing I been able to do is set it to 1% and that works but when I use the start off option it won’t turn off.

Ideas?

Also is there a way to add an option to detect presence base kn an entity provided and if in that area it detects a presence to set the lights at a certain level or just don’t do anything to those lights… Thoughts?

@parallelsys

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.

Currently no.

Blacky :smiley:

Here You. :slight_smile:

alias: Roku Automation New
description: ""
use_blueprint:
  path: Blackshome/sensor-light-add-on.yaml
  input:
    trigger_entities:
      - media_player.roku_3800x_7ce2
    trigger_on_state:
      - playing
    app_attribute: []
    trigger_off_state:
      - idle
    include_intermission: intermission_enable
    intermission_light_switch:
      entity_id:
        - light.kitchen
        - light.kitchen_breakfast_light
    intermission_include_light_control:
      - use_transition
      - use_brightness
    intermission_light_brightness: 23
    intermission_light_transition_on: 2
    include_end_turn_on: enable_end_turn_on
    end_light_switch:
      entity_id:
        - light.living_room
        - light.receiving_lights
        - light.kitchen_breakfast_light
        - light.kitchen_lights
    end_include_light_control:
      - use_transition
      - use_brightness
    end_light_brightness: 21
    include_start_turn_off: enable_start_turn_off
    off_include_light_control:
      - use_transition
    light_switch:
      entity_id:
        - light.kitchen_breakfast_light
        - light.kitchen_lights
        - light.receiving_lights
        - light.living_room
    off_light_transition_off: 2
    include_light_control:
      - use_brightness
    light_brightness: 1

@parallelsys

Try setting the brightness to 0%

alias: Roku Automation New
description: ""
use_blueprint:
  path: Blackshome/sensor-light-add-on.yaml
  input:
    trigger_entities:
      - media_player.roku_3800x_7ce2
    trigger_on_state:
      - playing
    app_attribute: []
    trigger_off_state:
      - idle
    include_intermission: intermission_enable
    intermission_light_switch:
      entity_id:
        - light.kitchen
        - light.kitchen_breakfast_light
    intermission_include_light_control:
      - use_transition
      - use_brightness
    intermission_light_brightness: 23
    intermission_light_transition_on: 2
    include_end_turn_on: enable_end_turn_on
    end_light_switch:
      entity_id:
        - light.living_room
        - light.receiving_lights
        - light.kitchen_breakfast_light
        - light.kitchen_lights
    end_include_light_control:
      - use_transition
      - use_brightness
    end_light_brightness: 21
    include_start_turn_off: enable_start_turn_off
    off_include_light_control:
      - use_transition
    light_switch:
      entity_id:
        - light.kitchen_breakfast_light
        - light.kitchen_lights
        - light.receiving_lights
        - light.living_room
    off_light_transition_off: 2
    include_light_control:
      - use_brightness
    light_brightness: 0

Blacky :smiley:

1 Like

I will try from the yaml file

So editing from the yaml file worked, the UI limited me to go as low as 1. I did a small work around to add time base which was to have another automation disable it during certain times and enable it after certain times. Your Sensor Light Blueprint has the ability to add time. Is this possible with this one?

@parallelsys

You can just type 0 and click save but normally you would have some lights but I going to look at it again to have no lights if you need to. I added that on a list to do.

Use the automation link to disable other blueprints. It is all designed to work this way. Click Here on the how to.

Blacky :smiley:

Hi @Blacky

I would like to use your Blueprint so that when the alarm goes off, the lights turn red and flash. Do you have any ideas how I can do this? Thanks

@cediqqu

You would just set up your trigger for you alarm, the flashing lights will probably be a script to run. Consider using the snapshot feature so when you reset your alarm all your lights go back to how it was before and you can use the automation link if you have my blueprints to control your lights so they will be disabled when the alarm goes OFF.

Blacky :smiley:

I’ll try it! Thank you very much!!

Unless my understanding of Intermission Mode is wrong, I think that there might be an issue in version 2.2. When intermission mode is triggered, Light 2 turns on as expected, but Light 1 which was turned on by the automation’s Trigger On state is turned off, as if the automation was exiting. When intermission mode ends, Light 2 is turned off as expected, but Light 1 is turned back on as if the automation was restarted. Is this normal behaviour of the intermission mode?

alias: New automation
description: ""
use_blueprint:
  path: Blackshome/sensor-light-add-on.yaml
  input:
    trigger_entities:
      - media_player.ht_appletv
    trigger_on_state:
      - "on"
      - playing
    trigger_off_state:
      - "off"
      - standby
    light_switch:
      entity_id:
        - light.ht_tv_backlight
    end_scenes: []
    include_intermission: intermission_enable
    intermission_state:
      - paused
      - idle
    intermission_light_switch:
      entity_id: light.ht_torchiere_light
    intermission_include_light_control:
      - use_brightness
      - use_transition
    intermission_light_brightness: 25
    intermission_light_transition_on: 5
    intermission_light_transition_off: 5
    intermission_include_light_colour_control: use_colour_temperature
    intermission_light_colour_temperature: 2500