core: Error setting up media_player.sonos

Home Assistant release with the issue:

0.83.0b0

Last working Home Assistant release (if known): unknown

Operating environment (Hass.io/Docker/Windows/etc.):

Docker version 18.09.0, build 4d60db4 on Raspberry Pi 3 running Raspbian GNU/Linux 9.6 (stretch) on Kernel 4.14.52-v7+

Component/platform:

https://www.home-assistant.io/components/sonos/

Description of problem: I used the integration discovery to setup a Sonos speaker. All I had to do was hit the “configure” button. I did not configure the sonos component manually in configuration.yaml, only enabled/configured it in the UI.

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


Traceback (if applicable):

2018-11-29 13:47:30 INFO (MainThread) [homeassistant.setup] Setting up sonos
2018-11-29 13:47:30 INFO (MainThread) [homeassistant.setup] Setup of domain sonos took 0.0 seconds.
2018-11-29 13:47:31 INFO (MainThread) [homeassistant.loader] Loaded media_player.sonos from homeassistant.components.media_player.sonos
2018-11-29 13:47:31 INFO (MainThread) [homeassistant.components.media_player] Setting up media_player.sonos
2018-11-29 13:47:31 ERROR (MainThread) [homeassistant.core] Error doing job: Future exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/media_player/sonos.py", line 182, in _setup_platform
    interface_addr=config.get(CONF_INTERFACE_ADDR))
  File "/usr/local/lib/python3.6/site-packages/pysonos/discovery.py", line 114, in discover
    _sock.sendto(really_utf8(PLAYER_SEARCH), (MCAST_GRP, MCAST_PORT))
OSError: [Errno 126] No error information

Additional information:

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Comments: 24 (21 by maintainers)

Most upvoted comments

@amelchio I just had another look and it turns out that the recent change in the Owntracks component was responsible for my problem. The sonos component just happened to be the last thing that was loaded before HA got stuck. Disabling the Owntracks component fixed my issue.