@cyphers wrote:
It's got to be a typo. An entire ecosystem across ~12 years has been built on ECP, and the very same page then goes on to describe ECP and then provide a literal Android app as sample code. That sentence just makes no sense and directly conflicts with everything below it. Roku would be castrating themselves to remove ECP.
Exactly this. The notice says that sending ECP commands from a channel is what's been discontinued, not ECP itself - which is literally the RESTful API meant for controlling Roku devices over a local area network. When they mention "3rd-party platforms", it's not crystal clear, but given the full context, they're most likely referring to remote 3rd-party platforms over the internet. 3rd-party platforms is not referring to other devices on the same local area network - that's not what a platform is. A 3rd party platform would be something like Amazon's Alexa where the control channel is coming from the internet and not from another local device on the same LAN (and Alexa would actually translate something like that within an Alexa skill on the device and still send the ECP command from the local device on the LAN rather than from the internet directly).
But since Roku has responded, we'll just wait and see what their engineers say after they've investigated why this quit working without them pushing a new firmware disabling it. This was almost certainly unintentional.
