Core: Manual config of Sonos no longer works since 0.7x

[willkramer]

Last working Home Assistant release (if known):
0.66 (though I jumped from 0.66 to 0.72)

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

Ubuntu 14.04.5 running in a VM

Component/platform:

Sonos

Description of problem:
Can't configure Sonos via configuration.yaml and manually specify your media player hosts.

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

sonos:
  media_player:
    hosts:
      - 10.5.1.140 # Kitchen 1
      - 10.5.1.141 # Kitchen 2
      - 10.5.1.142 # Dining Room 1
      - 10.5.1.143 # Dining Room 2
      - 10.5.1.144 # Living Room 1
      - 10.5.1.145 # Living Room 2
      - 10.5.1.146 # Foyer
      - 10.5.1.149 # Family Room Playbar
      - 10.5.1.151 # Guest Bathroom
      - 10.5.1.152 # Bedroom 1
      - 10.5.1.153 # Bedroom 2
      - 10.5.1.154 # Closest
      - 10.5.1.155 # Master Bathroom
      - 10.5.1.156 # Shower

Traceback (if applicable):

Additional information:
The Sonos component works fine if enabled through the integrations configuration but that then relies on auto discovery. It doesn't appear there is a way to setup Sonos without using the integrations configuration since the 0.7x release. It has also been reported that the same issue is occurring with the cast component.

[DubhAd]

I (also on a VM - VirtualBox) have the same issue.

Debian 9.4
Python 3.6.6 or Python 3.7.0
Home Assistant 0.73.1

Manual configuration via sonos: doesn't work (neither does cast: for cast devices).

[mdallaire]

I am seeing the same behavior on docker since 0.72
Same as issue #15146

[awarecan]

You guys didn't read release notes?

Another change is that Nest, Sonos and Cast will now have to be configured using a config entry. Config entries can be created via the integrations page in the config panel. This is a concept that we have been developing for a couple of months now and it’s our goal to eventually use this as the way to configure all components.

https://www.home-assistant.io/blog/2018/06/22/release-72/

[Vasiley]

IMAO .... manual config should always should be be a option. I have hue manually config along with being added via the intergrations page. I do not want discovery enabled at all times.

[DubhAd]

@awarecan However, the component pages say that manual config is still an option. Yes, the config entries are useful, but they're supposed to not be the only option.

[nrepian]

Same problem here. I am also unable to configure Sonos via the auto-discovery method ("No Sonos devices found on the network."), as they are on a different VLAN.

I do hope there is a way to manually configure this, or at least provide an IP address during the configuration process.

[ludeeus]

Same issue for the cast: component added here: https://github.com/home-assistant/home-assistant/issues/15401

[amelchio]

Closing as a duplicate of #15146.