Is esp8266ssdp/ssdp working?

[holgerlembke]

Hi.

If I take the esp8266ssdp/ssdp example (just fill in ssid/pwd), my esp does not show up in the devices list.

I have a standard Windows 10 Pro network, no firewall, no additional software installed.

Could some users please verfiy that the example is really working?

Thanks!

[holgerlembke]

adding SSDP.setDeviceType("upnp:rootdevice"); and it starts working.

[me-no-dev]

is this documented somewhere? I mean the device type? When I was reading the specs I was left with the impression that urn:schemas-upnp-org:device:Basic:1 is the one to be used

[holgerlembke]

I don't know.

Reading chapter "Device available - NOTIFY with ssdp:alive" of UPnP-arch-DeviceArchitecture-v2.0-20150220.pdf from https://openconnectivity.org/upnp/specifications it sounds like that is the way its done.

And because it works...

[me-no-dev]

it was working with the schema above as well back when I was writing it.
Reading about it here does not hint on any problem why the info would not display.

[holgerlembke]

I can only state what I observe on this Win10 box...

[me-no-dev]

that's cool. I have Win7 and Win10 virtual machines here and will take a look at the result.

[holgerlembke]

In the other news: right click on the device and requesting the properties does not work, too.

[kiwiwarwick]

Thanks for the info, I a had an issue in getting SSDP working (using the included example), after I added the line - SSDP.setDeviceType("upnp:rootdevice"); then it worked.

But like holgerlembke mentioned, the "Properties" option in Windows 10 doesn't work for this.

[azevedo-manuel]

I've compared some captures with other devices and I see at least there are three NOTIFY messages broadcast to the multicast address, instead of only one like the ESP8266SSDP library.

On a first look, only the NT header field is different on each message:
NT: upnp:root-device
NT: uuid:1406a136-e5ff-11e5-9730-64002d01c3f4
NT: urn:schemas-upnp-org:device:Basic:1

But looks like it might be enough for Windows 10 to complain.

In my case, double-clicking the icon opens the device's webpage, so, this might just as well do.

[saytinh]

I still can not view ESP8266 on Network of Windows after added SSDP.setDeviceType("upnp:rootdevice"); to SSDP.ino example. I used Windows 10 pro. Can you help me. Thanks

[azevedo-manuel]

Saytinh, it works. Be sure you apply it before SSDP.begin(); and that Network Discovery is enabled in your Windows 10.

[saytinh]

Yes, I added before SSDP.begin(); SSDP service is running; but NOT show ESP on network devices with list.
is there possible that my wifi router is not supported SSDP protocol?

[azevedo-manuel]

No clue, but I don't think so. SSDP uses 239.255.255.250 multicast address. If you're connected to the same subnet (computer and ESP are on the same subnet) then the router should have no impact on it, unless it's actively filtering multicast. Anyway, this "issue" forum is for reporting bugs, not troubleshooting particular cases.

[saytinh]

Hi azevedo-manuel,

I already can view ESP on the network list after adding SSDP.setDeviceType("upnp:rootdevice"); But clicking on the property of ESP there are still error like that:

Can you help me?

[luc-github]

Just to complete @holgerlembke finding, as before SSDP was working, here the commit which removed the upnp:root-device :c8d855c

About window 10 issue I can reproduce with some others device like my NAS Synology but not with my Internet access gateway - Is there a way to get description.xml or equivalent from other devices to compare with ESP one ? it may help to understand why properties work under win7 but not win10