Wow, did not know this was possible. Going to use this for sure so I can set my next alarm with my Google Home (“Ok Google, set alarm 7 hours from now”). Great!
Update: In the excitement I forgot that I still gave to use my phone for this to work. Nice project for the weekend: find a way to use my Google Home for this instead of the Google Assistant on my phone. Just because picking up your phone to control Home Automation is way too big of an effort 
In my setup, the end of my wakeup profile is switching off the alarm. It’s switched to on whenever I set my next alarm AND I am home. This way I can also set my alarm when I don’t spend the night at home ( and thus I don’t want my wakeup alarm to trigger for an empty house 
).
Right, Google Home won’t activate the task (I assume because it’s not actually setting the alarm on your phone). Which is a pain sometimes because I have my Google Home in my bedroom, so if I want to set my alarm with voice before I go to sleep, I say “Okay, Google” and both my phone and my Google Home activate, and usually the Home answers my request to set an alarm which isn’t what I want.
I’m not sure how I would have Google Home set the alarm and also send a request to HA to update. Honestly, not sure if it’s worth the time for me to try to implement. I’ll just keep whispering to my phone at night so that my Home doesn’t hear me “Okay, Google…set my alarm for tomorrow morning and don’t tell my Google Home” 
Just out of curiousity: why are you triggering MQTT automations through HTTP? Isn’t it more logical to trigger them through MQTT (since it’s super lightweight)? There is a MQTT extension for Tasker in the Play Store (MQTT Publisher).
Don’t get me wrong, looks like you did a very good job figuring out to make it work but I’m missing the point of using MQTT instead of “regular” HTTP post commands in this setup.
Hey Bob, the only reason that I’m triggering the automation through HTTP is because before your post, I didn’t know any better! I’m working on implementing a new trigger using MQTT Publisher from Google Play.
So, I have mosquito running on my HA server, so I guess the port number to publish to should be the port mosquito is running on? I’m implementing the new trigger right now and I’ll let you know how it goes. Thanks for the advice!
@astone Ok, perhaps I should have been more clear on that area. I’m using a CloudMQTT instance myself. Configuration is pretty straightforward.
mqtt:
broker: <redacted>.cloudmqtt.com
port: <redacted>
username: <redacted>
password: <redacted>
- alias: Set alarmtime_hour
trigger:
platform: mqtt
topic: "setHour"
action:
service: input_slider.select_value
data_template:
entity_id: input_slider.alarm_hour
value: '{{ trigger.payload}}'
- alias: Set alarmtime_minutes
trigger:
platform: mqtt
topic: "setMinutes"
action:
service: input_slider.select_value
data_template:
entity_id: input_slider.alarm_minutes
value: '{{ trigger.payload}}'Shouldn’t “%minutes” be quoted as well?
So:
{"topic":"setMinutes","payload":"%minutes"}Instead of:
{"topic":"setMinutes","payload":%minutes}So much work for an alarm clock?
@anon35356645 uhh yeahh well that’s kind of the whole point of Home Automation: spending lots of time configuring to make it easier for yourself at the end…
So, I tried setting up this trigger with MQTT Publisher and I couldn’t get it to work. Every time my task fired I got a message saying that MQTT Publisher crashed and then my server wouldn’t update. So I think I’ll stick with the HTTP Post for now because it’s working pretty well.
No, I don’t think %minutes should be quoted. To me, when you put something in quotes it means to send the string "%minutes" rather than the variable %minutes. In this case, I want to send whatever the value of %minutes is, so I don’t want to put it in quotes. Having it without quotes in my post requests has worked so far.
I personally think that it’s fun to mess with things like this to create something cool in the end, even if it does take a lot of time at first. Also, mine works right now, and I think it’s pretty cool.
For iOS users who would like an easier way to set their alarm, I have made a Workflow sequence using the REST API.
https://workflow.is/workflows/23ed6322b7634bd78009849c5e946942
You need to edit it to add your URL and password, and probably change the variable names (this sets values for 2 input sliders - one for the hour, one for the minute).
I’ve made an alarm clock that increases brightness of your lights automatically based on a chosen fade-in time (like phillips wakeup lights):
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.
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"I used this config
But how can i let the alarm go off on my iphone? i cant find it anywhere…
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 …
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.
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_upI 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:
time_date platform in value_template just like yours:'{{ states("sensor.time") == states("sensor.alarmclock_lights_time") }}'
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.
@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.