Dynamic create of profiles

[anderbytes 139]

I've been having some trouble creating specific profiles in my network.

My idea was to create one specific profile for each TV or device.

 

I've been trying to use the "Identification" fields to restrict and point which TV can take that profile, but it's been useless so far, like they're being ignored. In fields as "serial" or "model" I can type any sh** and still me TV gets the profile. All of the TVs do this.

 

 

Probably there's a specific combination and filling of fields that pinpoints each TV, but it's impossible to know what it is.

 

My question is: "Is it possible to Emby to auto-create a profile based on a existing device in the network?"

As Emby understand better the parameters exchanged with the devices, probably he is the best to say which fields has to be filled so a profile is accurately created.

 

 

I hope I explained myself correctly.

Thanks.

[marc_al 5]

 

 

Hello,

 

You are right, the Identification is probably the most difficult thing I have ever seen with Emby (For one TV, I have used Plex to see the the User-Agent because when you have 8-9 different DLNA clients it becomes really hard).

 

To be able to identify a machine (for the profile), you should enable the Debug log (and the DLNA debug log too).

After that you will need two parts for a profile to be accepted (at least it was the case 6 month ago. Perhaps now it is simpler)

 

You will need to fill one part with the http header (the USER-AGENT)

and another part with the fields (Constructer, URL (any one of them))

 

Please pay attention that the The USER-AGENT is case sensitive.

For example, on the WD TV Live, you must write

User-Agent

But for Denon, you must write USER-AGENT

 

You should look at in the log to see what you need.

Sometimes the answer will be different for the same DLNA client

For example,

One Medion TV returns for the User-Agent sometimes

MEDION TV DLNADOC/1.50

And sometimes

Microsoft-DLNA DLNADOC/1.50

 

As you can put more than one condition in the HTTP header, there is no problem (but if you don't know it you will have problems).

 

Something that is really missing in Emby would be a log analyser (or something like that). For example, when the default profile is used, Emby should tell Using Default profile for session XXX.

And all the given parameters of the client are listed after that (

so the log would tell Unknown...

User-Agent XXXXXX

URL of the product YYYY...

)

 

 

Personally, I use Plex to identify the User-Agent (it is simpler).

Marc

 

 

[anderbytes 139]

Thanks, I'll try that.

 

I believe the "Microsoft-DLNA DLNADOC/1.50" was you Windows Media Player talking to DLNA server. I uninstalled mine because of that.

[marc_al 5]

Hello,

 

Perhaps I should try again without it (but as I never use WMP it is not a big problem).

[anderbytes 139]

@@marc_al , passed all these days, I finally gave up the lazyness and tried to debug the above.

 

I had some trouble finding in the log what exactly I had to put in which field of Emby server.... but I finally did it.

 

Now... each device of mine has a specific profile, and I can manage by that.

 

 

Heys devs (@@Happy2Play and @Luke), Emby should really help us creating profiles.... "activate debug logging > activate dlna logging > explore logs and logs > try and error > deactivate the 2 debugs" shouldn't be the standard way of creating DLNA profiles. Right?

Thanks!

[marc_al 5]

Hello,

 

I am glad to hear! you managed to do it.

 

Greetings

Marc