Closed carryonrewardless closed 3 years ago
Thank you for the issue. No problem in doing it this way, though it would be better if you would make issues at the home-assistant/core issue tracker itself. This is fine too, but perhaps this issue will (be) contain(ing) some information that could be helpful to somebody else, but not easily found when searching in the hass-tracker.
Anyway, I see you've already enabled logging which is helpful. I am also guessing you are using the 'native' dlna_dmr component and not the code from this repository, correct? I am assuming this as you have explicitly enabled the discovery of this component in your configuration and also the given paths in the traceback.
In the logging I see a 404 status code, which means file from the DLNA/DMR device is requested, but not found. I am guessing the URL in the configuration for the Google_DLNA
is incorrect. I would expect the URL to be something else, probably a XML file, like in the Samsung_DLNA
entry.
You can find the URL by running the upnp-client search
command, like so:
$ upnp-client search
{"CACHE-CONTROL": "max-age=1800", "DATE": "Mon, 27 Jul 2020 18:52:21 GMT", "EXT": "", "LOCATION": "http://192.168.178.13:7676/rcr/", "SERVER": "SHP, UPnP/1.0, Samsung UPnP SDK/1.0", "ST": "urn:samsung.com:device:RemoteControlReceiver:1", "USN": "uuid:a849a632-dcd5-4583-8077-5e0a307c353f::urn:samsung.com:device:RemoteControlReceiver:1", "Content-Length": "0", "_timestamp": "2020-07-27 20:52:22.574635", "_address": "192.168.178.13:50035", "_udn": "uuid:a849a632-dcd5-4583-8077-5e0a307c353f", "_source": "search"}
...
This gives lots of output, but you're interested in the lines which contain the address to your google home (192.168.1.100
). Find those lines and try the LOCATION
from those lines.
Also, the provided logging does seem to be missing some lines. If the above doesn't resolve your issue, can you check if there aren't more lines?
Thank you for the issue. No problem in doing it this way, though it would be better if you would make issues at the home-assistant/core issue tracker itself.
Yes I was not sure about where to post this and had not been to that link before. I did post in the community forum but figured you may never see it there. We can move the discussion to the above if you wish. Yes I am using the native component and I have deleted log lines that were apparently not relevant.
I tried the upnp search command and got:
bash: ./upnp-client: /usr/local/bin/python: bad interpreter: No such file or directory
So I tried
python3 upnp-client search
and got
ModuleNotFoundError: No module named 'async_upnp_client'
I had to sudo su to get into the docker folder to do this. Maybe my install is not correct/complete? Thanks for yr assistance.
So I did a
pip3 install async_upnp_client
and it works but there are no lines for the Google Home Mini at all just for the Samsung TV and the ZTE router.
See https://pastebin.com/Cj0c3zgz
Nmap scan report for 192.168.1.100
Host is up (0.014s latency).
Not shown: 994 closed ports
PORT STATE SERVICE
7778/tcp open interwise
8008/tcp open http
8009/tcp open ajp13
8443/tcp open https-alt
9000/tcp open cslistener
10001/tcp open scp-config
MAC Address: 48:D6:D5:EF:15:F0 (Google)
A more recent log is here https://pastebin.com/SGuZXLPR
When I attempt to play a track to the TV using this in HA
media_player.play_media
entity_id: media_player.tv_samsung
media_content_id: >-
http://192.168.1.29:8123/local/Music/ColdChisel/East/01 - Cold Chisel -
Standing on the Outside.ogg
media_content_type: music
I get the following log https://pastebin.com/z4JGSU1Y and the TV gives a message to check the network connection.
SSDP (the discovery protocol UPnP uses) works by sending out a special packet on port 1900. See async_upnp_client search if you're interested. Some devices use a different port making them incompatible.
Have you tried other programs which allow you to stream to DLNA/DMR devices? For example, BubbleUPNP on Android. If those programs do find your Google Home Mini, then something is amiss in async_upnp_client
. If not, then the device might not be compatible.
My own Samsung TV does not want to play anything served from the home assistant server. It does not provide the required headers in the HTTP response. Using minedlnad I could play music and video.
Any luck so far?
I have issues trying to set up dlna media players on Raspbian - Buster. My aim is to stream local media (music, photos, videos) to a 2014 Samsung TV and to Google Home ( music only obviously). My config is
and my error log with debug looks like this
There has been some great work done on the dlna_dmr component. I would love to make use of it on my system but need some help with these errors.