Comment by madaxe_again
2 days ago
I did similar with our coffee machine a year ago - I was bored of getting home from the school run to a cold pot of coffee because the machine automatically turns off the hot plate after 30 minutes, and it seems there is no such thing as a WiFi connected drip coffee machine. Kettles, yes, coffee machines, no.
Dead simple. Cracked it open, chucked an ESP32 in there connected to the soft power button, and to the “machine is on” indicator on the display, which was conveniently on its own pin. No need for any thermal protection cleverness as the machine does that itself.
Now I just turn it back on when I’m heading home, and no longer have to wait for the pot to warm up again.
I then decided to stop using the “make coffee at time” functionality baked into the machine, as the kid gets up when the kid gets up, and the machine would either start early and wake her, or she’d get up before it and I’d have to go start it. Now, she opens her bedroom door, I get “kid is awake” alert on my phone, and the machine brews the coffee.
> Now, she opens her bedroom door, I get “kid is awake” alert on my phone, and the machine brews the coffee.
Out of all of the smart home threads and articles I've read over the years this is the only sentence that made me wish I had it. It's genius
Until the kid uses the bathroom in the middle of the night and goes back to bed. Though the GP seems to not mind stale coffee so perhaps he won't care.
Exceptions like the above make automations hard.
It seems pretty easy to throw in an earliest time to trigger it
DR stands for "didn't realize"; the first time it happens you just run back to the drawing board and add some safety boundaries on it.
So... just make sure the automation only becomes available from ~6 AM to 8 AM. ;)
2 replies →