cjconover / remoku Goto Github PK

Support discovery of Rokus on local network.  Javascript has no access to the 
discovery mechanism employed by Roku, SSDP, so another method is required.  One 
way to accomplish this is to sequentially request a specific resource known to 
exist on the Roku webserver sequentially trying each IP address in a subnet. 
e.g:
GET http://192.168.0.1:8060/query/apps
GET http://192.168.0.2:8060/query/apps
GET http://192.168.0.3:8060/query/apps

If a Roku exists at an address it will quickly respond with the list of apps.  
If it does not, the request will timeout after some period.  A script could 
check the result of loading an iframe after, for instance 500ms, and check ~120 
addresses a minute. For most home networks, this technique *could* be 'good 
enough'.

Replace html buttons with graphical interface from Roku Remote for Google 
Chrome by Ben Galliart. Add a mode switch to options to support use of either 
interface.

What steps will reproduce the problem?
1. Use the directional arrows to navigate the Roku UI.

What is the expected output? What do you see instead?
The Roku should react to network remote control in the same manner as IR remote 
control.  Instead, it occasionally will receive a keydown command without 
receiving a subsequent keyup command. This may be caused by network conditions 
and also by Remoku code deficiencies.

Possible fix(es) and/or workarounds:
It is possible to capture the response from the Roku after it has received a 
command, by checking if the iframe has loaded.  So the script could wait until 
the Roku acknowledges receipt of a command before sending another.

The keypress command is equivalent to a keydown followed by a keyup.  So an 
optional mode could be enabled that always uses keypress.  This would have an 
undesirable side-effect of forcing users to repeatedly 'click' the button to 
navigate long lists.

Remoku should allow channel launching via the
http://roku:8060/query/apps
and
http://roku:8060/launch/appid
URLs