New Sonos manual config not recognized in 0.72

[jjlawren]

Home Assistant release with the issue:

0.72

Last working Home Assistant release (if known):
0.71

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

Ubuntu 18.04 venv

Component/platform:

Sonos (https://www.home-assistant.io/components/sonos/)

Description of problem:
New top-level sonos component config seems to have no effect. Reverting to the old config under media_player works fine.

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

sonos:
  media_player:
    hosts:
      - 1.2.3.4
      - 1.2.3.5

Still works:

media_player:
  - platform: sonos
    entity_namespace: sonos
    hosts:
      - 1.2.3.4
      - 1.2.3.5

Traceback (if applicable):

Additional information:

[arsaboo]

You are missing a :. It should be

sonos:
  media_player:
    hosts:
      - 192.168.2.150
      - 192.168.2.69

[jjlawren]

Sorry, that was a typo above. It was included in the config while testing. I've edited the original comment.

[arsaboo]

Working for me here. Did you finish the integration in the Configuration panel?

[jjlawren]

Whenever I tried to add the integration it would complain "No Sonos devices found on the network".

[dancwilliams]

@jjlawren I am experiencing the same thing. New config doesn't work and I get the "No Sonos devices found on the network" message. Put the legacy config back in and it works great. Interesting...

Legacy config:

media_player:
  - platform: sonos
    hosts:
      - 172.20.20.210 # Kitchen
      #- 172.20.20.211 # Office
      - 172.20.20.212 # Patio
      - 172.20.20.213 # Guest House
      - 172.20.20.216 # Living Room
      - 172.20.20.217 # Main Bathroom

New Config:

sonos:
  media_player:
    hosts:
      - 172.20.20.210 # Kitchen
      #- 172.20.20.211 # Office
      - 172.20.20.212 # Patio
      - 172.20.20.213 # Guest House
      - 172.20.20.216 # Living Room
      - 172.20.20.217 # Main Bathroom

[RealGandy]

Does the device running home assistant have multiple network interfaces? Mine does and I needed to tell HA which interface to use with:

sonos:
  media_player:
    interface_addr: 192.168.2.80

[jjlawren]

Yes, as there are multiple subnets on the network. I’ve tried using interface_addr, both without and with an interface on the same subnet as the Sonos devices.

[PostSven]

i am having a similar issue, but i am using the docker image without the net==host as i am using traefik for reverse proxy.

[dancwilliams]

I am using Hass.io and only have a single interface.

[jckoester]

Same problem for me using home assistant 0,73 under hassio in a virtual machine. New config does not work at all, old config works.

[dancwilliams]

@arsaboo

Could you provide the config you used in your configuration.yaml for your Sonos setup? I am still tryin to run this down and if it works for you I really want to figure out what I am doing wrong.

I have my Sonos devices on a different subnet, so auto discovery is not available.

Below is my config. I even added the interface parameter even though I only have a single interface. But, when I go to the Configuration > Integrations page and click "CONFIGURE" beside Sonos, I get "Aborted No Sonos devices found on the network." As soon as I go back to my "legacy" configuration, everything works great. I am on 0.73.1 now.

sonos:
  media_player:
    interface_addr: 172.24.24.100
    hosts:
      - 172.20.20.210
      - 172.20.20.211
      - 172.20.20.212
      - 172.20.20.213
      - 172.20.20.216
      - 172.20.20.217

Thanks!

[arsaboo]

sonos:
  media_player:
    hosts:
      - 192.168.2.150
      - 192.168.2.69

[RosaEinhorn]

I am having the same issue. The legacy configuration is working fine while I cannot detect Sonos using discovery or the new configuration. (Already opened port 1400 TCP)

[PostSven]

I got it to work.

I had to expose port tcp 1400 on my docker container and use the following config:

sonos:
  media_player:
    interface_addr: xxx.xxx.xxx.xxx
    hosts:
      - xxx.xxx.xxx.xxx
      - xxx.xxx.xxx.xxx

[tynor88]

Same issue. Legacy config works fine.

[amelchio]

I will fix this, I just have to figure out how it is supposed to work in these modern times :)

Stick to the legacy config for now.

[balloob]

I was discussing this with @amelchio in the dev chat.

The solution will be to add an import step that just creates the entry. That is than invoked when the user has configured the Sonos component and if there are no entries:

Adding something like this to async_setup of the Sonos component:

if DOMAIN in config and not sonos_entries():
    hass.async_create_task(hass.config_entries.flow.async_init(
        DOMAIN, source=data_entry_flow.SOURCE_IMPORT)

[amelchio]

It will be some days before I can work on this but I expect to be able to fix it for 0.75 (if nobody beats me to it).

[jjlawren]

Confirming the new config now works for me.