#time trigger with offset not correct, but why?

1 messages · Page 1 of 1 (latest)

twin mural
#

timed automation based in an input datetime fails setting up, but I cant see why, all of the requirementes seem to be met?
copied the cnfig 1-1 from the documentation at https://www.home-assistant.io/docs/automation/trigger/#sensors-of-datetime-device-class-with-offsets

  - id: schakel_quooker_in_voor_wekker
    mode: queued
    triggers:
      trigger: time
      at:
        entity_id: input_datetime.alarmclock_wd
        offset: -00:15:00
Home Assistant

All the different ways how automations can be triggered.

#

or is the offset only available for a sensor, and not datetime??

grizzled blade
#

I don't think input_datetime is a timestamp

twin mural
#

crossposted there 😉

#

yeah I just saw the comma in that sentence. would be too bad if I had to create a sensor on the input_datetime just for that

#

let me try a WTH while we can....

#
grizzled blade
#

ooh good

wanton finch
twin mural
#

Ah, I believed your pr took care of that

wanton finch
#

it's not implemented yet and I'm pretty sure it will get pushback

twin mural
#

Ok let’s hope for the best…

#

why would it get pushback?

wanton finch
#

Well, I now know why it wasn't implemented in the first place, which was not the reason I thought it was

#

apparently iteration 1 was buggy

#

The way I implemented it, it should work fine.