Creating a alarm clock


#1

I didn’t find a component to create an alarm clock for my difficult morning, so i implement that.
It’s composed with simple modules :blush:

input_boolean :
  reveil:
    name: Reveil positionné
    initial: off
    icon: mdi:alarm
  lightreveil:
    name: Reveil Naturel
    initial: off
    icon: mdi:theme-light-dark

We declare 2 input_boolean to turn on the TV and to turn on bedroom’s light

input_select:
  choixreveil:
    name: "reveil matin"
    icon: mdi:alarm
    initial: "06:35"
    options:
      - "06:00"
      - "06:05"
      - "06:10"
      - "06:15"
      - "06:20"
      - "06:25"
      - "06:30"
      - "06:35"
      - "06:40"
      - "06:45"
      - "06:50"
      - "06:55"
      - "07:00"
      - "07:05"
      - "07:10"
      - "07:15"
      - "07:20"
      - "07:25"
      - "07:30"
      - "07:35"
      - "07:40"
      - "07:45"
      - "07:50"
      - "07:55"

Automation to turn on TV

  - alias: "reveil matin 06h20"
    trigger:
      - platform: time
        after: "06:20:00"
    condition:
      - platform: state
        entity_id: input_boolean.reveil
        state: 'on'
      - platform: state
        entity_id: input_select.choixreveil
        state: "06:20"
    action:
      service: shell_command.allumefreebox

Automation to turn on bedroom’s light (with transistion).

  - alias: "aurora 06h10"
    trigger:
      - platform: time
        after: "06:08:00"
    condition:
      - platform: state
        entity_id: input_boolean.reveil
        state: 'on'
      - platform: state
        entity_id: input_boolean.lightreveil
        state: "on"
      - platform: state
        entity_id: input_select.choixreveil
        state: "06:10"
    action:
      service: light.turn_on
      entity_id: light.chambre
      data:
       transition: 120


Turn off switch after X minutes
Creating an alarm clock ! updated
Input slider for generic thermostat
Templating in conditions/triggers
Template value in "for" (time since trigger)
Your favourite automations
Combine multiple conditions with an action for each within one automation
Why won't this trigger?!
Templating in automation not working
Turn on ? at ? for ? hours
Time Input Sliders Help
MQTT Light control over the day
Slider to set timer (minutes)
Create Alarm clock
Subtract time
Onkyo Receiver Sound Automation
Make a automation to turn on the light
Change Automation trigger parameter without restarting HA
Cant get input_select working
How to schedule an automation to disarm alarm?
Support for simple daily timers via Web Interface instead of yaml rules?
Automation Not Triggering on Time
Integration with elastix pbx
Input time
#2

It looks great, what does it mean in English?


#3

Reveil matin (“Alarm clock”)
reveil positionné (a boolean to turn on TV the morning) in english "alarm clock is on"
reveil naturel (a boolean to turn on the light the morning) in english “natural wakeup”

To turn on TV a shell command is called. This shell command runs http request to internet box to control it.


#4

This is pretty cool! Any ideas why when I copy this section into my config:

input_boolean :
  reveil:
    name: Reveil positionné
    initial: off
    icon: mdi:alarm
  lightreveil:
    name: Reveil Naturel
    initial: off

I get a box with the name “Input Boolean” like this:

How did you get the outer box with the name “Reveil Martin”?

Thanks!


#5

You have to ‘customize’ your items.


Newest member of the family
#6

thanks for sharing this. but i cannot understand the automation.

The time is suppose to be dynamic, right? Shouldn’t it follows the time I select in the input_select dropdown? The automation seems to work only on 6.20.

Please correct me if I am wrong.


#7

@masterkenobi You’ll have to write an “automation rule” for every item on the input_select option.


#8

ah… that’s what I am afraid of. it seems impractical to repeat the block of codes for every input_select options. Imagine, if I have 50 options, I have to repeat the same automation rule (with changes to the time) for 50 times! The most practical way to approach this is via loop but I can’t figure out how to do so in HASS.

Do you have any idea?


#9

Not a perfect way but… triggering an automation every…5 min. and having a condition comparing actual time with input_select state:

automation:
  - alias: "Alarm clock"
    trigger:
      platform: time
      minutes: '/5'
    condition:
      platform: template
      # this will report true if time in input_select (in format HH:MM ) is equal to actual time
      value_template: '{{ now.time().strftime("%H:%M") == states.input_select.alarm_clock.state }}'
    action:
#your action here

If you wanna try, report if it works.


Best way to code input boolean selection
Alarm clock
#10

thanks a lot. i have tried it. for action, i just made it to send notification via pushbullets. when the alarm is triggered, I received countless notifications non-stop. any idea what went wrong?


#11

