Home automation is a favorite in sci-fi, from Tony Starkâ€™s Jarvis, to Rosie the robotic maid on the Jetsons, and even the sliding doors pulled by a stagehandÂ Star Trek. In fact, most people have a favorite technology that should be just about ready to make an appearance in their own home. So where are these things? We asked you a few weeks ago and the overwhelming answer was that the software just isnâ€™t there yet.
Weâ€™re toddling throughÂ the smart home years, having been able to buy Internet-connected garage doors and thermostats for some time now. But for the most part all of these systems are islands under one roof. Automation is the topic of the current challenge for the 2016 Hackaday Prize. Developing the glue that can hold all of these pieces together would make a great entry. Why doesnâ€™t that glue yet exist?
I think the problem is really twofold. On the one hand, there isnâ€™t a clear way to make many devices work under one software. Second, there really isnâ€™t an obvious example of great user experience when it comes to home automation. Letâ€™s look at why and talk about what will eventually get us there.
Home Automation boils down to adding an automated layer between the people in the house and the human interfaces that control the house. This is actually a pretty hard sell. Do you lights need to be automated? Isnâ€™t it just lazy that you canâ€™t get up and press a light switch that works instantly without need of anything other than reliable mains power?
Thatâ€™s a tough question. Is your dishwasher a symbol of your laziness? After all, you still need to scrape any leftovers off, load the rack, run the thing, and empty it again. Now that I think of it, automating a dishwasher further would be a great entry too. But my point is that before widespread adoption a lot of people must have thought that needing an automatic dishwasher was lazy but now theyâ€™re highly desired. For smart homes to become widespread we need to make the benefits much greater than the pain of the transition.
A Tale of Two Switches
I happen to have two smarter-than-average light switches in my house. One is an actual Internet of Things Thing â€” a WeMo Light Switch â€” the other is a non-connected switch with some fancy features.Â The WeMo controls my porch lightÂ which IÂ want it to turn on at dusk and turn off at 11pm. ForÂ six years I used a switch with a programmable display that was a huge pain to set and reset as the length of days and time offset changed. It finally died (which a switch should never do)Â and I bought this one that has WiFiÂ but the software is horrible and as much of a pain as the old switch. After the stock setup didnâ€™t work I was thankfully able to get reliable service by switching to IFTTT to control it and havenâ€™t touched it since. After that experience I donâ€™t want to.
Earlier thisÂ summer I upgraded to LED recessed lighting in my living room. Itâ€™s waaaaay too bright and I needed a dimmer. I knew this was going to be an issue so I considered opting for a Wink Hub and the recessed lights and switch that go with it. I ended up with non-radio-controlled (normal) lights and a Lutron Maestro dimmer switch. This thing is awesome! You can easily set its min and max brightness for your lights, but you donâ€™t have to. UseÂ a double-tap for full brightness when you turn it on but it stillÂ remembers your dimmer setting. AÂ long-press to shut off gives you about a minute to get out of the room before shutting down.
AÂ thinkÂ the WeMo switch hardware is excellent. But considering the two switches, I love the Lutron and have a bad opinion of the WeMo for no other reason than a bad software setup experience. This is the core of the problem with Home Automation: the user canâ€™t separate a bad software experience from the hardware, and since they pay good money for the hardware they are likely to be turned off to any further automation adventures.
The concept that hardware costs money and software doesnâ€™t is part of the bigger problem. Hardware manufacturers have every incentive to build software that only works with their hardware â€” they make no money if you use their free app/website/etc. to run another manufacturerâ€™s hardware. This is a pretty tough issue to tackle.
But it does go beyond that. Letâ€™s say a hardware manufacturer were to allow third party hardware to run with their system. If that third party stuff works poorly it may sour the consumerâ€™s opinion of the entire system. Again, this issue doesnâ€™t have a clear solution.
I wantÂ to hear what you think about it â€” is the power of the pocket book (what technologies we buy and donâ€™t buy) the only leverage we have in this situation? What can we do to encourage manufacturers not to lock down theirÂ hardware systems to a proprietary ecosystem?
Weâ€™ve Solved This Before
Look to the PC industry. You can run the same program on a Dell, Acer, Asus, or Toshiba laptop. You can even change the operating system you run on those machines, and for that matter, software companies can make their products work on Macs. Itâ€™s because there are standards for defining what hardware is in these computers so that compilers may be built, and standards for how these computers communicate with the outside world (USB, Ethernet, WiFi, etc.). We need this for non-computer computing devices like lights, light switches, refrigerators, security cameras, doorbells, robot maids, and the like.
We Need a SoftwareÂ Champion
We need to separate hardware from software so the hardware companies can do what theyâ€™re best at â€” build affordable devices that work reliably year in and year out. I donâ€™t think this can happen until a clear software champion (or group of champions) appears. This means an intuitive interface that your average human can understand, configure, and intuitively operate at the same level you can operate a light switch.
This is a really hard problem. How do you think it should be approached? What is the incentive for someone to build these software tools? Get the conversation started below. As with the last installment Iâ€™ll pick out some of the most interesting comments and send out Hackaday t-shirts. From the last discussion we sent shirts out to [aleksclark], [DaveW], [Dax], [fountside], [Ian Lee], [j0z0r], [jan], [maxzillian], [Neil Cherry], and [sangwiss].
Are you into DIY home automation? Nowâ€™s a great time to show off some of your work. Enter your project now for the Automation challenge of the 2016 Hackaday Prize. Twenty entries will win $1000 each and go on to the vie for the grand prize of $150,000.