Introduction

Many Upnp devices are not fully compliant with the Upnp Specification.

It is our belief that the whole development community benefits from reasonably rigorous adherence to standards like Upnp.

This page contains a list of currently known infringements of the Upnp and Upnp AV specifications.

If you find a device that doesn't adhere to the UPnP standards let us know.

Linn Auskerry DS Devices

  • These devices contain a Upnp AV 1.0 MediaRenderer in an embedded Upnp device. (See "MediaRenderer:1 Device Template Version 1.01", p.5)

Linn Bute DS Devices

  • These devices do not supply a channel attribute in the LastChanged event XML for volume or mute events. (See RenderingControl:1 Service Template Version 1.01 p.63)

Sonos Zone Player ZP80

  • This device contains a Upnp AV 1.0 MediaRenderer in an embedded Upnp device. (See "MediaRenderer:1 Device Template Version 1.01", p.5)
  • This device contains a Upnp AV 1.0 MediaServer in an embedded Upnp device. (See "MediaServer:1 Device Template Version 1.01", p.5)

Sonos Zone Bridge 100

  • This device contains a Upnp AV 1.0 MediaRenderer in an embedded Upnp device. (See "MediaRenderer:1 Device Template Version 1.01", p.5)
  • This device contains a Upnp AV 1.0 MediaServer in an embedded Upnp device. (See "MediaServer:1 Device Template Version 1.01", p.5)

D-Link Media Server V1.05eu

  • SOAP responses do not include a trailing forward slash at the end of xmlns:upnp="urn:schemas-upnp-org:metadata-1-0/upnp"
  • SOAP responses do not include a trailing forward slash at the end of xmlns="urn:schemas-upnp-org:metadata-1-0/DIDL-Lite"

Media Tomb

  • Uses a Cache Control Max Age of 180 seconds for its SSDP upnp:alive notifications. The minimum value for this is 1800 seconds (See Upnp Device Architecture 1.0 p.16)

DigiFi

  • The Browse action of the ContentDirectory service will only return, up to a maximum of, 10 entries in a single call. (See ContentDirectory:1 Service Template Version 1.01 p.23)

EyeConnect

  • The action Browse of the ContentDirectory service returns incorrect results when an outstanding Browse is still in progress.

Superna Systems

  • All actions performed on AVTransport, RenderingControl, and ConnectionManager services respond with erroneous XML. The SOAP body contains an element that represents the action response, but this element is consistently in the wrong namespace. For instance, the response to an AVTransport Pause action should contain a <PauseResponse> element in the "urn:schemas-upnp-org:service:AVTransport:1" namespace. However, the <PauseResponse> element is actually in the "AVTransport" namespace. (See Upnp Device Architecture 1.0 p.50)

Twonky Media Server

  • In the presence of two or more network cards, the Twonky Media Server responds to M-SEARCH requests by advertising all the TCP/IP addresses that it has on all of the network interface cards. It should only advertise the TCP/IP address that it has on the network interface card from which it received the M-SEARCH request. This bug can cause UPnP Control Point software to hang waiting for a response from an inaccessible TCP/IP address.

Fuppes Media Server

  • Invalid device description XML. The XML describing an icon has two "height" nodes, as the "depth" node has been mistakenly labeled "height".
  • Invalid SCPDURL response for the "urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1" service.

TVersity

  • In the presence of more than one network interface, TVersity becomes confused about its IP address. It appears to advertise itself on all network interfaces with the IP-address that it was last thinking of, thus causing control point software to hang waiting for a response from an inaccessible location.