Closed animalillo closed 1 year ago
dlna_dmr documentation dlna_dmr source (message by IssueLinks)
Hey there @stevenlooman, @chishm, mind taking a look at this issue as it has been labeled with an integration (dlna_dmr
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
It is worth checking the logs for any errors. Please enable the following settings and try again:
logger:
default: warning
logs:
homeassistant.components.dlna_dmr: debug
async_upnp_client.profiles.profile: debug
async_upnp_client.profiles.dlna: debug
Thank you for your repply @chishm ! After enabling that debug mode i found those lines:
There might be something related with a dlna media server that i had set up for testing if that had any more luck than the built in feature, but no luck, i even tried moving the media server to the same network that the rendered is at, which is the current status (at 192.168.5.204:8200), but it still does not work
Any ideas of how to get this to work?
Sorry, this one has me stumped. It looks like the AnyCast is never going into a "playable" state. I can see that HomeAssistant is getting as far as setting the URL to play, but nothing further. If you want, you could try some more detailed logging with:
logger:
default: warning
logs:
homeassistant.components.dlna_dmr: debug
async_upnp_client.profiles.profile: debug
async_upnp_client.profiles.dlna: debug
async_upnp_client.traffic: debug
This will also log the low-level messages sent to and received from the device. There might be some clue in there. Please attach the log as a file rather than inline text, so GitHub doesn't try to format it.
Here is a trace attempting to show a picture, which deals the same result as a video and has the same final result: media player stuck in the loading spinner. A video one would make the trace file waaay bigger (i could provide one like that if needed, but tought this would be easier to look at).
Do you guys need any extra details? It would be nice to get this to work, looks like a neat feature :)
Thank you for the trace, and sorry about not getting back to you sooner. It looks like the device is never saying that it can "play" in its CurrentTransportActions
"state variable" (UPnP terminology). I'm not sure if that's because it hasn't sent the event correctly, or if it's because HA is meant to poll and isn't. I'd know for sure if I could see the debug trace when HA connects to the device, either when HA is started (if the device is already on) or when the device is turned on.
My thinking is that async_wait_for_can_play might need to poll the state variable inside the waiting loop, and a connection trace would confirm if this is the case.
Sorry for the long delay, I have been pretty busy and traveling around, but I managed to get a trace while booting the device.
I hope this one brings out some light in the matter :D
Thank you!
Thank you for the boot trace, and also my apologies for the long delay in responding (life happens to us all!).
It looks like HA is successfully subscribing to events from your device (at IP address 192.168.5.107), and is also receiving the events (NOTIFY messages). I'm not sure why the device never sends a notification that it can play after an URI is set, but my previous plan might still work.
Then again, it may not (I see in the initial trace that CurrentTransportActions
is empty), but I will try anyway.
No problem @chishm !
Let me know if you need anything, as of the why is not properly advertising, it probably has something to do with it being a cheap chineese product, but it works with most phone apps for this purpose so i wonder what they do differently. No way to know as those apps tend to be closed source tho.
Thank you for taking your time on the matter anyways! :)
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 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
The problem
I'm unable to play any media on an AnyCast DLNA media renderer, I've tried using local media, media by url, and a local dlna media server called vía service using the url, with no luck
What version of Home Assistant Core has the issue?
core-2022.4.5
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
DLNA Digital Media Renderer
Link to integration documentation on our website
https://www.home-assistant.io/integrations/dlna_dmr
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
Not sure if it could be related but the renderer device and the home assistant install are on different ip ranges, altough all trafic is able to go trough those networks and it does not seem to have trouble setting up the volume...