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
74.07k stars 31.09k forks source link

DLNA/UPnP: UpnpError('Unsupported data type: ui8', None) with Gerbera server #82351

Closed mill1000 closed 1 year ago

mill1000 commented 2 years ago

The problem

Gerbera is a UPnP media server forked from MediaTomb. A recent update introduced a new state variable with a data type of ui8. https://github.com/gerbera/gerbera/blob/a253e04b848e2f6a8cc2bd2ba55b5732040d85a6/web/cds.xml#L245-L248

This is a valid data type according to the UPnP Device Architecture v2.0.

The type needs to be added to the underlying UPnP client library here: https://github.com/StevenLooman/async_upnp_client/blob/57bf8ff654ac253115980b96ccd5ee6bc0ae1281/async_upnp_client/const.py#L46-L49

What version of Home Assistant Core has the issue?

core-2022.11.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

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?

2022-11-18 21:12:06.517 WARNING (MainThread) [homeassistant.components.dlna_dms] Failed connecting to recently alive device at http://10.100.1.2:49494/description.xml: UpnpError('Unsupported data type: ui8', None)

Additional information

No response

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!

Code owner commands Code owners of `dlna_dms` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Change the title of the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign dlna_dms` Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


dlna_dms documentation dlna_dms source (message by IssueLinks)

bouwew commented 2 years ago

I'm using Gerbera as well, seeing the same issue in Logs.

@StevenLooman for your attention.

chishm commented 2 years ago

I've made a PR to async_upnp_client which should hopefully fix this issue. See the link above.

zminde commented 1 year ago

First of all thanks to your team for their hard work, this is a very useful integration. It was working fine before this, no changes or upgrades were made to Home Assistant. Show "Server communication failure: UpnpXmlParseError('not well-formed (invalid token): line 3, column 769')" on today's MEDIA-DLNA Servers-VIDEO page in Home Assistant 2022.11.5 Supervisor 2022.11.2 Operating System 9.3 How should this be resolved and what could be the possible cause of this? 20221204135432

bouwew commented 1 year ago

@zminde Please create a new issue for the problem you are reporting.