Roku Developer Program

[TheEndless]

"RokuJoel" wrote:
A bug report was filed today.

No bug existed on file for this one already?? It's been a known/reported issue with the wireless interface since before the 2.9 firmware. Phil Irey (developer of DVPRemote) and I discovered it and reported it back in November of last year...

[ajb2011]

The Endless - I think it was your original post that gave me the workaround of a soft reset, so many thanks. I am just glad a bug is logged now, although I'd love to know the turnaround on somethng like that, if it is, in fact something Roku thinks should be fixed.

RokuJoel, are you referring to the case when the IP is wrong, that I just send it an http request to verify? The problem with that is, on my home network that IP is not associated with any device anymore. I also do not want to implement my own network scanning to try and find the device. I'd prefer SSDP to work as advertised, but I appreciate the suggstion.

[EnTerr]

"RokuJoel" wrote:

if you make an http request (with a timeout of course so your process doesn't get hung up waiting) to the port, you should be able to detect if it is a Roku pretty easily, by the resulting XML data, specifically the FriendlyName tag. I think some of the iPhone Roku remote apps might use this method, or something similar, as an alternative to SSDP.
- Joel

Opening hundreds of hanging TCP connections is a horrible idea, please do not suggest it!

[EnTerr]

"ajb2011" wrote:
If I soft reset my Roku, the SSDP starts to give me the correct IP again. Is this a known bug?

Yes, it as known, long-standing bug - to me at least and i bet to every single remote app that uses ECP discovery. The SSDP implementation is atrocious, i think i lamented that in couple of postings already. Roku did not pay attention so far but since they released iPhone remote last week, probably will now - check that many of the negative reviews are because of this.

You don't need to reset the player for a fix - instead you can:
a) power-cycle it (unplug power for couple of seconds) or
b) (with physical remote) repeat the network setup again - that does it

[destruk]

"EnTerr" wrote:

"RokuJoel" wrote:

if you make an http request (with a timeout of course so your process doesn't get hung up waiting) to the port, you should be able to detect if it is a Roku pretty easily, by the resulting XML data, specifically the FriendlyName tag. I think some of the iPhone Roku remote apps might use this method, or something similar, as an alternative to SSDP.
- Joel

Opening hundreds of hanging TCP connections is a horrible idea, please do not suggest it!

I think the idea is to ping all the IPs to see what replies - and then open the TCP connection between those addresses that are in use - in most home LANs you're talking about fewer than 10 devices. The roku always replies to ICMP.

[EnTerr]

"destruk" wrote:

"EnTerr" wrote:
Opening hundreds of hanging TCP connections is a horrible idea, please do not suggest it!

I think the idea is to ping all the IPs to see what replies - and then open the TCP connection between those addresses that are in use - in most home LANs you're talking about fewer than 10 devices. The roku always replies to ICMP.

Check the thread above, RokuJoel said:

"RokuJoel" wrote:
... if the connection fails, you *could* try the ugly but-usually-workable brute-force method: attempt to connect in succession to every ip address on the subnet on port 8060.

But i hear you on the icmp ping idea. That will work - that is unless some router has automated protection from network scans (i.e. mass icmp trips blockage)

[destruk]

ok, I sure hope they fix it - that would be easiest. This makes me wonder what other issues have been mentioned that aren't 'officially on a bug list' ?

[EnTerr]

"destruk" wrote:
ok, I sure hope they fix it - that would be easiest. This makes me wonder what other issues have been mentioned that aren't 'officially on a bug list' ?

If I were hired by Roku to work it out with the developers (which seems they did... at last!), I'd mine this forum for ideas, dream and suggestions - it is quite fertile. On the other hand, maybe each of us should summarize their desires/misgivings/ideas and email them upstream - as Tom Markworth suggested in a comment here: http://blog.roku.com/blog/2011/12/15/in ... -388362030

And speaking about bitching, WTF is the SDK for this year's firmware, "rOS" 3.x and 4.x?!? DevHome still shows 2.9 as the latest. Are we waiting on Santa Clause to bring updated SDK? The old man better ship it overnight, 'cause the weekend is coming

[TheEndless]

"EnTerr" wrote:
And speaking about bitching, WTF is the SDK for this year's firmware, "rOS" 3.x and 4.x?!? DevHome still shows 2.9 as the latest. Are we waiting on Santa Clause to bring updated SDK? The old man better ship it overnight, 'cause the weekend is coming

According to Joel earlier today (viewtopic.php?f=34&t=46212#p313444), they're working on it right now, so hopefully that means soon.

[sa2000]

Interesting that over 10 years later this is still happening on a Now TV roku stick

Model 3801UK running firmware 10.5.3

No real impact - other than wasting time investigating why i was seeing a lot of http connection errors in log files for an IP address that does not exist on my network and no traffic from it when checking with wireshark !

After some time investigating tracked it to this problem where an IP address change does not get reflected in the SSDP Search response !

and checking the response from the real IP address (http://192.168.68.111:8060) gives

<root xmlns="urn:schemas-upnp-org:device-1-0">
	<specVersion>
		<major>1</major>
		<minor>0</minor>
	</specVersion>
	<device>
		<deviceType>urn:roku-com:device:player:1-0</deviceType>
		<friendlyName>Now TV - YD008Nxxxxxx</friendlyName>
		<manufacturer>Roku</manufacturer>
		<manufacturerURL>http://www.roku.com/</manufacturerURL>
		<modelDescription>Roku Streaming Player Network Media</modelDescription>
		<modelName>3801UK</modelName>
		<modelNumber>3801UK</modelNumber>
		<modelURL>http://www.roku.com/</modelURL>
		<serialNumber>YD008Nxxxxxx</serialNumber>
		<UDN>uuid:29500008-780c-109e-8048-105932e15915</UDN>
		<iconList>
			<icon>
				<mimetype>image/png</mimetype>
				<width>360</width>
				<height>219</height>
				<depth>8</depth>
				<url>device-image.png</url>
			</icon>
		</iconList>
		<serviceList>
			<service>
				<serviceType>urn:roku-com:service:ecp:1</serviceType>
				<serviceId>urn:roku-com:serviceId:ecp1-0</serviceId>
				<controlURL/>
				<eventSubURL/>
				<SCPDURL>ecp_SCPD.xml</SCPDURL>
			</service>
			<service>
				<serviceType>urn:dial-multiscreen-org:service:dial:1</serviceType>
				<serviceId>urn:dial-multiscreen-org:serviceId:dial1-0</serviceId>
				<controlURL/>
				<eventSubURL/>
				<SCPDURL>dial_SCPD.xml</SCPDURL>
			</service>
		</serviceList>
	</device>
</root>