Closed ameuret closed 6 months 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)
dlna_dms documentation dlna_dms source (message by IssueLinks)
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.
As of the latest release, this issue is still present. Here are the rclone-side logs:
2024/02/09 11:59:56 INFO : /static/ContentDirectory.xml: 192.168.1.173:36026 GET 200
2024/02/09 11:59:56 INFO : /static/ConnectionManager.xml: 192.168.1.173:36026 GET 200
2024/02/09 11:59:56 INFO : /static/X_MS_MediaReceiverRegistrar.xml: 192.168.1.173:36026 GET 200
2024/02/09 11:59:56 INFO : /ctl: 192.168.1.173:36026 POST 200 "urn:schemas-upnp-org:service:ConnectionManager:1#GetProtocolInfo"
2024/02/09 11:59:56 INFO : /ctl: 192.168.1.173:36026 POST 200 "urn:schemas-upnp-org:service:ContentDirectory:1#GetSystemUpdateID"
2024/02/09 11:59:56 INFO : /ctl: 192.168.1.173:36026 POST 200 "urn:schemas-upnp-org:service:ContentDirectory:1#GetSearchCapabilities"
2024/02/09 11:59:56 INFO : /ctl: 192.168.1.173:36026 POST 200 "urn:schemas-upnp-org:service:ContentDirectory:1#GetSortCapabilities"
2024/02/09 11:59:56 INFO : /static/rclone-48x48.png: 192.168.1.4:52253 GET 200
2024/02/09 11:59:56 INFO : /static/rclone-120x120.png: 192.168.1.4:52253 GET 200
2024/02/09 11:59:56 INFO : /static/X_MS_MediaReceiverRegistrar.xml: 192.168.1.4:52253 GET 200
2024/02/09 11:59:56 INFO : /ctl: 192.168.1.4:52254 POST 200 "urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1#IsAuthorized"
2024/02/09 11:59:56 INFO : /static/ContentDirectory.xml: 192.168.1.4:52255 GET 200
2024/02/09 12:00:02 INFO : /ctl: 192.168.1.173:48588 POST 200 "urn:schemas-upnp-org:service:ContentDirectory:1#Browse"
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.
Issue still active in 2024.5.5
This is a bug in rclone. When it returns a result for Browse with the flag "BrowseMetadata", it is not including the fields "TotalMatches" or "NumberReturned". According to the UPnP-av-ContentDirectory-v1-Service spec (section 2.7.4.2), these are not optional and should be set to 1 for both when "BrowseMetadata" is used.
Arguably dlna_dmr
(and async-upnp-client) could be more tolerant here, but since rclone is open source it might be best to raise an issue there to fix it for all users.
PS: Also, hi and thank you for the bug report. I do appreciate that you've taken the time to report an issue, instead of ignoring it and the dlna_dmr component entirely.
Thanks a lot for taking the time to dig into foreign code and my please accept my apologies for assuming that rclone was undoubtedly more mature than your component ! 🙇🏻
The fix has been done in rclone and will find its way in the upcoming releases. :partying_face:
That's great news! Excellent work on getting the bug reported so well, you've made a good contribution to the open source community.
The problem
Rclone is launched using
rclone serve dlna --addr 0.0.0.0:8080 /home/arnaud/over/movies/
and vlc can browse and play media fine (Linux & iPad).What version of Home Assistant Core has the issue?
core-2023.11.1
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_dms
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?
Additional information
No response