Jump to content

Anyone using Denon HEOS

blublub

By blublub
in DLNA

 Share

Recommended Posts

blublub

blublub   10

Posted
Posted

Hi

 

I have a couple of HEOS devices and the combination of emby DLNA and HEOS is Nightmare.

 

Does anyone already have a HEOS profile?

Link to comment
Share on other sites
blublub

blublub   10

Posted
  • Author
Posted

Hi, welcome ! What issues are you having?

Hi Luke,

 

thx for answering so quickly.

 

Things are a little tricky here because of my setup. So I wasn't sure where the problem starts in the 1st place.

 

Ok, the setup:

HEOS is controlled via a Control4 system and sometimes, but just sometimes via our tablets/phone from the HEOS app - so let's focus on the main scenario.

 

Emby config:

I set up one specific user (HEOS) which can only view the music library. The user HEOS is set up in DLNA as the main profile/user.

 

 

After some digging I am now sure that it is a profile problem but I still can't pin Emby to use a custom profile, it seems to fall back to generic all the time - so streaming flac doesn't work, it is always trans-coding.

 

I guess once I have the profile working other issues can be resolve as well (i.e. I can't browser via genre).

 

Here is a debug log. The client I am browsing from is set in Control4 to the IP 192.168.7.53 - which is one of my HEOS devices.

MicroStack/1.0.1846
2016-12-04 07:00:34.9022 Debug UpnpContentDirectory: Renewing event subscription for  with timeout of 180 to <http://192.168.7.53:57160/dlna/4b148554ced15cba13013478c2cc8a57/contentdirectory/events>
2016-12-04 07:00:34.9022 Info HttpServer: HTTP Response 200 to 192.168.7.53. Time: 1ms. http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/contentdirectory/events
2016-12-04 07:00:37.8318 Info HttpServer: HTTP GET http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/description.xml. UserAgent: avhttp/2.9.9
2016-12-04 07:00:37.8322 Info Dlna: No matching device profile found. The default will need to be used.
	Host: 192.168.7.99
	Accept: text/html, application/xhtml+xml, */*
	User-Agent: avhttp/2.9.9
	Connection: close
2016-12-04 07:00:37.8322 Info HttpServer: HTTP Response 200 to 192.168.7.93. Time: 1ms. http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/description.xml
2016-12-04 07:00:37.8364 Info HttpServer: HTTP GET http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/description.xml. UserAgent: avhttp/2.9.9
2016-12-04 07:00:37.8364 Info Dlna: No matching device profile found. The default will need to be used.
	Host: 192.168.7.99
	Accept: text/html, application/xhtml+xml, */*
	User-Agent: avhttp/2.9.9
	Connection: close
2016-12-04 07:00:37.8364 Info HttpServer: HTTP Response 200 to 192.168.7.93. Time: 1ms. http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/description.xml
2016-12-04 07:00:37.8395 Info HttpServer: HTTP GET http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/description.xml. UserAgent: avhttp/2.9.9
2016-12-04 07:00:37.8395 Info Dlna: No matching device profile found. The default will need to be used.
	Host: 192.168.7.99
	Accept: text/html, application/xhtml+xml, */*
	User-Agent: avhttp/2.9.9
	Connection: close
2016-12-04 07:00:37.8401 Info HttpServer: HTTP Response 200 to 192.168.7.93. Time: 1ms. http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/description.xml
2016-12-04 07:00:37.8425 Info HttpServer: HTTP GET http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/description.xml. UserAgent: avhttp/2.9.9
2016-12-04 07:00:37.8425 Info Dlna: No matching device profile found. The default will need to be used.
	Host: 192.168.7.99
	Accept: text/html, application/xhtml+xml, */*
	User-Agent: avhttp/2.9.9
	Connection: close
2016-12-04 07:00:37.8432 Info HttpServer: HTTP Response 200 to 192.168.7.93. Time: 1ms. http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/description.xml
2016-12-04 07:00:37.8458 Info HttpServer: HTTP GET http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/description.xml. UserAgent: avhttp/2.9.9
2016-12-04 07:00:37.8461 Info Dlna: No matching device profile found. The default will need to be used.
	Host: 192.168.7.99
	Accept: text/html, application/xhtml+xml, */*
	User-Agent: avhttp/2.9.9
	Connection: close
2016-12-04 07:00:37.8461 Info HttpServer: HTTP Response 200 to 192.168.7.93. Time: 1ms. http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/description.xml
2016-12-04 07:00:37.8710 Info HttpServer: HTTP GET http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/description.xml. UserAgent: avhttp/2.9.9
2016-12-04 07:00:37.8713 Info Dlna: No matching device profile found. The default will need to be used.
	Host: 192.168.7.99
	Accept: text/html, application/xhtml+xml, */*
	User-Agent: avhttp/2.9.9
	Connection: close
2016-12-04 07:00:37.8713 Info HttpServer: HTTP Response 200 to 192.168.7.93. Time: 1ms. http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/description.xml
2016-12-04 07:00:37.8771 Info HttpServer: HTTP GET http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/description.xml. UserAgent: avhttp/2.9.9
2016-12-04 07:00:37.8771 Info Dlna: No matching device profile found. The default will need to be used.
	Host: 192.168.7.99
	Accept: text/html, application/xhtml+xml, */*
	User-Agent: avhttp/2.9.9
	Connection: close
2016-12-04 07:00:37.8771 Info HttpServer: HTTP Response 200 to 192.168.7.93. Time: 1ms. http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/description.xml
2016-12-04 07:00:37.8833 Info HttpServer: HTTP GET http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/description.xml. UserAgent: avhttp/2.9.9
2016-12-04 07:00:37.8833 Info Dlna: No matching device profile found. The default will need to be used.
	Host: 192.168.7.99
	Accept: text/html, application/xhtml+xml, */*
	User-Agent: avhttp/2.9.9
	Connection: close
2016-12-04 07:00:37.8833 Info HttpServer: HTTP Response 200 to 192.168.7.93. Time: 1ms. http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/description.xml
2016-12-04 07:00:37.8887 Info HttpServer: HTTP GET http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/description.xml. UserAgent: avhttp/2.9.9
2016-12-04 07:00:37.8891 Info Dlna: No matching device profile found. The default will need to be used.
	Host: 192.168.7.99
	Accept: text/html, application/xhtml+xml, */*
	User-Agent: avhttp/2.9.9
	Connection: close
2016-12-04 07:00:37.8891 Info HttpServer: HTTP Response 200 to 192.168.7.93. Time: 1ms. http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/description.xml
2016-12-04 07:00:37.9084 Info HttpServer: HTTP GET http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/description.xml. UserAgent: avhttp/2.9.9
2016-12-04 07:00:37.9084 Info Dlna: No matching device profile found. The default will need to be used.
	Host: 192.168.7.99
	Accept: text/html, application/xhtml+xml, */*
	User-Agent: avhttp/2.9.9
	Connection: close
2016-12-04 07:00:37.9091 Info HttpServer: HTTP Response 200 to 192.168.7.93. Time: 1ms. http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/description.xml
2016-12-04 07:00:37.9145 Info HttpServer: HTTP GET http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/description.xml. UserAgent: avhttp/2.9.9
2016-12-04 07:00:37.9145 Info Dlna: No matching device profile found. The default will need to be used.
	Host: 192.168.7.99
	Accept: text/html, application/xhtml+xml, */*
	User-Agent: avhttp/2.9.9
	Connection: close
2016-12-04 07:00:37.9151 Info HttpServer: HTTP Response 200 to 192.168.7.93. Time: 1ms. http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/description.xml
2016-12-04 07:00:37.9206 Info HttpServer: HTTP GET http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/description.xml. UserAgent: avhttp/2.9.9
2016-12-04 07:00:37.9206 Info Dlna: No matching device profile found. The default will need to be used.
	Host: 192.168.7.99
	Accept: text/html, application/xhtml+xml, */*
	User-Agent: avhttp/2.9.9
	Connection: close
2016-12-04 07:00:37.9213 Info HttpServer: HTTP Response 200 to 192.168.7.93. Time: 1ms. http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/description.xml
2016-12-04 07:00:37.9262 Info HttpServer: HTTP GET http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/description.xml. UserAgent: avhttp/2.9.9
2016-12-04 07:00:37.9262 Info Dlna: No matching device profile found. The default will need to be used.
	Host: 192.168.7.99
	Accept: text/html, application/xhtml+xml, */*
	User-Agent: avhttp/2.9.9
	Connection: close
2016-12-04 07:00:37.9262 Info HttpServer: HTTP Response 200 to 192.168.7.93. Time: 1ms. http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/description.xml
2016-12-04 07:00:37.9273 Info HttpServer: HTTP GET http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/description.xml. UserAgent: avhttp/2.9.9
2016-12-04 07:00:37.9273 Info Dlna: No matching device profile found. The default will need to be used.
	Host: 192.168.7.99
	Accept: text/html, application/xhtml+xml, */*
	User-Agent: avhttp/2.9.9
	Connection: close
2016-12-04 07:00:37.9273 Info HttpServer: HTTP Response 200 to 192.168.7.93. Time: 1ms. http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/description.xml
2016-12-04 07:00:48.1586 Info HttpServer: HTTP SUBSCRIBE http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/contentdirectory/events. UserAgent: POSIX UPnP/1.0 DLNADOC/1.50 Intel MicroStack/1.0.1846
2016-12-04 07:00:48.1586 Debug UpnpContentDirectory: Renewing event subscription for  with timeout of 180 to <http://192.168.7.51:51678/dlna/4b148554ced15cba13013478c2cc8a57/contentdirectory/events>
2016-12-04 07:00:48.1592 Info HttpServer: HTTP Response 200 to 192.168.7.51. Time: 1ms. http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/contentdirectory/events
2016-12-04 07:01:08.6557 Info HttpServer: HTTP SUBSCRIBE http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/contentdirectory/events. UserAgent: 
2016-12-04 07:01:08.6557 Debug UpnpContentDirectory: Renewing event subscription for  with timeout of 300 to <http://192.168.7.90:6666/>
2016-12-04 07:01:08.6563 Info HttpServer: HTTP Response 200 to 192.168.7.90. Time: 1ms. http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/contentdirectory/events
2016-12-04 07:02:04.6211 Info HttpServer: HTTP SUBSCRIBE http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/contentdirectory/events. UserAgent: POSIX UPnP/1.0 DLNADOC/1.50 Intel MicroStack/1.0.1846
2016-12-04 07:02:04.6211 Debug UpnpContentDirectory: Renewing event subscription for  with timeout of 180 to <http://192.168.7.53:57160/dlna/4b148554ced15cba13013478c2cc8a57/contentdirectory/events>
2016-12-04 07:02:04.6211 Info HttpServer: HTTP Response 200 to 192.168.7.53. Time: 1ms. http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/contentdirectory/events
2016-12-04 07:02:18.3941 Info HttpServer: HTTP SUBSCRIBE http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/contentdirectory/events. UserAgent: POSIX UPnP/1.0 DLNADOC/1.50 Intel MicroStack/1.0.1846
2016-12-04 07:02:18.3941 Debug UpnpContentDirectory: Renewing event subscription for  with timeout of 180 to <http://192.168.7.51:51678/dlna/4b148554ced15cba13013478c2cc8a57/contentdirectory/events>
2016-12-04 07:02:18.3941 Info HttpServer: HTTP Response 200 to 192.168.7.51. Time: 1ms. http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/contentdirectory/events
2016-12-04 07:03:29.4409 Info HttpServer: HTTP POST http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/contentdirectory/control. UserAgent: POSIX UPnP/1.0 DLNADOC/1.50 Intel MicroStack/1.0.1846
2016-12-04 07:03:29.4415 Info Dlna: No matching device profile found. The default will need to be used.
	Host: 192.168.7.99:8096
	User-Agent: POSIX UPnP/1.0 DLNADOC/1.50 Intel MicroStack/1.0.1846
	SOAPACTION: "urn:schemas-upnp-org:service:ContentDirectory:1#Browse"
	Content-Type: text/xml; charset="utf-8"
	Content-Length: 661
2016-12-04 07:03:29.4415 Debug UpnpContentDirectory: Received control request Browse
2016-12-04 07:03:29.4554 Info HttpServer: HTTP Response 200 to 192.168.7.53. Time: 15ms. http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/contentdirectory/control
2016-12-04 07:03:33.1297 Info HttpServer: HTTP POST http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/contentdirectory/control. UserAgent: POSIX UPnP/1.0 DLNADOC/1.50 Intel MicroStack/1.0.1846
2016-12-04 07:03:33.1303 Info Dlna: No matching device profile found. The default will need to be used.
	Host: 192.168.7.99:8096
	User-Agent: POSIX UPnP/1.0 DLNADOC/1.50 Intel MicroStack/1.0.1846
	SOAPACTION: "urn:schemas-upnp-org:service:ContentDirectory:1#Browse"
	Content-Type: text/xml; charset="utf-8"
	Content-Length: 692
2016-12-04 07:03:33.1303 Debug UpnpContentDirectory: Received control request Browse
2016-12-04 07:03:33.2137 Info HttpServer: HTTP Response 200 to 192.168.7.53. Time: 84ms. http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/contentdirectory/control
2016-12-04 07:03:34.6544 Info HttpServer: HTTP SUBSCRIBE http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/contentdirectory/events. UserAgent: POSIX UPnP/1.0 DLNADOC/1.50 Intel MicroStack/1.0.1846
2016-12-04 07:03:34.6544 Debug UpnpContentDirectory: Renewing event subscription for  with timeout of 180 to <http://192.168.7.53:57160/dlna/4b148554ced15cba13013478c2cc8a57/contentdirectory/events>
2016-12-04 07:03:34.6553 Info HttpServer: HTTP Response 200 to 192.168.7.53. Time: 1ms. http://192.168.7.99:8096/dlna/4b148554ced15cba13013478c2cc8a57/contentdirectory/events
2016-12-04 07:03:35.2867 Info HttpServer: HTTP GET http://192.168.7.99:8096/emby/System/Logs/Log?name=server-63616406400.txt. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0

thx for taking a look

Link to comment
Share on other sites
blublub

blublub   10

Posted
  • Author
Posted

What does your custom profile look like? Did you add identification criteria?

 

Profile is pretty much blank from scratch beside the identification part:

 

HTTP Headers / substring / Avega

 

The funny part is that "Avega" doesn't show up in the above debug log ! 

 

So here is the 2nd part:

;;79c401efbb48497654094fc95c0c64c9;false;;;false;fe7d715236f27315d3186be781484b9b;false. UserAgent: AvegaMediaServer/2.0 Linux/2.6
2016-12-03 20:52:34.6203 Info Dlna: No matching device profile found. The default will need to be used.
	User-Agent: AvegaMediaServer/2.0 Linux/2.6
	Host: 192.168.7.99:8096
	Accept: */*
	transferMode.dlna.org: Streaming

But now that I look at the log again think I understand it:

 

The 1st log shows browsing Emby DLNA from 192.168.7.93 - this would be my Control4 controller running the HEOS driver.

Playback however would be from a different IP, the actual HEOS player with probably another identification string -> Avega (2nd log)

 

Can I put two different ID substrings into one DLNA profile?

Link to comment
Share on other sites
Happy2Play

Happy2Play   8317

Posted
Posted

So looking at your custom profile xml, the headers section looks like this?
 

....\Emby-Server\config\dlna\user

    <Headers>
      <HttpHeaderInfo name="User-Agent" value="AvegaMediaServer" match="Substring" />
    </Headers>
Link to comment
Share on other sites
blublub

blublub   10

Posted
  • Author
Posted

 

So looking at your custom profile xml, the headers section looks like this?

 

....\Emby-Server\config\dlna\user

    <Headers>
      <HttpHeaderInfo name="User-Agent" value="AvegaMediaServer" match="Substring" />
    </Headers>

 

 

I have to check that tomorrow - sry, too late now and I have to SSH in for that, so not a quick task as I dont know where Emby is located

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing
×
×
  • Create New...