Thanks for the explanation. Your points are all very valid.
One thing I'm a little unclear on and maybe it's because I either didn't explain it well or I do not understand the underlying methodology. I didn't mean to imply the reverse engineering of the Hue protocols for this solution. Aren't the 4 current "Connected Home" devices that are supported by the echo using the Lighting API? Would a separate "Service" running locally on the private network be able to bridge the gap between the Echo and Indigo without impacting the security of indigo? This wouldn't need to use the protocols being used by Hue, SmartThings, Insteon or Wink. I was under the impression that the echo talks to these hubs directly using the Lighting API and then the only thing that would potentially break would be the connectivity between the "Service" app (software hub so to speak) and Indigo. I would think this would be no more fragile then any of the other Connected Home devices in that the only thing that could break it would be a change to the Lighting API.
Like I said at the beginning. I probably do not have a firm enough grasp on the technology being used with the Connected Home devices and the Lighting API.
Jeff