search

StevenLooman / home-assistant-dlna-dmr

DLNA/DMR component for home-assistant
Other
14 stars 1 forks source link

Adding Denon Radio fails: #2

Closed gpgmailencrypt closed 6 years ago

gpgmailencrypt commented 6 years ago

Hi, I get the following message, when trying to connect to my radio. Any ideas what went wrong?

2017-12-25 13:20:23 DEBUG (Thread-13) [custom_components.media_player.dlna_dmr] dlna_dmr.setup_platform
2017-12-25 13:20:23 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=notify>
2017-12-25 13:20:23 DEBUG (Thread-13) [custom_components.media_player.dlna_dmr] start_notify_view()
2017-12-25 13:20:23 DEBUG (Thread-13) [custom_components.media_player.dlna_dmr] Adding device: <DlnaDmrDevice('http://192.168.20.67:8080/description.xml')>
2017-12-25 13:20:23 DEBUG (MainThread) [custom_components.media_player.dlna_dmr] <DlnaDmrDevice('http://192.168.20.67:8080/description.xml')>.async_update()
2017-12-25 13:20:23 DEBUG (MainThread) [custom_components.media_player.dlna_dmr] <DlnaDmrDevice('http://192.168.20.67:8080/description.xml')>.async_update(): no device
2017-12-25 13:20:23 DEBUG (MainThread) [custom_components.media_player.dlna_dmr] <DlnaDmrDevice('http://192.168.20.67:8080/description.xml')>._async_init_device()
2017-12-25 13:20:23 DEBUG (MainThread) [chardet.universaldetector] no data received!
2017-12-25 13:20:23 DEBUG (MainThread) [custom_components.media_player.upnp_client] <UpnpService(urn:upnp-org:serviceId:RenderingControl)>.subscribe(): Got SID: uuid:ae060f90-876f-1f47-b95c-972047215fc7
2017-12-25 13:20:23 DEBUG (MainThread) [chardet.universaldetector] no data received!
2017-12-25 13:20:23 DEBUG (MainThread) [custom_components.media_player.upnp_client] <UpnpService(urn:upnp-org:serviceId:ConnectionManager)>.subscribe(): Got SID: uuid:c4c4bb99-6b74-1357-97b5-f63617408138
2017-12-25 13:20:23 DEBUG (MainThread) [chardet.universaldetector] no data received!
2017-12-25 13:20:23 DEBUG (MainThread) [custom_components.media_player.upnp_client] <UpnpService(urn:upnp-org:serviceId:AVTransport)>.subscribe(): Got SID: uuid:77f5ec75-c209-1d15-914c-826ab67f1566
2017-12-25 13:20:23 DEBUG (MainThread) [custom_components.media_player.dlna_dmr] <DlnaDmrDevice('http://192.168.20.67:8080/description.xml')>.async_update(): calling...
2017-12-25 13:20:23 DEBUG (MainThread) [custom_components.media_player.dlna_dmr] <DlnaDmrDevice('http://192.168.20.67:8080/description.xml')>._async_poll_transport_info()
2017-12-25 13:20:28 DEBUG (MainThread) [custom_components.media_player.dlna_dmr] Error in <custom_components.media_player.dlna_dmr.HassUpnpRequester object at 0x7f0eac522e80>.async_call_action(): 
2017-12-25 13:20:28 DEBUG (MainThread) [custom_components.media_player.dlna_dmr] <DlnaDmrDevice('http://192.168.20.67:8080/description.xml')>.async_update(): error on update: 
2017-12-25 13:20:28 DEBUG (MainThread) [custom_components.media_player.dlna_dmr] <DlnaDmrDevice('http://192.168.20.67:8080/description.xml')>.async_disconnect()
2017-12-25 13:20:28 DEBUG (MainThread) [chardet.universaldetector] no data received!
2017-12-25 13:20:28 ERROR (MainThread) [custom_components.media_player.upnp_client] Did not receive 200, but 412
2017-12-25 13:20:28 DEBUG (MainThread) [chardet.universaldetector] no data received!
2017-12-25 13:20:28 ERROR (MainThread) [custom_components.media_player.upnp_client] Did not receive 200, but 412
2017-12-25 13:20:28 DEBUG (MainThread) [chardet.universaldetector] no data received!
2017-12-25 13:20:28 ERROR (MainThread) [custom_components.media_player.upnp_client] Did not receive 200, but 412

description.xml.zip

StevenLooman commented 6 years ago

Hi, sorry for the late reply. I wasn't receiving any notifications for this repository.

Your radio reports HTTP status code 412, which states that a precondition has failed for the HTTP request. It is possible that the radio requires you (the module) to register any clients. Do any other apps require this?

Also, can you to get these files from your radio/UPnP service. The URLs are guesses:

StevenLooman commented 6 years ago

This component is now integrated into home assistant itself. You should use that instead. Netdisco/discovery will discover the device for you without any manual configuration.

Still, you still have to enable discovery of it explicitly. You can do this by opting-in discovery of dlna_dmr devices, like so in your config:

discovery:
  enable:
    - dlna_dmr