FAQ  •  Register  •  Login

Unable to detect an UPnP device

<<

Talium

Serviio newbie

Posts: 3

Joined: Wed Jan 07, 2015 7:04 pm

Post Fri Jan 09, 2015 12:36 pm

Unable to detect an UPnP device

Hi all,

I am currently trying to write a new transcoding profile for the Livebox, a very well known set top box used in France, and to modify the existing Samsung D-series TV profile, because my UE40D5700 isn't automatically detected by Serviio.

I use DeviceSpy as explained here : http://forum.serviio.org/viewtopic.php?f=5&t=19.

Here are the device description'x xml files given by DeviceSpy :

For the UE40D5700

  Code:
  <device>
    <deviceType>urn:schemas-upnp-org:device:MediaRenderer:1</deviceType>
   
    <df:X_deviceCategory>Display.TV.LCD Multimedia.DMR</df:X_deviceCategory>
    <dlna:X_DLNADOC xmlns:dlna="urn:schemas-dlna-org:device-1-0">DMR-1.50</dlna:X_DLNADOC>
    <friendlyName>TV salon</friendlyName>
    <manufacturer>Samsung Electronics</manufacturer>
    <manufacturerURL>http://www.samsung.com/sec</manufacturerURL>
    <modelDescription>Samsung TV DMR</modelDescription>
    <modelName>UE40D5700</modelName>
    <modelNumber>AllShare1.0</modelNumber>
    <modelURL>http://www.samsung.com/sec</modelURL>
    <serialNumber>20081224DMR</serialNumber>
    <UDN>uuid:342638c0-3736-1706-04a3-142f3a887bc7</UDN>
    <sec:deviceID>RLCKF5GZCVDTA</sec:deviceID>
    <iconList>

...


And the infos directly given by DeviceSpy :

Image

For the Livebox

  Code:
<?xml version="1.0" encoding="UTF-8"?>
<root xmlns="urn:schemas-upnp-org:device-1-0">
  <specVersion>
    <major>1</major>
    <minor>0</minor>
  </specVersion>
  <device>
    <deviceType>urn:schemas-upnp-org:device:Basic:1</deviceType>
    <friendlyName>décodeur TV d'Orange</friendlyName>
    <manufacturer>SAGEM</manufacturer>
    <modelName>IHD92</modelName>
    <UDN>uuid:1d639bb6-23b7-11e2-a021-7c03d83b9e40</UDN>
    <serviceList>
      <service>
        <serviceType>urn:schemas-orange-com:service:X_OrangeSTBRemoteControl:1</serviceType>
        <serviceId>urn:orange-com:serviceId:X_OrangeSTBRemoteControl</serviceId>
        <SCPDURL>/X_OrangeSTBRemoteControlDescription.xml</SCPDURL>
        <controlURL>/remoteControl/cmd</controlURL>
        <eventSubURL>/remoteControl/notifyEvent</eventSubURL>
     </service>
    </serviceList>
  </device>
</root>


My problem is that Serviio does not automatically detect the type of device he is dealing with, I have tried simply things for the moment, like this in the profile.xml :

For the Samsung TV

  Code:
      <Detection>
         <UPnPSearch>                  
            <ModelName>UE40D5700</ModelName>
         </UPnPSearch>


For the Livebox

  Code:
      <Detection>
         <UPnPSearch>                  
            <ModelName>IHD92</ModelName>
         </UPnPSearch>


I also tried using <FriendlyName>TV salon</FriendlyName>, or <FriendlyName>décodeur TV d'Orange</FriendlyName>. Wasn't better.
At one point I thought it was because the Device Description uses <friendlyName> but Serviio requires <FriendlyName> insted (with a capital F), but I don't know if this is relevant.

