💡 Sensor Light - Motion Sensor - Door Sensor - Sun Elevation - LUX Value - Scenes - Time - Light Control - Device Tracker - Night Lights

Yes that is correct.

Yea is is a nice feature.

Blacky :smiley:

I have a problem with the night light setting. It often crashes, and leaves lights on, when I trigger the night mode switch during the lights being on. Moreover, lights that are not activated during nighttime, when the night mode is triggered while on, will not turn off. Am I having a unique problem, or this is a program error?

Also, I often have zwave errors, saying ‘Failed to send the command after 1 attempts’ While I understand this should be solved on the zwave side, can we have the command sent a second time?

@rbhun

Have your selected If lights are ON, adjust the lights when crossing over?

Blacky :smiley:

(post deleted by author)

Hello,

testing this blueprint for the first time and using a motion sensor as a trigger. Sometimes the following happens:

  • light switch is physically turned off (unavailable to HA)
  • user switches the lights on but leaves the room before the motion sensor detects him/her
  • automation is not triggered and the lights stay on until he/she turns them off again or the automation timer is triggered

What is the best way to address this problem? Note that we still want to keep the ability to use a physical switch.

Thanks, jose

Thanks for sharing, I’m about to buy some of these!

I’ve narrowed it down to those being an issue with the do not disturb sensor. Even with it being active it doesn’t register it for the purpose of “night lights”. It does work as a bypass however.

alias: Kitchen lights
description: ""
use_blueprint:
  path: Blackshome/sensor-light.yaml
  input:
    motion_trigger:
      - binary_sensor.apollo_msr_2_2b2538_radar_zone_1_occupancy
      - binary_sensor.apollo_msr_2_2b2538_radar_zone_2_occupancy
      - binary_sensor.apollo_msr_2_2b2538_radar_zone_3_occupancy
    light_switch:
      entity_id: light.kitchen
    time_delay: 3
    include_light_control:
      - use_transition
      - use_brightness
    include_night_lights: night_lights_enabled
    night_lights_conditions:
      - time_enabled
      - entity_state_enabled
    night_lights_after_time: "01:00:00"
    night_lights_entity_state:
      - sensor.john_s_pixel_do_not_disturb_sensor
    night_lights_before_time: "08:00:00"
    night_lights:
      entity_id: light.kitchen
    night_time_delay: 1
    include_night_light_control:
      - use_brightness
      - use_transition
    night_light_brightness: 10
    night_light_transition_on: 2
    night_light_transition_off: 2
    light_transition_on: 0.5
    light_transition_off: 3

Sorry for my ambiguous question :smiley: …So the light will remain the same brightness with “Bypass Switch - Keep The Lights Current State” true, despite dynamic light?

Hey !
Love the blueprint.
Is there a simple way we could base the bypass Auto-OFF feature on a presence sensor (ie: when no one is detected for X amount of time by this sensor turn all the bypasses off) ? (or maybe there is a better way to use the blueprint and I don’t know of it)
My use case is as follows:
Lights in the living room are normally controlled by automation, girlfriend want to take a quick nap in the sofa so she turns on the OFF bypass via a wall switch.
I would like the bypass to reset when she ends her nap and go out of the room.

Currently I use an other automation that resets the bypass values when no presence is detected in the room for more than 5mins but would love it to be in the same integration.

Thanks in advance and sorry if I misunderstood something about the automation and that it is already a builtin feature