DLNA Player does not update the media title anymore

[trentjw]

this use to update the what input the sony 1040 receiver was on when it was swapped now it only updates when uninstalled and reinstalled and then it is stuck on whatever the receiver is on when reinstalled it no longer queries the reciever

[StevenLooman]

Thank you for this issue, @trentjw . This is possibly due to the receiver getting a new IP. Currently, the integration in Home Assistant does not properly handle this. The easiest fix - for now - is to make sure your receiver always has the same IP. You can do this by setting a static IP in the receiver, or let your router always give the same IP to the receiver (note that not all routers support this.)

[trentjw]

My receiver has a static IP address been the same one since I hooked it up, this was working until I updated home assistant to 118.5 and possibly broke in 118.4

…

On Mon, Dec 7, 2020, 10:12 AM Steven Looman ***@***.***> wrote: Thank you for this issue, @trentjw <https://github.com/trentjw> . This is possibly due to the receiver getting a new IP. Currently, the integration in Home Assistant does not properly handle this. The easiest fix - for now - is to make sure your receiver always has the same IP. You can do this by setting a static IP in the receiver, or let your router always give the same IP to the receiver (note that not all routers support this.) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#12 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC5HQ5MYX2EP77DGE5TKLNLSTUEEVANCNFSM4UQAB3WA> .

[trentjw]

Also the status of the receiver still updates from idle to playing just fine it does not update the media title anymore

…

On Mon, Dec 7, 2020, 11:39 AM Trenton Wilson ***@***.***> wrote: My receiver has a static IP address been the same one since I hooked it up, this was working until I updated home assistant to 118.5 and possibly broke in 118.4 On Mon, Dec 7, 2020, 10:12 AM Steven Looman ***@***.***> wrote: > Thank you for this issue, @trentjw <https://github.com/trentjw> . This > is possibly due to the receiver getting a new IP. Currently, the > integration in Home Assistant does not properly handle this. The easiest > fix - for now - is to make sure your receiver always has the same IP. You > can do this by setting a static IP in the receiver, or let your router > always give the same IP to the receiver (note that not all routers support > this.) > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#12 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AC5HQ5MYX2EP77DGE5TKLNLSTUEEVANCNFSM4UQAB3WA> > . >

[StevenLooman]

Not that much has changed recently in this component in home assistant: https://github.com/home-assistant/core/commits/dev/homeassistant/components/dlna_dmr

Can you enable logging by adding this to you configuration.yaml file?

logger:
  logs:
    homeassistant.components.dlna_dmr: debug
    async_upnp_client: debug

Please report anything you see with regard to dlna_dmr and/or async_upnp_client.

[trentjw]

my configuration straight up does not like your logger not valid

[trentjw]

I am running python 3.9 if that makes any difference

[trentjw]

the Playing part works it the stuff in the far right window that does not update anymore including the volume no longer updates either

Now if I unistall and reinstall the DLNA player it will grab all those settings that are current on the player but now it does not update until I uninstall and reinstall the DLNA player

[StevenLooman]

@trentjw Perhaps the indenting (the spaces before the lines) wasn't correct in the configuration.yaml file. Please check other parts of the file to see what it should be.

I can't do much without any logging.

Perhaps your receiver does not update like other devices. Normally there is a special "variable" that gets updated reflecting these properties (volume etc.)

[trentjw]

@trentjw Perhaps the indenting (the spaces before the lines) wasn't correct in the configuration.yaml file. Please check other parts of the file to see what it should be.

I can't do much without any logging.

Perhaps your receiver does not update like other devices. Normally there is a special "variable" that gets updated reflecting these properties (volume etc.)

I copied your logger directly into my configuration.yaml

yeah you are right must be my receiver that is the issue never mind that it was updating just fine until 118.4 sorry for wasting your time

[StevenLooman]

yeah you are right must be my receiver that is the issue never mind that it was updating just fine until 118.4 sorry for wasting your time

I don't mind investigating a bit more! I'm sure there are others who have the same problem and are helped as well when we fix your problem. Although not much has changed since a while (before 118.4), perhaps other parts have change which influence this component.

Can you show any (non-identifying, or change the identifying values) parts of your configuration? For me, indenting with two spaces works, perhaps it is a bit different in your case.

[StevenLooman]

You can also mail your configuration.yaml to me, then I can change it for you: [email protected] . Please do remove any usernames/passwords/tokens/secrets before mailing it!