Possible to allow a scheme based on sunrise / sunset

[mbuzina]

Checklist

• I checked for similar existing requests (both open and closed) before posting.
• My request is generic, other users may benefit from it too.

Proposal

Allow for a special version of the scheme schedule which only has a seperator for "around" sunrise, "around" high noon and "around" sunset (you might also allow dawn and dusk). I want to automate my shutters to be closed when the sun is down when I am away and a scheme schedule would be best for this.

Additional info

The time settings could be x hours y minutes before/after the event (dawn, sunrise, noon, sunset, dusk). Having dawn and sunrise with a different offset might produce conflicts, so you might want to limit those are guarantee that dawn is allway before sunrise, sunset allways before dusk.

[okaymak]

+1 for adding dusk and dawn options

[woble]

You could achieve the same using Sun2 integration in a regular HA automation. Sun2 comes with a bunch of sensor that you can offset with time as well.

Alternatively you could have some binary sensors that you can use as triggers in regular HA automations.

template:
  - binary_sensor:
      # --- MORNING PHASES ---
      - name: "Sun Morning Astronomical Twilight"
        unique_id: sun_morning_astronomical_twilight
        state: "{{ -12.0 >= state_attr('sun.sun', 'elevation') | float(0) > -18.0 and state_attr('sun.sun', 'rising') }}"

      - name: "Sun Morning Nautical Twilight"
        unique_id: sun_morning_nautical_twilight
        state: "{{ -6.0 >= state_attr('sun.sun', 'elevation') | float(0) > -12.0 and state_attr('sun.sun', 'rising') }}"

      - name: "Sun Morning Civil Twilight"
        unique_id: sun_morning_civil_twilight
        state: "{{ 0.0 >= state_attr('sun.sun', 'elevation') | float(0) > -6.0 and state_attr('sun.sun', 'rising') }}"

      - name: "Sun Morning Golden Hour"
        unique_id: sun_morning_golden_hour
        state: "{{ 6.0 >= state_attr('sun.sun', 'elevation') | float(0) > 0.0 and state_attr('sun.sun', 'rising') }}"

      # --- DAY ---
      - name: "Sun Is High Day"
        unique_id: sun_is_high_day
        state: "{{ state_attr('sun.sun', 'elevation') | float(0) > 6.0 }}"

      # --- EVENING PHASES ---
      - name: "Sun Evening Golden Hour"
        unique_id: sun_evening_golden_hour
        state: "{{ 6.0 >= state_attr('sun.sun', 'elevation') | float(0) > 0.0 and not state_attr('sun.sun', 'rising') }}"

      - name: "Sun Evening Civil Twilight"
        unique_id: sun_evening_civil_twilight
        state: "{{ 0.0 >= state_attr('sun.sun', 'elevation') | float(0) > -6.0 and not state_attr('sun.sun', 'rising') }}"

      - name: "Sun Evening Nautical Twilight"
        unique_id: sun_evening_nautical_twilight
        state: "{{ -6.0 >= state_attr('sun.sun', 'elevation') | float(0) > -12.0 and not state_attr('sun.sun', 'rising') }}"

      - name: "Sun Evening Astronomical Twilight"
        unique_id: sun_evening_astronomical_twilight
        state: "{{ -12.0 >= state_attr('sun.sun', 'elevation') | float(0) > -18.0 and not state_attr('sun.sun', 'rising') }}"

      # --- NIGHT ---
      - name: "Sun Is True Night"
        unique_id: sun_is_true_night
        state: "{{ state_attr('sun.sun', 'elevation') | float(0) <= -18.0 }}"

I can see how a visual graph that lets you select a part of the day by sun position and attach actions could be useful. However, implementing it and avoiding odd edge cases could be tricky. Also, depending on location and season, some sun phases may not occur, so you’d need to decide how to handle that, e.g. you can’t schedule something at a specific sun phase if it doesn’t happen then, unless you show every possible option year-round, which could confuse users because where they are some phases might not exist at all and would be irrelevant.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days