WTH Offset input_datetime automation trigger by input_number

Take the example of an alarm clock using an input_datetime to trigger an automation. Why can’t I trigger the automation with an offset from the input_datetime, using the value from an input_number rather than a fixed offset - i.e. 15 minutes before the alarm goes off, turn on the coffee machine; 30 minutes after my preset bedtime, turn down the heating.

To be clear: you are asking for the time trigger to support entities with a numeric value (or templates) in the offset option?

+1

Just gonna jump in with agreement here - I have already set this up by following someone’s guidelines to write some yaml in the config file, but for such a powerful and useful automation trigger it should not be locked behind manual yaml editing!

  • 15 minutes before alarm: fade lights on
  • 10 minutes before calendar event: turn entrance lights on
  • 20 minutes before calendar event tagged D&D: turn on guest mode
    etc.

Does offsets work at all for a time trigger wired to an input_datetime? Last I checked I am pretty sure they only worked when wired to a sensor.