Creating a alarm clock

Share your Projects!
219

I’ve been messing around with this clock.
It worked at one point. But now out of nothing it doesn’t anymore.

Problem seems to be that the trigger never gets to be true.

I use the following code as part of the trigger.
value_template: ‘{{ states.sensor.time.state == states.sensor.alarm_time.state}}’

When tested in templates while I now the times should match it still gives out a false result.
Looked at the single parts they both give the same value in that time frame.

What to do?

Found out what was wrong. Alarm Time Hours need to be in 2 digits format.

1 Like
220

Not sure if anybody here has already published this neat way of zero padding the input_slider values. If not, here you go…

{{ "{:02d}".format(states.input_slider.slider_name.state|int) }}

Applied as a sensor that displays the set hours and minutes on the front end:

sensor:
  set_timer:
          value_template: '{{ "{:02d}".format(states.input_slider.timer_hours_1.state|int) }}:{{ "{:02d}".format(states.input_slider.timer_minutes_1.state|int) }}'
          friendly_name: "Timer"
1 Like
221

I used this config

But how can i let the alarm go off on my iphone? i cant find it anywhere…

1 Like
222

I use the alarm clock, but want to use several alarm clocks (one for me and one for each of the kids). How do I get it? Do I have to duplicate the entire code and rename the switches, script, input slider, input bolean … or can I use any of it as it is?
Programming is quite new to me so i need some help …:confused:

223

Yes, I believe renaming the entities is mandatory, but the good news is: you could automate it !
The template devtool is your friend in your exploratory operations, invaluable in code generation and substitution, every session is bountyful and likely to end with a quick copy and paste.

224

I need help on identifying why my automation is not running even when the template in the trigger returns true (tested in the Developer Tools).

Sensors:

- platform: template
  sensors:
    alarm_clock_hour:
      value_template: '{{ states.input_slider.alarm_clock_hour.state|int }}'
    alarm_clock_minute:
      value_template: '{{ states.input_slider.alarm_clock_minute.state|int }}'
    alarm_clock_time:
      value_template: >-
        {{ states.sensor.alarm_clock_hour.state }}:
        {%- if states.sensor.alarm_clock_minute.state|length == 1 -%}
          0
        {%- endif -%}
          {{ states.sensor.alarm_clock_minute.state }}
    alarm_clock_time_long:
      value_template: >-
        {% if states.sensor.alarm_clock_hour.state|length == 1 -%}
          0
        {%- endif -%}
          {{ states.sensor.alarm_clock_hour.state }}:
        {%- if states.sensor.alarm_clock_minute.state|length == 1 -%}
          0
        {%- endif -%}
          {{ states.sensor.alarm_clock_minute.state }}
    alarm_clock_start:
      value_template: '{{ ((as_timestamp(now())|int + 300)|timestamp_custom("%H:%M")) }}'

Automation:

- alias: 'almclk_wake_up script triggered by alarm clock'
  trigger:
    platform: template
    value_template: '{{ states.sensor.alarm_clock_start.state == states.sensor.alarm_clock_time_long.state }}'
  condition:
    condition: state
    entity_id: input_boolean.alarm_clock_status
    state: 'on'
  action:
    service: script.wake_up
225

I found post#73 to be very informative at the time: a very nice rewording of the actual documentation on automation template and time triggers. tldr:

  • leverage the time_date platform in value_template just like yours:
    '{{ states("sensor.time") == states("sensor.alarmclock_lights_time") }}'
  • the other option is to trigger evaluation every ‘/n’ time unit with a time platform trigger since at: won’t take a template.

Relative time calculations can horribly complexify the template expression. I, for myself, try to stick to kiss approach, favoring decoupling in general and ultimately thinking packaging when it comes to my configuration.

226

@patkap thank you for your answer. I tried your suggestions, but unfortunately they did not work either.

This is so sad, I can’t understand why this is the only automation that’s not working.

227

Hi @mbonani,

