SSDP M-SEARCH

Archived
1

I am not getting response to SSDP requests on my network to find roku devices:


$ cat ssdp.txt
M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
MAN: "ssdp:discover"
ST: roku:ecp

$ nc 239.255.255.255 1900 < ssdp.txt

does anyone know if it works for them? I have ROKU XD|S roku device. Am I missing something?

2

It works fine for me. Two possible reasons you aren’t seeing a response:

  • the ssdp multicast ip address is 239.255.255.250. You used 239.255.255.255

  • From the External Control Guide, “If you view the response via wireshark and filter on port 1900 you can see the Roku’s response. Ncat has trouble receiving multicast traffic so viewing the response using ncat does not work.”

3

“vsrivastav” wrote:
I am not getting response to SSDP requests on my network to find roku devices:


$ cat ssdp.txt
M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
MAN: "ssdp:discover"
ST: roku:ecp

$ nc 239.255.255.255 1900 < ssdp.txt

does anyone know if it works for them? I have ROKU XD|S roku device. Am I missing something?

I just tried this in c# and got it to work. Sometimes, like 2 out of 10 times this times out…but overall ok. I am still trying to do a “POST”…

fun…fun…

4

“RokuChris” wrote:
It works fine for me. Two possible reasons you aren’t seeing a response:

  • the ssdp multicast ip address is 239.255.255.250. You used 239.255.255.255

  • From the External Control Guide, “If you view the response via wireshark and filter on port 1900 you can see the Roku’s response. Ncat has trouble receiving multicast traffic so viewing the response using ncat does not work.”
    Has the “WiFi Bug” been fixed which prevented reliable discovery for players using WiFi? If so, what release was this fixed in?

5

“pirey4” wrote:

“RokuChris” wrote:
It works fine for me. Two possible reasons you aren’t seeing a response:

  • the ssdp multicast ip address is 239.255.255.250. You used 239.255.255.255

  • From the External Control Guide, “If you view the response via wireshark and filter on port 1900 you can see the Roku’s response. Ncat has trouble receiving multicast traffic so viewing the response using ncat does not work.”
    Has the “WiFi Bug” been fixed which prevented reliable discovery for players using WiFi? If so, what release was this fixed in?

I guess not. I loop my search 10 times on a button click each search a second apart and it usually takes around 30 attempts before a fix.

6

The external control api ‘WiFi Bug’ is fixed in v2.8.

–Kevin

7

I am unable to get it working on my Roku, which is connected using wifi. I get several responses from my router if I do search type “ST: ssdp:all” , instead of “ST: roku:ecp”, however no response from roku.

It is not working on Roku XD|S
Checked the version:

software version 2.8 build 1150
hardware 2100X

I am using wireshark with filtering on udp.port == 1900 as suggested earlier in the post.
Roku XD|S