Wake-up light alarm with sunrise effect

Blueprints Exchange
,
458

I’m having an issue where now my lights turn on immediately to full brightness at the start of the routine, which is obviously a jarring way to wake up :grimacing:

My light target is a Zigbee group set up in zigbee2mqtt. I do have the Adaptive Lighting integration configured for these lights, but in the pre-sunrise actions I have it turn off Adaptive Lighting sleep mode and set manual control on.

So I do have some things that I can try to troubleshoot, has anyone else had a similar issue before though that might save me some time?

459

Hello botboy,

I do this in an automation:

- id: 4ae87ea5e506aaf1
  alias: Kitch Light on default
  initial_state: on
  triggers:
    - trigger: state
      entity_id: light.grp_kitch
      from: "off"
      to: "on"
  actions:
    - action: light.turn_on
      data:
        kelvin: 1700
        brightness: 96.9
        entity_id: "{{ trigger.entity_id }}"
460

Not sure I follow @Sir_Goodenough, your automation means that any time the light turns on it will override the settings to set the colour temperature and brightness?

461

You asked for every time I turn it on, it;'s too bright.
Select just the brightness and when it goes from off to on, it starts at this brightness. If you want to set the brightness later, that is an on to on and this will not trigger. If you want the starting brightness to be something variable, use a helper for the brightness number and set that helper in other automations (for instance time of day) or as a dashboard button.
Thinking out of the box is an awesome tool with Home Assistant…

What’s above is just an excerpt from my config.

462

Yes, but we are in the thread about the wake-up light alarm blueprint which provides an automation to fade the lights on gradually from dim to bright. My point was that when the automation turns the lights on they are meant to be very dim at the start, but instead they go to full brightness. I’m not talking about when I turn the lights on via any other means.

463

Sorry. I understand now.
I missed that, looking at too many posts and I just went the easy way.
I’ll let you keep working your X-Y problem.

1 Like
464

Hi Everybody, is there an Option to Implement an other Time Class? Something like:

      selector:
        entity:
          domain:
          - input_datetime

I would like to use a helper to set an time value instead of an device_class

Im using this Blueprint: Home Assistant Blueprint: Wake-up light alarm with sunrise effect · GitHub

465

Can there be an option to use other entity types than lights? I also want my blinds to open in the same way. Therefore, I mapped my cover as a light with the following code, but I don’t like this workaround.

light:
  - platform: template
    lights:
      slaapkamer_master_gordijn_light:
        friendly_name: "Gordijn als licht"
        turn_on:
          service: cover.open_cover
          target:
            entity_id: cover.slaapkamer_master_gordijn
        turn_off:
          service: cover.close_cover
          target:
            entity_id: cover.slaapkamer_master_gordijn
        set_level:
          service: cover.set_cover_position
          data:
            entity_id: cover.slaapkamer_master_gordijn
            position: "{{ brightness / 255 * 100 | int }}"
        value_template: >
          {{ state_attr('cover.slaapkamer_master_gordijn', 'current_position') | int > 0 }}
        level_template: >
          {{ state_attr('cover.slaapkamer_master_gordijn', 'current_position') | int }}
        icon_template: >-
          {% set pos = state_attr('cover.slaapkamer_master_gordijn','current_position') | int %}
          {% if pos == 0 %}
            mdi:blinds-closed
          {% elif pos == 100 %}
            mdi:blinds
          {% else %}
            mdi:blinds-open
          {% endif %}
466

I am encountering an odd sporadic error.
I have used the blueprint to create a sunrise effect with my bedroom fibaro dimmer 2 module for several years without any problems. A few months ago the dimmer module was getting marked as unavailable in the homeassistant app, and the sunrise effect began going awry. Some mornings the bulb would brighten as usual, other days it would immediately turn to full brightness, then the ‘sunrise’ didn’t happen at all.
As the fibaro module is around 8 years old I hypothesised that it was worn out, and decided to replace it with a nanoleaf bulb which the blueprint could also control the colour temperature.
However, the bulb is also turning immediately to full brightness instead of gently increasing in brightness, and it is also marked as unavailable in the homeassistant app if I use it in the sunrise effect blueprint.
Has anyone else encountered the same or similar problems?
Have you found a solution?