Discover

[acateon]

This might not be a bug, in that case I'm sorry in advance but anyhow... Hitachi and a whole lot of others OEM TVs with the same platform. All of these run the SmartTVue suit and the Acces (https://gl.access-company.com/news_event/archives/2017/170613/) DLNA server. There seams to be running services on two ports:

Netdisco finds the following: Found malformed XML at http://192.168.1.6:9080: status=ok

But as I scanned with gssdp-discover I happened to stumple upon port 2870 which has a full DLNA XLM scheme. I cant seam to repeat the discovery since gssdp dropps packages:

(gssdp-discover:3014): WARNING : Received packet lacks "\r\n\r\n" sequence. Packed dropped.

http://192.168.1.6:2870/dmr.xml show what looks like a full featuring DLNA/UPNP. /dmr_rcs.xml shows support for volume/channel control etc.. Would it be possible to update the discovery feature to discovery these TV:s?

<root xmlns="urn:schemas-upnp-org:device-1-0" xmlns:dlna="urn:schemas-dlna-org:device-1-0" xmlns:pnpx="http://schemas.microsoft.com/windows/pnpx/2005/11" xmlns:df="http://schemas.microsoft.com/windows/2008/09/devicefoundation" xmlns:microsoft="urn:schemas-microsoft-com:WMPNSS-1-0">
<specVersion>
<major>1</major>
<minor>0</minor>
</specVersion>
<device>
<dlna:X_DLNADOC>DMR-1.50</dlna:X_DLNADOC>
<dlna:X_DLNACAP xmlns:dlna="urn:schemas-dlna-org:device-1-0"/>
<deviceType>urn:schemas-upnp-org:device:MediaRenderer:1</deviceType>
<friendlyName>HITACHI TV</friendlyName>
<manufacturer>ACCESS CO., LTD.</manufacturer>
<manufacturerURL>http://www.access-company.com/</manufacturerURL>
<modelDescription>IPI Media Renderer</modelDescription>
<modelName>-</modelName>
<modelNumber>1.0</modelNumber>
<modelURL>http://www.access-company.com/</modelURL>
<UDN>uuid:13ca17c6-b6f2-19ef-a0d1-486dbb128856</UDN>
<serviceList>
<service>
<serviceType>urn:schemas-upnp-org:service:RenderingControl:1</serviceType>
<serviceId>urn:upnp-org:serviceId:RenderingControl</serviceId>
<SCPDURL>/dmr_rcs.xml</SCPDURL>
<controlURL>/RenderingControl/control</controlURL>
<eventSubURL>/RenderingControl/event</eventSubURL>
</service>
<service>
<serviceType>urn:schemas-upnp-org:service:ConnectionManager:1</serviceType>
<serviceId>urn:upnp-org:serviceId:ConnectionManager</serviceId>
<SCPDURL>/dmr_cms.xml</SCPDURL>
<controlURL>/ConnectionManager/control</controlURL>
<eventSubURL>/ConnectionManager/event</eventSubURL>
</service>
<service>
<serviceType>urn:schemas-upnp-org:service:AVTransport:1</serviceType>
<serviceId>urn:upnp-org:serviceId:AVTransport</serviceId>
<SCPDURL>/dmr_avts.xml</SCPDURL>
<controlURL>/AVTransport/control</controlURL>
<eventSubURL>/AVTransport/event</eventSubURL>
</service>
</serviceList>
<iconList>
<icon>
<mimetype>image/jpeg</mimetype>
<width>48</width>
<height>48</height>
<depth>24</depth>
<url>/icon/DMR-small.jpg</url>
</icon>
<icon>
<mimetype>image/jpeg</mimetype>
<width>120</width>
<height>120</height>
<depth>24</depth>
<url>/icon/DMR-large.jpg</url>
</icon>
<icon>
<mimetype>image/png</mimetype>
<width>48</width>
<height>48</height>
<depth>24</depth>
<url>/icon/DMR-small.png</url>
</icon>
<icon>
<mimetype>image/png</mimetype>
<width>120</width>
<height>120</height>
<depth>24</depth>
<url>/icon/DMR-large.png</url>
</icon>
</iconList>
</device>
</root>

[StevenLooman]

Hi, I am working on a DLNA DMR media_player component. It works for my purposes, but more testing is wanted! The repo is called home-assistant-dlna-dmr. You'll find instructions on how to install it, as it is not integrated right now.

Please test and leave some feedback.

[StevenLooman]

Also, if my component tested a bit, I'll add a pull request for netdisco to better support this. The current support for DLNA is incomplete in netdisco.

[acateon]

That’s awesome! I’ll give it try as soon as possible and get back to you with feedback.

[StevenLooman]

@acateon Any luck so far?

[acateon]

I tried your component out, seams to work fine. Created an issue in your repository about not being able to send a turn_off command...

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

[balloobbot]

This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