search

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
73.66k stars 30.8k forks source link

Frontier Silicon Internet Radio not working in 0.66.1 #13780

Closed ratyfu closed 6 years ago

ratyfu commented 6 years ago

Home Assistant release with the issue: 0.66.1

Last working Home Assistant release (if known):

Operating environment (Hass.io/Docker/Windows/etc.): Hassbian v.1.3.2 (03/16/2018) on a Raspberry Pi 3B

Component/platform: media_player.frontier_silicon

Description of problem: I have three of these devices: SMRS_18_A1 (Silvercrest Multiroom Speaker that uses UNDOK) I can see the entities in the frontend, also when I play stuff through other devices I can see what's playing. I cannot, however, power on the devices through homeassistant

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):


media_player:
  - platform: frontier_silicon
    host: 192.168.2.198
    password: 1337
  - platform: frontier_silicon
    host: 192.168.2.197
    password: 1337

Traceback (if applicable):

With auto discovery:

Apr  9 12:43:18 hassbian hass[599]: /srv/homeassistant/lib/python3.5/site-packages/afsapi/__init__.py:65: RuntimeWarning: coroutine 'ClientSession.close' was never awaited
Apr  9 12:43:18 hassbian hass[599]:   self.__session.close()

With configuration.yaml entry and PIN changed:

Apr  9 12:57:10 hassbian hass[17528]: #033[32m2018-04-09 12:57:10 INFO (MainThread) [root] AFSAPI Exception: Traceback (most recent call last):
Apr  9 12:57:10 hassbian hass[17528]:   File "/srv/homeassistant/lib/python3.5/site-packages/afsapi/__init__.py", line 95, in call
Apr  9 12:57:10 hassbian hass[17528]:     self.sid = yield from self.create_session()
Apr  9 12:57:10 hassbian hass[17528]:   File "/srv/homeassistant/lib/python3.5/site-packages/afsapi/__init__.py", line 84, in create_session
Apr  9 12:57:10 hassbian hass[17528]:     doc = objectify.fromstring(text)
Apr  9 12:57:10 hassbian hass[17528]:   File "src/lxml/objectify.pyx", line 1801, in lxml.objectify.fromstring
Apr  9 12:57:10 hassbian hass[17528]:   File "src/lxml/etree.pyx", line 3213, in lxml.etree.fromstring
Apr  9 12:57:10 hassbian hass[17528]:   File "src/lxml/parser.pxi", line 1876, in lxml.etree._parseMemoryDocument
Apr  9 12:57:10 hassbian hass[17528]:   File "src/lxml/parser.pxi", line 1757, in lxml.etree._parseDoc
Apr  9 12:57:10 hassbian hass[17528]:   File "src/lxml/parser.pxi", line 1067, in lxml.etree._BaseParser._parseUnicodeDoc
Apr  9 12:57:10 hassbian hass[17528]:   File "src/lxml/parser.pxi", line 600, in lxml.etree._ParserContext._handleParseResultDoc
Apr  9 12:57:10 hassbian hass[17528]:   File "src/lxml/parser.pxi", line 710, in lxml.etree._handleParseResult
Apr  9 12:57:10 hassbian hass[17528]:   File "src/lxml/parser.pxi", line 639, in lxml.etree._raiseParseError
Apr  9 12:57:10 hassbian hass[17528]:   File "<string>", line 1
Apr  9 12:57:10 hassbian hass[17528]: lxml.etree.XMLSyntaxError: Start tag expected, '<' not found, line 1, column 1

Additional information:

It was working before, but the speakers were very unreliable in general use, as they always would disconnect and I had to hard-power-toggle them in order for them to work again. I was able to control them through homeassistant though. The last time I tried was many months ago, so I don't know which version I was on then.

johan-de-jong commented 6 years ago

My Revo SuperConnect does turn on/off correctly with the plugin. I do see the same error message: 'Warning: coroutine 'ClientSession.close' was never awaited' every time the Home Assistant service is (re)started in my logs though.

Apr 15 12:47:02 hassbian hass[497]: /srv/homeassistant/lib/python3.5/site-packages/afsapi/__init__.py:65: RuntimeWarning: coroutine 'ClientSession.close' was never awaited
Apr 15 13:45:12 hassbian hass[497]: /srv/homeassistant/lib/python3.5/site-packages/afsapi/__init__.py:65: RuntimeWarning: coroutine 'ClientSession.close' was never awaited
balloobbot commented 6 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 :+1:

balloobbot commented 6 years ago

This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