None of this stuff is life-changing, but it's a very nice convenience and I find it well worth the (really minor) trouble. Though I'm using a zwave-based system, not wifi switches.
Edit: Also, crucially, our system works "as expected" if you don't know anything about it. I've never had a guest surprised or baffled by it, and it works fine if the network and/or controller is down. In some cases a single switch may turn on more than one light, but not in a weird or surprising way -- generally closer to "why didn't they just wire it that way in the first place?"
It's an insane amount of implementation complexity for what is a very simple problem.
I've got a couple of wifi-controlled Philips Hue lights. There isn't a simple "on" or "off" for these - they can be set to just about any colour and brightness. One, for instance, is set to wake my daughter up with an artificial sunrise over the space of about 15 mins in the morning, is off automatically during most of the day when there's no one in the house, and goes a very dim red at night.
As my wife has a habit of forgetting that they switch themselves off, she still fairly frequently physically switches it off at the wall. If it's still of at the point that the "dim for the evening" program is due to run, then it doesn't get triggered and I have to dig out my phone app to kick it off.
So I've just built a little switch using a Pi and a very cheap (in both senses of the word) touch screen running a web page with buttons on it that triggers various actions on the light such as setting the dimmer colour.
I'm waiting for the day when there's a cheap and good off the shelf switch that does this kind of thing properly for home automation.
But at a high level, it's pretty straightforward, and there's also almost certainly far better ways of doing it.
The key components are
- a Philips Hue light
- The Openhab[1] open source home automation server (currently running on an old Windows box that's always on for various other reasons). This controls the lights.
- Apache, also running on the same box. This provides a very simple web UI for the Pi.
- A Raspberry Pi - it's one of the original Pi model Bs.
- Firefox (Iceweasel version) on the Pi - the built-in one didn't seem to run the jquery that I needed.
- A cheapo touchscreen [2] attached to the Pi.
The OpenHab server has a plugin for Hue lights, and you can write scripts to make it do various things, such as switch on/off at a particular time, or on getting a command from somewhere else. It also has a REST API interface.
It's this API interface that the web app is calling. That's made up at the moment of 3 buttons (on, off and dim), and when one is pressed it sends a jquery REST call to the OpenHab server to trigger one of the commands. Technically, what it's doing is setting one of 3 OpenHab "buttons" to ON. This triggers the OpenHab rule to change the light.
The touchscreen attaches straight onto the Pi's GPIO pins. I pointed Firefox at the Apache on my server and set it to full screen mode. The screen's not great - it feels as cheap as you'd expect for £16 - but it works, and most importantly my daughter loves it.
Like I say, there's almost certainly better/simpler ways to achieve some of this - I suspect I could run the entire thing on the Pi for example, or replace the Pi with an old iPhone that I've got lying around. The OpenHab software also allows you to build a custom UI itself. But I like playing, and there's a bunch of tech things that I wanted to try out, and this seemed like a fun and useful project to test them out on.
My next plan is to get an Arduino and connect some dials to it to allow direct control of brightness and RGB.
[1] http://www.openhab.org/ [2] http://www.amazon.co.uk/dp/B00YE0UPES
Is it really that big of a leap to have other things be remote controlled?
I feel like every day I want the light turned on while i'm at my desk. Or i remember that i forgot to turn out the living room light when i'm in bed. Or when a friend texts me and i'd like to turn on the outside light for them.
Yeah, it's not a cure for cancer, but it's not useless either.
People like comfort, a friend of mine says that we come to earth to fight against pain (or discomfort).
There are practical scenarios that you would like to consider,
-e.g. you are on your way to the kitchen and lights turn
on on your way
-(not sure if we have a product with this feature but)
turn the temperature of lightning as it becomes night a
la f.lux
-Wake you up with lights
On the other hand even then with the exception of light temperature I would not consider it price/feature ratio worthy.There is a simple solution to that, using only standard switches and the standard power wire, -in fact I think this is a standard thing for fresh electricians-to-be to learn first year in school here.
Edit: I have this setup at home in my staircase so I don't have to walk up (or down) to turn on/off he lights.
And what if you're a renter and don't have the option of rewiring?
I think the important thing is bulb brightness along with temperature at night. The long term health costs may actually outweigh the cost of bulbs - maybe in another 5 or 10 years there with be some scientific data on that.
They don't connect to your wifi router per se, but create a mesh network among themselves. It's a very cool concept.
> The long term health costs may actually outweigh the cost of bulbs
Care to elaborate?
Overall it's been a success. But I admit part of fun was actually part of the trouble: writing code to control the lights.
A company looking for a billion dollar valuation (see Nest).