Also, Can you verify that you are actually firing the event on the minute that you have programmed?
Example. You set the alarm for 1:01. Home assistant fires the even at 1:00, 1:05, 1:10, etc. You’ll never get an alarm because the minutes never match up.
I think this sounds like the issue… Unfortunately i wouldn’t know how to check, or change it.
I am positive that the script that is called in the action is actually valid and working. I can call it and it sets a enables a greater set of action even resulting in the espresso machine being turned on
not exactly sure what yo want me to try here? should i copy past this instead of the strftime?
still, the time check works fine i think, its more the script that isn’tcalled after the condition value_template is met?
Or maybe the fact i have this all except the scripts grouped into an alarm_clock package…
Had strange Package behavior before (groups not reloading, scripts not loading)
I am stumped. Believe it or not, but i have entered an empty line between the trigger and the conditions like below. For the first time this alarm clock has fired.
How is this even possible??
Now have it play a sound on my iPhone…That must be something inconceivable ?
automation:
- alias: Alarm Clock
id: '1511601479002'
initial_state: 'on'
trigger:
- platform: time
minutes: '/1'
seconds: 00
condition:
condition: or
conditions:
- condition: and
conditions:
- condition: template
value_template: '{{ now().time().strftime("%H:%M") == states.sensor.alarmclock_wd_time_template.state }}'
- condition: state
entity_id: input_boolean.alarmclock_wd_enabled
state: 'on'
- condition: state
entity_id: binary_sensor.workday_sensor
state: 'on'
- condition: and
conditions:
- condition: template
value_template: '{{ now().time().strftime("%H:%M") == states.sensor.alarmclock_we_time_template.state }}'
- condition: state
entity_id: input_boolean.alarmclock_we_enabled
state: 'on'
- condition: state
entity_id: binary_sensor.workday_sensor
state: 'off'
action:
- service: script.alarmclock_ring