I've also tried to look at the serviio.log, in DEBUG mode, but I didn't found anything (the log is available here : http://talium.free.fr/Upload/serviio.log).

Does anyone have a clue on how to make this recognition work ?

Thanks for any useful tip !
<<

Illico

User avatar

DLNA master

Posts: 4646

Joined: Fri Jul 23, 2010 8:08 am

Location: France

Post Fri Jan 09, 2015 12:55 pm

Re: Unable to detect an UPnP device

I have done some tests, few years ago : viewtopic.php?f=5&t=6288&p=65519&hilit=livebox#p45442
<<

Talium

Serviio newbie

Posts: 3

Joined: Wed Jan 07, 2015 7:04 pm

Post Fri Jan 09, 2015 1:27 pm

Re: Unable to detect an UPnP device

Yes, I already saw your post, thanks !
But it was about the old Livebox (the white one), I am trying to write a profile for the new one (Livebox Play, the dark one, and I could add that the new Polaris interface released in December added some new supported video format, sadly not documented). Therefore the device detection fields aren't the same.

My problem is not about the transcoding or supported formats, but - for the moment - only about the automatic detection of the device (why the Model Name or Friendly Name for instance aren't recognized by Serviio).
<<

Illico

User avatar

DLNA master

Posts: 4646

Joined: Fri Jul 23, 2010 8:08 am

Location: France

Post Fri Jan 09, 2015 2:30 pm

Re: Unable to detect an UPnP device

For detection, do you try with HttpHeaders
  Code:
      <Detection>
         <HttpHeaders>
            <User-Agent>.*SOMETHING_HERE.*</User-Agent>
         </HttpHeaders>
      </Detection>


What are the IP address of your devices?
<<

Talium

Serviio newbie

Posts: 3

Joined: Wed Jan 07, 2015 7:04 pm

Post Wed Jan 14, 2015 9:49 pm

Re: Unable to detect an UPnP device

sorry for replying only now, I was in a business trip ...

I spent some time trying to figure out a solution. I solved my problem for the Samsung television, the Serviio's default detection pattern was wrong (it was using the friendly name field, which depends on your device name configured in the television configuration, so there is no way to have a common pattern this way), I used this instead :

  Code:
         <UPnPSearch>                  
            <ModelName>UE[0-9]{2}(C|D).*</ModelName>
            <ModelNumber>(1\.0)|(AllShare1\.0)</ModelNumber>
            <Manufacturer>Samsung Electronics</Manufacturer>
         </UPnPSearch>


But I still have some problem with the Livebox. I have tried your solution with HttpHeaders, and it works, sometimes (I can't understand why it doesn't work always), using <User-Agent>.*POSIX SAH DLNA Stack.*</User-Agent>.
But this is too generic, there are numerous different Livebox models, with different format support. And of course, I have one model, my girlfriend another one, as my parents ... :)
I don't understand why Devicespy can detect all the fields like Model Name or Manufacturer :

Image

but Serviio can't.
In the logs I see some requests concerning the Livebox (IP 192.168.0.3) like :

  Code:
DEBUG [ServiioHttpService] Incoming request from /192.168.0.3:51013: GET /deviceDescription/554eb7ab-ec62-334b-b534-7fd928109396 HTTP/1.1, headers = [Host: 192.168.0.78:8895,User-Agent: POSIX SAH DLNA Stack/1.0 UPnP/1.0 DLNADOC/1.50]]
DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaServer:1 from address /192.168.0.3:51014s


Oddly, on another device (a Raspberry runnin Openelec 5.0, using Kodi 14, IP 192.168.0.253), I can see some betters things in the logs :

  Code:
DEBUG [RendererSearchSender$RendererSearchWorker] Received search response: location: http://192.168.0.253:2039/, st: urn:schemas-upnp-org:device:MediaRenderer:1


And the device desciption's xml obtained with URL http://192.168.0.253:2039/ seems good :

  Code:
<root configId="1123621"><specVersion><major>1</major><minor>1</minor></specVersion><device><deviceType>urn:schemas-upnp-org:device:MediaRenderer:1</deviceType><friendlyName>FanghXBMC</friendlyName><manufacturer>XBMC Foundation</manufacturer><manufacturerURL>http://kodi.tv/</manufacturerURL><modelDescription>Kodi - Media Renderer</modelDescription><modelName>Kodi</modelName><modelNumber>14.0 Git:ad747d9</modelNumber><modelURL>http://kodi.tv/</modelURL><UDN>uuid:38bdad95-0d4c-27f9-5270-d0da0378bcce</UDN><presentationURL>http://192.168.0.253/</presentationURL><dlna:X_DLNADOC>DMR-1.50</dlna:X_DLNADOC>

[...]


but I can't auto detect it, using ModelName, or Manufacturer, or even <User-Agent>.*Kodi.*</User-Agent>.

So for me it's like Serviio can't always retrieve the UPnP informations ... Any thought ?

Return to Transcoding

Who is online

Users browsing this forum: No registered users and 42 guests

Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Designed by ST Software for PTF.