+1 to a bunch of things in this thread.
I started out with this project because I'd been wanting to build a DVR server for a long time, and I was waiting for something like the InfiniTV 4 to come along (WAF was non-existent if we couldn't use the thing with cable). I started with a 360 receiver, but it had habitual network problems, so I plopped the cash down for an Echo.
95% of the time, it's great, and all-in-all, it performs better than the STBs I got from Verizon, so it's an acceptable replacement (and eventually a financial break-even without having to pay STB rental fees). That said, the most important program on TV for my wife for all of 2013 is Game of Thrones, and GoT is when it tends to foul up the most. Especially in motion-scenes. If the camera is largely still and people aren't moving and just talking, it tends to work fine, but once the background starts to move, the frame desyncing becomes quite apparent.
The wife is putting up with it for now, and in two months, it won't be nearly as prominent as it has been in the last couple of weeks, but still, this has been frustrating. If I got a 360 that didn't suffer from the flow control issues and didn't sound like a vacuum cleaner, the Echo would probably go in a drawer somewhere.
Android support is a play-thing. Unless this is going to fix the problems we have now, Ceton really should just put it on ice and get the decoding problems worked out.
[Moderator note: comments regarding static IP for Echo have been moved to the appropriate thread--> http://www.thegreenbutton.tv/forums/vie ... 552#p49552]