Creating a alarm clock

Vantskruv · January 7, 2017, 6:49am

The rule is to break the failure which is in a current quantum state (hence everything is the fault).

How do you break this rule and opening the cats box? You do this by posting a message for help in a forum.

The problem is the timezone, actually I’ve tested it but in the wrong direction. I did turn on the timer just to see if works after night. I did set the time to 06:16, and the timezone I’m living in is Europe/Stockholm. The timer triggered one hour too early, in the logbook the switch was turned on at 05:16.

I did try it again, and the trigger is activated 1 hour too early.

So it seems even though I’ve the timezone setup correctly in configuration file, it still is wrong.

Vantskruv · January 7, 2017, 7:10am

Update:
I did add a field showing the current time (this is the time I do compare with in the conditions when triggering the action). The strange thing is that this field is showing current local time correctly, even though the trigger is activated one hour too early:

 - platform: template
   sensors:
     current_time:
       friendly_name: Nuvarande tid
       value_template: '{{ "%0.02d:%0.02d" | format(now().strftime("%-H") | int, now().strftime("%-M") | int) }}'

Update 2:
I solved the problem, though I’m not sure if this is a bug I have avoided in homeassistant.
What I did was to compare the values of. current_time with car_heat_time. It seems if compare the values from now() directly does not work (hence UTC is returned). If setting a value in homeassistant from now(), homeassistant will then, in a later state, convert this value to local time.

These two configuration files now works, but I’m unsure which ones is the most reliable approach.
Which is most reliable of setting trigger to:

poll every minute and then compare the times and button states
or
activate from a value_template comparison, and then check condition of button states.

The second method feels cleaner code-wise.
config.yaml (3.6 KB)

config2.yaml (3.5 KB)

daenny · January 7, 2017, 1:19pm

Nice that you found your issue. Good catch with showing the current time as custom sensor. But weird I am also on the same non UTC timezone and I last time I checked, it worked for me…
On which version are you?
You do not need the extra switch actually. You can directly switch the automation rule itself on and off. So the additional switch is just duplicating this behaviour. Then the second option is even cleaner in the configuration file. It gets triggered just as often I think (every time the sensor for the time changes, so every minute).

Did you also try using the timestamp_custom function? Can you check what a sensor with the template

'{{ (now().strftime("%s") | int | timestamp_custom("%H:%M")) }}'

shows? If that is the correct time, then the automated rule should work. Otherwise it’s a bug…

daenny · January 7, 2017, 1:50pm

By the way a good way to test and debug your rules quickly is using the template developers feature, left side second last icon.
There you can add your code to test and see what it would show. I also tested my rules this way.

And I still think that the timestamp_custom should just work :P. As you can see it shows 14:46, while it was 13:46 UTC time.

Vantskruv · January 7, 2017, 9:30pm

Thanks for your tips @daenny.

Tried running the command:
‘{{ (now().strftime("%s") | int | timestamp_custom("%H:%M")) }}’
in the template developers UI.

It was giving me a time of: 23:20
While the local time was: 22:20
UTC time was : 21:20

Going in via ssh to the server and typing ‘date’ in the terminal gave me an UTC time of: 21:20.
So there is something strange going on for sure. Maybe homeassistant is using two different timezones?

Edit:
Version of homeassistant I’m using is: 0.35.3
Version of python3 is: 3.4.2

daenny · January 7, 2017, 10:34pm

Yeah that is indeed weird. That would mean that somewhere your timezone settings are messed up.

You can verify your timezone:

'{{ (now().strftime("%s") | int | timestamp_custom("%H:%M %z%Z")) }}'
'{{ (now().strftime("%s") | int | timestamp_local }}'
'{{ (now().strftime("%Z") ) }}'

But I guess these would show for you +0200 as your timezone. Which is incorrect. Did you try setting a different timezone, with the same time, i.e. Europe/Amsterdam?
And can you run the date command with showing the timezone on your server via ssh:

date +'%T %z %Z'

Vantskruv · January 8, 2017, 12:26pm

Your code in the UI shows:
‘14:25 +0100CET’
‘2017-01-08 14:25:58’
‘CET’

While the code in ssh shows:
12:26:02 +0000 UTC

Weird indeed.

daenny · January 10, 2017, 12:48am

This is really weird indeed. So the timezone is set correctly, and the UTC time is correct on your server machine. But the time is still wrong…
But you say that:

now().strftime("%H:%M")