for me it works with that :

    trigger:
      - platform: time
        minutes: '/1'
        seconds: 0
    condition:
      - condition: state
        entity_id: input_boolean.automa
        state: 'on'
      - condition: state
        entity_id: calendar.jours_feries_en_france
        state: 'off'
      - condition: template
        value_template: '{{ ((now().strftime("%s") | int + 300) | timestamp_custom("%H:%M") == states.sensor.alarm_time.state) }}'
    action:
      - service: light.turn_on
        entity_id: light.chambre
        data:
          transition: 600
          brightness: 255

you could test with the trigger /1 minutes …

228

Just tested with the copied and pasted code you provided plus some missing bits …

input_slider:
  alarm_clock_hour:
    initial: 6
    min: 0
    max: 23
    step: 1
  alarm_clock_minute:
    initial: 45
    min: 0
    max: 59
    step: 1

input_boolean:
  alarm_clock_status:
    initial: on

sensor:
  - platform: time_date
    display_options:
      - 'time'
  - platform: template
    sensors:
      alarm_clock_hour:
        value_template: '{{ states.input_slider.alarm_clock_hour.state|int }}'
      alarm_clock_minute:
        value_template: '{{ states.input_slider.alarm_clock_minute.state|int }}'
      alarm_clock_time:
        value_template: >-
          {{ states.sensor.alarm_clock_hour.state }}:
          {%- if states.sensor.alarm_clock_minute.state|length == 1 -%}
            0
          {%- endif -%}
            {{ states.sensor.alarm_clock_minute.state }}
      alarm_clock_time_long:
        value_template: >-
          {% if states.sensor.alarm_clock_hour.state|length == 1 -%}
            0
          {%- endif -%}
            {{ states.sensor.alarm_clock_hour.state }}:
          {%- if states.sensor.alarm_clock_minute.state|length == 1 -%}
            0
          {%- endif -%}
            {{ states.sensor.alarm_clock_minute.state }}
      alarm_clock_start:
        value_template: '{{ ((as_timestamp(now())|int + 300)|timestamp_custom("%H:%M")) }}'

automation:
  - alias: 'almclk_wake_up script triggered by alarm clock'
    trigger:
      platform: template
      value_template: '{{ states.sensor.time.state == states.sensor.alarm_clock_time_long.state }}'
    condition:
      condition: state
      entity_id: input_boolean.alarm_clock_status
      state: 'on'
    action:
      service: persistent_notification.create
      data_template:
        title: 'Alarm!'
        message: '{{ trigger.to_state.state }}

Options !

229

@Vantskruv

I had the same problem with the time and changed the script from (now().strftime("%s") | int | timestamp_custom("%H:%M")) to as_timestamp (now()) | timestamp_custom("%H:%M") and now everything works fine.

230

I forgot to post I had the same problem. For some reason now().strftime("%s") returns weird values here, as_timestamp(now()) solved it.

((now().strftime("%s")|int)|timestamp_custom("%H:%M")) == 13:23

((as_timestamp(now())|int)|timestamp_custom("%H:%M")) == 17:23

231

@Vantskruv and @j.assuncao, are you guys using Hassio?

232

@mbonani Yes, i am using hass.io

233

Just started a test environment (Python virtualenv in a fresh installed Debian) and it worked fine:

((now().strftime("%s")|int)|timestamp_custom("%H:%M")) == 18:31

((as_timestamp(now())|int)|timestamp_custom("%H:%M")) == 18:31

It must be some problem with Hassio.

234

@mbonani can it be the configurations of time zone being different between Home Assistant and Resin OS??

I’ve tried to gain access to Hassio core via ssh on port 22222 but it gives me an error using Putty “Disconnected: No supported authentication methods available (server sent: publickey)”. I’ve used this: https://home-assistant.io/developers/hassio/debugging/

Can you please confirm if the timezone configuration is different?

235

@j.assuncao did you use pageant to load your private key before trying to access?

236

Different timezones

$ ssh -p 22222 [email protected]
root@hassio:~# date
Sun Aug 20 00:08:48 UTC 2017

$ ssh [email protected]
core-ssh:~# date
Sat Aug 19 20:09:55 EDT 2017
1 Like
237

@mbonani Yes, i used Pageant to load the key…

238

Just create a file named authorized_keys in the root of the resin-boot partition containing your public key in the following way:

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCg14Wi4…

You can copy this information from the SSH add-on configuration

1 Like