Additional logging for DLNA device info before matching with a profile

[aoberoi]

First, I am willing to contribute and help land this change. It will likely be a tiny one-liner. If I see some general agreement, esp from the core team, then I'll dive into the code and work on a PR.

Currently, DLNA profile matching is sort of a guess-and-check process, and encourages folks to be somewhat loose/sloppy with defining a custom profile to match their specific devices. Right now, I have no idea what fields in the UI such as Manufacturer, Model Name, Model Number, etc. are even matched against. The only fields that seem to be approachable are the headers, because headers are output in some existing logs today.

In my opinion, logging out exhaustive info about a connected device, even if its going to match to a generic default profile, would help folks craft more useful profiles. These would be specific enough to address a whole family of devices with the same capabilities (which will continue to evolve as new hardware comes out and new software for existing hardware also comes out). With better quality custom profiles, people might actually be able to share them with each other or back to the server project. I could see potential for a better UI being developed around this, but I think the first step is just a simple log line with as much detail as possible about DLNA devices.

It seems like the DLNA code might be moving out of this repo (see: jellyfin/jellyfin#10558). Let me know if I need to target a different branch or repo to help align with that work. Thanks!

[spali]

I appreciate the logging of the profile.
Maybe in a second step, why not let us show the profile details in the current device list and let us create a prefilled profile from there.