shows the correct time? So I assume that the Homeassistant internal UTC clock is off by one hour.
You can confirm my suspicion by running:

{{ now().strftime("%s") | int | timestamp_utc }}

Vantskruv · January 11, 2017, 11:32am

Yeah, these two lines do show the correct time:
{{ now().strftime("%H:%M") }}
{{ now().strftime("%s") | int | timestamp_utc }}

Edit:
Summing it up again:

1.    '{{ (now().strftime("%s") | int | timestamp_custom("%H:%M %z%Z")) }}'
2.    '{{ (now().strftime("%s") | int | timestamp_local()) }}'
3.    '{{ (now().strftime("%Z") ) }}'
4.    {{ now().strftime("%s") | int | timestamp_utc }}
5.    {{now().strftime("%H:%M")}}
6.    $ TZ='Europe/Stockholm' date //SSH terminal
7.    $ date //SSH terminal

1.    '13:38 +0100CET'
2.    '2017-01-11 13:38:45'
3.    'CET'
4.    2017-01-11 12:38:46
5.    12:38
6.    Wed 11 Jan 12:38:49 CET 2017
7.    Wed 11 Jan 11:38:51 UTC 2017

daenny · January 11, 2017, 12:15pm

At least it’s consistent. Apparently, for some reason your homeassistant’s UTC time is off by one hour. This explains the issues you were having. And it’s worthwhile to fix it, since otherwise, as soon as you switch to summer time, your timers will not work anymore at the suspected times but one hour off… But I have no clue what it causing the time shift…

Danielhiversen · January 11, 2017, 12:29pm

Have you sat the correct time_zone in the config?

github.com

Danielhiversen/home-assistant_config/blob/master/configuration.yaml#L9


homeassistant:
  # Location required to calculate the time the sun rises and sets
  latitude: !secret latitude
  longitude: !secret longitude
  elevation: 47
  unit_system: metric
  # Pick yours from here:
  # http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
  time_zone: Europe/Oslo
  # Name of the location where Home Assistant is running
  name: _
  customize: !include customize.yaml
  packages: !include_dir_named packages

frontend:

updater:
  include_used_components: true

Vantskruv · January 11, 2017, 1:31pm

Yes:
time_zone: Europe/Stockholm

Bob_NL · January 12, 2017, 6:33pm

This did it for me, thanks a lot!

- alias: 'Rule 9 - Wakeup Light'
  trigger:
    platform: time
    minutes: '/5'
    seconds: '0'
  condition:
    - condition: template
      value_template: '{{ (now().strftime("%s") | int | timestamp_custom("%H:%M")) == states.input_select.alarmtime.state  }}'
  action:
    service: light.turn_on
    data:
      entity_id: light.bed_room
      brightness: 255
      rgb_color: [255,255,255]
      transition: 1200

Bob_NL · January 12, 2017, 8:34pm

And now with radio (slowly increasing volume every minute):

