Google's entering the HA arena

Sacarino

Member
Very interesting... I will definitely be watching to see where this goes, specifically the music streaming. I had almost resigned myself to the AirPort/AirTunes/iAddict route, so I'm happy to see this new development.

From http://www.bgr.com/2011/05/10/google-announces-android-home/

Google announced on Tuesday a new feature of the Android operating system called Android @ Home. The framework and associated functions transform an Android device into a home automation controller that connects and directs all of the devices and appliances in the user’s home. Android @ Home framework can be used to control gaming consoles, lighting, appliances, irrigation systems and anything else developers can envision. Google also announced project tungsten as part of the Android @ Home product, which consists of a hub that runs the Android OS and the Android @ Home framework. Among the functions of a Tungsten hub, as shown off on stage at Google I/O 2011, is the ability to stream music directly from Music Beta by Google to any supported home audio device. Android @ Home is completely open and developing with the framework requires no fees and no registration.

Here's a longer, more in-depth article: http://www.mediapost.com/publications/?fa=Articles.showArticle&art_aid=150257 Very cool stuff! I dig the NFC concept, although I'm somewhat skeptical of the real-world application of it. Another lighting protocol should be interesting as well.
 
I wish more details were in the article, but below is the link. Basically, Google has announced "Android@Home," and it appears to control lighting and HVAC amoung other things.

http://www.engadget.com/2011/05/10/google-announces-android-at-home-framework/
 
I've been reading and searching but so far it all seems to be about software development (for Android) and APIs. Not exactly a solution. I think something is missing from the story so far.
 
I merged these 2 threads together, since they are about the same topic.

As for the announcement itself. I'm not convinced just yet that it is something we will benefit from in the near future, as it doesn't seem to support existing protocols.
 
I merged these 2 threads together, since they are about the same topic.

As for the announcement itself. I'm not convinced just yet that it is something we will benefit from in the near future, as it doesn't seem to support existing protocols.

Hopefully they will, like with other protocols they have developed, bought, adopted, release it as open source and protection from liability. The reason they probably didn't adopt ZWave or Zigbee is that both are "standards" but products need to be licensed. So you can't develop a product without paying someone for a license.

That is what the HA community has been missing since X10. An open source, non-proprietary protocol without having to answer to some company or license pool.
 
another tidbit of info:

Google. Based upon our conversations with Google at I/O, Android@Home will use a mesh networking protocol that functions in the 900MHz frequency bands just like Z-Wave -- but it's not Z-Wave. Google has developed its own wireless protocol and Android@Home framework that lets Android apps discover, connect, and communicate with electrical appliances and devices in the home. So yes, it's proprietary, but hey, it's "open."

http://goo.gl/UAjYo

on a side note, i will be looking into how to install adblock on my refrigerator and washer ;)
 
http://www.engadget.com/2011/05/11/editorial-android-home-is-the-best-worst-thing-that-could-happe/

more engadget feelings on this topic
 
The other thing is, this is just a software framework, it's hardware where things get complicated (judging by the lack of 'perfect' home automation light switch).
 
The other thing is, this is just a software framework, it's hardware where things get complicated (judging by the lack of 'perfect' home automation light switch).

Yeah, and actually lighting is the easy part (on/off/dim). It's when support for additional device types comes into play that things start to get complicated, they start to realize that things like appliances are all over the place in their capabilities and it is hard to come up with a one size definition.

I am a little disappointed that it seems so Android specific. I wish they would publish the protocol specs and not just release SDKs and HDKs... Hopefully that stuff is coming...
 
People, there's one thing that bugs me since the announcement. I don't quite get the "smart light bulb" part.

You gonna have the circuitry INSIDE the light bulb that you can wirelessly control. Fine. But when I turn the light off at the switch, there's no more power to feed that circuitry. Now you need some smarts at the switch level to be able to turn it back on. Why duplicate the effort? Just put that circuit in the switch!

Ok, there might be some edge cases where you don't have a physical switch for a load (in this case it's like having a Smarthome's InlineLinc, or X10's Socket Rocket). But that is an edge case.

I can think of some other crazy ways of using those smart bulbs. For example, create a scene that turns a series of smart lights ON at the switch (one load, like a chandelier), and then you can control each light bulb in that chandelier on its own. For instance, you could assign a certain frequency to each light bulb and create a light show that will be synchronized to the music playing in your Android phone. Crazy, but might be useful for those Christmas light displays. Again, an edge case.

Any ideas why they make such a big deal of those smart bulbs?
 
my guess is it's probably
1. the most basic HA component you could dive into; or most prevalent whichever way you want to say it. more lights in a house than say hvac units, garage door, irrigation, pools, etc.
2. easiest thing to come up with a prototype for. the light bulb is pretty much the same thing for the last 100 years or so and is a dead simple concept (now that it has been around so long lol)
Any ideas why they make such a big deal of those smart bulbs?
 
other cases may be a lamp that's not plugged into a wall controllable outlet, any drawstring type light (like you might find in a garage, basement, etc.). maybe this could be expanded to street lamps which again don't have switches on a wall per se.

i mean they probably just broke it down to the most basic component and went with that. is it the right choice? overall probably not for the same reasons you describe but using this method any light socket that can hold that bulb can now be controllable regardless of voltage, location, type of switch control, etc.

in the end they will probably come out with android controllable switches also as an option. they probably just wanted to show something different than typical HA to try to make it easier to brake into the market. people like shiny new things. they are coming up with something that has been around for a long time now so they have to try to put some kind of spin on it to get any serious attention.

also remember they are doing this for more than just lighting control so if they can develop a small chip that can be put into any device then they don't care if it is a light bulb, your washing machine/dryer, dish washer, oven, etc. it is a generic chip/tool for their HA. so this light bulb again was a simple prototype to show the capabilities of the same thing in other devices using a Universal method.

Ok, there might be some edge cases where you don't have a physical switch for a load (in this case it's like having a Smarthome's InlineLinc, or X10's Socket Rocket). But that is an edge case.

I can think of some other crazy ways of using those smart bulbs. For example, create a scene that turns a series of smart lights ON at the switch (one load, like a chandelier), and then you can control each light bulb in that chandelier on its own. For instance, you could assign a certain frequency to each light bulb and create a light show that will be synchronized to the music playing in your Android phone. Crazy, but might be useful for those Christmas light displays. Again, an edge case.
 
If you want to hit the mass market, you need something that the masses can do. Most people would never touch the wiring in their house, but pretty much everyone will unscrew a light bulb.
 
Yes, I guess the light bulb would be something that non-DIY crowd would be able to understand easily. And it maybe useful for commercial applications as well (like street lights that get brighter as Android user passes by) :rofl:

But for us (seasoned DIY-ers ;) ) I still think it is only as good as a prototype.
 
Back
Top