Let me know if you ever make any headway with setting your floorplan up! I’ve been trying to work on mine off and on for the last couple of months but there’s not really much documentation out there on the subject yet as far as getting it all working correctly.
Thank you so much for sharing this. Quick question for you regarding your scripts. I found the workday sensor as a HA component but wondered what the following are. Do I need them in my script for it to work?
input_boolean.vacation
input_boolean.company
calendar.holidays_in_united_states
calendar.work
Hey @Darren_Edwards no, you do not need those, they are specific to my installation, and used to check for various custom conditions (if it’s a holiday, I’ll probably be sleeping in; if I take PTO, I add it to my work calendar; etc)
Happy automating!
1 Like
Thank you @xstrex I have made a few changes of my own and ended up adding back in the “Alarm Clock Awake Pushed” automation so that entities (such as lights) don’t turn on when the actionable alert is first sent. My automation for ‘when awake button pushed’ then now turns on lights, turns on the coffee machine and starts my music playing in the kitchen. Thanks so much again for sharing your code. I can see so many applications.
1 Like
Hello
I have added this to my setup, but I can’t get it to work. There are no errors and I have adapted everything for my setup, but when I enter the time for the alarm nothing happens. I’m using it as a card into a group, I don’t know if it makes a difference…
Also, the alarm time is not remembered if I restart HA, so I have to set it up again from the panel. Is this normal?
Thanks
My problem is with the time sensors, that’s the part is not working for me.
If I put the automation for a fixed time (instead of it based on whatever set on the frontend), then it works fine.
There has been any changes in the way sensors work lately?
I think so because mines been hit or miss lately. I’ve just been too busy with work to figure it out.
As far as things being reset when you restart HA all you have to do is delete the initial: lines out of the input numbers and booleans. HA changed some things since I’ve wrote this and it’s definitely due for some updates.
I’ll try to get to it as soon as possible
Done something very similar. We have options for our alarm because we are both shift workers and each “morning” is so dynamic.
Can choose to wake up to the kettle on, heater on, Google Home playing music, bedroom lights on and the main lights on.
Also hit silence on our phones from the push notification to shut google home up.
Nothing better when it all comes together!
2 Likes
Hi, I really love the addition of these options. Any chance you can share your config? It would be much appreciated. Thanks
We use input booleans to turn on or off these different items
input_boolean: alarm_kettle: name: Alarm Kettle initial: off icon: mdi:kettle
Then the automation for the alarm is longer than it needs to be but I have made it so when the alarm equals the time then it will turn on the kettle for example. The kettle only triggers if the input boolean is on and someone is home. Had to include a backup if we got up earlier and walked out forgetting the alarm was going to trigger. Another thing is we can’t run the heater and the kettle at the same time so I had to ensure the heater was off before the kettle runs.
- alias: Alarm Kettle
trigger:
- platform: template
value_template: '{{ states.sensor.time.state == states.sensor.alarm_clock_time }}'
condition:
- condition: and
conditions:
- condition: state
entity_id: input_boolean.alarm_kettle
state: 'on'
- condition: state
entity_id: input_boolean.alarm_heater
state: 'off'
- condition: or
conditions:
- condition: state
entity_id: device_tracker.iphone1
state: home
- condition: state
entity_id: device_tracker.iphone2
state: home
action:
- service: switch.turn_on
entity_id: switch.kettle
1 Like