- alias: 'Rule 9 - Wakeup Light with Radio'
  trigger:
    platform: time
    minutes: '/5'
    seconds: '0'
  condition:
    condition: and
    conditions:
      - condition: template
        value_template: '{{ (now().strftime("%s") | int | timestamp_custom("%H:%M")) == states.input_select.alarmtime.state  }}'
      - condition: state
        entity_id: input_boolean.alarm_clock
        state: 'on'
  action:
    - service: light.turn_on
      data:
        entity_id: light.bed_room
        brightness: 255
        rgb_color: [255,255,255]
        transition: 1200   
    - service: media_player.play_media
      data:
        entity_id: media_player.bed_room
        media_content_id: http://vip-icecast.538.lw.triple-it.nl:80/RADIO538_MP3
        media_content_type: 'audio/mp4' 
    - service: media_player.volume_set
      data:
        entity_id: media_player.bed_room
        volume_level: '0.05'
    - delay: '00:01:00'
    - service: media_player.volume_set
      data:
        entity_id: media_player.bed_room
        volume_level: '0.10'
    - delay: '00:01:00'
    - service: media_player.volume_set
      data:
        entity_id: media_player.bed_room
        volume_level: '0.15'
    - delay: '00:01:00'
    - service: media_player.volume_set
      data:
        entity_id: media_player.bed_room
        volume_level: '0.20'
    - delay: '00:01:00'
    - service: media_player.volume_set
      data:
        entity_id: media_player.bed_room
        volume_level: '0.25'
    - delay: '00:01:00'
    - service: media_player.volume_set
      data:
        entity_id: media_player.bed_room
        volume_level: '0.30'
    - delay: '00:01:00' 
    - service: media_player.volume_set
      data:
        entity_id: media_player.bed_room
        volume_level: '0.35'
    - delay: '00:01:00'
    - service: media_player.volume_set
      data:
        entity_id: media_player.bed_room
        volume_level: '0.40'
    - delay: '00:01:00'
    - service: media_player.volume_set
      data:
        entity_id: media_player.bed_room
        volume_level: '0.45'
    - delay: '00:01:00'     
    - service: media_player.volume_set
      data:
        entity_id: media_player.bed_room
        volume_level: '0.50'
    - delay: '00:01:00' 
    - service: media_player.volume_set
      data:
        entity_id: media_player.bed_room
        volume_level: '0.55'
    - delay: '00:01:00'
    - service: media_player.volume_set
      data:
        entity_id: media_player.bed_room
        volume_level: '0.60'
    - delay: '00:01:00'
    - service: media_player.volume_set
      data:
        entity_id: media_player.bed_room
        volume_level: '0.65'
    - delay: '00:01:00'
    - service: media_player.volume_set
      data:
        entity_id: media_player.bed_room
        volume_level: '0.70'
    - delay: '00:01:00'
    - service: media_player.volume_set
      data:
        entity_id: media_player.bed_room
        volume_level: '0.75'
    - delay: '00:01:00'
    - service: media_player.volume_set
      data:
        entity_id: media_player.bed_room
        volume_level: '0.80'
    - delay: '00:01:00' 
    - service: media_player.volume_set
      data:
        entity_id: media_player.bed_room
        volume_level: '0.85'
    - delay: '00:01:00'
    - service: media_player.volume_set
      data:
        entity_id: media_player.bed_room
        volume_level: '0.90'
    - delay: '00:01:00'
    - service: media_player.volume_set
      data:
        entity_id: media_player.bed_room
        volume_level: '0.95'
    - delay: '00:01:00'     
    - service: media_player.volume_set
      data:
        entity_id: media_player.bed_room
        volume_level: '1.0'
    - delay: '00:01:00'

Bob_NL · January 13, 2017, 5:22pm

I’m trying to trigger my alarm clock 20 minutes before wakeup time but don’t succeed with the code. Can someone help me out?

Original code (which triggers perfectly fine at the time I set with the input boolean):

{{ (now().strftime("%s") | int | timestamp_custom("%H:%M")) == states.input_select.alarmtime.state   }}

Tried several options but none of them are correct:

{{ (now(--'00:20:00').strftime("%s") | int | timestamp_custom("%H:%M")) == states.input_select.alarmtime.state   }}

{{ (now(-1200).strftime("%s") | int | timestamp_custom("%H:%M")) == states.input_select.alarmtime.state   }}

{{ (now().strftime("%s") | int | timestamp_custom("%H:%M")) == states.input_select.alarmtime.state  -- "00:20:00" }}

{{ (now().strftime("%s") | int | timestamp_custom("%H:%M")) == states.input_select.alarmtime.state  -- 1200 }}

Using “00:20” instead of “00:20:00” also doesn’t work.

turboc · January 13, 2017, 5:31pm

syntax error or is the alarm going off at the wrong time? Because the calculations on the left side should add 20 minutes to the current time to compare against the time on your input boolean not subtract it.

Bob_NL · January 13, 2017, 5:34pm

I’m getting a syntax error in the frontend Templates page (and what I mean by that is that the output is blanc instead of “false” or “true”).

turboc · January 13, 2017, 5:37pm

I’m new to HA and templating so forgive me if this question is something I should know. But why the – 1200 on the last one and not just -1200

badgerhome · January 13, 2017, 5:37pm

anyone managed to add a “snooze” and “off” function? I’m using mqtt buttons with Wemos D1 and Button Shield and also Amazon Dash buttons for various other automations around the house.

A snooze and off function would be easy with two buttons (one for snooze that stops the script for 5mins and then starts it again using a delay. And off is self explanatory) but really id like one button. Anyone have any thoughts about this?

Cheers!

Bob_NL · January 13, 2017, 5:39pm

I’m rather new to HA as well and the double minus is just something I figured should be the syntax since equal also must contain 2 “==” instead of 1.

BTW: single minus isn’t working as well