to move away from alarm clocks toward using lighting.
My first proof-of-concept was with a vacation timer, which simply turned the switch on and off. I moved to WeMo, and have most of my controls via IFTTT.
At 7am, turn on
At 10am, turn off
When phone enters this circle, turn on
At midnight, turn off
I also part of the IFTTT Maker platform, so I also have curl commands to turn on and off
alias toggle_bedroom='curl -X POST https://maker.ifttt.com/trigger/toggle_bedroom_lights/with/key/NOT_GONNA_SHOW_MY_KEY_HERE &> /dev/null'
The WeMo switches are in inaccessable parts of the room, the light switch does nothing, and the smartphone is usually locked, so I bought a Google Home Mini so I can say Hey Google, make it dark and Hey Google, light it up.
Which, so far, is only slightly more developer than plug-and-play Smart Home, and it relies heavily on Cloud services, which is sub-optimal when you have CENSORED home internet. This morning was a perfect example; everything was dark because IFTTT couldn't tell WeMo to wake me up, and when I did wake up, Home said "I can't find the Internet."
So, putting ouimeaux on my Raspberry Pi and having the core schedule be local instead of cloud is, as of this morning, a high-priority project for me.
Once the Pi is handling the scheduled tasks of turning on and off the lights, the next task is to use Mozilla's Common Voice to get the voice control off the cloud as well.
The move to Philips Hue as Nick Rowe suggests with his project and video is, as of last night, a step too far in terms of Spouse Acceptance Factor. (Explicitly. I showed her the video and she said she thinks it's dumb.) I might go there anyway, eventually.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I was inspired by this
to move away from alarm clocks toward using lighting.
My first proof-of-concept was with a vacation timer, which simply turned the switch on and off. I moved to WeMo, and have most of my controls via IFTTT.
I also part of the IFTTT Maker platform, so I also have
curlcommands to turn on and offThe WeMo switches are in inaccessable parts of the room, the light switch does nothing, and the smartphone is usually locked, so I bought a Google Home Mini so I can say
Hey Google, make it darkandHey Google, light it up.Which, so far, is only slightly more developer than plug-and-play Smart Home, and it relies heavily on Cloud services, which is sub-optimal when you have CENSORED home internet. This morning was a perfect example; everything was dark because IFTTT couldn't tell WeMo to wake me up, and when I did wake up, Home said "I can't find the Internet."
So, putting ouimeaux on my Raspberry Pi and having the core schedule be local instead of cloud is, as of this morning, a high-priority project for me.
Once the Pi is handling the scheduled tasks of turning on and off the lights, the next task is to use Mozilla's Common Voice to get the voice control off the cloud as well.
The move to Philips Hue as Nick Rowe suggests with his project and video is, as of last night, a step too far in terms of Spouse Acceptance Factor. (Explicitly. I showed her the video and she said she thinks it's dumb.) I might go there anyway, eventually.