I’m aware this is a long shot, but I wanted to do my due dilegence. Hoping this reaches a Roku Engineer. I have opened a support ticket with Roku Customer Support for an answer to my inquiry, but my questions along with supplied information/documentation have been ignored with a canned response of “it won’t work/not meant for non-home networks” without any acknowledgement of the syntax question. I’m a wireless network engineer at a university and understand all too well the “futility/struggles” of supporting devices typically used in home environments. With that said, we have made amazing progress in the past year to give student’s the “Home Experience” in the residence halls. Student’s are able to register and connect their Rokus, Apple TVs, ChromeCasts, Google Home Minis, Amazon Echos, etc to the wireless network and utilize them as they were at home through the use of a software module with our wireless vendor called “AirGroup” from HPE/Aruba – an mDNS/SSDP proxy/gateway -
https://community.arubanetworks.com/t5/Controller-Based-WLANs/What-are-the-AirGroup-service-IDs-requ... - which was also necessary for the _googlezone mDNS service which is needed for multi-room control.
However, the one application we have been unable to get discovery working with AirGroup has been the Roku Remote control app.
We performed packet-captures and worked with our vendor HPE Aruba and their developers informed us that the service “Roku:ECP” is invalid syntax with uPnP Architecture 1.0. I’ve included the response from our vendor (from last year during our initial testing – I’m finally taking the time to pursue this further again as more and more students are taking advantage of our services and this has been the one last piece asked of us that isn’t capable yet): Good Morning. Thank you for your patience. Our development team informed that the service (Roku:ecp) used by the Roku devices are not currently supported in Aruba OS. Aruba OS is compliant with https://www.ietf.org/rfc/rfc2141.txt - does specify that the URN must contain the pre-fix “urn:” – something that I immediately noticed while debugging the AirGroup Service for suppressed queries (every other one contained a prefix of uuid or urn) - but not the roku:ecp.[/font]
My question I was trying to get answer was if Roku agreed that they're using invalid syntax in regards to the uPnp Architecture 1.0, why they weren't following that syntax, and if it would be possible to get it compliant with the uPnP Architecture so that we would be able to AirGroup the service to give students this capability. For now they use the IP Address (which I'm thankful that Roku added that feature and the "Dorm Mode/Captive Portal" feature years ago - but it's the last single piece that isn't working - and with our IP Address lease time can be - IP Addresses can periodically change on the students. It would also be beneficial as enterprise vendors such as HPE Aruba and Cisco are recognizing this need, implementating software solutions, as other universities are running into this same problem with the Roku being singled out - http://community.arubanetworks.com/t5/Wireless-Access/Roku-streaming-stick-Not-registering-with-AirG...
I'm not expecting much will come from this. I tried the general support route with all the information I provided above - but it was immediately discarded/ignored with "public network - too many ip addresses - it's designed for home use" even though my specific repeated inquiry was about the "Syntax/Architecture" and reference that AirGroup gets around that limitation by building a "Virtual Home Discovery Domain" - which is why the YouTube App on the Roku works wonderful with casting from smartphones, controlling Google Home Mini music from smartphone music app, and controlling Apple TV from Apple HomePod works as well.
Thank you for your time.
