home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.06k stars 29.73k forks source link

DLNA/UPnP Digital Media Server error when accessing media list #68486

Closed OMVMMG closed 2 years ago

OMVMMG commented 2 years ago

The problem

The following error is shown in the DLNA media folder:

Server failure: UpnpActionResponseError('Error during async_call(), status: 500, upnp error: 720 (Cannot process the request. java.lang.IllegalArgumentException: fromIndex(0) > toIndex(-1).)')

What version of Home Assistant Core has the issue?

2022.3.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 Server

Link to integration documentation on our website

https://www.home-assistant.io/integrations/dlna_dms

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

probot-home-assistant[bot] commented 2 years ago

dlna_dms documentation dlna_dms source (message by IssueLinks)

probot-home-assistant[bot] commented 2 years ago

Hey there @chishm, mind taking a look at this issue as it has been labeled with an integration (dlna_dms) you are listed as a code owner for? Thanks! (message by CodeOwnersMention)

chishm commented 2 years ago

Thank you for the bug report. To help diagnose this further, can you please enable the following logging configuration, try again, and post the log here? You may want to check the log first, for any file names or IP addresses that you don't want to post publicly.

logger:
  default: warning
  logs:
    homeassistant.components.dlna_dms: debug
    async_upnp_client.profiles.profile: debug
    async_upnp_client.profiles.dlna: debug

Also, can you please tell me what software you use for your media server?

github-actions[bot] commented 2 years ago

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.