Can you post some logs from alarm triggering? I haven’t tested the code on my config, as I have only 3 options in my input_select, but tested the condition on template editor from hass page and it return False almost all the time, so in theory shouldn’t trigger so often.


#12

somehow i manage to fix it by adding seconds: 0 under the trigger.

By the way, in my input_select, the time option is using 15 minutes steps. For example…

alarmclock:
  name: "Alarm Clock"
  icon: mdi:alarm
  initial: "09:00"
  options:
    - "05:00"
    - "05:15"
    - "05:30"
    - "05:45"
    - "06:00"
    - "06:15"
    - "06:30"
    - "06:45"
    - "07:00"
    - "07:15"
    - "07:30"
    - "07:45"
    - "08:00"
    - "08:15"
    - "08:30"
    - "08:45"
    - "09:00"
    - "09:15"
    - "09:30"
    - "09:45"
    - "10:00"
    - "23:15"
    - "23:30"
    - "23:45"
    - "00:00"

Is it correct if I change the automation trigger to minutes: '/15' ?


#13

Sure! As you have mostly 15 minutes intervals, /15 should be ok.


#14

it works like a charm this morning. I have modified the script to add another input_boolean of “Weekdays Only” so that the alarm only runs on weekdays if it is ‘On’. Here is what i did…

input_boolean:
  alarmweekday:
    name: Weekdays Only
    initial: off
    icon: mdi:alarm

automation:
  - alias: 'Alarm Clock'
    trigger:
      platform: time
      minutes: '/15'
      seconds: 0
    condition:
      - platform: state
        entity_id: input_boolean.alarmstatus
        state: 'on'
      - platform: template
        value_template: '{% if is_state("input_boolean.alarmweekday", "on") %}{{ now.time().strftime("%H:%M") == states.input_select.alarmclock.state and (now.time().strftime("%a") == "Mon" or now.time().strftime("%a") == "Tue" or now.time().strftime("%a") == "Wed" or now.time().strftime("%a") == "Thu" or now.time().strftime("%a") == "Fri") }}{% else %}{{ now.time().strftime("%H:%M") == states.input_select.alarmclock.state }}{% endif %}'
    action:
      service: notify.notify
      data:
        message: 'Time to Wake Up'
        title: ""

#15

Yeah ! thanks to you two for that i experiment that tomorrow.

any idea for that

  - alias: "aurora 06h00"
    trigger:
      - platform: time
        after: "05:50:00"
    condition:
      - platform: state
        entity_id: input_boolean.reveil
        state: 'on'
      - platform: state
        entity_id: input_boolean.lightreveil
        state: "on"
      - platform: state
        entity_id: input_select.choixreveil
        state: "06:00"
    action:
      service: light.turn_on
      entity_id: light.chambre
      data:
       transition: 600
  - alias: "aurora 06h05"
    trigger:
      - platform: time
        after: "05:55:00"
    condition:
      - platform: state
        entity_id: input_boolean.reveil
        state: 'on'
      - platform: state
        entity_id: input_boolean.lightreveil
        state: "on"
      - platform: state
        entity_id: input_select.choixreveil
        state: "06:05"
    action:
      service: light.turn_on
      entity_id: light.chambre
      data:
       transition: 600

I think thatr is impossible to substract minutes to time in a value_template …


#16

How do you like this version

input_slider:
  slider_houres:
    name: Houres
    initial: 6
    min: 0
    max: 23
    step: 1
  slider_minutes:
    name: Minutes
initial: 0
min: 0
max: 55
step: 5

Automation:

- alias: Alarm Clock Slider
   trigger:
      platform: time
      minutes: '/5'
      seconds: 0
   condition:
    - platform: state
      entity_id: input_boolean.alarm
      state: 'on'
    - platform: template
      value_template: '{{ now.time().strftime("%H") == states.input_slider.slider_houres.state and now.time().strftime("%M") == states.input_slider.slider_minutes.state }}'
   action:
      service: light.turn_on
      entity_id: light.ground_light

#17

Slider seems neater way to do it. Thanks. Will try it out.


#18

It seems there is a problem with the code. The slider value for below 10 is only one digit, whereas the below 10 value for now.time().strftime("%H") or now.time().strftime("%M") are zero-padded. So, the above conditional statement for hour or minute below 10 will always return false.

To rectify this, just change to this…

now.time().strftime("%-H")
or
now.time().strftime("%-M")

Refering to http://strftime.org/


#19

Yes. morning noticed that too . In the evening, everything worked perfectly :slight_smile:


#20

I believe you could just move the value template line into the trigger section. That way you don’t need the part that checks the time every 15 minutes. so far it works for me.

trigger:
  platform: template
  value_template: '{{ now.time().strftime("%-H") == states.input_slider.slider_houres.state and now.time().strftime("%-M") == states.input_slider.slider_minutes.state }}'

Automation to turn light on depending on sensor values