Trigger Sun Offset Template in Blueprint

[Control]

Mostly everything in HA accepts a template
But Sun a trigger offset is not accepted I don’t know why
Even it accepted the template in the blueprint from Input selected or Input number

like this example below

  input:
  
    Sunrise_Offset:
      name: Sunrise Offset
      description: Offset time After Sunrise event.
      selector:
        select:
          options:
            - label: None
              value: "00:00:00"
            - label: 15 Min
              value: "00:15:00"
trigger:
  platform: sun
  event: sunrise
  offset: !input Sunrise_Offset

# or 

  input:

    hours:
      name: Sunrise Offset Hours
      description: Offset in Hours After Sunrise event.
      selector:
        number:
          min: 0
          max: 6
    minutes:
      name: Sunrise Offset minutes
      description: Offset in minutes After Sunrise event.
      selector:
        number:
          min: 0
          max: 59   

trigger:
  platform: sun
  event: sunrise
  offset:
    hours: !input hours
    minutes: !input minutes
    seconds: "00"

for that, we need to expand this to helpers like input_number or input_select to be able to control this time from the front end

[DefenestrateIT]

Use A time selector

  input:
    sunrise_time:
      name: Sunrise - Offset - time
      description: Offset the sunrise time.
      default: "-1:00:00"
      selector:
        time: {}

trigger:
  platform: sun
  event: sunrise
  offset: !input sunrise_time

[Control]

hi @DefenestrateIT Thanks for your replay
I knew this methode my request about use template to order to control it from front-end not inside blueprint

[DefenestrateIT]

Then you will probably need to convert a number (integer) to time & use - platform: template

[Control]

lets say we have two helper input_number one control H and other Control Min how to it in template inside blue print

any ideas ?

[DefenestrateIT]

I wouldn’t, just keep everything as time.
if I want to offset the sunrise time by + 1hr & 35 min’s

    sunrise_time:
      name: Sunrise - Offset - time
      description: Offset the sunrise time.
      default: "1:35:00"
      selector:
        time: {}

if i wanted to subtract the that time

    sunrise_time:
      name: Sunrise - Offset - time
      description: Offset the sunrise time.
      default: "-1:35:00"
      selector:
        time: {}

if I wanted it on a dashboard I would use A time helper &

  input:
    sunrise_time:
      name: Sunrise - Offset - time
      description: Offset the sunrise time.
      selector:
        entity: 
          domain: input_datetime

[Control]

@DefenestrateIT can use input_datetime directly without

  input:
    sunrise_time:
      name: Sunrise - Offset - time
      description: Offset the sunrise time.
      default: "-1:00:00"
      selector:
        entity: 
          domain: input_datetime

like using

variables:

if it works, please provide example

[DefenestrateIT]

I don’t understand…
What are you trying to do?
I assume you want to make a blueprint with A trigger at sunrise, but you want to offset that time, Correct?
Why don’t you want to use the time selector?
If you want to know where to make a time helper…
Settings > Devices & Services > Helpers

[Control]

I assume you want to make a blueprint with A trigger at sunrise, but you want to offset that time, Correct? yes
Why don’t you want to use the time selector? to keep everything fixed not changeable for that I try not use selector

[DefenestrateIT]

So you want to have a trigger for A particular time all year?

trigger:
  - platform: time
    at: !input sunrise_time

[Control]

not fix all time that point i can change it from dashboard

[DefenestrateIT]

@Control

not fix all time that point i can change it from dashboard

So you don’t want it on A dashboard? then:

@DefenestrateIT

  input:
    sunrise_time:
      name: Sunrise - Offset - time
      description: Offset the sunrise time.
      default: "-1:00:00"
      selector:
        time: {}

Otherwise why aren’t you doing this as an Automation-Script? Why are you trying to make a blueprint?
Settings > Automations & Scenes

@Control

to keep everything fixed not changeable for that I try not use selector

trigger:
  platform: sun
  event: sunrise
  offset: 01:35:00

[Control]

Otherwise why aren’t you doing this as an Automation-Script?
to keep everything simple UI for that I prefer to use a blueprint in case I need to change
my question
Is there a way to use any type of helper to modify the offset in the blueprint without using the sector method?
like import ( input_datetime or input_number or input_select ) State through (variables: ) to blueprint
like this example

       minutes: "{{ states('input_number.minutes')|int(0) }}"

Actually, I use this template

{{ states('input_select.sunrise_after_offset_hour') }}:{{ states('input_select.sunrise_after_offset_min') }}:00

any way to use it blueprint without using the sector method?

[DefenestrateIT]

@Control

to keep everything simple UI

A blueprint won’t make it simple. Blueprints are only any good if you want to reuse the same code.

@Control

Is there a way to use any type of helper to modify the offset in the blueprint without using the sector method?

If you want to Hard Code a time, you can.

@Control

State through (variables: )

Why do you want to use variables?
Your Entity’s are both “input_select” which has a string (word) value, so your approach from the beginning just makes everything 100 times harder. you want to use either “input_number.” or preferably “input_datetime.”
But if you must use a “input_select” then use a “choose” function (if functions for templating) to convert from a “string” to “time”.

[Control]

@DefenestrateIT

A blueprint won’t make it simple. Blueprints are only any good if you want to reuse the same code.

Exactly reuse the same code without the need to create it again

@DefenestrateIT

Why do you want to use variables?

to minimize UI in Blueprint

@DefenestrateIT

Your Entity’s are both “input_select” which has a string (word) value, so your approach from the beginning just makes everything 100 times harder. you want to use either “input_number.” or preferably “input_datetime.”

I use input_select because it gives me a nice drop list in the Dashboard
it’s ok to switch input_number not a problem in that

for input_datetime My local Time use AM/PM when I use input_datetime it makes it confusing for that I avoid it for this type of configuration

@DefenestrateIT

But if you must use a “input_select” then use a “choose” function (if functions for templating) to convert from a “string” to “time”.

any example, please

[DefenestrateIT]

@Control

for input_datetime My local Time use AM/PM when I use input_datetime it makes it confusing for that I avoid it for this type of configuration

Don’t think of “input_datetime” as AM/PM it is time. if you want to use it as AM/PM you can or 24hr or Hours:Minutes:Seconds

@Control

any example, please

Not today, i’m going to bed. but your problem is that you want to use it as A trigger so the templating is diffecult, but an E.g.

{{ 15 if input_select.sunrise_after_offset_min == '15 mins' }}

[Control]

@DefenestrateIT

Not today, i’m going to bed. but your problem is that you want to use it as A trigger so the templating is diffecult, but an E.g.

Ok dear GoodNight
Exactly difficult because using it as a trigger “not part of the action”
According to my reading in many posts Offset in Trigger Sun is unable to templating even in normal Automation for that using elevation or azimuth method to solve this problem

All that can solve by accepting Offset for templating this what I requested in this post