I don’t see what I entered wrongly
oh BUGGER I had entity id instead of entity_id (you did too in your reply LOL)
haha! Thanks so much for your help. I entered it in the graphical editor and it goes into the .yaml file as:
- action:
- data:
entity_id: switch.coffeemaker
service: switch.turn_on
- data:
It was only the underscore that was defeating me. But you’re a champ.
glad it’s working. btw, i’m envious you only have to drink coffee once every 4 weeks.
hahaha! Well the rest of the time my standard wemo on/off times work it’s just every 4th sunday I have to get up earlier. Thanks so much for your help. I learnt a lot. Thanks.
I reckon you should simply integrate with Google Calendar. That way you get the strength of their recurring scheduling, and keep your config simple…
JP
I had thought of that if I couldn’t get it working through Home Assistant. In fact way back I did look at doing this but I don’t see how it is possible. Easy to trigger something from a notification, but not from a specific notification that I can see.
You should be able to this also by a simple automation conditions
- action:
service: switch.turn_on
entity_id: switch.coffeemaker
condition:
condition: and
conditions:
- condition: state
entitiy_id: switch.coffeemaker
state: 'off'
for:
days: 28 # not sure if days is an actual variable. if not just use hours: 672
- conditon: ANY OTHER CONDITON
Simply add any desired trigger. Could be every morning at 6.
Not tested, but should work
Thanks for the suggestion.
I’d make a binary commandline sensor:
binary_sensor:
- platform: command_line
command: ‘date +%e | grep 28 && echo 1 || echo 0’
name: day28_sensor
Then just run your automation based on that condition. Will work thru reboots.