"S4Tech" wrote:
Yes, my IP address does start with "192.." so that must be the problem. Well then, I don't really understand the benefit of the External Control Protocol if external web applications can't communicate with the Roku device without jumping through a lot of hoops. I guess I will have to rethink the design on the web application I am trying to build.
Generally, ECP is used for applications that are external to the Roku as opposed to external to the network. For example, remote control smartphone applications used to control a Roku that is on the same local network. Web applications should be able to communicate with a Roku using ECP without "jumping through a lot of hoops" if they are on the same local network as the Roku.
Even though your web application is hosted remotely, is it being run (from a web browser) by a device on the Roku's local network, or are you trying to access your Roku from a remote location?
There's nothing to stop you using ECP to control a Roku on a different network. However, the network's firewall has to be configured to allow that. By default, this is not usually the case otherwise anyone, anywhere in the world, would have access to a user's Roku. Many routers have a port forwarding option you can use to forward remote requests for a specific port (8060) to a specific local device (192...).