Android @ Home

Discussion in 'General Discussion' started by nickrusanov, May 11, 2011.

  1. nickrusanov

    nickrusanov

    Joined:
    Aug 5, 2004
    Messages:
    308
    Likes Received:
    0
    Location:
    russia
    nickrusanov, May 11, 2011
    #1
  2. nickrusanov

    kjayakumar

    Joined:
    Oct 27, 2008
    Messages:
    448
    Likes Received:
    0
    Hi Nick,

    Yes, it is quite exciting. It will be interesting once Google shares what exactly this framework is. If it is what we think it is, ie: a TCP/IP API with which automation devices can talk to handsets, then it should be quite feasible to interface that to C-Bus through products like the Colour Touch and Wiser.
     
    kjayakumar, May 12, 2011
    #2
  3. nickrusanov

    nickrusanov

    Joined:
    Aug 5, 2004
    Messages:
    308
    Likes Received:
    0
    Location:
    russia
    I think it's a wrong way - to see what will happen and then get into the trend.

    Schneider should come to Google and talk about C-Bus to be included by standard into the package

    Or it will be as always - all others are supported, C-Bus on sideways =(
     
    nickrusanov, May 12, 2011
    #3
  4. nickrusanov

    kjayakumar

    Joined:
    Oct 27, 2008
    Messages:
    448
    Likes Received:
    0
    I understand what you are saying. But I think it is not fair to imply that Schneider/Clipsal is just sitting back and following trends set by other people. In fact, I would not be at all surprised if Google's engineers had seen what Schneider/Clipsal is doing with products like CTC/Wiser/PICED and thought, hey, that's a good idea, why don't we "invent" the wheel, weld it to Google's transmission and call it Android@Home.
     
    kjayakumar, May 16, 2011
    #4
Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.